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

[Von Gosling]

+1, very glad to see the pulsar to embrace the openmessaging spec in the coming 
soon


Best Regards,
Von Gosling

> 在 2018年9月14日，10:57，Dave Fisher  写道：
> 
> Hi -
> 
>> On Sep 13, 2018, at 7:04 PM, Willem Jiang > > wrote:
>> 
>> I think this line is generated from the template to explain the
>> purpose of the project.
>> It's no harmful to keep it there I guess.
> 
> It is an expanded version of the original text as seen on 
> http://incubator.apache.org/projects/pulsar.html 
> 
> 
> Pulsar is a highly scalable, low latency messaging platform running on 
> commodity hardware. It provides simple pub-sub semantics over topics, 
> guaranteed at-least-once delivery of messages, automatic cursor management 
> for subscribers, and cross-datacenter replication.
> 
> Vs.
> 
 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; 
> 
> Modification is “lightweight compute framework” replaces "guaranteed 
> at-least-once delivery of messages"
> 
>>> 
> 
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> 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 

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

[Dave Fisher]

Hi -

> On Sep 13, 2018, at 7:04 PM, Willem Jiang  wrote:
> 
> I think this line is generated from the template to explain the
> purpose of the project.
> It's no harmful to keep it there I guess.

It is an expanded version of the original text as seen on 
http://incubator.apache.org/projects/pulsar.html

Pulsar is a highly scalable, low latency messaging platform running on 
commodity hardware. It provides simple pub-sub semantics over topics, 
guaranteed at-least-once delivery of messages, automatic cursor management for 
subscribers, and cross-datacenter replication.

Vs.

>>> 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;

Modification is “lightweight compute framework” replaces "guaranteed 
at-least-once delivery of messages"

>> 

> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> 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 

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

[Willem Jiang]

I think this line is generated from the template to explain the
purpose of the project.
It's no harmful to keep it there I guess.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

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.
>
> -
> To unsubscribe, e-mail: 

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

[Jerry Peng]

+1 

On Thu, Sep 13, 2018 at 7:56 AM Karthik Ramasamy 
wrote:

> +1 (non-binding)
>
> Cheers
> /Karthik
>
> > On Sep 12, 2018, at 2:42 PM, Ali Ahmed  wrote:
> >
> > +1 (non-binding)
> >
> >> On Wed, Sep 12, 2018 at 11:09 AM Sijie Guo  wrote:
> >>
> >> +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
> >>> 

Re: Auto-cleaning up Stale PRs

[Sid Anand]

Apache Airflow has, at any point, >200 PRs open. During the slower summer
months, we've been merging 100-200 PRs a month. We have been growing the
community -- we have <600 contributors, ~200 companies using it, and 20+
committers. A person is promoted to "Committer" in recognition for work
he/she has done without an expectation of future work in maintaining the
code base. Hence, minting new committers doesn't always translate into
greater bench strength where merging PRs is concerned. That said, we are
actively adding new committers. The last 4-5 committers we added have been
super active maintainers, so the coverage on PRs and questions has been
getting better.

There are many causes of Cold-case PRs:

   1. Submitter is not actively responding
  1. One example is that we requested tests and they were never written
  2. Discussion ensued on the PR and the submitter did not accept the
  community's feedback
   2. Committers didn't get to it in a timely manner and after a while the
   engagement fell

We are in a better position now to handle (2) -- this was not the case a
year ago. We're at least able to keep up with our in-flow of PRs
week-to-week, but are still having challenges with the
previously-established backlog. But, (1) is also a contributor to stale PRs.

We do have a lot of stale PRs to manually handle -- I spent all of Summer
2017 pinging submitters of old PRs and I find myself in the same position
now.

Probot/stale is a useful tool. It has legitimate use-cases. A policy
reflects the health/mentality/approaches of the community. A tool like this
enforces the policy. Let's not overlook adoption of what would be a very
useful tool to the community due to a meta conversation about policy. I
think everyone on this list cares about growing a healthy and vibrant
community. We also care about being efficient with our spare time.  This
tools can help us manage both.

Also, I am not suggesting that we close JIRA, just stale PRs. JIRAs need to
be kept open so we don't lose visibility of bugs/features/etc... This tool
doesn't handle JIRA closing anyway.

-s

On Thu, Sep 13, 2018 at 1:37 AM Mark Thomas  wrote:

> On 12/09/18 19:16, Sid Anand wrote:
> > A stale PR is defined by a policy -- for example, 60 days without any
> > movement on the PR.
>
> Automatically closing such issues is not going to do anything to aid
> community building and is likely to actively damage such efforts.
>
> > 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.
>
> That is the wrong solution the problem.
>
> If reporters of issues are not responding to questions and there is
> genuinely nothing the community can do to progress the issue without
> their input then closing the issue is fair enough. But that should very
> much be the exception rather than the rule. In projects I am involved in
> I probably do that a handful of times a year. However, even in a good
> chunk of those cases, the main reason for the lack of response from the
> OP is that the community did not respond to the original report for an
> excessively long time.
>
> If the committers are not responding to issues in a timely manner then
> the solution is to start looking for more committers.
>
> Reporting an issue is often the first interaction someone new to the
> community has with the project. It should be treated as an opportunity
> to attract new members to the community and to grow the project.
>
> Mark
>
>
> >
> > -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 

Re: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1

[Jim Jagielski]

+1 on release... and +1 on removing the SHA-1s

> On Sep 11, 2018, at 7:34 PM, Henk P. Penning  wrote:
> 
> On Wed, 12 Sep 2018, Jerry Peng wrote:
> 
>> Date: Wed, 12 Sep 2018 00:31:35 +0200
>> From: Jerry Peng 
>> To: general@incubator.apache.org
>> Cc: d...@pulsar.incubator.apache.org
>> Subject: [VOTE] Pulsar Release 2.1.1-incubating Candidate 1
>> This is the first release candidate for Apache Pulsar, version
>> 2.1.1-incubating.
> 
>> Source and binary files:
>> https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.1-incubating-candidate-1/
> 
>> SHA-1 checksums:
> 
> Hi,
> 
>  SHA-1 checksum files shouldn't be publish checksums anymore.
> 
>  https://www.apache.org/dev/release-distribution#sigs-and-sums
> 
>  Please remove ; the vote may continue.
> 
>  Thanks ; regards,
> 
>  Henk Penning
> 
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> 
>> 506c172b13c1581f9b52769a4c6594541628b928
>> apache-pulsar-2.1.1-incubating-bin.tar.gz
>> de3a74449a78d0713998544237dde59765ee121f
>> apache-pulsar-2.1.1-incubating-src.tar.gz
>> 1d38554e58cfd733fc2d54ec1442747daeb8fc1b
>> apache-pulsar-io-connectors-2.1.1-incubating-bin.tar.gz
>> 
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachepulsar-1026
>> 
>> The tag to be voted upon:
>> v2.1.1-incubating-candidate-1 68faf85083025b29bb6ab39028a1d467bd3d5217
>> https://github.com/apache/incubator-pulsar/releases/tag/v2.1.1-incubating-candidate-1
>> 
>> Pulsar's KEYS file containing PGP keys we use to sign the release:
>> https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS
>> 
>> Please download the the source package, and follow the README to build and
>> run the Pulsar standalone service.
>> 
>> Here is a guide for validating a release candidate:
>> https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation
>> 


-
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

[Jim Jagielski]

+1 (binding)

> On Sep 12, 2018, at 11: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 

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

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Sep 12, 2018 at 11:40 PM 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.

-
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

[Sergio Fernández]

+1 (binding)

On Wed, Sep 12, 2018, 08: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.
>

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

[Justin Mclean]

HI,

+1 (binding)

Thanks,
Justin

-
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

[Karthik Ramasamy]

+1 (non-binding)

Cheers
/Karthik

> On Sep 12, 2018, at 2:42 PM, Ali Ahmed  wrote:
> 
> +1 (non-binding)
> 
>> On Wed, Sep 12, 2018 at 11:09 AM Sijie Guo  wrote:
>> 
>> +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.
>>> 
>> 
> 
> 
> -- 
> -Ali

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

Re: Incubator Workshop

[Justin Mclean]

Hi,

> Would such a course seek to teach the principles or the rules?

It’s currently an hour long, and while I do/would explain why some things are 
done that way, it’s not a deep dive into the underlying principles as I don’t 
think there enough time to do that. I think it’s easier to know policy and then 
understand why it that way and how the preinicaples apply, rather than the 
other way about, but I could be mistaken.

You're welcome to review it and give feedback on it which I’ll take into 
consideration and apply. I use the Apache Wombat material I made some time ago, 
a real release of an incubating project Pony Mail, and review a real (unnamed) 
TLP project LICENSE and NOTICE file and give some simple scenarios/candidates 
for committership and have an open discussion of if people should be 
committers. They are no correct answers to if the release should be released 
(but it probably should be), the LICENSE and NOTICE are OK (they have a few 
issues), or if the committers should be voted in ( it would depend on the PMC 
in question), that is all up to the participants.

> 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.

If you look at the incubator policy [1] you’ll note it uses MUST and SHALL 
quite carefully (as per [2]), no where does it say releases MUST be voted on so 
yes I’m aware a formal vote is not required. However I’m only aware of one TLP 
project that doesn’t vote on committers/releases in the way that most projects 
do (Apache SVN) and vaguely remember them making major changes on how releases 
were made at some point after one didn’t go so well. The exact detail of those 
differences I’m unaware of. I can’t recall a single incubator project in the 
last 5 years that hasn’t voted on releases. Anyone know of other examples where 
projects don’t vote on releases or committers? Is so please share them.

> 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.

If anyone (including you) can give me examples then I’ll certainly use them. 
The projects I’m involved in (or have been involved in) are certainly quite 
different to each other but I can't think of any major ways (with the exception 
of the Incubator) that they apply the principles in different ways. Some have 
set different bars for committership and some more welcoming than others but 
that’s not really a big difference in that regard.

> 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.

Patches are welcome.

Thanks,
Justin

1. https://incubator.apache.org/policy/incubation.html
2. https://www.ietf.org/rfc/rfc2119.txt
-
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

[Mark Thomas]

On 12/09/18 19:16, Sid Anand wrote:
> A stale PR is defined by a policy -- for example, 60 days without any
> movement on the PR.

Automatically closing such issues is not going to do anything to aid
community building and is likely to actively damage such efforts.

> 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.

That is the wrong solution the problem.

If reporters of issues are not responding to questions and there is
genuinely nothing the community can do to progress the issue without
their input then closing the issue is fair enough. But that should very
much be the exception rather than the rule. In projects I am involved in
I probably do that a handful of times a year. However, even in a good
chunk of those cases, the main reason for the lack of response from the
OP is that the community did not respond to the original report for an
excessively long time.

If the committers are not responding to issues in a timely manner then
the solution is to start looking for more committers.

Reporting an issue is often the first interaction someone new to the
community has with the project. It should be treated as an opportunity
to attract new members to the community and to grow the project.

Mark


> 
> -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
>>
>>
>>
>>
> 


-
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

[Ali Ahmed]

+1 (non-binding)

On Wed, Sep 12, 2018 at 11:09 AM Sijie Guo  wrote:

> +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.
> >
>


-- 
-Ali

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Jean-Baptiste Onofré]

Hi,

It's an interesting project. I have two questions:

1. do you have some interactions/dependencies with other Apache
projects, especially CXF for instance ?
2. what's the comparison between brpc and gRPC ? An alternative ?
Different features ?

I might be interested by mentoring the project, I would like to
understand exactly the target/purposes.

Thanks !
Regards
JB

On 13/09/2018 08:20, Tan,Zhongyi wrote:
> Hi, guys,
> 
> brpc is one open source RPC framework that is very popular in baidu and china.
> We want to contribute it to ASF to make it more successful.
> And we are looking for champion and mentor for this project,
> if anyone would like to volunteer, we will be very appreciated.
> 
> Thanks.
> 
> 
> Here is the draft for brpc proposal.
> 
> 
> # brpc Proposal
> 
> ## Abstract
> 
> brpc is an industrial-grade RPC framework for building reliable and 
> high-performance services.
> 
> ## Proposal
> 
> We propose to contribute the brpc codebase and associated artifacts(e.g. 
> documentation etc.) to the Apache Software Foundation, and aim to  build a 
> wider open community around it in the 'Apache Way'.
> 
> 
> ## Background
> 
> The RPC framework used in Baidu before 2014 was developed at 2008 and limited 
> in protocols and performance, and there were also serveral implementations 
> focused on their own scenarios from Baidu's different BU. As an 
> infrastructural team in Baidu, we tried to build a new framework to unify all 
> RPC scenarios inside. The framework was named "baidu-rpc" internally the 
> early versions were adopted and online at late 2014. The framework was 
> rapidly iterated at 2015-2017, and thousands kinds of services and almost all 
> core services adopted it. And in 2017, we opensourced it as "brpc" and hope 
> to get more adoptions and contributions from outside. At the time of 
> opensourcing, there're more than 1 million instances inside Baidu using 
> baidu-rpc (not counting clients).
> 
> 
> ## Rationale
> 
> brpc has been approved inside baidu, since many high performance core 
> services are using it.
> And since its open source, it has been adopted by several other companies, 
> including Iqiyi, Didi, Sougou, BiliBili etc.
> 
> ## Current Status
> 
> brpc has been an open source project on GitHub (https://github.com/brpc/brpc) 
> since 2017.
> 
> Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
> popular repositories in topic of rpc category in GitHub rpc catelogy.
> It has been widely used in Baidu, with 1,000,000+ instances and thousands 
> kinds of services.
> Besides, many other companies have already used it also, such as Iqiyi, Didi, 
> Sougou, BiliBili etc.
> 
> ### Meritocracy
> 
> brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
> Since its opensource in 2017, it has already followed meritocracy principles.
> It accepts multiple contributions from other companies.
> And now, the core developers are from several different companies.
> 
> We will follow Apache way to encourage more developers to contribute in this 
> project.
> We know that only active and committed developers from a diverse set of 
> backgrounds
> can make brpc a successful project.
> 
> 
> ### Community
> 
> brpc has been building an active community since its open source. Currently,
> the community includes over 31 contributors.
> The core developers of brpc are listed below.
> 
> ### Core Developers
> 
> * Ge Jun(https://github.com/jamesge jge...@gmail.com)
> * Chen Zhangyi(https://github.com/chenzhangyi frozen@gmail.com)
> * Jiang Rujie(https://github.com/old-bear jrjb...@gmail.com)
> * Zhu Jiashun(http://github.com/zyearn zhujiashun2...@gmail.com)
> * Wang Yao(https://github.com/ipconfigme ipconfi...@gmail.com)
> 
> ### Alignment
> 
> brpc is useful for building reliable and high-performance applications.
> Since ASF has many famous performance-related and rpc-related projects,
> we believe that ASF is a perfect choice to help brpc project to attract
> more developers and users as well as having more cooperation with existing 
> projects.
> 
> ## Known Risks
> 
> ### Orphaned Products
> 
> Since our core developers are from different companies and many companies are 
> using it,
> the risk of the project being abandoned is minimal.
> For example, Baidu is extensively using it in their production environment
> and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
> their production applications.
> 
> 
> ### Inexperience with Open Source
> 
> brpc has been an active open source project for more than one year.
> During that time, the project has attracted 30+ contributors and gained a lot 
> of attention.
> The core developers are all active users and followers of open source.
> 
> ### Homogenous Developers
> 
> brpc was created inside Baidu, but after brpc was open sourced, it received a 
> lot of bug fixes and enhancements from other developers not working at Baidu.
> And the core developers now are 

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

[Jean-Baptiste Onofré]

+1 (binding)

Good luck !

Regards
JB

On 12/09/2018 17: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 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  
> 
> RESOLVED, that all responsibilities pertaining to the Apache Incubator 
> Pulsar podling encumbered upon the Apache Incubator PMC are hereafter 
> discharged. 

-- 
Jean-Baptiste Onofré

We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Tan,Zhongyi]

Hi, guys,

brpc is one open source RPC framework that is very popular in baidu and china.
We want to contribute it to ASF to make it more successful.
And we are looking for champion and mentor for this project,
if anyone would like to volunteer, we will be very appreciated.

Thanks.


Here is the draft for brpc proposal.


# brpc Proposal

## Abstract

brpc is an industrial-grade RPC framework for building reliable and 
high-performance services.

## Proposal

We propose to contribute the brpc codebase and associated artifacts(e.g. 
documentation etc.) to the Apache Software Foundation, and aim to  build a 
wider open community around it in the 'Apache Way'.


## Background

The RPC framework used in Baidu before 2014 was developed at 2008 and limited 
in protocols and performance, and there were also serveral implementations 
focused on their own scenarios from Baidu's different BU. As an infrastructural 
team in Baidu, we tried to build a new framework to unify all RPC scenarios 
inside. The framework was named "baidu-rpc" internally the early versions were 
adopted and online at late 2014. The framework was rapidly iterated at 
2015-2017, and thousands kinds of services and almost all core services adopted 
it. And in 2017, we opensourced it as "brpc" and hope to get more adoptions and 
contributions from outside. At the time of opensourcing, there're more than 1 
million instances inside Baidu using baidu-rpc (not counting clients).


## Rationale

brpc has been approved inside baidu, since many high performance core services 
are using it.
And since its open source, it has been adopted by several other companies, 
including Iqiyi, Didi, Sougou, BiliBili etc.

## Current Status

brpc has been an open source project on GitHub (https://github.com/brpc/brpc) 
since 2017.

Currently it has more than 7.3k stars, 1.6k forks, and is one of the most 
popular repositories in topic of rpc category in GitHub rpc catelogy.
It has been widely used in Baidu, with 1,000,000+ instances and thousands kinds 
of services.
Besides, many other companies have already used it also, such as Iqiyi, Didi, 
Sougou, BiliBili etc.

### Meritocracy

brpc was originally created by Ge Jun and Chen zhangyi inside baidu from 2014.
Since its opensource in 2017, it has already followed meritocracy principles.
It accepts multiple contributions from other companies.
And now, the core developers are from several different companies.

We will follow Apache way to encourage more developers to contribute in this 
project.
We know that only active and committed developers from a diverse set of 
backgrounds
can make brpc a successful project.


### Community

brpc has been building an active community since its open source. Currently,
the community includes over 31 contributors.
The core developers of brpc are listed below.

### Core Developers

* Ge Jun(https://github.com/jamesge jge...@gmail.com)
* Chen Zhangyi(https://github.com/chenzhangyi frozen@gmail.com)
* Jiang Rujie(https://github.com/old-bear jrjb...@gmail.com)
* Zhu Jiashun(http://github.com/zyearn zhujiashun2...@gmail.com)
* Wang Yao(https://github.com/ipconfigme ipconfi...@gmail.com)

### Alignment

brpc is useful for building reliable and high-performance applications.
Since ASF has many famous performance-related and rpc-related projects,
we believe that ASF is a perfect choice to help brpc project to attract
more developers and users as well as having more cooperation with existing 
projects.

## Known Risks

### Orphaned Products

Since our core developers are from different companies and many companies are 
using it,
the risk of the project being abandoned is minimal.
For example, Baidu is extensively using it in their production environment
and many large corporations including Iqiyi, Didi, Sougou, BiliBili use it in 
their production applications.


### Inexperience with Open Source

brpc has been an active open source project for more than one year.
During that time, the project has attracted 30+ contributors and gained a lot 
of attention.
The core developers are all active users and followers of open source.

### Homogenous Developers

brpc was created inside Baidu, but after brpc was open sourced, it received a 
lot of bug fixes and enhancements from other developers not working at Baidu.
And the core developers now are from different companies now.

### Reliance on Salaried Developers

Baidu invested in brpc as a general rpc framework used in company widely.
The core developers have been dedicated to this project for about four years.
And after its open source, developers around the world have involved in.
Besides, we want more developers and researchers to contribute to the project.

### An Excessive Fascination with the Apache Brand

The mission of brpc is to help developers build reliable and high-performance 
services quickly and easily.
It has been widely used in production environment throughout Baidu and after 
opensource, it has gained much attention and