[RESULT] [VOTE] Pulsar into the Apache Incubator

[Bryan Call]

Thank you for all that participated in the VOTE.

The VOTE has ended and have this result :

9 +1 binding votes
7 +1 non-binding votes
No 0 votes
No -1 votes

With this Pulsar is officially accepted as Apache incubator project.
Congratulations!

+1 binding tally:
Raphael Bircher
Dave Fisher
Jean-Baptiste Onofré
Jim Jagielski
Phil Sorber
P. Taylor Goetz
Julian Hyde
Mohammad Noureldin
Luke Han

-Bryan

> On May 16, 2017, at 7:39 PM, Bryan Call  wrote:
> 
> Hi All,
> 
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
> 
> The ASF voting rules are described:
> 
>   https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which 
> only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
>   https://wiki.apache.org/incubator/PulsarProposal
> 
> -Bryan
> 
> 
> = Pulsar Proposal =
> 
> == Abstract ==
> 
> 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.
> 
> == Proposal ==
> 
> Pub-sub messaging is a very common design pattern that is increasingly found
> in distributed systems powering Internet applications. These applications
> provide real-time services, and need publish-latencies of 5ms on average and
> no more than 15ms at the 99th percentile. At Internet scale, these
> applications require a messaging system with ordering, strong durability, and
> delivery guarantees. In order to handle the “five 9’s” durability requirements
> of a production environment, the messages have to be committed on multiple
> disks or nodes.
> 
> Pulsar has been developed at Yahoo to address these specific requirements by
> providing a hosted service supporting millions of topics for multiple tenants.
> The current incarnation of Pulsar has been open-sourced under Apache license
> in September 2016 and it is the direct evolution of systems that were
> developed at Yahoo since 2011.
> 
> We believe there is currently no other system that provides a multi-tenant
> hosted messaging platform capable of supporting a huge number of topics while
> maintaining strict guarantees for durability, ordering and low latency.
> Current solutions would require to run multiple individual clusters with
> additional operational work and capacity overhead.
> 
> Since the open sourcing of Pulsar, the development has been done exclusively
> on the public Github repository and two major releases were shipped (1.15 and
> 1.16), along with multiple minor ones. Several other companies have expressed
> interest in the project and its future direction.
> 
> == Rationale ==
> 
> Pulsar is a platform that is built on top of several other Apache projects. In
> particular, Apache BookKeeper is used to store the data and Apache ZooKeeper
> is used for coordination and metadata storage. Pulsar is also interoperable
> out of the box with Apache Storm, to provide an easy to use stream processing
> solution.
> 
> We want to establish a community outside the scope of initial core developers
> at Yahoo and we believe that the Apache Foundation is a great fit and long-
> term home for Pulsar, as it provides an established process for community-
> driven development and decision making by consensus. This is exactly the model
> we want to adopt for future Pulsar development.
> 
> == Initial Goals ==
> 
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Furthermore, we plan for
> incremental development, and releases along with the Apache guidelines.
> 
> == Current Status ==
> 
> Pulsar has been in service at large scale for more than 2 years at Yahoo. In
> this time around 60 different applications were integrated with Pulsar. Other
> companies are evaluating it as well and have been contributing code to the
> project.
> 
> === Meritocracy ===
> 
> We value meritocracy and we understand that it is the basis to form an open
> community that encourages multiple companies and individuals to contribute and
> get invested in the project future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to all
> contributors.
> 
> === Community ===
> 
> We have validated, through the interest demonstrated by Pulsar users at Yahoo,
> that a reliable hosted pub-sub messaging platform represent a very important
> building block for web-scale distributed applications. We believe that many
> companies can benefit by applying the 

Re: [VOTE] Pulsar into the Apache Incubator

[Liang Chen]

+1
good luck!

Regards
Liang



--
View this message in context: 
http://apache-incubator-general.996316.n3.nabble.com/VOTE-Pulsar-into-the-Apache-Incubator-tp54918p54958.html
Sent from the Apache Incubator - General mailing list archive at Nabble.com.

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

Re: [VOTE] Pulsar into the Apache Incubator

[Xinyu Zhou]

+1(non-binding)

Glad to see ASF will have another messaging solution~

On Fri, May 19, 2017 at 6:04pm, Luke Han < luke...@gmail.com 
[luke...@gmail.com] > wrote:
+1 (binding)


Best Regards!
-

Luke Han

On Thu, May 18, 2017 at 11:09 PM, Mohammad Noureldin <
nour.moham...@gmail.com> wrote:

> +1 (binding)
>
> On May 18, 2017 15:31, "Pierre Smits"  wrote:
>
> > +1, from the peanut gallery.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Thu, May 18, 2017 at 1:03 AM, vintagewang 
> > wrote:
> >
> > > +1(non-binding)
> > >
> > > Pulsar is a powerful mq， I like it.
> > >
> > >
> > >
> > > On Wed, May 17, 2017 at 2:44 PM, Julian Hyde  wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > > On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz <
> ptgo...@gmail.com>
> > > > wrote:
> > > > >
> > > > >> +1 (binding)
> > > > >>
> > > > >> -Taylor
> > > > >>
> > > > >>> On May 16, 2017, at 10:39 PM, Bryan Call 
> wrote:
> > > > >>>
> > > > >>> Hi All,
> > > > >>>
> > > > >>> As the champion for Pulsar, I would like to start a VOTE to bring
> > the
> > > > >>> project in as Apache incubator podling.
> > > > >>>
> > > > >>> The ASF voting rules are described:
> > > > >>>
> > > > >>> https://www.apache.org/foundation/voting.html
> > > > >>>
> > > > >>> A vote for accepting a new Apache Incubator podling is a majority
> > > vote
> > > > >> for which
> > > > >>> only Incubator PMC member votes are binding.
> > > > >>>
> > > > >>> This vote will run for at least 72 hours. Please VOTE as follows
> > > > >>> [] +1 Accept Pulsar into the Apache Incubator
> > > > >>> [] +0 Abstain.
> > > > >>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> > > > >>>
> > > > >>> The proposal is listed below, but you can also access it on the
> > wiki:
> > > > >>>
> > > > >>> https://wiki.apache.org/incubator/PulsarProposal
> > > > >>>
> > > > >>> -Bryan
> > > > >>>
> > > > >>>
> > > > >>> = Pulsar Proposal =
> > > > >>>
> > > > >>> == Abstract ==
> > > > >>>
> > > > >>> 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.
> > > > >>>
> > > > >>> == Proposal ==
> > > > >>>
> > > > >>> Pub-sub messaging is a very common design pattern that is
> > > increasingly
> > > > >> found
> > > > >>> in distributed systems powering Internet applications. These
> > > > applications
> > > > >>> provide real-time services, and need publish-latencies of 5ms on
> > > > average
> > > > >> and
> > > > >>> no more than 15ms at the 99th percentile. At Internet scale,
> these
> > > > >>> applications require a messaging system with ordering, strong
> > > > >> durability, and
> > > > >>> delivery guarantees. In order to handle the “five 9’s” durability
> > > > >> requirements
> > > > >>> of a production environment, the messages have to be committed on
> > > > >> multiple
> > > > >>> disks or nodes.
> > > > >>>
> > > > >>> Pulsar has been developed at Yahoo to address these specific
> > > > >> requirements by
> > > > >>> providing a hosted service supporting millions of topics for
> > multiple
> > > > >> tenants.
> > > > >>> The current incarnation of Pulsar has been open-sourced under
> > Apache
> > > > >> license
> > > > >>> in September 2016 and it is the direct evolution of systems that
> > were
> > > > >>> developed at Yahoo since 2011.
> > > > >>>
> > > > >>> We believe there is currently no other system that provides a
> > > > >> multi-tenant
> > > > >>> hosted messaging platform capable of supporting a huge number of
> > > topics
> > > > >> while
> > > > >>> maintaining strict guarantees for durability, ordering and low
> > > latency.
> > > > >>> Current solutions would require to run multiple individual
> clusters
> > > > with
> > > > >>> additional operational work and capacity overhead.
> > > > >>>
> > > > >>> Since the open sourcing of Pulsar, the development has been done
> > > > >> exclusively
> > > > >>> on the public Github repository and two major releases were
> shipped
> > > > >> (1.15 and
> > > > >>> 1.16), along with multiple minor ones. Several other companies
> have
> > > > >> expressed
> > > > >>> interest in the project and its future direction.
> > > > >>>
> > > > >>> == Rationale ==
> > > > >>>
> > > > >>> Pulsar is a platform that is built on top of several other Apache
> > > > >> projects. In
> > > > >>> particular, Apache BookKeeper is used to store the data and
> Apache
> > > > 

Re: [VOTE] Pulsar into the Apache Incubator

[Luke Han]

+1 (binding)


Best Regards!
-

Luke Han

On Thu, May 18, 2017 at 11:09 PM, Mohammad Noureldin <
nour.moham...@gmail.com> wrote:

> +1 (binding)
>
> On May 18, 2017 15:31, "Pierre Smits"  wrote:
>
> > +1, from the peanut gallery.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Thu, May 18, 2017 at 1:03 AM, vintagewang 
> > wrote:
> >
> > > +1(non-binding)
> > >
> > > Pulsar is a powerful mq， I like it.
> > >
> > >
> > >
> > > On Wed, May 17, 2017 at 2:44 PM, Julian Hyde  wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > > On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> > > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz <
> ptgo...@gmail.com>
> > > > wrote:
> > > > >
> > > > >> +1 (binding)
> > > > >>
> > > > >> -Taylor
> > > > >>
> > > > >>> On May 16, 2017, at 10:39 PM, Bryan Call 
> wrote:
> > > > >>>
> > > > >>> Hi All,
> > > > >>>
> > > > >>> As the champion for Pulsar, I would like to start a VOTE to bring
> > the
> > > > >>> project in as Apache incubator podling.
> > > > >>>
> > > > >>> The ASF voting rules are described:
> > > > >>>
> > > > >>>   https://www.apache.org/foundation/voting.html
> > > > >>>
> > > > >>> A vote for accepting a new Apache Incubator podling is a majority
> > > vote
> > > > >> for which
> > > > >>> only Incubator PMC member votes are binding.
> > > > >>>
> > > > >>> This vote will run for at least 72 hours. Please VOTE as follows
> > > > >>> [] +1 Accept Pulsar into the Apache Incubator
> > > > >>> [] +0 Abstain.
> > > > >>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> > > > >>>
> > > > >>> The proposal is listed below, but you can also access it on the
> > wiki:
> > > > >>>
> > > > >>>   https://wiki.apache.org/incubator/PulsarProposal
> > > > >>>
> > > > >>> -Bryan
> > > > >>>
> > > > >>>
> > > > >>> = Pulsar Proposal =
> > > > >>>
> > > > >>> == Abstract ==
> > > > >>>
> > > > >>> 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.
> > > > >>>
> > > > >>> == Proposal ==
> > > > >>>
> > > > >>> Pub-sub messaging is a very common design pattern that is
> > > increasingly
> > > > >> found
> > > > >>> in distributed systems powering Internet applications. These
> > > > applications
> > > > >>> provide real-time services, and need publish-latencies of 5ms on
> > > > average
> > > > >> and
> > > > >>> no more than 15ms at the 99th percentile. At Internet scale,
> these
> > > > >>> applications require a messaging system with ordering, strong
> > > > >> durability, and
> > > > >>> delivery guarantees. In order to handle the “five 9’s” durability
> > > > >> requirements
> > > > >>> of a production environment, the messages have to be committed on
> > > > >> multiple
> > > > >>> disks or nodes.
> > > > >>>
> > > > >>> Pulsar has been developed at Yahoo to address these specific
> > > > >> requirements by
> > > > >>> providing a hosted service supporting millions of topics for
> > multiple
> > > > >> tenants.
> > > > >>> The current incarnation of Pulsar has been open-sourced under
> > Apache
> > > > >> license
> > > > >>> in September 2016 and it is the direct evolution of systems that
> > were
> > > > >>> developed at Yahoo since 2011.
> > > > >>>
> > > > >>> We believe there is currently no other system that provides a
> > > > >> multi-tenant
> > > > >>> hosted messaging platform capable of supporting a huge number of
> > > topics
> > > > >> while
> > > > >>> maintaining strict guarantees for durability, ordering and low
> > > latency.
> > > > >>> Current solutions would require to run multiple individual
> clusters
> > > > with
> > > > >>> additional operational work and capacity overhead.
> > > > >>>
> > > > >>> Since the open sourcing of Pulsar, the development has been done
> > > > >> exclusively
> > > > >>> on the public Github repository and two major releases were
> shipped
> > > > >> (1.15 and
> > > > >>> 1.16), along with multiple minor ones. Several other companies
> have
> > > > >> expressed
> > > > >>> interest in the project and its future direction.
> > > > >>>
> > > > >>> == Rationale ==
> > > > >>>
> > > > >>> Pulsar is a platform that is built on top of several other Apache
> > > > >> projects. In
> > > > >>> particular, Apache BookKeeper is used to store the data and
> Apache
> > > > >> ZooKeeper
> > > > >>> is used for coordination and metadata storage. Pulsar is also
> > > > >> interoperable
> > > > >>> out of the box with Apache Storm, 

Re: [VOTE] Pulsar into the Apache Incubator

[Mohammad Noureldin]

+1 (binding)

On May 18, 2017 15:31, "Pierre Smits"  wrote:

> +1, from the peanut gallery.
>
> Best regards,
>
> Pierre Smits
>
> ORRTIZ.COM 
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>
> On Thu, May 18, 2017 at 1:03 AM, vintagewang 
> wrote:
>
> > +1(non-binding)
> >
> > Pulsar is a powerful mq， I like it.
> >
> >
> >
> > On Wed, May 17, 2017 at 2:44 PM, Julian Hyde  wrote:
> >
> > > +1 (binding)
> > >
> > > > On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz 
> > > wrote:
> > > >
> > > >> +1 (binding)
> > > >>
> > > >> -Taylor
> > > >>
> > > >>> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> > > >>>
> > > >>> Hi All,
> > > >>>
> > > >>> As the champion for Pulsar, I would like to start a VOTE to bring
> the
> > > >>> project in as Apache incubator podling.
> > > >>>
> > > >>> The ASF voting rules are described:
> > > >>>
> > > >>>   https://www.apache.org/foundation/voting.html
> > > >>>
> > > >>> A vote for accepting a new Apache Incubator podling is a majority
> > vote
> > > >> for which
> > > >>> only Incubator PMC member votes are binding.
> > > >>>
> > > >>> This vote will run for at least 72 hours. Please VOTE as follows
> > > >>> [] +1 Accept Pulsar into the Apache Incubator
> > > >>> [] +0 Abstain.
> > > >>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> > > >>>
> > > >>> The proposal is listed below, but you can also access it on the
> wiki:
> > > >>>
> > > >>>   https://wiki.apache.org/incubator/PulsarProposal
> > > >>>
> > > >>> -Bryan
> > > >>>
> > > >>>
> > > >>> = Pulsar Proposal =
> > > >>>
> > > >>> == Abstract ==
> > > >>>
> > > >>> 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.
> > > >>>
> > > >>> == Proposal ==
> > > >>>
> > > >>> Pub-sub messaging is a very common design pattern that is
> > increasingly
> > > >> found
> > > >>> in distributed systems powering Internet applications. These
> > > applications
> > > >>> provide real-time services, and need publish-latencies of 5ms on
> > > average
> > > >> and
> > > >>> no more than 15ms at the 99th percentile. At Internet scale, these
> > > >>> applications require a messaging system with ordering, strong
> > > >> durability, and
> > > >>> delivery guarantees. In order to handle the “five 9’s” durability
> > > >> requirements
> > > >>> of a production environment, the messages have to be committed on
> > > >> multiple
> > > >>> disks or nodes.
> > > >>>
> > > >>> Pulsar has been developed at Yahoo to address these specific
> > > >> requirements by
> > > >>> providing a hosted service supporting millions of topics for
> multiple
> > > >> tenants.
> > > >>> The current incarnation of Pulsar has been open-sourced under
> Apache
> > > >> license
> > > >>> in September 2016 and it is the direct evolution of systems that
> were
> > > >>> developed at Yahoo since 2011.
> > > >>>
> > > >>> We believe there is currently no other system that provides a
> > > >> multi-tenant
> > > >>> hosted messaging platform capable of supporting a huge number of
> > topics
> > > >> while
> > > >>> maintaining strict guarantees for durability, ordering and low
> > latency.
> > > >>> Current solutions would require to run multiple individual clusters
> > > with
> > > >>> additional operational work and capacity overhead.
> > > >>>
> > > >>> Since the open sourcing of Pulsar, the development has been done
> > > >> exclusively
> > > >>> on the public Github repository and two major releases were shipped
> > > >> (1.15 and
> > > >>> 1.16), along with multiple minor ones. Several other companies have
> > > >> expressed
> > > >>> interest in the project and its future direction.
> > > >>>
> > > >>> == Rationale ==
> > > >>>
> > > >>> Pulsar is a platform that is built on top of several other Apache
> > > >> projects. In
> > > >>> particular, Apache BookKeeper is used to store the data and Apache
> > > >> ZooKeeper
> > > >>> is used for coordination and metadata storage. Pulsar is also
> > > >> interoperable
> > > >>> out of the box with Apache Storm, to provide an easy to use stream
> > > >> processing
> > > >>> solution.
> > > >>>
> > > >>> We want to establish a community outside the scope of initial core
> > > >> developers
> > > >>> at Yahoo and we believe that the Apache Foundation is a great fit
> and
> > > >> long-
> > > >>> term home for Pulsar, as it provides an established process for
> > > >> community-
> > > >>> driven development and decision making by consensus. This is
> 

Re: [VOTE] Pulsar into the Apache Incubator

[Pierre Smits]

+1, from the peanut gallery.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Thu, May 18, 2017 at 1:03 AM, vintagewang  wrote:

> +1(non-binding)
>
> Pulsar is a powerful mq， I like it.
>
>
>
> On Wed, May 17, 2017 at 2:44 PM, Julian Hyde  wrote:
>
> > +1 (binding)
> >
> > > On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> > >
> > > +1 (non-binding)
> > >
> > > On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz 
> > wrote:
> > >
> > >> +1 (binding)
> > >>
> > >> -Taylor
> > >>
> > >>> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> > >>>
> > >>> Hi All,
> > >>>
> > >>> As the champion for Pulsar, I would like to start a VOTE to bring the
> > >>> project in as Apache incubator podling.
> > >>>
> > >>> The ASF voting rules are described:
> > >>>
> > >>>   https://www.apache.org/foundation/voting.html
> > >>>
> > >>> A vote for accepting a new Apache Incubator podling is a majority
> vote
> > >> for which
> > >>> only Incubator PMC member votes are binding.
> > >>>
> > >>> This vote will run for at least 72 hours. Please VOTE as follows
> > >>> [] +1 Accept Pulsar into the Apache Incubator
> > >>> [] +0 Abstain.
> > >>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> > >>>
> > >>> The proposal is listed below, but you can also access it on the wiki:
> > >>>
> > >>>   https://wiki.apache.org/incubator/PulsarProposal
> > >>>
> > >>> -Bryan
> > >>>
> > >>>
> > >>> = Pulsar Proposal =
> > >>>
> > >>> == Abstract ==
> > >>>
> > >>> 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.
> > >>>
> > >>> == Proposal ==
> > >>>
> > >>> Pub-sub messaging is a very common design pattern that is
> increasingly
> > >> found
> > >>> in distributed systems powering Internet applications. These
> > applications
> > >>> provide real-time services, and need publish-latencies of 5ms on
> > average
> > >> and
> > >>> no more than 15ms at the 99th percentile. At Internet scale, these
> > >>> applications require a messaging system with ordering, strong
> > >> durability, and
> > >>> delivery guarantees. In order to handle the “five 9’s” durability
> > >> requirements
> > >>> of a production environment, the messages have to be committed on
> > >> multiple
> > >>> disks or nodes.
> > >>>
> > >>> Pulsar has been developed at Yahoo to address these specific
> > >> requirements by
> > >>> providing a hosted service supporting millions of topics for multiple
> > >> tenants.
> > >>> The current incarnation of Pulsar has been open-sourced under Apache
> > >> license
> > >>> in September 2016 and it is the direct evolution of systems that were
> > >>> developed at Yahoo since 2011.
> > >>>
> > >>> We believe there is currently no other system that provides a
> > >> multi-tenant
> > >>> hosted messaging platform capable of supporting a huge number of
> topics
> > >> while
> > >>> maintaining strict guarantees for durability, ordering and low
> latency.
> > >>> Current solutions would require to run multiple individual clusters
> > with
> > >>> additional operational work and capacity overhead.
> > >>>
> > >>> Since the open sourcing of Pulsar, the development has been done
> > >> exclusively
> > >>> on the public Github repository and two major releases were shipped
> > >> (1.15 and
> > >>> 1.16), along with multiple minor ones. Several other companies have
> > >> expressed
> > >>> interest in the project and its future direction.
> > >>>
> > >>> == Rationale ==
> > >>>
> > >>> Pulsar is a platform that is built on top of several other Apache
> > >> projects. In
> > >>> particular, Apache BookKeeper is used to store the data and Apache
> > >> ZooKeeper
> > >>> is used for coordination and metadata storage. Pulsar is also
> > >> interoperable
> > >>> out of the box with Apache Storm, to provide an easy to use stream
> > >> processing
> > >>> solution.
> > >>>
> > >>> We want to establish a community outside the scope of initial core
> > >> developers
> > >>> at Yahoo and we believe that the Apache Foundation is a great fit and
> > >> long-
> > >>> term home for Pulsar, as it provides an established process for
> > >> community-
> > >>> driven development and decision making by consensus. This is exactly
> > the
> > >> model
> > >>> we want to adopt for future Pulsar development.
> > >>>
> > >>> == Initial Goals ==
> > >>>
> > >>> The initial goals will be to move the existing codebase to Apache and
> > >>> integrate with the Apache development process. Furthermore, we plan
> for
> > >>> incremental development, and releases along with the Apache
> guidelines.
> > >>>
> 

Re: [VOTE] Pulsar into the Apache Incubator

[vintagewang]

+1(non-binding)

Pulsar is a powerful mq， I like it.



On Wed, May 17, 2017 at 2:44 PM, Julian Hyde  wrote:

> +1 (binding)
>
> > On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> >
> > +1 (non-binding)
> >
> > On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz 
> wrote:
> >
> >> +1 (binding)
> >>
> >> -Taylor
> >>
> >>> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> >>>
> >>> Hi All,
> >>>
> >>> As the champion for Pulsar, I would like to start a VOTE to bring the
> >>> project in as Apache incubator podling.
> >>>
> >>> The ASF voting rules are described:
> >>>
> >>>   https://www.apache.org/foundation/voting.html
> >>>
> >>> A vote for accepting a new Apache Incubator podling is a majority vote
> >> for which
> >>> only Incubator PMC member votes are binding.
> >>>
> >>> This vote will run for at least 72 hours. Please VOTE as follows
> >>> [] +1 Accept Pulsar into the Apache Incubator
> >>> [] +0 Abstain.
> >>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> >>>
> >>> The proposal is listed below, but you can also access it on the wiki:
> >>>
> >>>   https://wiki.apache.org/incubator/PulsarProposal
> >>>
> >>> -Bryan
> >>>
> >>>
> >>> = Pulsar Proposal =
> >>>
> >>> == Abstract ==
> >>>
> >>> 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.
> >>>
> >>> == Proposal ==
> >>>
> >>> Pub-sub messaging is a very common design pattern that is increasingly
> >> found
> >>> in distributed systems powering Internet applications. These
> applications
> >>> provide real-time services, and need publish-latencies of 5ms on
> average
> >> and
> >>> no more than 15ms at the 99th percentile. At Internet scale, these
> >>> applications require a messaging system with ordering, strong
> >> durability, and
> >>> delivery guarantees. In order to handle the “five 9’s” durability
> >> requirements
> >>> of a production environment, the messages have to be committed on
> >> multiple
> >>> disks or nodes.
> >>>
> >>> Pulsar has been developed at Yahoo to address these specific
> >> requirements by
> >>> providing a hosted service supporting millions of topics for multiple
> >> tenants.
> >>> The current incarnation of Pulsar has been open-sourced under Apache
> >> license
> >>> in September 2016 and it is the direct evolution of systems that were
> >>> developed at Yahoo since 2011.
> >>>
> >>> We believe there is currently no other system that provides a
> >> multi-tenant
> >>> hosted messaging platform capable of supporting a huge number of topics
> >> while
> >>> maintaining strict guarantees for durability, ordering and low latency.
> >>> Current solutions would require to run multiple individual clusters
> with
> >>> additional operational work and capacity overhead.
> >>>
> >>> Since the open sourcing of Pulsar, the development has been done
> >> exclusively
> >>> on the public Github repository and two major releases were shipped
> >> (1.15 and
> >>> 1.16), along with multiple minor ones. Several other companies have
> >> expressed
> >>> interest in the project and its future direction.
> >>>
> >>> == Rationale ==
> >>>
> >>> Pulsar is a platform that is built on top of several other Apache
> >> projects. In
> >>> particular, Apache BookKeeper is used to store the data and Apache
> >> ZooKeeper
> >>> is used for coordination and metadata storage. Pulsar is also
> >> interoperable
> >>> out of the box with Apache Storm, to provide an easy to use stream
> >> processing
> >>> solution.
> >>>
> >>> We want to establish a community outside the scope of initial core
> >> developers
> >>> at Yahoo and we believe that the Apache Foundation is a great fit and
> >> long-
> >>> term home for Pulsar, as it provides an established process for
> >> community-
> >>> driven development and decision making by consensus. This is exactly
> the
> >> model
> >>> we want to adopt for future Pulsar development.
> >>>
> >>> == Initial Goals ==
> >>>
> >>> The initial goals will be to move the existing codebase to Apache and
> >>> integrate with the Apache development process. Furthermore, we plan for
> >>> incremental development, and releases along with the Apache guidelines.
> >>>
> >>> == Current Status ==
> >>>
> >>> Pulsar has been in service at large scale for more than 2 years at
> >> Yahoo. In
> >>> this time around 60 different applications were integrated with Pulsar.
> >> Other
> >>> companies are evaluating it as well and have been contributing code to
> >> the
> >>> project.
> >>>
> >>> === Meritocracy ===
> >>>
> >>> We value meritocracy and we understand that it is the basis to form an
> >> open
> >>> community that encourages multiple companies and individuals to
> >> contribute and
> >>> get 

Re: [VOTE] Pulsar into the Apache Incubator

[Julian Hyde]

+1 (binding)

> On May 17, 2017, at 1:58 PM, Jia Zhai  wrote:
> 
> +1 (non-binding)
> 
> On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz  wrote:
> 
>> +1 (binding)
>> 
>> -Taylor
>> 
>>> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
>>> 
>>> Hi All,
>>> 
>>> As the champion for Pulsar, I would like to start a VOTE to bring the
>>> project in as Apache incubator podling.
>>> 
>>> The ASF voting rules are described:
>>> 
>>>   https://www.apache.org/foundation/voting.html
>>> 
>>> A vote for accepting a new Apache Incubator podling is a majority vote
>> for which
>>> only Incubator PMC member votes are binding.
>>> 
>>> This vote will run for at least 72 hours. Please VOTE as follows
>>> [] +1 Accept Pulsar into the Apache Incubator
>>> [] +0 Abstain.
>>> [] -1 Do not accept Pulsar into the Apache Incubator because ...
>>> 
>>> The proposal is listed below, but you can also access it on the wiki:
>>> 
>>>   https://wiki.apache.org/incubator/PulsarProposal
>>> 
>>> -Bryan
>>> 
>>> 
>>> = Pulsar Proposal =
>>> 
>>> == Abstract ==
>>> 
>>> 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.
>>> 
>>> == Proposal ==
>>> 
>>> Pub-sub messaging is a very common design pattern that is increasingly
>> found
>>> in distributed systems powering Internet applications. These applications
>>> provide real-time services, and need publish-latencies of 5ms on average
>> and
>>> no more than 15ms at the 99th percentile. At Internet scale, these
>>> applications require a messaging system with ordering, strong
>> durability, and
>>> delivery guarantees. In order to handle the “five 9’s” durability
>> requirements
>>> of a production environment, the messages have to be committed on
>> multiple
>>> disks or nodes.
>>> 
>>> Pulsar has been developed at Yahoo to address these specific
>> requirements by
>>> providing a hosted service supporting millions of topics for multiple
>> tenants.
>>> The current incarnation of Pulsar has been open-sourced under Apache
>> license
>>> in September 2016 and it is the direct evolution of systems that were
>>> developed at Yahoo since 2011.
>>> 
>>> We believe there is currently no other system that provides a
>> multi-tenant
>>> hosted messaging platform capable of supporting a huge number of topics
>> while
>>> maintaining strict guarantees for durability, ordering and low latency.
>>> Current solutions would require to run multiple individual clusters with
>>> additional operational work and capacity overhead.
>>> 
>>> Since the open sourcing of Pulsar, the development has been done
>> exclusively
>>> on the public Github repository and two major releases were shipped
>> (1.15 and
>>> 1.16), along with multiple minor ones. Several other companies have
>> expressed
>>> interest in the project and its future direction.
>>> 
>>> == Rationale ==
>>> 
>>> Pulsar is a platform that is built on top of several other Apache
>> projects. In
>>> particular, Apache BookKeeper is used to store the data and Apache
>> ZooKeeper
>>> is used for coordination and metadata storage. Pulsar is also
>> interoperable
>>> out of the box with Apache Storm, to provide an easy to use stream
>> processing
>>> solution.
>>> 
>>> We want to establish a community outside the scope of initial core
>> developers
>>> at Yahoo and we believe that the Apache Foundation is a great fit and
>> long-
>>> term home for Pulsar, as it provides an established process for
>> community-
>>> driven development and decision making by consensus. This is exactly the
>> model
>>> we want to adopt for future Pulsar development.
>>> 
>>> == Initial Goals ==
>>> 
>>> The initial goals will be to move the existing codebase to Apache and
>>> integrate with the Apache development process. Furthermore, we plan for
>>> incremental development, and releases along with the Apache guidelines.
>>> 
>>> == Current Status ==
>>> 
>>> Pulsar has been in service at large scale for more than 2 years at
>> Yahoo. In
>>> this time around 60 different applications were integrated with Pulsar.
>> Other
>>> companies are evaluating it as well and have been contributing code to
>> the
>>> project.
>>> 
>>> === Meritocracy ===
>>> 
>>> We value meritocracy and we understand that it is the basis to form an
>> open
>>> community that encourages multiple companies and individuals to
>> contribute and
>>> get invested in the project future. We will encourage and monitor
>>> participation and make sure to extend privileges and responsibilities to
>> all
>>> contributors.
>>> 
>>> === Community ===
>>> 
>>> We have validated, through the interest demonstrated by Pulsar users at
>> Yahoo,
>>> that a reliable hosted pub-sub messaging platform represent a very
>> important
>>> building 

Re: [VOTE] Pulsar into the Apache Incubator

[Jia Zhai]

+1 (non-binding)

On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz  wrote:

> +1 (binding)
>
> -Taylor
>
> > On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> >
> > Hi All,
> >
> > As the champion for Pulsar, I would like to start a VOTE to bring the
> > project in as Apache incubator podling.
> >
> > The ASF voting rules are described:
> >
> >https://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> for which
> > only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [] +1 Accept Pulsar into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept Pulsar into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >
> >https://wiki.apache.org/incubator/PulsarProposal
> >
> > -Bryan
> >
> >
> > = Pulsar Proposal =
> >
> > == Abstract ==
> >
> > 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.
> >
> > == Proposal ==
> >
> > Pub-sub messaging is a very common design pattern that is increasingly
> found
> > in distributed systems powering Internet applications. These applications
> > provide real-time services, and need publish-latencies of 5ms on average
> and
> > no more than 15ms at the 99th percentile. At Internet scale, these
> > applications require a messaging system with ordering, strong
> durability, and
> > delivery guarantees. In order to handle the “five 9’s” durability
> requirements
> > of a production environment, the messages have to be committed on
> multiple
> > disks or nodes.
> >
> > Pulsar has been developed at Yahoo to address these specific
> requirements by
> > providing a hosted service supporting millions of topics for multiple
> tenants.
> > The current incarnation of Pulsar has been open-sourced under Apache
> license
> > in September 2016 and it is the direct evolution of systems that were
> > developed at Yahoo since 2011.
> >
> > We believe there is currently no other system that provides a
> multi-tenant
> > hosted messaging platform capable of supporting a huge number of topics
> while
> > maintaining strict guarantees for durability, ordering and low latency.
> > Current solutions would require to run multiple individual clusters with
> > additional operational work and capacity overhead.
> >
> > Since the open sourcing of Pulsar, the development has been done
> exclusively
> > on the public Github repository and two major releases were shipped
> (1.15 and
> > 1.16), along with multiple minor ones. Several other companies have
> expressed
> > interest in the project and its future direction.
> >
> > == Rationale ==
> >
> > Pulsar is a platform that is built on top of several other Apache
> projects. In
> > particular, Apache BookKeeper is used to store the data and Apache
> ZooKeeper
> > is used for coordination and metadata storage. Pulsar is also
> interoperable
> > out of the box with Apache Storm, to provide an easy to use stream
> processing
> > solution.
> >
> > We want to establish a community outside the scope of initial core
> developers
> > at Yahoo and we believe that the Apache Foundation is a great fit and
> long-
> > term home for Pulsar, as it provides an established process for
> community-
> > driven development and decision making by consensus. This is exactly the
> model
> > we want to adopt for future Pulsar development.
> >
> > == Initial Goals ==
> >
> > The initial goals will be to move the existing codebase to Apache and
> > integrate with the Apache development process. Furthermore, we plan for
> > incremental development, and releases along with the Apache guidelines.
> >
> > == Current Status ==
> >
> > Pulsar has been in service at large scale for more than 2 years at
> Yahoo. In
> > this time around 60 different applications were integrated with Pulsar.
> Other
> > companies are evaluating it as well and have been contributing code to
> the
> > project.
> >
> > === Meritocracy ===
> >
> > We value meritocracy and we understand that it is the basis to form an
> open
> > community that encourages multiple companies and individuals to
> contribute and
> > get invested in the project future. We will encourage and monitor
> > participation and make sure to extend privileges and responsibilities to
> all
> > contributors.
> >
> > === Community ===
> >
> > We have validated, through the interest demonstrated by Pulsar users at
> Yahoo,
> > that a reliable hosted pub-sub messaging platform represent a very
> important
> > building block for web-scale distributed applications. We believe that
> many
> > companies can benefit by applying the same model and that bringing
> Pulsar to
> > 

Re: [VOTE] Pulsar into the Apache Incubator

[P. Taylor Goetz]

+1 (binding)

-Taylor

> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> 
> Hi All,
> 
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
> 
> The ASF voting rules are described:
> 
>https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which 
> only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
>https://wiki.apache.org/incubator/PulsarProposal
> 
> -Bryan
> 
> 
> = Pulsar Proposal =
> 
> == Abstract ==
> 
> 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.
> 
> == Proposal ==
> 
> Pub-sub messaging is a very common design pattern that is increasingly found
> in distributed systems powering Internet applications. These applications
> provide real-time services, and need publish-latencies of 5ms on average and
> no more than 15ms at the 99th percentile. At Internet scale, these
> applications require a messaging system with ordering, strong durability, and
> delivery guarantees. In order to handle the “five 9’s” durability requirements
> of a production environment, the messages have to be committed on multiple
> disks or nodes.
> 
> Pulsar has been developed at Yahoo to address these specific requirements by
> providing a hosted service supporting millions of topics for multiple tenants.
> The current incarnation of Pulsar has been open-sourced under Apache license
> in September 2016 and it is the direct evolution of systems that were
> developed at Yahoo since 2011.
> 
> We believe there is currently no other system that provides a multi-tenant
> hosted messaging platform capable of supporting a huge number of topics while
> maintaining strict guarantees for durability, ordering and low latency.
> Current solutions would require to run multiple individual clusters with
> additional operational work and capacity overhead.
> 
> Since the open sourcing of Pulsar, the development has been done exclusively
> on the public Github repository and two major releases were shipped (1.15 and
> 1.16), along with multiple minor ones. Several other companies have expressed
> interest in the project and its future direction.
> 
> == Rationale ==
> 
> Pulsar is a platform that is built on top of several other Apache projects. In
> particular, Apache BookKeeper is used to store the data and Apache ZooKeeper
> is used for coordination and metadata storage. Pulsar is also interoperable
> out of the box with Apache Storm, to provide an easy to use stream processing
> solution.
> 
> We want to establish a community outside the scope of initial core developers
> at Yahoo and we believe that the Apache Foundation is a great fit and long-
> term home for Pulsar, as it provides an established process for community-
> driven development and decision making by consensus. This is exactly the model
> we want to adopt for future Pulsar development.
> 
> == Initial Goals ==
> 
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Furthermore, we plan for
> incremental development, and releases along with the Apache guidelines.
> 
> == Current Status ==
> 
> Pulsar has been in service at large scale for more than 2 years at Yahoo. In
> this time around 60 different applications were integrated with Pulsar. Other
> companies are evaluating it as well and have been contributing code to the
> project.
> 
> === Meritocracy ===
> 
> We value meritocracy and we understand that it is the basis to form an open
> community that encourages multiple companies and individuals to contribute and
> get invested in the project future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to all
> contributors.
> 
> === Community ===
> 
> We have validated, through the interest demonstrated by Pulsar users at Yahoo,
> that a reliable hosted pub-sub messaging platform represent a very important
> building block for web-scale distributed applications. We believe that many
> companies can benefit by applying the same model and that bringing Pulsar to
> Apache will get the community to grow stronger.
> 
> === Core Developers ===
> 
> Pulsar has been initially developed at Yahoo and received significant
> contributions from Yahoo Japan. After having open-sourced the project there
> have been contribution from developers from several external companies.
> 
> === Alignment ===
> 
> Pulsar builds 

Re: [VOTE] Pulsar into the Apache Incubator

[Phil Sorber]

+1 (binding)

On Wed, May 17, 2017 at 8:21 AM Jim Jagielski  wrote:

> Make it so! +1! (binding)
>
> > On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> >
> > Hi All,
> >
> > As the champion for Pulsar, I would like to start a VOTE to bring the
> > project in as Apache incubator podling.
> >
> > The ASF voting rules are described:
> >
> >   https://www.apache.org/foundation/voting.html
> >
> > A vote for accepting a new Apache Incubator podling is a majority vote
> for which
> > only Incubator PMC member votes are binding.
> >
> > This vote will run for at least 72 hours. Please VOTE as follows
> > [] +1 Accept Pulsar into the Apache Incubator
> > [] +0 Abstain.
> > [] -1 Do not accept Pulsar into the Apache Incubator because ...
> >
> > The proposal is listed below, but you can also access it on the wiki:
> >
> >   https://wiki.apache.org/incubator/PulsarProposal
> >
> > -Bryan
> >
> >
> > = Pulsar Proposal =
> >
> > == Abstract ==
> >
> > 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.
> >
> > == Proposal ==
> >
> > Pub-sub messaging is a very common design pattern that is increasingly
> found
> > in distributed systems powering Internet applications. These applications
> > provide real-time services, and need publish-latencies of 5ms on average
> and
> > no more than 15ms at the 99th percentile. At Internet scale, these
> > applications require a messaging system with ordering, strong
> durability, and
> > delivery guarantees. In order to handle the “five 9’s” durability
> requirements
> > of a production environment, the messages have to be committed on
> multiple
> > disks or nodes.
> >
> > Pulsar has been developed at Yahoo to address these specific
> requirements by
> > providing a hosted service supporting millions of topics for multiple
> tenants.
> > The current incarnation of Pulsar has been open-sourced under Apache
> license
> > in September 2016 and it is the direct evolution of systems that were
> > developed at Yahoo since 2011.
> >
> > We believe there is currently no other system that provides a
> multi-tenant
> > hosted messaging platform capable of supporting a huge number of topics
> while
> > maintaining strict guarantees for durability, ordering and low latency.
> > Current solutions would require to run multiple individual clusters with
> > additional operational work and capacity overhead.
> >
> > Since the open sourcing of Pulsar, the development has been done
> exclusively
> > on the public Github repository and two major releases were shipped
> (1.15 and
> > 1.16), along with multiple minor ones. Several other companies have
> expressed
> > interest in the project and its future direction.
> >
> > == Rationale ==
> >
> > Pulsar is a platform that is built on top of several other Apache
> projects. In
> > particular, Apache BookKeeper is used to store the data and Apache
> ZooKeeper
> > is used for coordination and metadata storage. Pulsar is also
> interoperable
> > out of the box with Apache Storm, to provide an easy to use stream
> processing
> > solution.
> >
> > We want to establish a community outside the scope of initial core
> developers
> > at Yahoo and we believe that the Apache Foundation is a great fit and
> long-
> > term home for Pulsar, as it provides an established process for
> community-
> > driven development and decision making by consensus. This is exactly the
> model
> > we want to adopt for future Pulsar development.
> >
> > == Initial Goals ==
> >
> > The initial goals will be to move the existing codebase to Apache and
> > integrate with the Apache development process. Furthermore, we plan for
> > incremental development, and releases along with the Apache guidelines.
> >
> > == Current Status ==
> >
> > Pulsar has been in service at large scale for more than 2 years at
> Yahoo. In
> > this time around 60 different applications were integrated with Pulsar.
> Other
> > companies are evaluating it as well and have been contributing code to
> the
> > project.
> >
> > === Meritocracy ===
> >
> > We value meritocracy and we understand that it is the basis to form an
> open
> > community that encourages multiple companies and individuals to
> contribute and
> > get invested in the project future. We will encourage and monitor
> > participation and make sure to extend privileges and responsibilities to
> all
> > contributors.
> >
> > === Community ===
> >
> > We have validated, through the interest demonstrated by Pulsar users at
> Yahoo,
> > that a reliable hosted pub-sub messaging platform represent a very
> important
> > building block for web-scale distributed applications. We believe that
> many
> > companies can benefit by applying the same model and that bringing
> Pulsar to
> > 

Re: [VOTE] Pulsar into the Apache Incubator

[Jim Jagielski]

Make it so! +1! (binding)

> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> 
> Hi All,
> 
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
> 
> The ASF voting rules are described:
> 
>   https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which 
> only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
>   https://wiki.apache.org/incubator/PulsarProposal
> 
> -Bryan
> 
> 
> = Pulsar Proposal =
> 
> == Abstract ==
> 
> 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.
> 
> == Proposal ==
> 
> Pub-sub messaging is a very common design pattern that is increasingly found
> in distributed systems powering Internet applications. These applications
> provide real-time services, and need publish-latencies of 5ms on average and
> no more than 15ms at the 99th percentile. At Internet scale, these
> applications require a messaging system with ordering, strong durability, and
> delivery guarantees. In order to handle the “five 9’s” durability requirements
> of a production environment, the messages have to be committed on multiple
> disks or nodes.
> 
> Pulsar has been developed at Yahoo to address these specific requirements by
> providing a hosted service supporting millions of topics for multiple tenants.
> The current incarnation of Pulsar has been open-sourced under Apache license
> in September 2016 and it is the direct evolution of systems that were
> developed at Yahoo since 2011.
> 
> We believe there is currently no other system that provides a multi-tenant
> hosted messaging platform capable of supporting a huge number of topics while
> maintaining strict guarantees for durability, ordering and low latency.
> Current solutions would require to run multiple individual clusters with
> additional operational work and capacity overhead.
> 
> Since the open sourcing of Pulsar, the development has been done exclusively
> on the public Github repository and two major releases were shipped (1.15 and
> 1.16), along with multiple minor ones. Several other companies have expressed
> interest in the project and its future direction.
> 
> == Rationale ==
> 
> Pulsar is a platform that is built on top of several other Apache projects. In
> particular, Apache BookKeeper is used to store the data and Apache ZooKeeper
> is used for coordination and metadata storage. Pulsar is also interoperable
> out of the box with Apache Storm, to provide an easy to use stream processing
> solution.
> 
> We want to establish a community outside the scope of initial core developers
> at Yahoo and we believe that the Apache Foundation is a great fit and long-
> term home for Pulsar, as it provides an established process for community-
> driven development and decision making by consensus. This is exactly the model
> we want to adopt for future Pulsar development.
> 
> == Initial Goals ==
> 
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Furthermore, we plan for
> incremental development, and releases along with the Apache guidelines.
> 
> == Current Status ==
> 
> Pulsar has been in service at large scale for more than 2 years at Yahoo. In
> this time around 60 different applications were integrated with Pulsar. Other
> companies are evaluating it as well and have been contributing code to the
> project.
> 
> === Meritocracy ===
> 
> We value meritocracy and we understand that it is the basis to form an open
> community that encourages multiple companies and individuals to contribute and
> get invested in the project future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to all
> contributors.
> 
> === Community ===
> 
> We have validated, through the interest demonstrated by Pulsar users at Yahoo,
> that a reliable hosted pub-sub messaging platform represent a very important
> building block for web-scale distributed applications. We believe that many
> companies can benefit by applying the same model and that bringing Pulsar to
> Apache will get the community to grow stronger.
> 
> === Core Developers ===
> 
> Pulsar has been initially developed at Yahoo and received significant
> contributions from Yahoo Japan. After having open-sourced the project there
> have been contribution from developers from several external companies.
> 
> === Alignment ===
> 
> 

Re: [VOTE] Pulsar into the Apache Incubator

[Jean-Baptiste Onofré]

+1 (binding)

Regards
JB

On 05/17/2017 04:39 AM, Bryan Call wrote:

Hi All,

As the champion for Pulsar, I would like to start a VOTE to bring the
project in as Apache incubator podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote for which
only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept Pulsar into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Pulsar into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/PulsarProposal

-Bryan


= Pulsar Proposal =

== Abstract ==

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.

== Proposal ==

Pub-sub messaging is a very common design pattern that is increasingly found
in distributed systems powering Internet applications. These applications
provide real-time services, and need publish-latencies of 5ms on average and
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong durability, and
delivery guarantees. In order to handle the “five 9’s” durability requirements
of a production environment, the messages have to be committed on multiple
disks or nodes.

Pulsar has been developed at Yahoo to address these specific requirements by
providing a hosted service supporting millions of topics for multiple tenants.
The current incarnation of Pulsar has been open-sourced under Apache license
in September 2016 and it is the direct evolution of systems that were
developed at Yahoo since 2011.

We believe there is currently no other system that provides a multi-tenant
hosted messaging platform capable of supporting a huge number of topics while
maintaining strict guarantees for durability, ordering and low latency.
Current solutions would require to run multiple individual clusters with
additional operational work and capacity overhead.

Since the open sourcing of Pulsar, the development has been done exclusively
on the public Github repository and two major releases were shipped (1.15 and
1.16), along with multiple minor ones. Several other companies have expressed
interest in the project and its future direction.

== Rationale ==

Pulsar is a platform that is built on top of several other Apache projects. In
particular, Apache BookKeeper is used to store the data and Apache ZooKeeper
is used for coordination and metadata storage. Pulsar is also interoperable
out of the box with Apache Storm, to provide an easy to use stream processing
solution.

We want to establish a community outside the scope of initial core developers
at Yahoo and we believe that the Apache Foundation is a great fit and long-
term home for Pulsar, as it provides an established process for community-
driven development and decision making by consensus. This is exactly the model
we want to adopt for future Pulsar development.

== Initial Goals ==

The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. Furthermore, we plan for
incremental development, and releases along with the Apache guidelines.

== Current Status ==

Pulsar has been in service at large scale for more than 2 years at Yahoo. In
this time around 60 different applications were integrated with Pulsar. Other
companies are evaluating it as well and have been contributing code to the
project.

=== Meritocracy ===

We value meritocracy and we understand that it is the basis to form an open
community that encourages multiple companies and individuals to contribute and
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities to all
contributors.

=== Community ===

We have validated, through the interest demonstrated by Pulsar users at Yahoo,
that a reliable hosted pub-sub messaging platform represent a very important
building block for web-scale distributed applications. We believe that many
companies can benefit by applying the same model and that bringing Pulsar to
Apache will get the community to grow stronger.

=== Core Developers ===

Pulsar has been initially developed at Yahoo and received significant
contributions from Yahoo Japan. After having open-sourced the project there
have been contribution from developers from several external companies.

=== Alignment ===

Pulsar builds upon other Apache projects such as ZooKeeper and BookKeeper,
along with a number of other Apache libraries. We have already integrated with
Storm and we envision to integrate with multiple other systems in the
streaming and big data space.

== 

Re: [VOTE] Pulsar into the Apache Incubator

[Dave Fisher]

+1 (binding)

Regards,
Dave

Sent from my iPhone

> On May 16, 2017, at 10:39 PM, Bryan Call  wrote:
> 
> Hi All,
> 
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
> 
> The ASF voting rules are described:
> 
>https://www.apache.org/foundation/voting.html
> 
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which 
> only Incubator PMC member votes are binding.
> 
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
> 
> The proposal is listed below, but you can also access it on the wiki:
> 
>https://wiki.apache.org/incubator/PulsarProposal
> 
> -Bryan
> 
> 
> = Pulsar Proposal =
> 
> == Abstract ==
> 
> 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.
> 
> == Proposal ==
> 
> Pub-sub messaging is a very common design pattern that is increasingly found
> in distributed systems powering Internet applications. These


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

Re: [VOTE] Pulsar into the Apache Incubator

[Raphael Bircher]

+1 (binding)

Am .05.2017, 04:39 Uhr, schrieb Bryan Call :


Hi All,

As the champion for Pulsar, I would like to start a VOTE to bring the
project in as Apache incubator podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote  
for which

only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept Pulsar into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Pulsar into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/PulsarProposal

-Bryan


= Pulsar Proposal =

== Abstract ==

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.

== Proposal ==

Pub-sub messaging is a very common design pattern that is increasingly  
found

in distributed systems powering Internet applications. These applications
provide real-time services, and need publish-latencies of 5ms on average  
and

no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong  
durability, and
delivery guarantees. In order to handle the “five 9’s” durability  
requirements
of a production environment, the messages have to be committed on  
multiple

disks or nodes.

Pulsar has been developed at Yahoo to address these specific  
requirements by
providing a hosted service supporting millions of topics for multiple  
tenants.
The current incarnation of Pulsar has been open-sourced under Apache  
license

in September 2016 and it is the direct evolution of systems that were
developed at Yahoo since 2011.

We believe there is currently no other system that provides a  
multi-tenant
hosted messaging platform capable of supporting a huge number of topics  
while

maintaining strict guarantees for durability, ordering and low latency.
Current solutions would require to run multiple individual clusters with
additional operational work and capacity overhead.

Since the open sourcing of Pulsar, the development has been done  
exclusively
on the public Github repository and two major releases were shipped  
(1.15 and
1.16), along with multiple minor ones. Several other companies have  
expressed

interest in the project and its future direction.

== Rationale ==

Pulsar is a platform that is built on top of several other Apache  
projects. In
particular, Apache BookKeeper is used to store the data and Apache  
ZooKeeper
is used for coordination and metadata storage. Pulsar is also  
interoperable
out of the box with Apache Storm, to provide an easy to use stream  
processing

solution.

We want to establish a community outside the scope of initial core  
developers
at Yahoo and we believe that the Apache Foundation is a great fit and  
long-
term home for Pulsar, as it provides an established process for  
community-
driven development and decision making by consensus. This is exactly the  
model

we want to adopt for future Pulsar development.

== Initial Goals ==

The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. Furthermore, we plan for
incremental development, and releases along with the Apache guidelines.

== Current Status ==

Pulsar has been in service at large scale for more than 2 years at  
Yahoo. In
this time around 60 different applications were integrated with Pulsar.  
Other
companies are evaluating it as well and have been contributing code to  
the

project.

=== Meritocracy ===

We value meritocracy and we understand that it is the basis to form an  
open
community that encourages multiple companies and individuals to  
contribute and

get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities to  
all

contributors.

=== Community ===

We have validated, through the interest demonstrated by Pulsar users at  
Yahoo,
that a reliable hosted pub-sub messaging platform represent a very  
important
building block for web-scale distributed applications. We believe that  
many
companies can benefit by applying the same model and that bringing  
Pulsar to

Apache will get the community to grow stronger.

=== Core Developers ===

Pulsar has been initially developed at Yahoo and received significant
contributions from Yahoo Japan. After having open-sourced the project  
there

have been contribution from developers from several external companies.

=== Alignment ===

Pulsar builds upon other Apache projects such as ZooKeeper and  
BookKeeper,
along with a number of other Apache libraries. We have already  
integrated with

Storm 

Re: [VOTE] Pulsar into the Apache Incubator

[Sijie Guo]

+1 (non-binding)

Great to see Pulsar joining the ASF and more and more projects are built
over Apache BookKeeper!

- Sijie

On Tue, May 16, 2017 at 7:39 PM, Bryan Call  wrote:

> Hi All,
>
> As the champion for Pulsar, I would like to start a VOTE to bring the
> project in as Apache incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for
> which
> only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Pulsar into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Pulsar into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/PulsarProposal
>
> -Bryan
>
>
> = Pulsar Proposal =
>
> == Abstract ==
>
> 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.
>
> == Proposal ==
>
> Pub-sub messaging is a very common design pattern that is increasingly
> found
> in distributed systems powering Internet applications. These applications
> provide real-time services, and need publish-latencies of 5ms on average
> and
> no more than 15ms at the 99th percentile. At Internet scale, these
> applications require a messaging system with ordering, strong durability,
> and
> delivery guarantees. In order to handle the “five 9’s” durability
> requirements
> of a production environment, the messages have to be committed on multiple
> disks or nodes.
>
> Pulsar has been developed at Yahoo to address these specific requirements
> by
> providing a hosted service supporting millions of topics for multiple
> tenants.
> The current incarnation of Pulsar has been open-sourced under Apache
> license
> in September 2016 and it is the direct evolution of systems that were
> developed at Yahoo since 2011.
>
> We believe there is currently no other system that provides a multi-tenant
> hosted messaging platform capable of supporting a huge number of topics
> while
> maintaining strict guarantees for durability, ordering and low latency.
> Current solutions would require to run multiple individual clusters with
> additional operational work and capacity overhead.
>
> Since the open sourcing of Pulsar, the development has been done
> exclusively
> on the public Github repository and two major releases were shipped (1.15
> and
> 1.16), along with multiple minor ones. Several other companies have
> expressed
> interest in the project and its future direction.
>
> == Rationale ==
>
> Pulsar is a platform that is built on top of several other Apache
> projects. In
> particular, Apache BookKeeper is used to store the data and Apache
> ZooKeeper
> is used for coordination and metadata storage. Pulsar is also interoperable
> out of the box with Apache Storm, to provide an easy to use stream
> processing
> solution.
>
> We want to establish a community outside the scope of initial core
> developers
> at Yahoo and we believe that the Apache Foundation is a great fit and long-
> term home for Pulsar, as it provides an established process for community-
> driven development and decision making by consensus. This is exactly the
> model
> we want to adopt for future Pulsar development.
>
> == Initial Goals ==
>
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Furthermore, we plan for
> incremental development, and releases along with the Apache guidelines.
>
> == Current Status ==
>
> Pulsar has been in service at large scale for more than 2 years at Yahoo.
> In
> this time around 60 different applications were integrated with Pulsar.
> Other
> companies are evaluating it as well and have been contributing code to the
> project.
>
> === Meritocracy ===
>
> We value meritocracy and we understand that it is the basis to form an open
> community that encourages multiple companies and individuals to contribute
> and
> get invested in the project future. We will encourage and monitor
> participation and make sure to extend privileges and responsibilities to
> all
> contributors.
>
> === Community ===
>
> We have validated, through the interest demonstrated by Pulsar users at
> Yahoo,
> that a reliable hosted pub-sub messaging platform represent a very
> important
> building block for web-scale distributed applications. We believe that many
> companies can benefit by applying the same model and that bringing Pulsar
> to
> Apache will get the community to grow stronger.
>
> === Core Developers ===
>
> Pulsar has been initially developed at Yahoo and received significant
> contributions from Yahoo Japan. After having open-sourced the 

[VOTE] Pulsar into the Apache Incubator

[Bryan Call]

Hi All,

As the champion for Pulsar, I would like to start a VOTE to bring the
project in as Apache incubator podling.

The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote for 
which 
only Incubator PMC member votes are binding.

This vote will run for at least 72 hours. Please VOTE as follows
[] +1 Accept Pulsar into the Apache Incubator
[] +0 Abstain.
[] -1 Do not accept Pulsar into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki:

https://wiki.apache.org/incubator/PulsarProposal

-Bryan


= Pulsar Proposal =

== Abstract ==

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.

== Proposal ==

Pub-sub messaging is a very common design pattern that is increasingly found
in distributed systems powering Internet applications. These applications
provide real-time services, and need publish-latencies of 5ms on average and
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong durability, and
delivery guarantees. In order to handle the “five 9’s” durability requirements
of a production environment, the messages have to be committed on multiple
disks or nodes.

Pulsar has been developed at Yahoo to address these specific requirements by
providing a hosted service supporting millions of topics for multiple tenants.
The current incarnation of Pulsar has been open-sourced under Apache license
in September 2016 and it is the direct evolution of systems that were
developed at Yahoo since 2011.

We believe there is currently no other system that provides a multi-tenant
hosted messaging platform capable of supporting a huge number of topics while
maintaining strict guarantees for durability, ordering and low latency.
Current solutions would require to run multiple individual clusters with
additional operational work and capacity overhead.

Since the open sourcing of Pulsar, the development has been done exclusively
on the public Github repository and two major releases were shipped (1.15 and
1.16), along with multiple minor ones. Several other companies have expressed
interest in the project and its future direction.

== Rationale ==

Pulsar is a platform that is built on top of several other Apache projects. In
particular, Apache BookKeeper is used to store the data and Apache ZooKeeper
is used for coordination and metadata storage. Pulsar is also interoperable
out of the box with Apache Storm, to provide an easy to use stream processing
solution.

We want to establish a community outside the scope of initial core developers
at Yahoo and we believe that the Apache Foundation is a great fit and long-
term home for Pulsar, as it provides an established process for community-
driven development and decision making by consensus. This is exactly the model
we want to adopt for future Pulsar development.

== Initial Goals ==

The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. Furthermore, we plan for
incremental development, and releases along with the Apache guidelines.

== Current Status ==

Pulsar has been in service at large scale for more than 2 years at Yahoo. In
this time around 60 different applications were integrated with Pulsar. Other
companies are evaluating it as well and have been contributing code to the
project.

=== Meritocracy ===

We value meritocracy and we understand that it is the basis to form an open
community that encourages multiple companies and individuals to contribute and
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities to all
contributors.

=== Community ===

We have validated, through the interest demonstrated by Pulsar users at Yahoo,
that a reliable hosted pub-sub messaging platform represent a very important
building block for web-scale distributed applications. We believe that many
companies can benefit by applying the same model and that bringing Pulsar to
Apache will get the community to grow stronger.

=== Core Developers ===

Pulsar has been initially developed at Yahoo and received significant
contributions from Yahoo Japan. After having open-sourced the project there
have been contribution from developers from several external companies.

=== Alignment ===

Pulsar builds upon other Apache projects such as ZooKeeper and BookKeeper,
along with a number of other Apache libraries. We have already integrated with
Storm and we envision to integrate with multiple other systems in the
streaming and big data space.

== Known Risks ==

=== Orphaned Products ===

Yahoo has been doing most