[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website

[Bertrand Delacretaz (JIRA)]

[ 
https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809682#comment-16809682
 ] 

Bertrand Delacretaz commented on INCUBATOR-231:
---

Thanks Dave, your changes work for me.

+1 for a CLUTCH.md, and we might just keep a warning about clutch and a link to 
that page in the README.

How about moving the clutch data links to http://incubator.apache.org/clutch/ 
and adding a link to CLUTCH.md there? That URL then becomes the "all you need 
to know about clutch" one.

> Cleanup Git-generated Incubator website
> ---
>
> Key: INCUBATOR-231
> URL: https://issues.apache.org/jira/browse/INCUBATOR-231
> Project: Incubator
>  Issue Type: Task
>Reporter: Bertrand Delacretaz
>Priority: Major
> Attachments: clutch-analysis.tar.gz, clutch-pages.tar.gz, 
> clutch.py.diff.txt, clutch2data.txt, clutch2data.txt, clutch2status.txt, 
> gitbox.clutch.data.txt, gitbox.svn.diff.txt
>
>
> [http://incubator.apache.org/] is generated from 
> [https://github.com/apache/incubator] but a few things (clutch, project 
> pages) are still maintained under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/]
> We should cleanup and unify for consistency, and there's a number of folders 
> in svn that are not used anymore. Everything should move to Git to avoid 
> confusion.
> Also, a lot of the projects information in the XML files found under 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/] is 
> duplicated in other places, LDAP, podlings websites etc - it would be good to 
> clean that up and simplify those pages to adapt to our current workflows, 
> while preserving history where it makes sense.
> There are also YAML files with yet more duplicated information at 
> [http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/] , 
> not sure if that's used or useful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE]: Release Apache Dubbo Spring Boot Project (Incubating) 2.7.1

[sebb]

On Thu, 4 Apr 2019 at 04:42, Mercy  wrote:
>
> Hello all,
>
> This is a call for the vote to release Apache Dubbo Spring Boot Project 
> (Incubating) version 2.7.1
>
> The Apache Dubbo community has voted on and approved a proposal to release
> Apache Dubbo Spring Boot Project (Incubating) 2.7.1.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache Dubbo™ (incubating) is a high-performance, java based, open source
> RPC framework. Dubbo offers three key functionalities, which include
> interface based remote call, fault tolerance & load balancing, and
> automatic service registration & discovery.
>
> Dubbo community vote and result thread:
> https://lists.apache.org/thread.html/ded40621ad7572a84c71cc6ad5a9843c3e073e405d051e7053e8700b@%3Cdev.dubbo.apache.org%3E
>
> The release candidates :
> 2.7.1:https://dist.apache.org/repos/dist/dev/incubator/dubbo/spring-boot-project/2.7.1
>
> The staging repo:
> https://repository.apache.org/content/repositories/orgapachedubbo-1017
>
> Git tag for the release:
> 2.7.1: 
> https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/2.7.1
>
> Hash for the release tag:
> 2.7.1: 01fbe79c71f73f65ae1fa1239f9fba30a8300192
>
> Release Notes:
> 2.7.1: 
> https://github.com/apache/incubator-dubbo-spring-boot-project/releases/tag/2.7.1
>
> The artifacts have been signed with Key: 
> 87F025027A831ED2B86E7F08A7F508EFDA68B4F5, which can be found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/dubbo/KEYS

IMO it's better to link to the KEYS on www.apache.org, i.e.
https://www.apache.org/dist/incubator/dubbo/KEYS
as that is where downloaders should be directed by the download page

> The vote will be open for at least 72 hours or until the necessary number of 
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache Dubbo (Incubating) Team
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.14.0 [RC3]

[Gian Merlino]

It didn't include the disclaimer - thanks for pointing that out.

By the way, one of our mentors has already voted +1 for this
0.14.0-incubating release on dev@druid, so I think that means we are just
looking for a couple more IPMC votes.

On Wed, Apr 3, 2019 at 6:10 AM sebb  wrote:

> Top-posting:
>
> Announcements of podling release should please include the standard
> Incubation disclaimer. (AFAICT this did not happen with the previous
> Druid announce)
>
> See for example:
>
>
> https://lists.apache.org/thread.html/d94b89e6c4e83f2364607b47020ca715aaa7fae1a3b97b374b93ca7f@%3Cgeneral.incubator.apache.org%3E
>
> https://lists.apache.org/thread.html/ec3d6b90a2b0054eb2f0a2e4ba2e09a594463720e2b28e75b315c693@%3Cgeneral.incubator.apache.org%3E
>
> https://lists.apache.org/thread.html/8993ecb33e0f73e69faabba8c1f07d3a9965a178df1698c42fc9f4b2@%3Cgeneral.incubator.apache.org%3E
>
> Please bear this in mind when the vote has finished.
>
> Thanks.
>
> On Wed, 3 Apr 2019 at 00:58, Jonathan Wei  wrote:
> >
> > Hi IPMC,
> >
> > The Apache Druid community has voted on and approved a proposal to
> release
> > Apache Druid (incubating) 0.14.0 (rc3).
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Project description: Apache Druid (incubating) is a high performance
> > analytics data store for event-driven data.
> >
> > The community voting thread can be found here:
> > https://www.mail-archive.com/dev@druid.apache.org/msg01924.html
> >
> > The release notes are available here:
> > https://github.com/apache/incubator-druid/issues/7126
> >
> > The release candidate has been tagged in GitHub as
> > druid-0.14.0-incubating-rc3 (f169ada), available here:
> >
> https://github.com/apache/incubator-druid/releases/tag/druid-0.14.0-incubating-rc3
> >
> > The artifacts to be voted on are located here:
> >
> https://dist.apache.org/repos/dist/dev/incubator/druid/0.14.0-incubating-rc3/
> >
> > A staged Maven repository is available for review at:
> > https://repository.apache.org/content/repositories/orgapachedruid-1003/
> >
> > Release artifacts are signed with the key [1AC4483E]:
> > https://people.apache.org/keys/committer/jonwei.asc
> >
> > This key and the key of other committers can also be found in the
> project's
> > KEYS file here:
> > https://dist.apache.org/repos/dist/release/incubator/druid/KEYS
> >
> > As part of the validation process, the release artifacts can be generated
> > from source by running:
> > mvn clean install -Papache-release,dist
> >
> > The RAT license check can be run from source by:
> > mvn apache-rat:check -Prat
> >
> > This vote will be open for at least 72 hours. The vote will pass if a
> > majority of at least three +1 IPMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Druid (incubating) 0.14.0
> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Thank you IPMC! We appreciate your efforts in helping the Apache Druid
> > community to validate this release.
> >
> > On behalf of the Apache Druid PPMC,
> > Jon
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[DISCUSS] Graduate Apache PLC4X (incubating) as a TLP

[Christofer Dutz]

Hi all,

Since Apache PLC4X (incubating) entered the incubator in December 2017 we have 
attracted quite a number of new PPMCs,
committers and contributors that didn’t have any experience with Apache and the 
Apache Way.

However have we managed to educate these new individuals and have grown to a 
community that operates nicely following
the Apache Way. All issues reported have been addressed and our last releases 
usually passed without any objections.

We recently had a discussion on graduation [5] and just finished a community 
vote [2] on the matter which resulted in 7 (binding) +1, 1 (non-binding) +1 and 
no 0 or -1 votes [1].
In another discussion prior to the vote we decided to reduce the number of 
PMCs/Committers to those existing who explicitly expressed the wish to be 
included [3].
This was due to the fact that when setting up the project outside of Apache, a 
lot of my colleagues initially expressed the wish to participate and we 
included them in the initial contributor list.
However most of these never did anything and some didn’t even sign up for our 
mailing lists.
Some have expressed the wish to go emeritus and we used a vote [4] to define 
the initial PMC for the TLP.

We would like to continue the graduation process and hereby ask you all for 
your opinion on this.

Chris

[1] 
https://lists.apache.org/thread.html/d53c159c6e8973a6e763635c90bc0f52e0c4fa576da80f553bc4aa40@%3Cdev.plc4x.apache.org%3E
[2] 
https://lists.apache.org/thread.html/9a4cf5b1ad7b59e79ae33f3d09032e7942a7191a319335303e16d286@%3Cdev.plc4x.apache.org%3E
[3] 
https://lists.apache.org/thread.html/d14e972889dad4ca9cb72f2447edb422df2742f8d71bf140618ba021@%3Cdev.plc4x.apache.org%3E
[4] 
https://lists.apache.org/thread.html/7a979438fa050bc873a4df0da9b628edaa61d350a17364b837a059d3@%3Cdev.plc4x.apache.org%3E
[5] 
https://lists.apache.org/thread.html/0a590c8aabced1b46e1200aeface51e9fe34cdf01ed7753a6779ce55@%3Cdev.plc4x.apache.org%3E


---

Establish the Apache PLC4X Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a set of libraries for communicating with industrial
programmable logic controllers (PLCs) using a variety of protocols but
with a shared API.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache PLC4X Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache PLC4X Project be and hereby is responsible for
the creation and maintenance of software related to a set of libraries
for communicating with industrial programmable logic controllers (PLCs)
using a variety of protocols but with a shared API; and be it further

RESOLVED, that the office of "Vice President, Apache PLC4X" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache PLC4X
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache PLC4X Project;
and be it further

RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache PLC4X Project:

* Christofer Dutzmailto:cd...@apache.org>>
* Julian Feinauermailto:jfeina...@apache.org>>
* Justin Mclean  mailto:jmcl...@apache.org>>
* Markus Sommer  mailto:msom...@apache.org>>
* Sebastian Rühl mailto:sru...@apache.org>>
* Tim Mitsch mailto:tmit...@apache.org>>

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Christofer Dutz be
appointed to the office of Vice President, Apache PLC4X, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further

RESOLVED, that the initial Apache PLC4X PMC be and hereby is tasked with
the creation of a set of bylaws intended to encourage open development
and increased participation in the Apache PLC4X Project; and be it
further

RESOLVED, that the Apache PLC4X Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator PLC4X podling; and
be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
PLC4X podling encumbered upon the Apache Incubator PMC are hereafter
discharged.

Re: Podling use of StackOverflow

[Ted Dunning]

Just subscribe to appropriate tags on stack overflow and direct
notifications to the dev list.

Then encourage the community to answer on stack overflow.


On Wed, Apr 3, 2019 at 6:32 PM Dave Fisher  wrote:

> I think a user@ mailing list is better for the project’s sustainability
> and Apache.
>
> I have examples related to POI where there is substantial StackOverflow
> support happening.
>
> 12 years ago I became a POI committer for answering user questions.
>
> Recently we asked an active StackOverflow answer if he was interested in
> being a committer and StackOverflow was his community.
>
> Apache records are always better than stuff at another company. Gmane and
> markmail email links have rotted away.
>
> I would encourage a user list for the visibility for the PMC in
> understanding what’s happening along with a more coherent community!
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Apr 3, 2019, at 6:02 PM, Alan Gates  wrote:
> >
> > The superset podling is working out their processes around FAQs and
> > answering user questions.  One thing that they have suggested is that
> they
> > encourage people to use StackOverflow for questions and answers given the
> > ease of searching old questions, etc.  You can see the mail thread at
> >
> https://lists.apache.org/thread.html/1cd1c1e7d02d712ec4e1a13a50cb6016318be5e55ca023b10087cb61@%3Cdev.superset.apache.org%3E
> >
> > Personally I think encouraging podlings to use tools they and everyone
> are
> > comfortable with and that meet our criteria of being open to all is a
> good
> > thing, but I wanted to check if there was official policy on this before
> > they proceed with it.
> >
> > Alan.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Podling use of StackOverflow

[Julian Hyde]

It can be frustrating when someone posts a question to both the user list and 
to StackOverflow. It means that the community has to answer the question in two 
places.

But like many problems, that is an opportunity. Answering StackOverflow 
questions is a great way for people to contribute without writing code. If you 
take the view that everyone reading or writing StackOverflow is part of the 
community — and I do — then StackOverflow is an excellent way to grow community.

Julian


 

> On Apr 4, 2019, at 10:33 AM, Ted Dunning  wrote:
> 
> Just subscribe to appropriate tags on stack overflow and direct
> notifications to the dev list.
> 
> Then encourage the community to answer on stack overflow.
> 
> 
> On Wed, Apr 3, 2019 at 6:32 PM Dave Fisher  wrote:
> 
>> I think a user@ mailing list is better for the project’s sustainability
>> and Apache.
>> 
>> I have examples related to POI where there is substantial StackOverflow
>> support happening.
>> 
>> 12 years ago I became a POI committer for answering user questions.
>> 
>> Recently we asked an active StackOverflow answer if he was interested in
>> being a committer and StackOverflow was his community.
>> 
>> Apache records are always better than stuff at another company. Gmane and
>> markmail email links have rotted away.
>> 
>> I would encourage a user list for the visibility for the PMC in
>> understanding what’s happening along with a more coherent community!
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Apr 3, 2019, at 6:02 PM, Alan Gates  wrote:
>>> 
>>> The superset podling is working out their processes around FAQs and
>>> answering user questions.  One thing that they have suggested is that
>> they
>>> encourage people to use StackOverflow for questions and answers given the
>>> ease of searching old questions, etc.  You can see the mail thread at
>>> 
>> https://lists.apache.org/thread.html/1cd1c1e7d02d712ec4e1a13a50cb6016318be5e55ca023b10087cb61@%3Cdev.superset.apache.org%3E
>>> 
>>> Personally I think encouraging podlings to use tools they and everyone
>> are
>>> comfortable with and that meet our criteria of being open to all is a
>> good
>>> thing, but I wanted to check if there was official policy on this before
>>> they proceed with it.
>>> 
>>> Alan.
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Graduate Apache PLC4X (incubating) as a TLP

[Dave Fisher]

Hi -

I am for graduation. I appreciate the need to narrow the PMC to those who are 
active. I’ll note that one of your recent additions (noted on the Oct 2018 
report) did not continue while the other did.

Graduating with only 6 PMC is pretty narrow. Are there other developers active 
who look like you will want to add to the committer / PMC soon after graduation?

Best Regards,
Dave

> On Apr 4, 2019, at 6:59 AM, Christofer Dutz  wrote:
> 
> Hi all,
> 
> Since Apache PLC4X (incubating) entered the incubator in December 2017 we 
> have attracted quite a number of new PPMCs,
> committers and contributors that didn’t have any experience with Apache and 
> the Apache Way.
> 
> However have we managed to educate these new individuals and have grown to a 
> community that operates nicely following
> the Apache Way. All issues reported have been addressed and our last releases 
> usually passed without any objections.
> 
> We recently had a discussion on graduation [5] and just finished a community 
> vote [2] on the matter which resulted in 7 (binding) +1, 1 (non-binding) +1 
> and no 0 or -1 votes [1].
> In another discussion prior to the vote we decided to reduce the number of 
> PMCs/Committers to those existing who explicitly expressed the wish to be 
> included [3].
> This was due to the fact that when setting up the project outside of Apache, 
> a lot of my colleagues initially expressed the wish to participate and we 
> included them in the initial contributor list.
> However most of these never did anything and some didn’t even sign up for our 
> mailing lists.
> Some have expressed the wish to go emeritus and we used a vote [4] to define 
> the initial PMC for the TLP.
> 
> We would like to continue the graduation process and hereby ask you all for 
> your opinion on this.
> 
> Chris
> 
> [1] 
> https://lists.apache.org/thread.html/d53c159c6e8973a6e763635c90bc0f52e0c4fa576da80f553bc4aa40@%3Cdev.plc4x.apache.org%3E
> [2] 
> https://lists.apache.org/thread.html/9a4cf5b1ad7b59e79ae33f3d09032e7942a7191a319335303e16d286@%3Cdev.plc4x.apache.org%3E
> [3] 
> https://lists.apache.org/thread.html/d14e972889dad4ca9cb72f2447edb422df2742f8d71bf140618ba021@%3Cdev.plc4x.apache.org%3E
> [4] 
> https://lists.apache.org/thread.html/7a979438fa050bc873a4df0da9b628edaa61d350a17364b837a059d3@%3Cdev.plc4x.apache.org%3E
> [5] 
> https://lists.apache.org/thread.html/0a590c8aabced1b46e1200aeface51e9fe34cdf01ed7753a6779ce55@%3Cdev.plc4x.apache.org%3E
> 
> 
> ---
> 
> Establish the Apache PLC4X Project
> 
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a set of libraries for communicating with industrial
> programmable logic controllers (PLCs) using a variety of protocols but
> with a shared API.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache PLC4X Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache PLC4X Project be and hereby is responsible for
> the creation and maintenance of software related to a set of libraries
> for communicating with industrial programmable logic controllers (PLCs)
> using a variety of protocols but with a shared API; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache PLC4X" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache PLC4X
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache PLC4X Project;
> and be it further
> 
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache PLC4X Project:
> 
> * Christofer Dutzmailto:cd...@apache.org>>
> * Julian Feinauermailto:jfeina...@apache.org>>
> * Justin Mclean  mailto:jmcl...@apache.org>>
> * Markus Sommer  mailto:msom...@apache.org>>
> * Sebastian Rühl mailto:sru...@apache.org>>
> * Tim Mitsch mailto:tmit...@apache.org>>
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Christofer Dutz be
> appointed to the office of Vice President, Apache PLC4X, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
> 
> RESOLVED, that the initial Apache PLC4X PMC be and hereby is tasked with
> the creation of a set of bylaws intended to encourage open development
> and increased participation in the Apache PLC4X Project; and be it
> further
> 
> RESOLVED, that the Apache PLC4X Project be a

[ANNOUNCE] Apache NetBeans (incubating) 11.0 released

[Laszlo Kishalmi]

The Apache NetBeans team is proud to announce the release of Apache
NetBeans (incubating) 11.0.

Apache NetBeans (incubating) 11.0 constitutes all cluster in the Apache 
NetBeans Git repo, which together provide the NetBeans Platform (i.e., the 
underlying application framework), as well as all the modules that provide the 
Java SE, Java EE, PHP, JavaScript and Groovy features of Apache NetBeans.

In short, Apache NetBeans (incubating) 11.0 is a full IDE for Java SE, Java EE, 
PHP and JavaScript development with some Groovy language support.

Read more on our download page:

https://netbeans.apache.org/download/nb110/nb110.html

New & Noteworthy features of the 11.0 Release:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.0+New+and+Noteworthy

See the below for the donation status of features that have not been
donated or included in Apache builds yet, i.e., are not part of Apache
NetBeans (incubating) 11.0, e.g., features for working with C/C++, JavaCard,
and more:

https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition

Work is being done on bringing netbeans.org to Apache. In the
meantime, refer to the below for all details related to Apache
NetBeans:

https://cwiki.apache.org/confluence/display/NETBEANS

Laszlo Kishalmi
on behalf of Apache NetBeans PPMC


Apache NetBeans is an effort undergoing incubation at The Apache
Software Foundation (ASF), sponsored by the Apache Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Podling use of StackOverflow

[Greg Stein]

Totally agreed with Julian here.

Community growth is one of the hardest aspects of a healthy, Apache
community. It is a never-ending and always-needed process. Shutting out
paths to growth, or partitioning where/how people might participate in the
community is a clear yellow flag. Reach out and embrace participants no
matter where they may congregate, and welcome them and include them into
the larger community.

Cheers,
-g


On Thu, Apr 4, 2019 at 1:03 PM Julian Hyde  wrote:

> It can be frustrating when someone posts a question to both the user list
> and to StackOverflow. It means that the community has to answer the
> question in two places.
>
> But like many problems, that is an opportunity. Answering StackOverflow
> questions is a great way for people to contribute without writing code. If
> you take the view that everyone reading or writing StackOverflow is part of
> the community — and I do — then StackOverflow is an excellent way to grow
> community.
>
> Julian
>
>
>
>
> > On Apr 4, 2019, at 10:33 AM, Ted Dunning  wrote:
> >
> > Just subscribe to appropriate tags on stack overflow and direct
> > notifications to the dev list.
> >
> > Then encourage the community to answer on stack overflow.
> >
> >
> > On Wed, Apr 3, 2019 at 6:32 PM Dave Fisher 
> wrote:
> >
> >> I think a user@ mailing list is better for the project’s sustainability
> >> and Apache.
> >>
> >> I have examples related to POI where there is substantial StackOverflow
> >> support happening.
> >>
> >> 12 years ago I became a POI committer for answering user questions.
> >>
> >> Recently we asked an active StackOverflow answer if he was interested in
> >> being a committer and StackOverflow was his community.
> >>
> >> Apache records are always better than stuff at another company. Gmane
> and
> >> markmail email links have rotted away.
> >>
> >> I would encourage a user list for the visibility for the PMC in
> >> understanding what’s happening along with a more coherent community!
> >>
> >> Regards,
> >> Dave
> >>
> >> Sent from my iPhone
> >>
> >>> On Apr 3, 2019, at 6:02 PM, Alan Gates  wrote:
> >>>
> >>> The superset podling is working out their processes around FAQs and
> >>> answering user questions.  One thing that they have suggested is that
> >> they
> >>> encourage people to use StackOverflow for questions and answers given
> the
> >>> ease of searching old questions, etc.  You can see the mail thread at
> >>>
> >>
> https://lists.apache.org/thread.html/1cd1c1e7d02d712ec4e1a13a50cb6016318be5e55ca023b10087cb61@%3Cdev.superset.apache.org%3E
> >>>
> >>> Personally I think encouraging podlings to use tools they and everyone
> >> are
> >>> comfortable with and that meet our criteria of being open to all is a
> >> good
> >>> thing, but I wanted to check if there was official policy on this
> before
> >>> they proceed with it.
> >>>
> >>> Alan.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache PLC4X (incubating) as a TLP

[Christofer Dutz]

Hi Dave,

The one addition you mention explicitly said, that due to changes at work he 
will not be able to participate and is not willing to invest his private time 
:-( ... But we are more than willing to re-invite past contributors later, if 
they decided not to be carried over now.

And yes, there are potential candidates that we are keeping an eye on, which we 
will probably invite soon.

We know there are way larger communities in the incubator but as far as I 
understand incubation, it's all about the projects learning to become good 
Apache communities and that they demonstrate their fitness to do correct 
releases. I guess we have proven that and continuing to grow community is and 
will remain the goal of every Apache project throughout it's existence.

Chris


Outlook für Android herunterladen


From: Dave Fisher 
Sent: Thursday, April 4, 2019 8:14:00 PM
To: general@incubator.apache.org
Subject: Re: [DISCUSS] Graduate Apache PLC4X (incubating) as a TLP

Hi -

I am for graduation. I appreciate the need to narrow the PMC to those who are 
active. I’ll note that one of your recent additions (noted on the Oct 2018 
report) did not continue while the other did.

Graduating with only 6 PMC is pretty narrow. Are there other developers active 
who look like you will want to add to the committer / PMC soon after graduation?

Best Regards,
Dave

> On Apr 4, 2019, at 6:59 AM, Christofer Dutz  wrote:
>
> Hi all,
>
> Since Apache PLC4X (incubating) entered the incubator in December 2017 we 
> have attracted quite a number of new PPMCs,
> committers and contributors that didn’t have any experience with Apache and 
> the Apache Way.
>
> However have we managed to educate these new individuals and have grown to a 
> community that operates nicely following
> the Apache Way. All issues reported have been addressed and our last releases 
> usually passed without any objections.
>
> We recently had a discussion on graduation [5] and just finished a community 
> vote [2] on the matter which resulted in 7 (binding) +1, 1 (non-binding) +1 
> and no 0 or -1 votes [1].
> In another discussion prior to the vote we decided to reduce the number of 
> PMCs/Committers to those existing who explicitly expressed the wish to be 
> included [3].
> This was due to the fact that when setting up the project outside of Apache, 
> a lot of my colleagues initially expressed the wish to participate and we 
> included them in the initial contributor list.
> However most of these never did anything and some didn’t even sign up for our 
> mailing lists.
> Some have expressed the wish to go emeritus and we used a vote [4] to define 
> the initial PMC for the TLP.
>
> We would like to continue the graduation process and hereby ask you all for 
> your opinion on this.
>
> Chris
>
> [1] 
> https://lists.apache.org/thread.html/d53c159c6e8973a6e763635c90bc0f52e0c4fa576da80f553bc4aa40@%3Cdev.plc4x.apache.org%3E
> [2] 
> https://lists.apache.org/thread.html/9a4cf5b1ad7b59e79ae33f3d09032e7942a7191a319335303e16d286@%3Cdev.plc4x.apache.org%3E
> [3] 
> https://lists.apache.org/thread.html/d14e972889dad4ca9cb72f2447edb422df2742f8d71bf140618ba021@%3Cdev.plc4x.apache.org%3E
> [4] 
> https://lists.apache.org/thread.html/7a979438fa050bc873a4df0da9b628edaa61d350a17364b837a059d3@%3Cdev.plc4x.apache.org%3E
> [5] 
> https://lists.apache.org/thread.html/0a590c8aabced1b46e1200aeface51e9fe34cdf01ed7753a6779ce55@%3Cdev.plc4x.apache.org%3E
>
>
> ---
>
> Establish the Apache PLC4X Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to a set of libraries for communicating with industrial
> programmable logic controllers (PLCs) using a variety of protocols but
> with a shared API.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache PLC4X Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache PLC4X Project be and hereby is responsible for
> the creation and maintenance of software related to a set of libraries
> for communicating with industrial programmable logic controllers (PLCs)
> using a variety of protocols but with a shared API; and be it further
>
> RESOLVED, that the office of "Vice President, Apache PLC4X" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache PLC4X
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache PLC4X Project;
> and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed t

Re: [ANNOUNCE] Apache NetBeans (incubating) 11.0 released

[Wade Chandler]

Great job Lazlo and everyone else; thanks so much for all your hard work!
This is awesome news!

Wade

On Thu, Apr 4, 2019, 18:57 Laszlo Kishalmi  wrote:

> The Apache NetBeans team is proud to announce the release of Apache
> NetBeans (incubating) 11.0.
>
> Apache NetBeans (incubating) 11.0 constitutes all cluster in the Apache
> NetBeans Git repo, which together provide the NetBeans Platform (i.e., the
> underlying application framework), as well as all the modules that provide
> the Java SE, Java EE, PHP, JavaScript and Groovy features of Apache
> NetBeans.
>
> In short, Apache NetBeans (incubating) 11.0 is a full IDE for Java SE,
> Java EE, PHP and JavaScript development with some Groovy language support.
>
> Read more on our download page:
>
> https://netbeans.apache.org/download/nb110/nb110.html
>
> New & Noteworthy features of the 11.0 Release:
>
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+11.0+New+and+Noteworthy
>
> See the below for the donation status of features that have not been
> donated or included in Apache builds yet, i.e., are not part of Apache
> NetBeans (incubating) 11.0, e.g., features for working with C/C++,
> JavaCard,
> and more:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
>
> Work is being done on bringing netbeans.org to Apache. In the
> meantime, refer to the below for all details related to Apache
> NetBeans:
>
> https://cwiki.apache.org/confluence/display/NETBEANS
>
> Laszlo Kishalmi
> on behalf of Apache NetBeans PPMC
>
>
> Apache NetBeans is an effort undergoing incubation at The Apache
> Software Foundation (ASF), sponsored by the Apache Incubator.
> Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other
> successful ASF projects. While incubation status is not necessarily a
> reflection of the completeness or stability of the code, it does
> indicate that the project has yet to be fully endorsed by the ASF.
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Podling use of StackOverflow

[Ted Dunning]

I sometimes used cut and paste in such cases. And if questions are
reflected into the dev or user, the duplications are apparent.

On Thu, Apr 4, 2019, 11:03 AM Julian Hyde  wrote:

> It can be frustrating when someone posts a question to both the user list
> and to StackOverflow. It means that the community has to answer the
> question in two places.
>
> But like many problems, that is an opportunity. Answering StackOverflow
> questions is a great way for people to contribute without writing code. If
> you take the view that everyone reading or writing StackOverflow is part of
> the community — and I do — then StackOverflow is an excellent way to grow
> community.
>
> Julian
>
>
>
>
> > On Apr 4, 2019, at 10:33 AM, Ted Dunning  wrote:
> >
> > Just subscribe to appropriate tags on stack overflow and direct
> > notifications to the dev list.
> >
> > Then encourage the community to answer on stack overflow.
> >
> >
> > On Wed, Apr 3, 2019 at 6:32 PM Dave Fisher 
> wrote:
> >
> >> I think a user@ mailing list is better for the project’s sustainability
> >> and Apache.
> >>
> >> I have examples related to POI where there is substantial StackOverflow
> >> support happening.
> >>
> >> 12 years ago I became a POI committer for answering user questions.
> >>
> >> Recently we asked an active StackOverflow answer if he was interested in
> >> being a committer and StackOverflow was his community.
> >>
> >> Apache records are always better than stuff at another company. Gmane
> and
> >> markmail email links have rotted away.
> >>
> >> I would encourage a user list for the visibility for the PMC in
> >> understanding what’s happening along with a more coherent community!
> >>
> >> Regards,
> >> Dave
> >>
> >> Sent from my iPhone
> >>
> >>> On Apr 3, 2019, at 6:02 PM, Alan Gates  wrote:
> >>>
> >>> The superset podling is working out their processes around FAQs and
> >>> answering user questions.  One thing that they have suggested is that
> >> they
> >>> encourage people to use StackOverflow for questions and answers given
> the
> >>> ease of searching old questions, etc.  You can see the mail thread at
> >>>
> >>
> https://lists.apache.org/thread.html/1cd1c1e7d02d712ec4e1a13a50cb6016318be5e55ca023b10087cb61@%3Cdev.superset.apache.org%3E
> >>>
> >>> Personally I think encouraging podlings to use tools they and everyone
> >> are
> >>> comfortable with and that meet our criteria of being open to all is a
> >> good
> >>> thing, but I wanted to check if there was official policy on this
> before
> >>> they proceed with it.
> >>>
> >>> Alan.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Graduate Apache PLC4X (incubating) as a TLP

[Dave Fisher]

Hi Chris,

Thanks! My concern is that in the past the IPMC has graduated podlings with 5 
PMC members that fairly quickly ended up in the Attic.

With potential committers in view I’m less concerned!

There are plenty of successful projects with 5-10 active PMC.

+1

Regards,
Dave

Sent from my iPhone

> On Apr 4, 2019, at 6:08 PM, Christofer Dutz  wrote:
> 
> Hi Dave,
> 
> The one addition you mention explicitly said, that due to changes at work he 
> will not be able to participate and is not willing to invest his private time 
> :-( ... But we are more than willing to re-invite past contributors later, if 
> they decided not to be carried over now.
> 
> And yes, there are potential candidates that we are keeping an eye on, which 
> we will probably invite soon.
> 
> We know there are way larger communities in the incubator but as far as I 
> understand incubation, it's all about the projects learning to become good 
> Apache communities and that they demonstrate their fitness to do correct 
> releases. I guess we have proven that and continuing to grow community is and 
> will remain the goal of every Apache project throughout it's existence.
> 
> Chris
> 
> 
> Outlook für Android herunterladen
> 
> 
> From: Dave Fisher 
> Sent: Thursday, April 4, 2019 8:14:00 PM
> To: general@incubator.apache.org
> Subject: Re: [DISCUSS] Graduate Apache PLC4X (incubating) as a TLP
> 
> Hi -
> 
> I am for graduation. I appreciate the need to narrow the PMC to those who are 
> active. I’ll note that one of your recent additions (noted on the Oct 2018 
> report) did not continue while the other did.
> 
> Graduating with only 6 PMC is pretty narrow. Are there other developers 
> active who look like you will want to add to the committer / PMC soon after 
> graduation?
> 
> Best Regards,
> Dave
> 
>> On Apr 4, 2019, at 6:59 AM, Christofer Dutz  
>> wrote:
>> 
>> Hi all,
>> 
>> Since Apache PLC4X (incubating) entered the incubator in December 2017 we 
>> have attracted quite a number of new PPMCs,
>> committers and contributors that didn’t have any experience with Apache and 
>> the Apache Way.
>> 
>> However have we managed to educate these new individuals and have grown to a 
>> community that operates nicely following
>> the Apache Way. All issues reported have been addressed and our last 
>> releases usually passed without any objections.
>> 
>> We recently had a discussion on graduation [5] and just finished a community 
>> vote [2] on the matter which resulted in 7 (binding) +1, 1 (non-binding) +1 
>> and no 0 or -1 votes [1].
>> In another discussion prior to the vote we decided to reduce the number of 
>> PMCs/Committers to those existing who explicitly expressed the wish to be 
>> included [3].
>> This was due to the fact that when setting up the project outside of Apache, 
>> a lot of my colleagues initially expressed the wish to participate and we 
>> included them in the initial contributor list.
>> However most of these never did anything and some didn’t even sign up for 
>> our mailing lists.
>> Some have expressed the wish to go emeritus and we used a vote [4] to define 
>> the initial PMC for the TLP.
>> 
>> We would like to continue the graduation process and hereby ask you all for 
>> your opinion on this.
>> 
>> Chris
>> 
>> [1] 
>> https://lists.apache.org/thread.html/d53c159c6e8973a6e763635c90bc0f52e0c4fa576da80f553bc4aa40@%3Cdev.plc4x.apache.org%3E
>> [2] 
>> https://lists.apache.org/thread.html/9a4cf5b1ad7b59e79ae33f3d09032e7942a7191a319335303e16d286@%3Cdev.plc4x.apache.org%3E
>> [3] 
>> https://lists.apache.org/thread.html/d14e972889dad4ca9cb72f2447edb422df2742f8d71bf140618ba021@%3Cdev.plc4x.apache.org%3E
>> [4] 
>> https://lists.apache.org/thread.html/7a979438fa050bc873a4df0da9b628edaa61d350a17364b837a059d3@%3Cdev.plc4x.apache.org%3E
>> [5] 
>> https://lists.apache.org/thread.html/0a590c8aabced1b46e1200aeface51e9fe34cdf01ed7753a6779ce55@%3Cdev.plc4x.apache.org%3E
>> 
>> 
>> ---
>> 
>> Establish the Apache PLC4X Project
>> 
>> WHEREAS, the Board of Directors deems it to be in the best interests of
>> the Foundation and consistent with the Foundation's purpose to establish
>> a Project Management Committee charged with the creation and maintenance
>> of open-source software, for distribution at no charge to the public,
>> related to a set of libraries for communicating with industrial
>> programmable logic controllers (PLCs) using a variety of protocols but
>> with a shared API.
>> 
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> (PMC), to be known as the "Apache PLC4X Project", be and hereby is
>> established pursuant to Bylaws of the Foundation; and be it further
>> 
>> RESOLVED, that the Apache PLC4X Project be and hereby is responsible for
>> the creation and maintenance of software related to a set of libraries
>> for communicating with industrial programmable logic controllers (PLCs)
>> using