Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

2018-09-12 Thread Jia Zhai 
+1  (non-binding)

Best Wishes.


On Thu, Sep 13, 2018 at 4:49 AM sebb  wrote:

> On 12 September 2018 at 16:40, Dave Fisher  wrote:
> > Hi -
> >
> > The Apache Pulsar project is ready to graduate as a TLP. They entered
> > Incubation on June 1, 2017, have had many releases and have grown the
> > community.
> >
> > Vote:
> > [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> > [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
> >
> > At the mentors request they did a maturity model analysis [1] and wrote
> > contribution guidelines. [2]
> >
> > The Graduation Proposal was written and discussed on the dev list. [3] At
> > the mentor's recommendation the By-Laws Clause was removed.
> >
> > The new prospective PMC is set and the VOTE thread in the podling is here
> > [4] with these results. [5]
> >
> > Regards,
> > Dave
> >
> > [1]
> >
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> > [2] http://pulsar.incubator.apache.org/en/contributing/
> > [3]
> >
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> > [4]
> >
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> > [5]
> >
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
> >
> >
> > 
> >
> > Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
> > commodity hardware. It provides simple pub-sub and queue semantics over
> > topics, lightweight compute framework, automatic cursor management for
> > subscribers, and cross-datacenter replication.
>
> Such detail as provided in the last sentence is unusual for graduation
> resolutions.
> I think the last sentence should be dropped from the resolution; it's
> not necessary.
>
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> > for the creation and maintenance of software related to a highly
> > scalable, low latency messaging platform running on commodity hardware.
> > It provides simple pub-sub and queue semantics over topics, lightweight
> > compute framework, automatic cursor management for subscribers, and
> > cross-datacenter replication; and be it further
>
> Ditto
>
> > RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Pulsar
> > 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 Pulsar Project:
> >
> > * Boyang Jerry Peng 
> > * Brad McMillen 
> > * David Fisher 
> > * Francis Christopher Liu 
> > * Hiroyuki Sakai 
> > * Ivan Brendan Kelly 
> > * Jai Asher 
> > * Jia Zhai 
> > * Jim Jagielski 
> > * Joe Francis 
> > * Ludwig Pummer 
> > * Masahiro Sakamoto 
> > * Masakazu Kitajo 
> > * Matteo Merli 
> > * Nozomi Kurihara 
> > * P. Taylor Goetz 
> > * Rajan Dhabalia 
> > * Sahaya Andrews 
> > * Sanjeev Kulkarni 
> > * Sebastián Schepens 
> > * Siddharth Boobna 
> > * Sijie Guo 
> > * Yuki Shiga 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> > to the office of Vice President, Apache Pulsar, 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 Apache Pulsar Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator Pulsar
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
>

RE: Incubator Workshop

2018-09-12 Thread ross 
Would such a course seek to teach the principles or the rules?

I ask because your original proposal says " making and voting on releases and 
voting on committers into the projects". There are no ***rules*** about having 
to vote. There are principles about how to build and recognize consensus. But, 
despite what much of the incubator documentation says, there are no formal 
rules about it.

I'm 100% for teaching people the principles of consensus building around 
releases and honoring people with committership. Even better if such a course 
gave concrete examples of how different communities apply those principles in 
different ways. However, I'm 100% against an opinionated piece that gives the 
impression that there is only one way to do things here in Apache. We already 
have way too much of that in Incubator docs.

Ross

-Original Message-
From: Justin Mclean  
Sent: Monday, September 10, 2018 3:54 PM
To: general@incubator.apache.org
Subject: Re: Incubator Workshop

Hi,

> For my part, most courseware is just an *extremely* slow form of 
> reading. I really don't need to have somebody read to me.

I tend to agree I also prefer to read something than watch a video, when I do I 
using speed it up. However different people learn in different ways. Currently 
we have a couple of ways people learn this stuff; from the website, by guidance 
by mentors, discussion on mailing lists, and possibly from conferences or 
conference recordings. I’ve just finished a qualification in adult learning and 
some of the biggest takeaways from it was people learn in differs ways but 
learn best when exposed to a a variety of ways and the effectiveness of the “do 
it fast”, “do it slow”, “let them do it” method for learning practical skills.

Thanks,
Justin


-
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] Graduate Apache Pulsar (incubating) as a TLP

2018-09-12 Thread sebb 
On 12 September 2018 at 16:40, Dave Fisher  wrote:
> Hi -
>
> The Apache Pulsar project is ready to graduate as a TLP. They entered
> Incubation on June 1, 2017, have had many releases and have grown the
> community.
>
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
>
> At the mentors request they did a maturity model analysis [1] and wrote
> contribution guidelines. [2]
>
> The Graduation Proposal was written and discussed on the dev list. [3] At
> the mentor's recommendation the By-Laws Clause was removed.
>
> The new prospective PMC is set and the VOTE thread in the podling is here
> [4] with these results. [5]
>
> Regards,
> Dave
>
> [1]
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> [2] http://pulsar.incubator.apache.org/en/contributing/
> [3]
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> [5]
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>
>
> 
>
> Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.

Such detail as provided in the last sentence is unusual for graduation
resolutions.
I think the last sentence should be dropped from the resolution; it's
not necessary.

> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further

Ditto

> RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> 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 Pulsar Project:
>
> * Boyang Jerry Peng 
> * Brad McMillen 
> * David Fisher 
> * Francis Christopher Liu 
> * Hiroyuki Sakai 
> * Ivan Brendan Kelly 
> * Jai Asher 
> * Jia Zhai 
> * Jim Jagielski 
> * Joe Francis 
> * Ludwig Pummer 
> * Masahiro Sakamoto 
> * Masakazu Kitajo 
> * Matteo Merli 
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia 
> * Sahaya Andrews 
> * Sanjeev Kulkarni 
> * Sebastián Schepens 
> * Siddharth Boobna 
> * Sijie Guo 
> * Yuki Shiga 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> to the office of Vice President, Apache Pulsar, 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 Apache Pulsar Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pulsar
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.

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

Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

2018-09-12 Thread Matt Sicker 
+1 (binding)

On Wed, 12 Sep 2018 at 10:40, Dave Fisher  wrote:

> Hi -
>
> The Apache Pulsar project is ready to graduate as a TLP. They entered
> Incubation on June 1, 2017, have had many releases and have grown the
> community.
>
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
>
> At the mentors request they did a maturity model analysis [1] and wrote
> contribution guidelines. [2]
>
> The Graduation Proposal was written and discussed on the dev list. [3] At
> the mentor's recommendation the By-Laws Clause was removed.
>
> The new prospective PMC is set and the VOTE thread in the podling is here
> [4] with these results. [5]
>
> Regards,
> Dave
>
> [1]
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> [2] http://pulsar.incubator.apache.org/en/contributing/
> [3]
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> [5]
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>
>
> 
>
> Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> 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 Pulsar Project:
>
> * Boyang Jerry Peng 
> * Brad McMillen 
> * David Fisher 
> * Francis Christopher Liu 
> * Hiroyuki Sakai 
> * Ivan Brendan Kelly 
> * Jai Asher 
> * Jia Zhai 
> * Jim Jagielski 
> * Joe Francis 
> * Ludwig Pummer 
> * Masahiro Sakamoto 
> * Masakazu Kitajo 
> * Matteo Merli 
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia 
> * Sahaya Andrews 
> * Sanjeev Kulkarni 
> * Sebastián Schepens 
> * Siddharth Boobna 
> * Sijie Guo 
> * Yuki Shiga 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> to the office of Vice President, Apache Pulsar, 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 Apache Pulsar Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pulsar
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>


-- 
Matt Sicker

Re: Auto-cleaning up Stale PRs

2018-09-12 Thread Sid Anand 
A stale PR is defined by a policy -- for example, 60 days without any
movement on the PR.

Stale PRs would be bad experiences in general for community members, but
after no movement for 60 days, this is just about cleaning up PRs that are
not getting feedback from the committers or PR submitters.

-s

On Wed, Sep 12, 2018 at 10:58 AM Dave Fisher  wrote:

> Hi -
>
> I was pointing out a potential community problem which is what we are
> about here in the Incubator.
>
> On Sep 12, 2018, at 10:27 AM, Sid Anand  wrote:
>
> A stale PR has not activity for some length of time.
> https://github.com/probot/stale
>
> The policy file example shown on that link it pretty easy to follow, so
> I'll avoid pasting a wall of text into this email.
>
> This seems like a pretty valuable and much-needed piece of management-y
> software. Unfortunately, I was informed Apache Infra could not grant write
> perms to this GitHub plugin. I'd like to understand how we decide which
> plugins on GitHub get whitelisted?
>
>
> The Incubator does not make these decisions. The Apache Infrastructure
> team makes these.
>
> You can contact Infra - https://www.apache.org/dev/infra-contact
>
> Regards,
> Dave
>
>
> -s
>
> On Wed, Sep 12, 2018 at 7:39 AM Dave Fisher  wrote:
>
> Hi -
>
> What if the stale PR is from a new community member who is trying to make
> a contribution? Those should be handled by a committer with direct
> discussion.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> On Sep 11, 2018, at 7:40 PM, Hagay Lupesko  wrote:
>
> Im also interested in this PR policy automation.
>
> For Apache MXNet, there is no automation that I am aware of that handles
> that. And it can be super helpful in handling stale PRs...
>
> Hagay
>
> On Tue, Sep 11, 2018, 12:07 Sid Anand  wrote:
>
> Hi Folks!
> I wanted a policy-driven approach to automatically label, comment, and
> close inactive/stale PRs. Probot does this, but need some write perms to
> GitHub.
>
> https://github.com/probot/stale
>
> I just learned this is not possible per
> https://issues.apache.org/jira/browse/INFRA-17005
>
> How are other projects solving this problem? And why is probot not on
>
> say
>
> an approved list of GitHub integrations?
>
> -s
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>
>

Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

2018-09-12 Thread Sijie Guo 
+1!! (non-binding)

- Sijie

On Wed, Sep 12, 2018 at 8:40 AM Dave Fisher  wrote:

> Hi -
>
> The Apache Pulsar project is ready to graduate as a TLP. They entered
> Incubation on June 1, 2017, have had many releases and have grown the
> community.
>
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
>
> At the mentors request they did a maturity model analysis [1] and wrote
> contribution guidelines. [2]
>
> The Graduation Proposal was written and discussed on the dev list. [3] At
> the mentor's recommendation the By-Laws Clause was removed.
>
> The new prospective PMC is set and the VOTE thread in the podling is here
> [4] with these results. [5]
>
> Regards,
> Dave
>
> [1]
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> [2] http://pulsar.incubator.apache.org/en/contributing/
> [3]
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> [5]
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>
>
> 
>
> Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> 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 Pulsar Project:
>
> * Boyang Jerry Peng 
> * Brad McMillen 
> * David Fisher 
> * Francis Christopher Liu 
> * Hiroyuki Sakai 
> * Ivan Brendan Kelly 
> * Jai Asher 
> * Jia Zhai 
> * Jim Jagielski 
> * Joe Francis 
> * Ludwig Pummer 
> * Masahiro Sakamoto 
> * Masakazu Kitajo 
> * Matteo Merli 
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia 
> * Sahaya Andrews 
> * Sanjeev Kulkarni 
> * Sebastián Schepens 
> * Siddharth Boobna 
> * Sijie Guo 
> * Yuki Shiga 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> to the office of Vice President, Apache Pulsar, 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 Apache Pulsar Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pulsar
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>

Re: Auto-cleaning up Stale PRs

2018-09-12 Thread Dave Fisher 
Hi -

I was pointing out a potential community problem which is what we are about 
here in the Incubator.

> On Sep 12, 2018, at 10:27 AM, Sid Anand  wrote:
> 
> A stale PR has not activity for some length of time.
> https://github.com/probot/stale
> 
> The policy file example shown on that link it pretty easy to follow, so
> I'll avoid pasting a wall of text into this email.
> 
> This seems like a pretty valuable and much-needed piece of management-y
> software. Unfortunately, I was informed Apache Infra could not grant write
> perms to this GitHub plugin. I'd like to understand how we decide which
> plugins on GitHub get whitelisted?

The Incubator does not make these decisions. The Apache Infrastructure team 
makes these.

You can contact Infra - https://www.apache.org/dev/infra-contact 


Regards,
Dave

> 
> -s
> 
> On Wed, Sep 12, 2018 at 7:39 AM Dave Fisher  wrote:
> 
>> Hi -
>> 
>> What if the stale PR is from a new community member who is trying to make
>> a contribution? Those should be handled by a committer with direct
>> discussion.
>> 
>> Regards,
>> Dave
>> 
>> Sent from my iPhone
>> 
>>> On Sep 11, 2018, at 7:40 PM, Hagay Lupesko  wrote:
>>> 
>>> Im also interested in this PR policy automation.
>>> 
>>> For Apache MXNet, there is no automation that I am aware of that handles
>>> that. And it can be super helpful in handling stale PRs...
>>> 
>>> Hagay
>>> 
 On Tue, Sep 11, 2018, 12:07 Sid Anand  wrote:
 
 Hi Folks!
 I wanted a policy-driven approach to automatically label, comment, and
 close inactive/stale PRs. Probot does this, but need some write perms to
 GitHub.
 
 https://github.com/probot/stale
 
 I just learned this is not possible per
 https://issues.apache.org/jira/browse/INFRA-17005
 
 How are other projects solving this problem? And why is probot not on
>> say
 an approved list of GitHub integrations?
 
 -s
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 



signature.asc
Description: Message signed with OpenPGP

Re: Auto-cleaning up Stale PRs

2018-09-12 Thread Sid Anand 
A stale PR has not activity for some length of time.
https://github.com/probot/stale

The policy file example shown on that link it pretty easy to follow, so
I'll avoid pasting a wall of text into this email.

This seems like a pretty valuable and much-needed piece of management-y
software. Unfortunately, I was informed Apache Infra could not grant write
perms to this GitHub plugin. I'd like to understand how we decide which
plugins on GitHub get whitelisted?

-s

On Wed, Sep 12, 2018 at 7:39 AM Dave Fisher  wrote:

> Hi -
>
> What if the stale PR is from a new community member who is trying to make
> a contribution? Those should be handled by a committer with direct
> discussion.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Sep 11, 2018, at 7:40 PM, Hagay Lupesko  wrote:
> >
> > Im also interested in this PR policy automation.
> >
> > For Apache MXNet, there is no automation that I am aware of that handles
> > that. And it can be super helpful in handling stale PRs...
> >
> > Hagay
> >
> >> On Tue, Sep 11, 2018, 12:07 Sid Anand  wrote:
> >>
> >> Hi Folks!
> >> I wanted a policy-driven approach to automatically label, comment, and
> >> close inactive/stale PRs. Probot does this, but need some write perms to
> >> GitHub.
> >>
> >> https://github.com/probot/stale
> >>
> >> I just learned this is not possible per
> >> https://issues.apache.org/jira/browse/INFRA-17005
> >>
> >> How are other projects solving this problem? And why is probot not on
> say
> >> an approved list of GitHub integrations?
> >>
> >> -s
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

2018-09-12 Thread Davor Bonaci 
+1 (binding)

On Wed, Sep 12, 2018 at 8:41 AM Dave Fisher  wrote:

> +1 - binding - Graduate Pulsar!
>
> Regards,
> Dave
>
> On Sep 12, 2018, at 8:40 AM, Dave Fisher  wrote:
>
> Hi -
>
> The Apache Pulsar project is ready to graduate as a TLP. They entered
> Incubation on June 1, 2017, have had many releases and have grown the
> community.
>
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
>
> At the mentors request they did a maturity model analysis [1] and wrote
> contribution guidelines. [2]
>
> The Graduation Proposal was written and discussed on the dev list. [3] At
> the mentor's recommendation the By-Laws Clause was removed.
>
> The new prospective PMC is set and the VOTE thread in the podling is here
> [4] with these results. [5]
>
> Regards,
> Dave
>
> [1]
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
> [2] http://pulsar.incubator.apache.org/en/contributing/
> [3]
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
> [4]
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
> [5]
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>
>
> 
>
> Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> 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 Pulsar Project:
>
> * Boyang Jerry Peng 
> * Brad McMillen 
> * David Fisher 
> * Francis Christopher Liu 
> * Hiroyuki Sakai 
> * Ivan Brendan Kelly 
> * Jai Asher 
> * Jia Zhai 
> * Jim Jagielski 
> * Joe Francis 
> * Ludwig Pummer 
> * Masahiro Sakamoto 
> * Masakazu Kitajo 
> * Matteo Merli 
> * Nozomi Kurihara 
> * P. Taylor Goetz 
> * Rajan Dhabalia 
> * Sahaya Andrews 
> * Sanjeev Kulkarni 
> * Sebastián Schepens 
> * Siddharth Boobna 
> * Sijie Guo 
> * Yuki Shiga 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> to the office of Vice President, Apache Pulsar, 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 Apache Pulsar Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Pulsar
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
>
>

Re: [VOTE] Graduate Apache Pulsar (incubating) as a TLP

2018-09-12 Thread Dave Fisher 
+1 - binding - Graduate Pulsar!

Regards,
Dave

> On Sep 12, 2018, at 8:40 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> The Apache Pulsar project is ready to graduate as a TLP. They entered 
> Incubation on June 1, 2017, have had many releases and have grown the 
> community.
> 
> Vote:
> [ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
> [ ] -1 - Do not recommend graduation of Apache Pulsar because ….
> 
> At the mentors request they did a maturity model analysis [1] and wrote 
> contribution guidelines. [2]
> 
> The Graduation Proposal was written and discussed on the dev list. [3] At the 
> mentor's recommendation the By-Laws Clause was removed.
> 
> The new prospective PMC is set and the VOTE thread in the podling is here [4] 
> with these results. [5]
> 
> Regards,
> Dave
> 
> [1] 
> https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
>  
> 
> [2] http://pulsar.incubator.apache.org/en/contributing/ 
> 
> [3] 
> https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
>  
> 
> [4] 
> https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
>  
> 
> [5] 
> https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
>  
> 
> 
> 
> 
> 
> Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
> commodity hardware. It provides simple pub-sub and queue semantics over
> topics, lightweight compute framework, automatic cursor management for
> subscribers, and cross-datacenter replication.
> 
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Pulsar Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
> 
> RESOLVED, that the Apache Pulsar Project be and hereby is responsible
> for the creation and maintenance of software related to a highly
> scalable, low latency messaging platform running on commodity hardware.
> It provides simple pub-sub and queue semantics over topics, lightweight
> compute framework, automatic cursor management for subscribers, and
> cross-datacenter replication; and be it further
> 
> RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Pulsar
> 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 Pulsar Project:
> 
> * Boyang Jerry Peng mailto:jerryp...@apache.org>>
> * Brad McMillen mailto:bra...@apache.org>>
> * David Fisher mailto:w...@apache.org>>
> * Francis Christopher Liu mailto:tof...@apache.org>>
> * Hiroyuki Sakai mailto:hrsa...@apache.org>>
> * Ivan Brendan Kelly mailto:iv...@apache.org>>
> * Jai Asher mailto:j...@apache.org>>
> * Jia Zhai mailto:zhai...@apache.org>>
> * Jim Jagielski mailto:j...@apache.org>>
> * Joe Francis mailto:j...@apache.org>>
> * Ludwig Pummer mailto:ludw...@apache.org>>
> * Masahiro Sakamoto mailto:massa...@apache.org>>
> * Masakazu Kitajo mailto:mas...@apache.org>>
> * Matteo Merli mailto:mme...@apache.org>>
> * Nozomi Kurihara mailto:nkuri...@apache.org>>
> * P. Taylor Goetz mailto:ptgo...@apache.org>>
> * Rajan Dhabalia mailto:rdhaba...@apache.org>>
> * Sahaya Andrews mailto:andr...@apache.org>>
> * Sanjeev Kulkarni mailto:sanjee...@apache.org>>
> * Sebastián Schepens mailto:sschep...@apache.org>>
> * Siddharth Boobna mailto:sboo...@apache.org>>
> * Sijie Guo mailto:si...@apache.org>>
> * Yuki Shiga mailto:yush...@apache.org>>
> 
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
> to the office of Vice President, Apache Pulsar, to serve in accordance
> with and subject to the direction of the Board of Directors and the
>

[VOTE] Graduate Apache Pulsar (incubating) as a TLP

2018-09-12 Thread Dave Fisher 
Hi -

The Apache Pulsar project is ready to graduate as a TLP. They entered 
Incubation on June 1, 2017, have had many releases and have grown the community.

Vote:
[ ] +1 - Recommend Graduation of Apache Pulsar as a TLP
[ ] -1 - Do not recommend graduation of Apache Pulsar because ….

At the mentors request they did a maturity model analysis [1] and wrote 
contribution guidelines. [2]

The Graduation Proposal was written and discussed on the dev list. [3] At the 
mentor's recommendation the By-Laws Clause was removed.

The new prospective PMC is set and the VOTE thread in the podling is here [4] 
with these results. [5]

Regards,
Dave

[1] 
https://github.com/apache/incubator-pulsar/wiki/Apache-Maturity-Model-Assessment-for-Pulsar
 

[2] http://pulsar.incubator.apache.org/en/contributing/ 

[3] 
https://lists.apache.org/thread.html/b0914461f57253237e4a3c9151342f6d4fa37359dfc98a07adf9f36f@%3Cdev.pulsar.apache.org%3E
 

[4] 
https://lists.apache.org/thread.html/93198abe36564a9e11a2a1bfe3ea8f35998444dbafea830f8b39df7b@%3Cdev.pulsar.apache.org%3E
 

[5] 
https://lists.apache.org/thread.html/64841a07ba3dee2271f4098f9142afd41acffae1736275592aab4c83@%3Cdev.pulsar.apache.org%3E
 





Establish the Apache Pulsar 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 highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub and queue semantics over
topics, lightweight compute framework, automatic cursor management for
subscribers, and cross-datacenter replication.

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

RESOLVED, that the Apache Pulsar Project be and hereby is responsible
for the creation and maintenance of software related to a highly
scalable, low latency messaging platform running on commodity hardware.
It provides simple pub-sub and queue semantics over topics, lightweight
compute framework, automatic cursor management for subscribers, and
cross-datacenter replication; and be it further

RESOLVED, that the office of "Vice President, Apache Pulsar" 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 Pulsar
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache Pulsar
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 Pulsar Project:

* Boyang Jerry Peng mailto:jerryp...@apache.org>>
* Brad McMillen mailto:bra...@apache.org>>
* David Fisher mailto:w...@apache.org>>
* Francis Christopher Liu mailto:tof...@apache.org>>
* Hiroyuki Sakai mailto:hrsa...@apache.org>>
* Ivan Brendan Kelly mailto:iv...@apache.org>>
* Jai Asher mailto:j...@apache.org>>
* Jia Zhai mailto:zhai...@apache.org>>
* Jim Jagielski mailto:j...@apache.org>>
* Joe Francis mailto:j...@apache.org>>
* Ludwig Pummer mailto:ludw...@apache.org>>
* Masahiro Sakamoto mailto:massa...@apache.org>>
* Masakazu Kitajo mailto:mas...@apache.org>>
* Matteo Merli mailto:mme...@apache.org>>
* Nozomi Kurihara mailto:nkuri...@apache.org>>
* P. Taylor Goetz mailto:ptgo...@apache.org>>
* Rajan Dhabalia mailto:rdhaba...@apache.org>>
* Sahaya Andrews mailto:andr...@apache.org>>
* Sanjeev Kulkarni mailto:sanjee...@apache.org>>
* Sebastián Schepens mailto:sschep...@apache.org>>
* Siddharth Boobna mailto:sboo...@apache.org>>
* Sijie Guo mailto:si...@apache.org>>
* Yuki Shiga mailto:yush...@apache.org>>

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matteo Merli be appointed
to the office of Vice President, Apache Pulsar, 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 Apache Pulsar Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator Pulsar
podling; and be it further

[ANNOUNCE] Release Apache SkyWalking (incubating) version 5.0.0-RC2

2018-09-12 Thread ???? Sheng Wu 
Hi all,


Apache SkyWalking (incubating) Team is glad to announce the first release of 
Apache SkyWalking Incubating 5.0.0-RC2.


SkyWalking: APM (application performance monitor) tool for distributed systems, 
especially designed for microservices, cloud native and container-based 
(Docker, Kubernetes, Mesos) architectures. 
Underlying technology is a distributed tracing system.


Vote Thread: 
https://lists.apache.org/thread.html/98828ecc0459bc28c379c2f9e49628a21dfa2bf5f26561a998b353b7@%3Cgeneral.incubator.apache.org%3E


Download Links : http://skywalking.apache.org/downloads/


Release Notes : 
https://github.com/apache/incubator-skywalking/tree/v5.0.0-RC2/CHANGES.md


Website: http://skywalking.apache.org/


SkyWalking Resources:
- Issue: https://github.com/apache/incubator-skywalking/issues
- Mailing list: d...@skywalkiing.incubator.apache.org
- Documents: 
https://github.com/apache/incubator-skywalking/tree/v5.0.0-RC2/docs/README.md




- Apache SkyWalking (incubating) Team


=
*Disclaimer*


Apache SkyWalking (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the name of Apache
Incubator PMC. 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.



--
Sheng Wu
Apache SkyWalking

Re: [RESULT][VOTE] Release Apache SkyWalking (incubating) version 5.0.0-RC2

2018-09-12 Thread Sheng Wu 
Hi all,

The vote for releasing Apache SkyWalking 5.0.0-RC2 (incubating) is closed, now.

Vote result:
3 (+1 binding) (Ignasi, Mick and William)

Thank you everyone for taking the time to review the release and help us.

I will process to publish the release and send ANNOUNCE.

Justin,
   Our 5.x branch and master branch compiling document links have been fixed 
already, will be included in next release.

Sheng Wu
Apache SkyWalking

On 2018/09/08 13:18:54, "吴晟 Sheng Wu"  wrote: 
> Hi All,
> This is a call for vote to release Apache SkyWalking (Incubating) version 
> 5.0.0-RC2.
> 
> 
> The Apache SkyWalking community has tested, voted and approved the proposed
> release of Apache SkyWalking (Incubating) 5.0.0-RC2
> 
> 
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
> 
> 
> SkyWalking: APM (application performance monitor) tool for distributed 
> systems, 
> especially designed for microservices, cloud native and container-based 
> (Docker, Kubernetes, Mesos) architectures. 
> Underlying technology is a distributed tracing system.
> 
> 
> 
> 
> Last RC release broke in IPMC vote, because our source release LICENSE and 
> NOTICE have issues[1],
> which are fixed in this release.
> 
> 
> Vote Thread:
> 
> 
> https://lists.apache.org/thread.html/442a5fc5a6b987c081e3932c967489fc746bf5ce887dfa5d5130d602@%3Cdev.skywalking.apache.org%3E
> 
> 
> 
> 
> Release notes:
> 
> 
> 
> 
> * https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md#500-rc
> 
> 
> 
> 
> Release Candidate:
> 
> 
> 
> 
> https://dist.apache.org/repos/dist/dev/incubator/skywalking/5.0.0-RC2/
> * sha512 checksums
> - 
> 867f66cbbda4d54c2ce8be2ae1b24f7f9fca745a8ccbb8a5a3689be86fbb47411125c65f9dc6b870f61847abc805376cdcb53952b406bf7f204af80fdf5ceacc
>  apache-skywalking-apm-incubating-5.0.0-RC2-src.tgz
> - 
> a02a44da7090af2f958f5d7816ec7b8d1b379c91e6fc52d35259ca3ad4396c7663e0c64b3652426ca2ad4953e5c1a2f5db1c138ca6f9c411b5f3cd014a785831
>  apache-skywalking-apm-incubating-5.0.0-RC2.tar.gz
> - 
> 9a66409411e89f6eec2bc173187971fdea803d5d81450b5f74311902938564c66215c239e400cb2db91324d9e9903f59e8acb46c5a1c1e5f3e189ffa25e74124
>  apache-skywalking-apm-incubating-5.0.0-RC2.zip
> 
> 
> 
> 
> Maven 2 staging repository:
> 
> 
> 
> 
> * 
> https://repository.apache.org/content/repositories/orgapacheskywalking-1020/org/apache/skywalking/
> 
> 
> 
> 
> Release Tag :
> 
> 
> 
> 
> * (GitHub Tag) https://github.com/apache/incubator-skywalking/tree/v5.0.0-RC2
> 
> 
> 
> 
> Release CommitID :
> 
> 
> 
> 
> * 
> https://github.com/apache/incubator-skywalking/tree/30fad9f822e96dfa4d8018b3f7b32e4f11521263
> * Git submodule
> * skywalking-ui: 
> https://github.com/apache/incubator-skywalking-ui/tree/ad3ee45dbadfae35d77238bdd7a1df593158f109
> * apm-protocol/apm-network/src/main/proto: 
> https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/c02c12af12116121e25155d1f3fca0fadee5f2e9
> 
> 
> 
> 
> Keys to verify the Release Candidate :
> 
> 
> 
> 
> * https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS 
> corresponding to wush...@apache.org
> 
> 
> 
> 
> Guide to build the release from source :
> 
> 
> 
> 
> * 
> https://github.com/apache/incubator-skywalking/blob/v5.0.0-RC2/docs/en/How-to-build.md
>  
> * `docs/en/How-to-build.md` in source release.
> 
> 
> 
> 
> Voting will start now (2018/9/8 date) and will remain open for at least 72 
> hours, Request IPMC to give their vote.
> [ ] +1 Release this package.
> [ ] +0 No opinion.
> [ ] -1 Do not release this package because
> 
> 
> 
> 
> [1] 
> https://lists.apache.org/thread.html/9a16dac30bf74d6aa96ee23e1b35edd040f468ef536ad155e50c97b8@%3Cgeneral.incubator.apache.org%3E
> 
> 
> 
> --
> Sheng Wu
> Apache SkyWalking

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

Re: Auto-cleaning up Stale PRs

2018-09-12 Thread Dave Fisher 
Hi -

What if the stale PR is from a new community member who is trying to make a 
contribution? Those should be handled by a committer with direct discussion.

Regards,
Dave

Sent from my iPhone

> On Sep 11, 2018, at 7:40 PM, Hagay Lupesko  wrote:
> 
> Im also interested in this PR policy automation.
> 
> For Apache MXNet, there is no automation that I am aware of that handles
> that. And it can be super helpful in handling stale PRs...
> 
> Hagay
> 
>> On Tue, Sep 11, 2018, 12:07 Sid Anand  wrote:
>> 
>> Hi Folks!
>> I wanted a policy-driven approach to automatically label, comment, and
>> close inactive/stale PRs. Probot does this, but need some write perms to
>> GitHub.
>> 
>> https://github.com/probot/stale
>> 
>> I just learned this is not possible per
>> https://issues.apache.org/jira/browse/INFRA-17005
>> 
>> How are other projects solving this problem? And why is probot not on say
>> an approved list of GitHub integrations?
>> 
>> -s
>> 


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

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

2018-09-12 Thread Justin Mclean 
Hi,

> Regarding affiliations for committers, I would say that it's not that we
> have "copied" from the only TLP that had it in their "Team" page.
> I just did a spot check and it seems to be a quite common practice across
> the board. Few examples (taken ramdomly):
> http://hive.apache.org/people.html 
> http://storm.apache.org/contribute/People.html 
> 
> http://activemq.apache.org/team.html 
> http://camel.apache.org/team.html 
> http://zookeeper.apache.org/credits.html 
> 
> http://avro.apache.org/credits.html 
As I said popular TLP projects tend to be copied and not checked if they comply 
with policy, it’s certainly not your project fault/issue, we have had similar
issues (on multiple occasions) with LICENSE and NOTICE files and more recently 
with project guidelines/bylaws.

We probably need to bring this up on trademarks to get sorted.

Thanks,
Justin

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

2018-09-12 Thread Matteo Merli 
> We will make sure we clean up creator language.

Just following up here: the change was already made yesterday (
https://github.com/apache/incubator-pulsar/pull/2557). The website is not
yet updated because of unrelated issues in the website Jenkins job.
Hopefully it will be fixed in next few hours.

> Sounds fine to me. They just copied something that a TLP project probably
shouldn’t be doing. It not the first time that has happened with that
project.

Regarding affiliations for committers, I would say that it's not that we
have "copied" from the only TLP that had it in their "Team" page.
I just did a spot check and it seems to be a quite common practice across
the board. Few examples (taken ramdomly):
http://hive.apache.org/people.html
http://storm.apache.org/contribute/People.html
http://activemq.apache.org/team.html
http://camel.apache.org/team.html
http://zookeeper.apache.org/credits.html
http://avro.apache.org/credits.html


On Tue, Sep 11, 2018 at 11:38 PM Dave Fisher  wrote:

> Hi Justin,
>
> Sent from my iPhone
>
> > On Sep 11, 2018, at 2:22 PM, Justin Mclean 
> wrote:
> >
> > Hi,
> >
> >>> I'm curious to why organisations are mention on the team page [2]
> >>
> >> I think we've followed what other projects are doing. e.g.
> >> https://spark.apache.org/committers.html
> >>
> >> Any ASF policy on this that we can follow?
> >
> > Well projects should be independent [1] and lists who works for who may
> make some question that, Who you work for  should have no relevance on an
> Apache project and I would not expect it to be listed on a team page.
>
> I think that this is debatable. I’d love to discuss it. In the case of
> Pulsar it has been important in showing independence. Mentors and even
> Sally have worked through a couple of situations in the podling. She has
> offered to help out with a graduation announcement. We will make sure we
> clean up creator language.
>
> >
> > Re actually policy on this then yes [2] and in particular [3] Note:
> > "Should not include corporate affiliations of actual contributors.
> Committers are expected to participate in Apache projects as individuals,
> and not as representatives of any employers. Including corporate
> affiliations on pages that are primarily about the community of individuals
> on a project can give the wrong impression to new community members about
> the fact that projects are managed by PMCs of individuals, and not managed
> by outside organizations."
>
> We will cleanup this page on graduation.
>
> I’ll start the VOTE in the morning.
>
> Regards,
> Dave
>
> >
> > Thanks,
> > Justin
> >
> > 1. http://community.apache.org/projectIndependence.html
> > 2. https://www.apache.org/foundation/marks/linking
> > 3. https://www.apache.org/foundation/marks/linking#whoweare
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> --
Matteo Merli

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-RC2

2018-09-12 Thread Willem Jiang 
+1 (Binding)

1. Checked signed key and sha512 of source and binary package of
https://dist.apache.org/repos/dist/dev/incubator/skywalking
2. Source code build successfully
3. Checked the artifacts in the staging repository
4. LICENSE and NOTICE are OK in source code and distribution package
5. Apache RAT checked
6. DISCLAIMER existed

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem
On Sat, Sep 8, 2018 at 9:19 PM 吴晟 Sheng Wu  wrote:
>
> Hi All,
> This is a call for vote to release Apache SkyWalking (Incubating) version 
> 5.0.0-RC2.
>
>
> The Apache SkyWalking community has tested, voted and approved the proposed
> release of Apache SkyWalking (Incubating) 5.0.0-RC2
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
>
> SkyWalking: APM (application performance monitor) tool for distributed 
> systems,
> especially designed for microservices, cloud native and container-based 
> (Docker, Kubernetes, Mesos) architectures.
> Underlying technology is a distributed tracing system.
>
>
>
>
> Last RC release broke in IPMC vote, because our source release LICENSE and 
> NOTICE have issues[1],
> which are fixed in this release.
>
>
> Vote Thread:
>
>
> https://lists.apache.org/thread.html/442a5fc5a6b987c081e3932c967489fc746bf5ce887dfa5d5130d602@%3Cdev.skywalking.apache.org%3E
>
>
>
>
> Release notes:
>
>
>
>
> * https://github.com/apache/incubator-skywalking/blob/master/CHANGES.md#500-rc
>
>
>
>
> Release Candidate:
>
>
>
>
> https://dist.apache.org/repos/dist/dev/incubator/skywalking/5.0.0-RC2/
> * sha512 checksums
> - 
> 867f66cbbda4d54c2ce8be2ae1b24f7f9fca745a8ccbb8a5a3689be86fbb47411125c65f9dc6b870f61847abc805376cdcb53952b406bf7f204af80fdf5ceacc
>  apache-skywalking-apm-incubating-5.0.0-RC2-src.tgz
> - 
> a02a44da7090af2f958f5d7816ec7b8d1b379c91e6fc52d35259ca3ad4396c7663e0c64b3652426ca2ad4953e5c1a2f5db1c138ca6f9c411b5f3cd014a785831
>  apache-skywalking-apm-incubating-5.0.0-RC2.tar.gz
> - 
> 9a66409411e89f6eec2bc173187971fdea803d5d81450b5f74311902938564c66215c239e400cb2db91324d9e9903f59e8acb46c5a1c1e5f3e189ffa25e74124
>  apache-skywalking-apm-incubating-5.0.0-RC2.zip
>
>
>
>
> Maven 2 staging repository:
>
>
>
>
> * 
> https://repository.apache.org/content/repositories/orgapacheskywalking-1020/org/apache/skywalking/
>
>
>
>
> Release Tag :
>
>
>
>
> * (GitHub Tag) https://github.com/apache/incubator-skywalking/tree/v5.0.0-RC2
>
>
>
>
> Release CommitID :
>
>
>
>
> * 
> https://github.com/apache/incubator-skywalking/tree/30fad9f822e96dfa4d8018b3f7b32e4f11521263
> * Git submodule
> * skywalking-ui: 
> https://github.com/apache/incubator-skywalking-ui/tree/ad3ee45dbadfae35d77238bdd7a1df593158f109
> * apm-protocol/apm-network/src/main/proto: 
> https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/c02c12af12116121e25155d1f3fca0fadee5f2e9
>
>
>
>
> Keys to verify the Release Candidate :
>
>
>
>
> * https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS 
> corresponding to wush...@apache.org
>
>
>
>
> Guide to build the release from source :
>
>
>
>
> * 
> https://github.com/apache/incubator-skywalking/blob/v5.0.0-RC2/docs/en/How-to-build.md
> * `docs/en/How-to-build.md` in source release.
>
>
>
>
> Voting will start now (2018/9/8 date) and will remain open for at least 72 
> hours, Request IPMC to give their vote.
> [ ] +1 Release this package.
> [ ] +0 No opinion.
> [ ] -1 Do not release this package because
>
>
>
>
> [1] 
> https://lists.apache.org/thread.html/9a16dac30bf74d6aa96ee23e1b35edd040f468ef536ad155e50c97b8@%3Cgeneral.incubator.apache.org%3E
>
>
>
> --
> Sheng Wu
> Apache SkyWalking

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

Re: Project probe: AsyncFlows Framework

2018-09-12 Thread Bertrand Delacretaz 
Hi,

On Wed, Sep 12, 2018 at 2:09 PM Dmitriy Pavlov  wrote:
> ...If there are no sufficient volunteers involved, the project has a high risk
> that development is stopped and the project is retired...

More precisely, an Apache project requires at least 3 active PMC
members [1] to operate.

So, when a project is ready to exit the Incubator it needs these 3 PMC
members, and we usually like to have a small buffer so graduating with
less than 5 active PMC members is not realistic IMO. And we like
having an initial community to demonstrate that the project interests
more than one person.

-Bertrand

[1] https://www.apache.org/foundation/how-it-works.html

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

Re: Project probe: AsyncFlows Framework

2018-09-12 Thread Dmitriy Pavlov 
Hi Constantine,

Anyway, thank you for bringing this idea here. I hope the project will find
enthusiasts.

About similar projects, it's totally not a problem. Let's Darwin decide.

About community. Unfortunately, it is a paramount thing in Apache projects.
If there are no sufficient volunteers involved, the project has a high risk
that development is stopped and the project is retired.

Sincerely,
Dmitriy Pavlov

вт, 11 сент. 2018 г. в 4:31, Dave Fisher :

> Hi Constantine,
>
> I took a few minutes to look into your project. You have some interesting
> ideas. You might want to look into the features of some current Apache
> projects and incubator podlings.
>
> (1) Events
> Pulsar
> Kafka
> ActiveMQ
> (2) Topologies
> Storm
> Heron
> Airflow
> I’m sure there are many.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Sep 10, 2018, at 2:48 PM, Constantine Plotnikov <
> constantine.plotni...@gmail.com> wrote:
> >
> > Hello All!
> >
> > I would like to probe if there is interest in the project AsyncFlows that
> > define DSL for asynchronous programming. The project is approximately the
> > same domain as Netty, MINA, HttpCore Async, Vert.X - asynchronous network
> > applications. However I belive tha the project provides higher level DSL
> > and significantly more usable from developer's perspective.
> >
> > The project repository: https://github.com/const/asyncflows
> > The home page has small developers guilde for the framework.
> >
> > The biggest problem with the project is that there is no community for it
> > now. And I'm the sole its developer, and I'm able to spend only some
> small
> > time on it. The project is getting out of the research stage. I'm getting
> > to the point of infrastructure setup (CI, maven central, etc), and
> > theoretically some of this effort would not be needed if the project
> would
> > join some meta-project like Apache, and there would be a default legal
> > framework for accepting contribution.
> >
> > I'm interested:
> > 1. Are there developers that interested in working on such project?
> > 2. Are there developers that interested in using such project?
> > 3. Is the project suitable for Apach Incubator considering that there are
> > already projects for the similar domain at Apache?
> > 4. Is the project suitable for Apache Incubator considering the current
> > lack of community and small resources that I could dedicate to it?
> >
> > Best Regards,
> > Constantine Plotnikov
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-RC2

2018-09-12 Thread ???? Sheng Wu 
>  - how come the binary comes in zip format but the source does not.


Just someone write the release script doesn't write that part. No special 
reason. Maybe add it, too?



Sheng Wu
Apache SkyWalking

From Wu Sheng 's phone.


-- Original --
From: Mick Semb Wever 
Date: Wed,Sep 12,2018 6:33 PM
To: general 
Subject: Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-RC2




> Voting will start now (2018/9/8 date) and will remain open for at least 
> 72 hours, Request IPMC to give their vote.
> [ ] +1 Release this package.
> [ ] +0 No opinion.
> [ ] -1 Do not release this package because


+1

Checked
 - sha512s ok
 - checked maven artefacts
 - source artefact builds
 - source artefact contents
 - DISCLAIMER, LICENSE and NOTICE files


Question:
 - how come the binary comes in zip format but the source does not.

regards,
Mick

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

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-RC2

2018-09-12 Thread Mick Semb Wever 


> Voting will start now (2018/9/8 date) and will remain open for at least 
> 72 hours, Request IPMC to give their vote.
> [ ] +1 Release this package.
> [ ] +0 No opinion.
> [ ] -1 Do not release this package because


+1

Checked
 - sha512s ok
 - checked maven artefacts
 - source artefact builds
 - source artefact contents
 - DISCLAIMER, LICENSE and NOTICE files


Question:
 - how come the binary comes in zip format but the source does not.

regards,
Mick

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

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

2018-09-12 Thread Justin Mclean 
HI,

> In the case of Pulsar it has been important in showing independence. Mentors 
> and even Sally have worked through a couple of situations in the podling. She 
> has offered to help out with a graduation announcement. We will make sure we 
> clean up creator language.

Sounds fine to me. They just copied something that a TLP project probably 
shouldn’t be doing. It not the first time that has happened with that project.

> We will cleanup this page on graduation.

Great.

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