Discussion:
[VOTE] Pulsar into the Apache Incubator
(too old to reply)
Bryan Call
2017-05-17 02:39:01 UTC
Permalink
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 of the development and, given that many internal
platforms depends on Pulsar, it is heavily invested in the long term success
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache community.

=== Inexperience with Open Source ===

Many Pulsar contributors are already familiar with the open source process and
several of them are committers on other Apache projects. We will be actively
working with experienced Apache community members to improve our project.

=== Homogenous Developers ===

The initial committers are employed by large companies including Yahoo, Yahoo!
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the project.

=== Reliance on Salaried Developers ===

It is expected that Pulsar development will occur on both salaried time and on
volunteer time, after hours. The majority of initial committers are paid by
their employer to contribute to this project. However, they are all passionate
about the project, and we are confident that the project will continue even if
no salaried developers contribute to the project.

=== Relationships with Other Apache Products ===

As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache communities.

=== An Excessive Fascination with the Apache Brand ===

We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in 2016. This
proposal is not for the purpose of generating publicity. Rather, we want to
make sure to create a very inclusive and meritocratic community, outside the
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and contributors
understand the implication of making it an Apache project.

== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar,
Pub-sub Messaging at Scale]]

== Initial Source ==

The Pulsar codebase is currently hosted on Github:
https://github.com/yahoo/pulsar. This is the exact codebase that we would
migrate to the Apache Software Foundation.

== Source and Intellectual Property Submission Plan ==

The Pulsar source code in Github is currently licensed under Apache License
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar fulfills
and passes the conditions for being an Incubator project in the ASF, Yahoo
will transition the source code ownership to the Apache Software Foundation
via the Software Grant Agreement.

== External Dependencies ==

To the best of our knowledge, all of Pulsar dependencies are distributed under
Apache compatible licenses.

=== External dependencies licensed under Apache License 2.0: ===

Athenz, JCommander, HPPC - High Performance Primitive Collections for Java,
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty, DataSketches,
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty, SnakeYAML

=== ASF Projects: ===

BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)

=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)

== Required Resources ==

=== Mailing lists ===
* ***@pulsar.incubator.apache.org
* ***@pulsar.incubator.apache.org
* ***@pulsar.incubator.apache.org
* ***@pulsar.incubator.apache.org (with moderated subscriptions)

=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar

=== Issue Tracking ===
* JIRA Pulsar (PULSAR)

== Initial Committers ==
* Matteo Merli - <***@apache.org>
* Joe Francis - <***@yahoo-inc.com>
* Rajan Dhabalia - <***@yahoo-inc.com>
* Sahaya Andrews Albert - <***@yahoo-inc.com>
* Maurice Barnum - <***@yahoo-inc.com>
* Ludwig Pummer - <***@yahoo-inc.com>
* Jai Asher - <***@yahoo-inc.com>
* Siddharth Boobna - <***@apache.org>
* Nozomi Kurihara - <***@yahoo-corp.jp>
* Yuki Shiga - <***@yahoo-corp.jp>
* Masakazu Kitajo - <***@apache.org>
* Sebastián Schepens - <***@mercadolibre.com>
* Brad McMillen - <***@yahoo-inc.com>
* Bobbey Reese - <***@yahoo-inc.com>
* Masahiro Sakamoto <***@yahoo-corp.jp>
* Hiroyuki Sakai <***@yahoo-corp.jp>

== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo

== Sponsors ==

=== Champion ===
* Bryan Call

=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu

=== Sponsoring Entity ===
* The Apache Incubator PMC



---------------------------------------------------------------------
To unsubscribe, e-mail: general-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
Sijie Guo
2017-05-17 04:58:12 UTC
Permalink
+1 (non-binding)

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

- Sijie
Post by 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.
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 ...
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 of the development and, given that many internal
platforms depends on Pulsar, it is heavily invested in the long term success
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache community.
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source process and
several of them are committers on other Apache projects. We will be actively
working with experienced Apache community members to improve our project.
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo, Yahoo!
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the project.
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time and on
volunteer time, after hours. The majority of initial committers are paid by
their employer to contribute to this project. However, they are all passionate
about the project, and we are confident that the project will continue even if
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache communities.
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in 2016. This
proposal is not for the purpose of generating publicity. Rather, we want to
make sure to create a very inclusive and meritocratic community, outside the
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and contributors
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar,
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we would
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache License
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar fulfills
and passes the conditions for being an Incubator project in the ASF, Yahoo
will transition the source code ownership to the Apache Software Foundation
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are distributed under
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for Java,
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty, DataSketches,
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty, SnakeYAML
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
Raphael Bircher
2017-05-17 08:43:48 UTC
Permalink
+1 (binding)
Post by 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.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority vote=
=
Post by Bryan Call
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 ...
https://wiki.apache.org/incubator/PulsarProposal
-Bryan
=3D Pulsar Proposal =3D
=3D=3D Abstract =3D=3D
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.
=3D=3D Proposal =3D=3D
Pub-sub messaging is a very common design pattern that is increasingly=
=
Post by Bryan Call
found
in distributed systems powering Internet applications. These applicati=
ons
Post by Bryan Call
provide real-time services, and need publish-latencies of 5ms on avera=
ge =
Post by Bryan Call
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 =E2=80=9Cfive 9=E2=80=99s=E2=
=80=9D durability =
Post by Bryan Call
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 =
=
Post by Bryan Call
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 topic=
s =
Post by Bryan Call
while
maintaining strict guarantees for durability, ordering and low latency=
.
Post by Bryan Call
Current solutions would require to run multiple individual clusters wi=
th
Post by Bryan Call
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.
=3D=3D Rationale =3D=3D
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 =
=
Post by Bryan Call
long-
term home for Pulsar, as it provides an established process for =
community-
driven development and decision making by consensus. This is exactly t=
he =
Post by Bryan Call
model
we want to adopt for future Pulsar development.
=3D=3D Initial Goals =3D=3D
The initial goals will be to move the existing codebase to Apache and
integrate with the Apache development process. Furthermore, we plan fo=
r
Post by Bryan Call
incremental development, and releases along with the Apache guidelines=
.
Post by Bryan Call
=3D=3D Current Status =3D=3D
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=
. =
Post by Bryan Call
Other
companies are evaluating it as well and have been contributing code to=
=
Post by Bryan Call
the
project.
=3D=3D=3D Meritocracy =3D=3D=3D
We value meritocracy and we understand that it is the basis to form an=
=
Post by Bryan Call
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 =
Post by Bryan Call
all
contributors.
=3D=3D=3D Community =3D=3D=3D
We have validated, through the interest demonstrated by Pulsar users a=
t =
Post by Bryan Call
Yahoo,
that a reliable hosted pub-sub messaging platform represent a very =
important
building block for web-scale distributed applications. We believe that=
=
Post by Bryan Call
many
companies can benefit by applying the same model and that bringing =
Pulsar to
Apache will get the community to grow stronger.
=3D=3D=3D Core Developers =3D=3D=3D
Pulsar has been initially developed at Yahoo and received significant
contributions from Yahoo Japan. After having open-sourced the project =
=
Post by Bryan Call
there
have been contribution from developers from several external companies=
.
Post by Bryan Call
=3D=3D=3D Alignment =3D=3D=3D
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.
=3D=3D Known Risks =3D=3D
=3D=3D=3D Orphaned Products =3D=3D=3D
Yahoo has been doing most of the development and, given that many =
internal
platforms depends on Pulsar, it is heavily invested in the long term =
success
of the the project. Yahoo has a long history participating in open-sou=
rce
Post by Bryan Call
projects, and has been also a long time contributor to the Apache =
community.
=3D=3D=3D Inexperience with Open Source =3D=3D=3D
Many Pulsar contributors are already familiar with the open source =
process and
several of them are committers on other Apache projects. We will be =
actively
working with experienced Apache community members to improve our proje=
ct.
Post by Bryan Call
=3D=3D=3D Homogenous Developers =3D=3D=3D
The initial committers are employed by large companies including Yahoo=
, =
Post by Bryan Call
Yahoo!
Japan, Salesforce and MercadoLibre. We hope to grow the community and =
to
Post by Bryan Call
include additional committers based on their contributions to the =
project.
=3D=3D=3D Reliance on Salaried Developers =3D=3D=3D
It is expected that Pulsar development will occur on both salaried tim=
e =
Post by Bryan Call
and on
volunteer time, after hours. The majority of initial committers are pa=
id =
Post by Bryan Call
by
their employer to contribute to this project. However, they are all =
passionate
about the project, and we are confident that the project will continue=
=
Post by Bryan Call
even if
no salaried developers contribute to the project.
=3D=3D=3D Relationships with Other Apache Products =3D=3D=3D
As mentioned in the Rationale section, Pulsar is closely dependent and=
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing =
to
Post by Bryan Call
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache =
communities.
=3D=3D=3D An Excessive Fascination with the Apache Brand =3D=3D=3D
We are applying to the Incubator process because we think it is the ne=
xt
Post by Bryan Call
logical step for the Pulsar project after open-sourcing the code in =
2016. This
proposal is not for the purpose of generating publicity. Rather, we wa=
nt =
Post by Bryan Call
to
make sure to create a very inclusive and meritocratic community, outsi=
de =
Post by Bryan Call
the
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and =
contributors
understand the implication of making it an Apache project.
=3D=3D Documentation =3D=3D
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar=
,
Post by Bryan Call
Pub-sub Messaging at Scale]]
=3D=3D Initial Source =3D=3D
https://github.com/yahoo/pulsar. This is the exact codebase that we wo=
uld
Post by Bryan Call
migrate to the Apache Software Foundation.
=3D=3D Source and Intellectual Property Submission Plan =3D=3D
The Pulsar source code in Github is currently licensed under Apache =
License
v2.0 and the copyright is assigned to Yahoo. All the contributions fro=
m
Post by Bryan Call
external parties have been received under Apache style CLA. If Pulsar =
=
Post by Bryan Call
fulfills
and passes the conditions for being an Incubator project in the ASF, =
Yahoo
will transition the source code ownership to the Apache Software =
Foundation
via the Software Grant Agreement.
=3D=3D External Dependencies =3D=3D
To the best of our knowledge, all of Pulsar dependencies are distribut=
ed =
Post by Bryan Call
under
Apache compatible licenses.
=3D=3D=3D External dependencies licensed under Apache License 2.0: =3D=
=3D=3D
Post by Bryan Call
Athenz, JCommander, HPPC - High Performance Primitive Collections for =
=
Post by Bryan Call
Java,
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty, =
DataSketches,
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty, =
SnakeYAML
=3D=3D=3D ASF Projects: =3D=3D=3D
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=3D=3D=3D Others: =3D=3D=3D
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
=3D=3D Required Resources =3D=3D
=3D=3D=3D Mailing lists =3D=3D=3D
=3D=3D=3D Git Repository =3D=3D=3D
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=3D=3D=3D Issue Tracking =3D=3D=3D
* JIRA Pulsar (PULSAR)
=3D=3D Initial Committers =3D=3D
=3D=3D Affiliations =3D=3D
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebasti=C3=A1n Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
=3D=3D Sponsors =3D=3D
=3D=3D=3D Champion =3D=3D=3D
* Bryan Call
=3D=3D=3D Nominated Mentors =3D=3D=3D
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=3D=3D=3D Sponsoring Entity =3D=3D=3D
* The Apache Incubator PMC
---------------------------------------------------------------------
-- =

My introduction


---------------------------------------------------------------------
To unsubscribe, e-mail: general-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
Dave Fisher
2017-05-17 10:31:00 UTC
Permalink
+1 (binding)

Regards,
Dave

Sent from my iPhone
Post by 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.
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 ...
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-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
Jean-Baptiste Onofré
2017-05-17 12:27:02 UTC
Permalink
+1 (binding)

Regards
JB
Post by 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.
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 ...
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 of the development and, given that many internal
platforms depends on Pulsar, it is heavily invested in the long term success
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache community.
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source process and
several of them are committers on other Apache projects. We will be actively
working with experienced Apache community members to improve our project.
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo, Yahoo!
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the project.
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time and on
volunteer time, after hours. The majority of initial committers are paid by
their employer to contribute to this project. However, they are all passionate
about the project, and we are confident that the project will continue even if
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache communities.
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in 2016. This
proposal is not for the purpose of generating publicity. Rather, we want to
make sure to create a very inclusive and meritocratic community, outside the
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and contributors
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar,
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we would
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache License
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar fulfills
and passes the conditions for being an Incubator project in the ASF, Yahoo
will transition the source code ownership to the Apache Software Foundation
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are distributed under
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for Java,
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty, DataSketches,
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty, SnakeYAML
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
--
Jean-Baptiste Onofré
***@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
Jim Jagielski
2017-05-17 14:15:54 UTC
Permalink
Make it so! +1! (binding)
Post by 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.
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 ...
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 of the development and, given that many internal
platforms depends on Pulsar, it is heavily invested in the long term success
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache community.
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source process and
several of them are committers on other Apache projects. We will be actively
working with experienced Apache community members to improve our project.
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo, Yahoo!
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the project.
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time and on
volunteer time, after hours. The majority of initial committers are paid by
their employer to contribute to this project. However, they are all passionate
about the project, and we are confident that the project will continue even if
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache communities.
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in 2016. This
proposal is not for the purpose of generating publicity. Rather, we want to
make sure to create a very inclusive and meritocratic community, outside the
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and contributors
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar,
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we would
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache License
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar fulfills
and passes the conditions for being an Incubator project in the ASF, Yahoo
will transition the source code ownership to the Apache Software Foundation
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are distributed under
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for Java,
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty, DataSketches,
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty, SnakeYAML
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: general-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
Phil Sorber
2017-05-17 16:11:01 UTC
Permalink
+1 (binding)
Post by Jim Jagielski
Make it so! +1! (binding)
Post by 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.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority vote
for which
Post by Bryan Call
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 ...
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
Post by Bryan Call
subscribers, and cross-datacenter replication.
== Proposal ==
Pub-sub messaging is a very common design pattern that is increasingly
found
Post by Bryan Call
in distributed systems powering Internet applications. These applications
provide real-time services, and need publish-latencies of 5ms on average
and
Post by Bryan Call
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong
durability, and
Post by Bryan Call
delivery guarantees. In order to handle the “five 9’s” durability
requirements
Post by Bryan Call
of a production environment, the messages have to be committed on
multiple
Post by Bryan Call
disks or nodes.
Pulsar has been developed at Yahoo to address these specific
requirements by
Post by Bryan Call
providing a hosted service supporting millions of topics for multiple
tenants.
Post by Bryan Call
The current incarnation of Pulsar has been open-sourced under Apache
license
Post by Bryan Call
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
Post by Bryan Call
hosted messaging platform capable of supporting a huge number of topics
while
Post by Bryan Call
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
Post by Bryan Call
on the public Github repository and two major releases were shipped
(1.15 and
Post by Bryan Call
1.16), along with multiple minor ones. Several other companies have
expressed
Post by Bryan Call
interest in the project and its future direction.
== Rationale ==
Pulsar is a platform that is built on top of several other Apache
projects. In
Post by Bryan Call
particular, Apache BookKeeper is used to store the data and Apache
ZooKeeper
Post by Bryan Call
is used for coordination and metadata storage. Pulsar is also
interoperable
Post by Bryan Call
out of the box with Apache Storm, to provide an easy to use stream
processing
Post by Bryan Call
solution.
We want to establish a community outside the scope of initial core
developers
Post by Bryan Call
at Yahoo and we believe that the Apache Foundation is a great fit and
long-
Post by Bryan Call
term home for Pulsar, as it provides an established process for
community-
Post by Bryan Call
driven development and decision making by consensus. This is exactly the
model
Post by Bryan Call
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
Post by Bryan Call
this time around 60 different applications were integrated with Pulsar.
Other
Post by Bryan Call
companies are evaluating it as well and have been contributing code to
the
Post by Bryan Call
project.
=== Meritocracy ===
We value meritocracy and we understand that it is the basis to form an
open
Post by Bryan Call
community that encourages multiple companies and individuals to
contribute and
Post by Bryan Call
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities to
all
Post by Bryan Call
contributors.
=== Community ===
We have validated, through the interest demonstrated by Pulsar users at
Yahoo,
Post by Bryan Call
that a reliable hosted pub-sub messaging platform represent a very
important
Post by Bryan Call
building block for web-scale distributed applications. We believe that
many
Post by Bryan Call
companies can benefit by applying the same model and that bringing
Pulsar to
Post by Bryan Call
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
Post by Bryan Call
have been contribution from developers from several external companies.
=== Alignment ===
Pulsar builds upon other Apache projects such as ZooKeeper and
BookKeeper,
Post by Bryan Call
along with a number of other Apache libraries. We have already
integrated with
Post by Bryan Call
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 of the development and, given that many
internal
Post by Bryan Call
platforms depends on Pulsar, it is heavily invested in the long term
success
Post by Bryan Call
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache
community.
Post by Bryan Call
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source
process and
Post by Bryan Call
several of them are committers on other Apache projects. We will be
actively
Post by Bryan Call
working with experienced Apache community members to improve our project.
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo,
Yahoo!
Post by Bryan Call
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the
project.
Post by Bryan Call
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time
and on
Post by Bryan Call
volunteer time, after hours. The majority of initial committers are paid
by
Post by Bryan Call
their employer to contribute to this project. However, they are all
passionate
Post by Bryan Call
about the project, and we are confident that the project will continue
even if
Post by Bryan Call
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache
communities.
Post by Bryan Call
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in
2016. This
Post by Bryan Call
proposal is not for the purpose of generating publicity. Rather, we want
to
Post by Bryan Call
make sure to create a very inclusive and meritocratic community, outside
the
Post by Bryan Call
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and
contributors
Post by Bryan Call
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing
Pulsar,
Post by Bryan Call
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we
would
Post by Bryan Call
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache
License
Post by Bryan Call
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar
fulfills
Post by Bryan Call
and passes the conditions for being an Incubator project in the ASF,
Yahoo
Post by Bryan Call
will transition the source code ownership to the Apache Software
Foundation
Post by Bryan Call
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are distributed
under
Post by Bryan Call
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for
Java,
Post by Bryan Call
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty,
DataSketches,
Post by Bryan Call
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty,
SnakeYAML
Post by Bryan Call
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
---------------------------------------------------------------------
P. Taylor Goetz
2017-05-17 17:11:58 UTC
Permalink
+1 (binding)

-Taylor
Post by 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.
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 ...
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 of the development and, given that many internal
platforms depends on Pulsar, it is heavily invested in the long term success
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache community.
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source process and
several of them are committers on other Apache projects. We will be actively
working with experienced Apache community members to improve our project.
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo, Yahoo!
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the project.
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time and on
volunteer time, after hours. The majority of initial committers are paid by
their employer to contribute to this project. However, they are all passionate
about the project, and we are confident that the project will continue even if
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache communities.
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in 2016. This
proposal is not for the purpose of generating publicity. Rather, we want to
make sure to create a very inclusive and meritocratic community, outside the
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and contributors
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar,
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we would
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache License
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar fulfills
and passes the conditions for being an Incubator project in the ASF, Yahoo
will transition the source code ownership to the Apache Software Foundation
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are distributed under
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for Java,
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty, DataSketches,
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty, SnakeYAML
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: general-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
Jia Zhai
2017-05-17 17:58:01 UTC
Permalink
+1 (non-binding)
Post by Raphael Bircher
+1 (binding)
-Taylor
Post by 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.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority vote
for which
Post by Bryan Call
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 ...
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
Post by Bryan Call
subscribers, and cross-datacenter replication.
== Proposal ==
Pub-sub messaging is a very common design pattern that is increasingly
found
Post by Bryan Call
in distributed systems powering Internet applications. These applications
provide real-time services, and need publish-latencies of 5ms on average
and
Post by Bryan Call
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong
durability, and
Post by Bryan Call
delivery guarantees. In order to handle the “five 9’s” durability
requirements
Post by Bryan Call
of a production environment, the messages have to be committed on
multiple
Post by Bryan Call
disks or nodes.
Pulsar has been developed at Yahoo to address these specific
requirements by
Post by Bryan Call
providing a hosted service supporting millions of topics for multiple
tenants.
Post by Bryan Call
The current incarnation of Pulsar has been open-sourced under Apache
license
Post by Bryan Call
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
Post by Bryan Call
hosted messaging platform capable of supporting a huge number of topics
while
Post by Bryan Call
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
Post by Bryan Call
on the public Github repository and two major releases were shipped
(1.15 and
Post by Bryan Call
1.16), along with multiple minor ones. Several other companies have
expressed
Post by Bryan Call
interest in the project and its future direction.
== Rationale ==
Pulsar is a platform that is built on top of several other Apache
projects. In
Post by Bryan Call
particular, Apache BookKeeper is used to store the data and Apache
ZooKeeper
Post by Bryan Call
is used for coordination and metadata storage. Pulsar is also
interoperable
Post by Bryan Call
out of the box with Apache Storm, to provide an easy to use stream
processing
Post by Bryan Call
solution.
We want to establish a community outside the scope of initial core
developers
Post by Bryan Call
at Yahoo and we believe that the Apache Foundation is a great fit and
long-
Post by Bryan Call
term home for Pulsar, as it provides an established process for
community-
Post by Bryan Call
driven development and decision making by consensus. This is exactly the
model
Post by Bryan Call
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
Post by Bryan Call
this time around 60 different applications were integrated with Pulsar.
Other
Post by Bryan Call
companies are evaluating it as well and have been contributing code to
the
Post by Bryan Call
project.
=== Meritocracy ===
We value meritocracy and we understand that it is the basis to form an
open
Post by Bryan Call
community that encourages multiple companies and individuals to
contribute and
Post by Bryan Call
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities to
all
Post by Bryan Call
contributors.
=== Community ===
We have validated, through the interest demonstrated by Pulsar users at
Yahoo,
Post by Bryan Call
that a reliable hosted pub-sub messaging platform represent a very
important
Post by Bryan Call
building block for web-scale distributed applications. We believe that
many
Post by Bryan Call
companies can benefit by applying the same model and that bringing
Pulsar to
Post by Bryan Call
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
Post by Bryan Call
have been contribution from developers from several external companies.
=== Alignment ===
Pulsar builds upon other Apache projects such as ZooKeeper and
BookKeeper,
Post by Bryan Call
along with a number of other Apache libraries. We have already
integrated with
Post by Bryan Call
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 of the development and, given that many
internal
Post by Bryan Call
platforms depends on Pulsar, it is heavily invested in the long term
success
Post by Bryan Call
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache
community.
Post by Bryan Call
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source
process and
Post by Bryan Call
several of them are committers on other Apache projects. We will be
actively
Post by Bryan Call
working with experienced Apache community members to improve our project.
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo,
Yahoo!
Post by Bryan Call
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the
project.
Post by Bryan Call
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time
and on
Post by Bryan Call
volunteer time, after hours. The majority of initial committers are paid
by
Post by Bryan Call
their employer to contribute to this project. However, they are all
passionate
Post by Bryan Call
about the project, and we are confident that the project will continue
even if
Post by Bryan Call
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache
communities.
Post by Bryan Call
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in
2016. This
Post by Bryan Call
proposal is not for the purpose of generating publicity. Rather, we want
to
Post by Bryan Call
make sure to create a very inclusive and meritocratic community, outside
the
Post by Bryan Call
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and
contributors
Post by Bryan Call
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar,
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we
would
Post by Bryan Call
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache
License
Post by Bryan Call
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar
fulfills
Post by Bryan Call
and passes the conditions for being an Incubator project in the ASF,
Yahoo
Post by Bryan Call
will transition the source code ownership to the Apache Software
Foundation
Post by Bryan Call
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are distributed
under
Post by Bryan Call
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for
Java,
Post by Bryan Call
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty,
DataSketches,
Post by Bryan Call
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty,
SnakeYAML
Post by Bryan Call
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
---------------------------------------------------------------------
Julian Hyde
2017-05-17 18:44:29 UTC
Permalink
+1 (binding)
Post by Sijie Guo
+1 (non-binding)
Post by Raphael Bircher
+1 (binding)
-Taylor
Post by 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.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority vote
for which
Post by Bryan Call
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 ...
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
Post by Bryan Call
subscribers, and cross-datacenter replication.
== Proposal ==
Pub-sub messaging is a very common design pattern that is increasingly
found
Post by Bryan Call
in distributed systems powering Internet applications. These applications
provide real-time services, and need publish-latencies of 5ms on average
and
Post by Bryan Call
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong
durability, and
Post by Bryan Call
delivery guarantees. In order to handle the “five 9’s” durability
requirements
Post by Bryan Call
of a production environment, the messages have to be committed on
multiple
Post by Bryan Call
disks or nodes.
Pulsar has been developed at Yahoo to address these specific
requirements by
Post by Bryan Call
providing a hosted service supporting millions of topics for multiple
tenants.
Post by Bryan Call
The current incarnation of Pulsar has been open-sourced under Apache
license
Post by Bryan Call
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
Post by Bryan Call
hosted messaging platform capable of supporting a huge number of topics
while
Post by Bryan Call
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
Post by Bryan Call
on the public Github repository and two major releases were shipped
(1.15 and
Post by Bryan Call
1.16), along with multiple minor ones. Several other companies have
expressed
Post by Bryan Call
interest in the project and its future direction.
== Rationale ==
Pulsar is a platform that is built on top of several other Apache
projects. In
Post by Bryan Call
particular, Apache BookKeeper is used to store the data and Apache
ZooKeeper
Post by Bryan Call
is used for coordination and metadata storage. Pulsar is also
interoperable
Post by Bryan Call
out of the box with Apache Storm, to provide an easy to use stream
processing
Post by Bryan Call
solution.
We want to establish a community outside the scope of initial core
developers
Post by Bryan Call
at Yahoo and we believe that the Apache Foundation is a great fit and
long-
Post by Bryan Call
term home for Pulsar, as it provides an established process for
community-
Post by Bryan Call
driven development and decision making by consensus. This is exactly the
model
Post by Bryan Call
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
Post by Bryan Call
this time around 60 different applications were integrated with Pulsar.
Other
Post by Bryan Call
companies are evaluating it as well and have been contributing code to
the
Post by Bryan Call
project.
=== Meritocracy ===
We value meritocracy and we understand that it is the basis to form an
open
Post by Bryan Call
community that encourages multiple companies and individuals to
contribute and
Post by Bryan Call
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities to
all
Post by Bryan Call
contributors.
=== Community ===
We have validated, through the interest demonstrated by Pulsar users at
Yahoo,
Post by Bryan Call
that a reliable hosted pub-sub messaging platform represent a very
important
Post by Bryan Call
building block for web-scale distributed applications. We believe that
many
Post by Bryan Call
companies can benefit by applying the same model and that bringing
Pulsar to
Post by Bryan Call
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
Post by Bryan Call
have been contribution from developers from several external companies.
=== Alignment ===
Pulsar builds upon other Apache projects such as ZooKeeper and
BookKeeper,
Post by Bryan Call
along with a number of other Apache libraries. We have already
integrated with
Post by Bryan Call
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 of the development and, given that many
internal
Post by Bryan Call
platforms depends on Pulsar, it is heavily invested in the long term
success
Post by Bryan Call
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache
community.
Post by Bryan Call
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source
process and
Post by Bryan Call
several of them are committers on other Apache projects. We will be
actively
Post by Bryan Call
working with experienced Apache community members to improve our project.
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo,
Yahoo!
Post by Bryan Call
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the
project.
Post by Bryan Call
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time
and on
Post by Bryan Call
volunteer time, after hours. The majority of initial committers are paid
by
Post by Bryan Call
their employer to contribute to this project. However, they are all
passionate
Post by Bryan Call
about the project, and we are confident that the project will continue
even if
Post by Bryan Call
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache
communities.
Post by Bryan Call
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in
2016. This
Post by Bryan Call
proposal is not for the purpose of generating publicity. Rather, we want
to
Post by Bryan Call
make sure to create a very inclusive and meritocratic community, outside
the
Post by Bryan Call
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and
contributors
Post by Bryan Call
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar,
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we
would
Post by Bryan Call
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache
License
Post by Bryan Call
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar
fulfills
Post by Bryan Call
and passes the conditions for being an Incubator project in the ASF,
Yahoo
Post by Bryan Call
will transition the source code ownership to the Apache Software
Foundation
Post by Bryan Call
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are distributed
under
Post by Bryan Call
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for
Java,
Post by Bryan Call
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty,
DataSketches,
Post by Bryan Call
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty,
SnakeYAML
Post by Bryan Call
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: general-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
vintagewang
2017-05-17 23:03:04 UTC
Permalink
+1(non-binding)

Pulsar is a powerful mq I like it.
Post by Raphael Bircher
+1 (binding)
Post by Sijie Guo
+1 (non-binding)
Post by Raphael Bircher
+1 (binding)
-Taylor
Post by 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.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority vote
for which
Post by Bryan Call
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 ...
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
Post by Bryan Call
subscribers, and cross-datacenter replication.
== Proposal ==
Pub-sub messaging is a very common design pattern that is increasingly
found
Post by Bryan Call
in distributed systems powering Internet applications. These
applications
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
provide real-time services, and need publish-latencies of 5ms on
average
Post by Sijie Guo
Post by Raphael Bircher
and
Post by Bryan Call
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong
durability, and
Post by Bryan Call
delivery guarantees. In order to handle the “five 9’s” durability
requirements
Post by Bryan Call
of a production environment, the messages have to be committed on
multiple
Post by Bryan Call
disks or nodes.
Pulsar has been developed at Yahoo to address these specific
requirements by
Post by Bryan Call
providing a hosted service supporting millions of topics for multiple
tenants.
Post by Bryan Call
The current incarnation of Pulsar has been open-sourced under Apache
license
Post by Bryan Call
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
Post by Bryan Call
hosted messaging platform capable of supporting a huge number of topics
while
Post by Bryan Call
maintaining strict guarantees for durability, ordering and low latency.
Current solutions would require to run multiple individual clusters
with
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
additional operational work and capacity overhead.
Since the open sourcing of Pulsar, the development has been done
exclusively
Post by Bryan Call
on the public Github repository and two major releases were shipped
(1.15 and
Post by Bryan Call
1.16), along with multiple minor ones. Several other companies have
expressed
Post by Bryan Call
interest in the project and its future direction.
== Rationale ==
Pulsar is a platform that is built on top of several other Apache
projects. In
Post by Bryan Call
particular, Apache BookKeeper is used to store the data and Apache
ZooKeeper
Post by Bryan Call
is used for coordination and metadata storage. Pulsar is also
interoperable
Post by Bryan Call
out of the box with Apache Storm, to provide an easy to use stream
processing
Post by Bryan Call
solution.
We want to establish a community outside the scope of initial core
developers
Post by Bryan Call
at Yahoo and we believe that the Apache Foundation is a great fit and
long-
Post by Bryan Call
term home for Pulsar, as it provides an established process for
community-
Post by Bryan Call
driven development and decision making by consensus. This is exactly
the
Post by Sijie Guo
Post by Raphael Bircher
model
Post by Bryan Call
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
Post by Bryan Call
this time around 60 different applications were integrated with Pulsar.
Other
Post by Bryan Call
companies are evaluating it as well and have been contributing code to
the
Post by Bryan Call
project.
=== Meritocracy ===
We value meritocracy and we understand that it is the basis to form an
open
Post by Bryan Call
community that encourages multiple companies and individuals to
contribute and
Post by Bryan Call
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities
to
Post by Sijie Guo
Post by Raphael Bircher
all
Post by Bryan Call
contributors.
=== Community ===
We have validated, through the interest demonstrated by Pulsar users at
Yahoo,
Post by Bryan Call
that a reliable hosted pub-sub messaging platform represent a very
important
Post by Bryan Call
building block for web-scale distributed applications. We believe that
many
Post by Bryan Call
companies can benefit by applying the same model and that bringing
Pulsar to
Post by Bryan Call
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
Post by Bryan Call
have been contribution from developers from several external companies.
=== Alignment ===
Pulsar builds upon other Apache projects such as ZooKeeper and
BookKeeper,
Post by Bryan Call
along with a number of other Apache libraries. We have already
integrated with
Post by Bryan Call
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 of the development and, given that many
internal
Post by Bryan Call
platforms depends on Pulsar, it is heavily invested in the long term
success
Post by Bryan Call
of the the project. Yahoo has a long history participating in
open-source
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
projects, and has been also a long time contributor to the Apache
community.
Post by Bryan Call
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source
process and
Post by Bryan Call
several of them are committers on other Apache projects. We will be
actively
Post by Bryan Call
working with experienced Apache community members to improve our
project.
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo,
Yahoo!
Post by Bryan Call
Japan, Salesforce and MercadoLibre. We hope to grow the community and
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
include additional committers based on their contributions to the
project.
Post by Bryan Call
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time
and on
Post by Bryan Call
volunteer time, after hours. The majority of initial committers are
paid
Post by Sijie Guo
Post by Raphael Bircher
by
Post by Bryan Call
their employer to contribute to this project. However, they are all
passionate
Post by Bryan Call
about the project, and we are confident that the project will continue
even if
Post by Bryan Call
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache
communities.
Post by Bryan Call
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the
next
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
logical step for the Pulsar project after open-sourcing the code in
2016. This
Post by Bryan Call
proposal is not for the purpose of generating publicity. Rather, we
want
Post by Sijie Guo
Post by Raphael Bircher
to
Post by Bryan Call
make sure to create a very inclusive and meritocratic community,
outside
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and
contributors
Post by Bryan Call
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing
Pulsar,
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we
would
Post by Bryan Call
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache
License
Post by Bryan Call
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar
fulfills
Post by Bryan Call
and passes the conditions for being an Incubator project in the ASF,
Yahoo
Post by Bryan Call
will transition the source code ownership to the Apache Software
Foundation
Post by Bryan Call
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are
distributed
Post by Sijie Guo
Post by Raphael Bircher
under
Post by Bryan Call
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for
Java,
Post by Bryan Call
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty,
DataSketches,
Post by Bryan Call
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty,
SnakeYAML
Post by Bryan Call
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
Pierre Smits
2017-05-18 13:31:43 UTC
Permalink
+1, from the peanut gallery.

Best regards,

Pierre Smits

ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
Post by vintagewang
+1(non-binding)
Pulsar is a powerful mq I like it.
Post by Raphael Bircher
+1 (binding)
Post by Sijie Guo
+1 (non-binding)
Post by Raphael Bircher
+1 (binding)
-Taylor
Post by 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.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority
vote
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
for which
Post by Bryan Call
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 ...
https://wiki.apache.org/incubator/PulsarProposal
-Bryan
= Pulsar Proposal =
== Abstract ==
Pulsar is a highly scalable, low latency messaging platform running
on
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor
management for
Post by Bryan Call
subscribers, and cross-datacenter replication.
== Proposal ==
Pub-sub messaging is a very common design pattern that is
increasingly
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
found
Post by Bryan Call
in distributed systems powering Internet applications. These
applications
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
provide real-time services, and need publish-latencies of 5ms on
average
Post by Sijie Guo
Post by Raphael Bircher
and
Post by Bryan Call
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong
durability, and
Post by Bryan Call
delivery guarantees. In order to handle the “five 9’s” durability
requirements
Post by Bryan Call
of a production environment, the messages have to be committed on
multiple
Post by Bryan Call
disks or nodes.
Pulsar has been developed at Yahoo to address these specific
requirements by
Post by Bryan Call
providing a hosted service supporting millions of topics for multiple
tenants.
Post by Bryan Call
The current incarnation of Pulsar has been open-sourced under Apache
license
Post by Bryan Call
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
Post by Bryan Call
hosted messaging platform capable of supporting a huge number of
topics
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
while
Post by Bryan Call
maintaining strict guarantees for durability, ordering and low
latency.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Current solutions would require to run multiple individual clusters
with
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
additional operational work and capacity overhead.
Since the open sourcing of Pulsar, the development has been done
exclusively
Post by Bryan Call
on the public Github repository and two major releases were shipped
(1.15 and
Post by Bryan Call
1.16), along with multiple minor ones. Several other companies have
expressed
Post by Bryan Call
interest in the project and its future direction.
== Rationale ==
Pulsar is a platform that is built on top of several other Apache
projects. In
Post by Bryan Call
particular, Apache BookKeeper is used to store the data and Apache
ZooKeeper
Post by Bryan Call
is used for coordination and metadata storage. Pulsar is also
interoperable
Post by Bryan Call
out of the box with Apache Storm, to provide an easy to use stream
processing
Post by Bryan Call
solution.
We want to establish a community outside the scope of initial core
developers
Post by Bryan Call
at Yahoo and we believe that the Apache Foundation is a great fit and
long-
Post by Bryan Call
term home for Pulsar, as it provides an established process for
community-
Post by Bryan Call
driven development and decision making by consensus. This is exactly
the
Post by Sijie Guo
Post by Raphael Bircher
model
Post by Bryan Call
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
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
incremental development, and releases along with the Apache
guidelines.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
== Current Status ==
Pulsar has been in service at large scale for more than 2 years at
Yahoo. In
Post by Bryan Call
this time around 60 different applications were integrated with
Pulsar.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Other
Post by Bryan Call
companies are evaluating it as well and have been contributing code
to
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
project.
=== Meritocracy ===
We value meritocracy and we understand that it is the basis to form
an
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
open
Post by Bryan Call
community that encourages multiple companies and individuals to
contribute and
Post by Bryan Call
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and responsibilities
to
Post by Sijie Guo
Post by Raphael Bircher
all
Post by Bryan Call
contributors.
=== Community ===
We have validated, through the interest demonstrated by Pulsar users
at
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo,
Post by Bryan Call
that a reliable hosted pub-sub messaging platform represent a very
important
Post by Bryan Call
building block for web-scale distributed applications. We believe
that
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
many
Post by Bryan Call
companies can benefit by applying the same model and that bringing
Pulsar to
Post by Bryan Call
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
Post by Bryan Call
have been contribution from developers from several external
companies.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Alignment ===
Pulsar builds upon other Apache projects such as ZooKeeper and
BookKeeper,
Post by Bryan Call
along with a number of other Apache libraries. We have already
integrated with
Post by Bryan Call
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 of the development and, given that many
internal
Post by Bryan Call
platforms depends on Pulsar, it is heavily invested in the long term
success
Post by Bryan Call
of the the project. Yahoo has a long history participating in
open-source
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
projects, and has been also a long time contributor to the Apache
community.
Post by Bryan Call
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source
process and
Post by Bryan Call
several of them are committers on other Apache projects. We will be
actively
Post by Bryan Call
working with experienced Apache community members to improve our
project.
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Homogenous Developers ===
The initial committers are employed by large companies including
Yahoo,
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo!
Post by Bryan Call
Japan, Salesforce and MercadoLibre. We hope to grow the community and
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
include additional committers based on their contributions to the
project.
Post by Bryan Call
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried
time
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
and on
Post by Bryan Call
volunteer time, after hours. The majority of initial committers are
paid
Post by Sijie Guo
Post by Raphael Bircher
by
Post by Bryan Call
their employer to contribute to this project. However, they are all
passionate
Post by Bryan Call
about the project, and we are confident that the project will
continue
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
even if
Post by Bryan Call
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent
and
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache
communities.
Post by Bryan Call
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the
next
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
logical step for the Pulsar project after open-sourcing the code in
2016. This
Post by Bryan Call
proposal is not for the purpose of generating publicity. Rather, we
want
Post by Sijie Guo
Post by Raphael Bircher
to
Post by Bryan Call
make sure to create a very inclusive and meritocratic community,
outside
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and
contributors
Post by Bryan Call
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing
Pulsar,
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we
would
Post by Bryan Call
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache
License
Post by Bryan Call
v2.0 and the copyright is assigned to Yahoo. All the contributions
from
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
external parties have been received under Apache style CLA. If Pulsar
fulfills
Post by Bryan Call
and passes the conditions for being an Incubator project in the ASF,
Yahoo
Post by Bryan Call
will transition the source code ownership to the Apache Software
Foundation
Post by Bryan Call
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are
distributed
Post by Sijie Guo
Post by Raphael Bircher
under
Post by Bryan Call
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for
Java,
Post by Bryan Call
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty,
DataSketches,
Post by Bryan Call
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty,
SnakeYAML
Post by Bryan Call
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
------------------------------------------------------------
---------
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
---------------------------------------------------------------------
---------------------------------------------------------------------
Mohammad Noureldin
2017-05-18 15:09:54 UTC
Permalink
+1 (binding)
Post by Pierre Smits
+1, from the peanut gallery.
Best regards,
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
Post by vintagewang
+1(non-binding)
Pulsar is a powerful mq I like it.
Post by Raphael Bircher
+1 (binding)
Post by Sijie Guo
+1 (non-binding)
Post by Raphael Bircher
+1 (binding)
-Taylor
Post by Bryan Call
Hi All,
As the champion for Pulsar, I would like to start a VOTE to bring
the
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
project in as Apache incubator podling.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority
vote
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
for which
Post by Bryan Call
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
https://wiki.apache.org/incubator/PulsarProposal
-Bryan
= Pulsar Proposal =
== Abstract ==
Pulsar is a highly scalable, low latency messaging platform running
on
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
commodity hardware. It provides simple pub-sub semantics over
topics,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
guaranteed at-least-once delivery of messages, automatic cursor
management for
Post by Bryan Call
subscribers, and cross-datacenter replication.
== Proposal ==
Pub-sub messaging is a very common design pattern that is
increasingly
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
found
Post by Bryan Call
in distributed systems powering Internet applications. These
applications
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
provide real-time services, and need publish-latencies of 5ms on
average
Post by Sijie Guo
Post by Raphael Bircher
and
Post by Bryan Call
no more than 15ms at the 99th percentile. At Internet scale, these
applications require a messaging system with ordering, strong
durability, and
Post by Bryan Call
delivery guarantees. In order to handle the “five 9’s” durability
requirements
Post by Bryan Call
of a production environment, the messages have to be committed on
multiple
Post by Bryan Call
disks or nodes.
Pulsar has been developed at Yahoo to address these specific
requirements by
Post by Bryan Call
providing a hosted service supporting millions of topics for
multiple
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
tenants.
Post by Bryan Call
The current incarnation of Pulsar has been open-sourced under
Apache
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
license
Post by Bryan Call
in September 2016 and it is the direct evolution of systems that
were
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
developed at Yahoo since 2011.
We believe there is currently no other system that provides a
multi-tenant
Post by Bryan Call
hosted messaging platform capable of supporting a huge number of
topics
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
while
Post by Bryan Call
maintaining strict guarantees for durability, ordering and low
latency.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Current solutions would require to run multiple individual clusters
with
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
additional operational work and capacity overhead.
Since the open sourcing of Pulsar, the development has been done
exclusively
Post by Bryan Call
on the public Github repository and two major releases were shipped
(1.15 and
Post by Bryan Call
1.16), along with multiple minor ones. Several other companies have
expressed
Post by Bryan Call
interest in the project and its future direction.
== Rationale ==
Pulsar is a platform that is built on top of several other Apache
projects. In
Post by Bryan Call
particular, Apache BookKeeper is used to store the data and Apache
ZooKeeper
Post by Bryan Call
is used for coordination and metadata storage. Pulsar is also
interoperable
Post by Bryan Call
out of the box with Apache Storm, to provide an easy to use stream
processing
Post by Bryan Call
solution.
We want to establish a community outside the scope of initial core
developers
Post by Bryan Call
at Yahoo and we believe that the Apache Foundation is a great fit
and
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
long-
Post by Bryan Call
term home for Pulsar, as it provides an established process for
community-
Post by Bryan Call
driven development and decision making by consensus. This is
exactly
Post by vintagewang
Post by Raphael Bircher
the
Post by Sijie Guo
Post by Raphael Bircher
model
Post by Bryan Call
we want to adopt for future Pulsar development.
== Initial Goals ==
The initial goals will be to move the existing codebase to Apache
and
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrate with the Apache development process. Furthermore, we plan
for
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
incremental development, and releases along with the Apache
guidelines.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
== Current Status ==
Pulsar has been in service at large scale for more than 2 years at
Yahoo. In
Post by Bryan Call
this time around 60 different applications were integrated with
Pulsar.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Other
Post by Bryan Call
companies are evaluating it as well and have been contributing code
to
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
project.
=== Meritocracy ===
We value meritocracy and we understand that it is the basis to form
an
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
open
Post by Bryan Call
community that encourages multiple companies and individuals to
contribute and
Post by Bryan Call
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and
responsibilities
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
all
Post by Bryan Call
contributors.
=== Community ===
We have validated, through the interest demonstrated by Pulsar
users
Post by vintagewang
at
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo,
Post by Bryan Call
that a reliable hosted pub-sub messaging platform represent a very
important
Post by Bryan Call
building block for web-scale distributed applications. We believe
that
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
many
Post by Bryan Call
companies can benefit by applying the same model and that bringing
Pulsar to
Post by Bryan Call
Apache will get the community to grow stronger.
=== Core Developers ===
Pulsar has been initially developed at Yahoo and received
significant
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
contributions from Yahoo Japan. After having open-sourced the
project
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
there
Post by Bryan Call
have been contribution from developers from several external
companies.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Alignment ===
Pulsar builds upon other Apache projects such as ZooKeeper and
BookKeeper,
Post by Bryan Call
along with a number of other Apache libraries. We have already
integrated with
Post by Bryan Call
Storm and we envision to integrate with multiple other systems in
the
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
streaming and big data space.
== Known Risks ==
=== Orphaned Products ===
Yahoo has been doing most of the development and, given that many
internal
Post by Bryan Call
platforms depends on Pulsar, it is heavily invested in the long
term
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
success
Post by Bryan Call
of the the project. Yahoo has a long history participating in
open-source
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
projects, and has been also a long time contributor to the Apache
community.
Post by Bryan Call
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source
process and
Post by Bryan Call
several of them are committers on other Apache projects. We will be
actively
Post by Bryan Call
working with experienced Apache community members to improve our
project.
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Homogenous Developers ===
The initial committers are employed by large companies including
Yahoo,
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo!
Post by Bryan Call
Japan, Salesforce and MercadoLibre. We hope to grow the community
and
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
include additional committers based on their contributions to the
project.
Post by Bryan Call
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried
time
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
and on
Post by Bryan Call
volunteer time, after hours. The majority of initial committers are
paid
Post by Sijie Guo
Post by Raphael Bircher
by
Post by Bryan Call
their employer to contribute to this project. However, they are all
passionate
Post by Bryan Call
about the project, and we are confident that the project will
continue
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
even if
Post by Bryan Call
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent
and
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrated with BookKeeper and ZooKeeper and Storm. There are
ongoing
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache
communities.
Post by Bryan Call
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the
next
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
logical step for the Pulsar project after open-sourcing the code in
2016. This
Post by Bryan Call
proposal is not for the purpose of generating publicity. Rather, we
want
Post by Sijie Guo
Post by Raphael Bircher
to
Post by Bryan Call
make sure to create a very inclusive and meritocratic community,
outside
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and
contributors
Post by Bryan Call
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing
Pulsar,
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that
we
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
would
Post by Bryan Call
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache
License
Post by Bryan Call
v2.0 and the copyright is assigned to Yahoo. All the contributions
from
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
external parties have been received under Apache style CLA. If
Pulsar
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
fulfills
Post by Bryan Call
and passes the conditions for being an Incubator project in the
ASF,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo
Post by Bryan Call
will transition the source code ownership to the Apache Software
Foundation
Post by Bryan Call
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are
distributed
Post by Sijie Guo
Post by Raphael Bircher
under
Post by Bryan Call
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections
for
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Java,
Post by Bryan Call
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty,
DataSketches,
Post by Bryan Call
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient,
Jetty,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
SnakeYAML
Post by Bryan Call
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI,
Codec,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
subscriptions)
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
------------------------------------------------------------
---------
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
------------------------------------------------------------
---------
Post by vintagewang
Post by Raphael Bircher
---------------------------------------------------------------------
Luke Han
2017-05-19 10:04:40 UTC
Permalink
+1 (binding)


Best Regards!
---------------------

Luke Han

On Thu, May 18, 2017 at 11:09 PM, Mohammad Noureldin <
Post by Raphael Bircher
+1 (binding)
Post by Pierre Smits
+1, from the peanut gallery.
Best regards,
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
Post by vintagewang
+1(non-binding)
Pulsar is a powerful mq I like it.
Post by Raphael Bircher
+1 (binding)
Post by Sijie Guo
+1 (non-binding)
On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz <
Post by Raphael Bircher
+1 (binding)
-Taylor
Post by Bryan Call
Hi All,
As the champion for Pulsar, I would like to start a VOTE to bring
the
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
project in as Apache incubator podling.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority
vote
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
for which
Post by Bryan Call
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
https://wiki.apache.org/incubator/PulsarProposal
-Bryan
= Pulsar Proposal =
== Abstract ==
Pulsar is a highly scalable, low latency messaging platform
running
Post by Pierre Smits
Post by vintagewang
on
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
commodity hardware. It provides simple pub-sub semantics over
topics,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
guaranteed at-least-once delivery of messages, automatic cursor
management for
Post by Bryan Call
subscribers, and cross-datacenter replication.
== Proposal ==
Pub-sub messaging is a very common design pattern that is
increasingly
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
found
Post by Bryan Call
in distributed systems powering Internet applications. These
applications
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
provide real-time services, and need publish-latencies of 5ms on
average
Post by Sijie Guo
Post by Raphael Bircher
and
Post by Bryan Call
no more than 15ms at the 99th percentile. At Internet scale,
these
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
applications require a messaging system with ordering, strong
durability, and
Post by Bryan Call
delivery guarantees. In order to handle the “five 9’s” durability
requirements
Post by Bryan Call
of a production environment, the messages have to be committed on
multiple
Post by Bryan Call
disks or nodes.
Pulsar has been developed at Yahoo to address these specific
requirements by
Post by Bryan Call
providing a hosted service supporting millions of topics for
multiple
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
tenants.
Post by Bryan Call
The current incarnation of Pulsar has been open-sourced under
Apache
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
license
Post by Bryan Call
in September 2016 and it is the direct evolution of systems that
were
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
developed at Yahoo since 2011.
We believe there is currently no other system that provides a
multi-tenant
Post by Bryan Call
hosted messaging platform capable of supporting a huge number of
topics
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
while
Post by Bryan Call
maintaining strict guarantees for durability, ordering and low
latency.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Current solutions would require to run multiple individual
clusters
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
with
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
additional operational work and capacity overhead.
Since the open sourcing of Pulsar, the development has been done
exclusively
Post by Bryan Call
on the public Github repository and two major releases were
shipped
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
(1.15 and
Post by Bryan Call
1.16), along with multiple minor ones. Several other companies
have
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
expressed
Post by Bryan Call
interest in the project and its future direction.
== Rationale ==
Pulsar is a platform that is built on top of several other Apache
projects. In
Post by Bryan Call
particular, Apache BookKeeper is used to store the data and
Apache
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
ZooKeeper
Post by Bryan Call
is used for coordination and metadata storage. Pulsar is also
interoperable
Post by Bryan Call
out of the box with Apache Storm, to provide an easy to use
stream
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
processing
Post by Bryan Call
solution.
We want to establish a community outside the scope of initial
core
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
developers
Post by Bryan Call
at Yahoo and we believe that the Apache Foundation is a great fit
and
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
long-
Post by Bryan Call
term home for Pulsar, as it provides an established process for
community-
Post by Bryan Call
driven development and decision making by consensus. This is
exactly
Post by vintagewang
Post by Raphael Bircher
the
Post by Sijie Guo
Post by Raphael Bircher
model
Post by Bryan Call
we want to adopt for future Pulsar development.
== Initial Goals ==
The initial goals will be to move the existing codebase to Apache
and
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrate with the Apache development process. Furthermore, we
plan
Post by Pierre Smits
Post by vintagewang
for
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
incremental development, and releases along with the Apache
guidelines.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
== Current Status ==
Pulsar has been in service at large scale for more than 2 years
at
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo. In
Post by Bryan Call
this time around 60 different applications were integrated with
Pulsar.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Other
Post by Bryan Call
companies are evaluating it as well and have been contributing
code
Post by Pierre Smits
Post by vintagewang
to
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
project.
=== Meritocracy ===
We value meritocracy and we understand that it is the basis to
form
Post by Pierre Smits
Post by vintagewang
an
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
open
Post by Bryan Call
community that encourages multiple companies and individuals to
contribute and
Post by Bryan Call
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and
responsibilities
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
all
Post by Bryan Call
contributors.
=== Community ===
We have validated, through the interest demonstrated by Pulsar
users
Post by vintagewang
at
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo,
Post by Bryan Call
that a reliable hosted pub-sub messaging platform represent a
very
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
important
Post by Bryan Call
building block for web-scale distributed applications. We believe
that
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
many
Post by Bryan Call
companies can benefit by applying the same model and that
bringing
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Pulsar to
Post by Bryan Call
Apache will get the community to grow stronger.
=== Core Developers ===
Pulsar has been initially developed at Yahoo and received
significant
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
contributions from Yahoo Japan. After having open-sourced the
project
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
there
Post by Bryan Call
have been contribution from developers from several external
companies.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Alignment ===
Pulsar builds upon other Apache projects such as ZooKeeper and
BookKeeper,
Post by Bryan Call
along with a number of other Apache libraries. We have already
integrated with
Post by Bryan Call
Storm and we envision to integrate with multiple other systems in
the
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
streaming and big data space.
== Known Risks ==
=== Orphaned Products ===
Yahoo has been doing most of the development and, given that many
internal
Post by Bryan Call
platforms depends on Pulsar, it is heavily invested in the long
term
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
success
Post by Bryan Call
of the the project. Yahoo has a long history participating in
open-source
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
projects, and has been also a long time contributor to the Apache
community.
Post by Bryan Call
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open
source
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
process and
Post by Bryan Call
several of them are committers on other Apache projects. We will
be
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
actively
Post by Bryan Call
working with experienced Apache community members to improve our
project.
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Homogenous Developers ===
The initial committers are employed by large companies including
Yahoo,
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo!
Post by Bryan Call
Japan, Salesforce and MercadoLibre. We hope to grow the community
and
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
include additional committers based on their contributions to the
project.
Post by Bryan Call
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both
salaried
Post by Pierre Smits
Post by vintagewang
time
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
and on
Post by Bryan Call
volunteer time, after hours. The majority of initial committers
are
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
paid
Post by Sijie Guo
Post by Raphael Bircher
by
Post by Bryan Call
their employer to contribute to this project. However, they are
all
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
passionate
Post by Bryan Call
about the project, and we are confident that the project will
continue
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
even if
Post by Bryan Call
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely
dependent
Post by Pierre Smits
Post by vintagewang
and
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrated with BookKeeper and ZooKeeper and Storm. There are
ongoing
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrate with other projects such Apache Spark. We look forward
to
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
collaborating with those communities, as well as other Apache
communities.
Post by Bryan Call
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is
the
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
next
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
logical step for the Pulsar project after open-sourcing the code
in
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
2016. This
Post by Bryan Call
proposal is not for the purpose of generating publicity. Rather,
we
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
want
Post by Sijie Guo
Post by Raphael Bircher
to
Post by Bryan Call
make sure to create a very inclusive and meritocratic community,
outside
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
umbrella of a single company. Yahoo has a long standing history
of
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
contributing to Apache projects and the Pulsar developers and
contributors
Post by Bryan Call
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing
Pulsar,
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that
we
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
would
Post by Bryan Call
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under
Apache
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
License
Post by Bryan Call
v2.0 and the copyright is assigned to Yahoo. All the
contributions
Post by Pierre Smits
Post by vintagewang
from
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
external parties have been received under Apache style CLA. If
Pulsar
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
fulfills
Post by Bryan Call
and passes the conditions for being an Incubator project in the
ASF,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo
Post by Bryan Call
will transition the source code ownership to the Apache Software
Foundation
Post by Bryan Call
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are
distributed
Post by Sijie Guo
Post by Raphael Bircher
under
Post by Bryan Call
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections
for
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Java,
Post by Bryan Call
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty,
DataSketches,
Post by Bryan Call
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient,
Jetty,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
SnakeYAML
Post by Bryan Call
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI,
Codec,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
subscriptions)
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
------------------------------------------------------------
---------
org
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
------------------------------------------------------------
---------
org
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
------------------------------------------------------------
---------
Xinyu Zhou
2017-05-19 11:13:48 UTC
Permalink
+1(non-binding)

Glad to see ASF will have another messaging solution~

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


Best Regards!
---------------------

Luke Han

On Thu, May 18, 2017 at 11:09 PM, Mohammad Noureldin <
Post by Raphael Bircher
+1 (binding)
Post by Pierre Smits
+1, from the peanut gallery.
Best regards,
Pierre Smits
ORRTIZ.COM <http://www.orrtiz.com>
OFBiz based solutions & services
OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/
Post by vintagewang
+1(non-binding)
Pulsar is a powerful mq I like it.
Post by Raphael Bircher
+1 (binding)
Post by Sijie Guo
+1 (non-binding)
On Thu, May 18, 2017 at 1:11 AM, P. Taylor Goetz <
Post by Raphael Bircher
+1 (binding)
-Taylor
Post by Bryan Call
Hi All,
As the champion for Pulsar, I would like to start a VOTE to bring
the
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
project in as Apache incubator podling.
https://www.apache.org/foundation/voting.html
A vote for accepting a new Apache Incubator podling is a majority
vote
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
for which
Post by Bryan Call
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
https://wiki.apache.org/incubator/PulsarProposal
-Bryan
= Pulsar Proposal =
== Abstract ==
Pulsar is a highly scalable, low latency messaging platform
running
Post by Pierre Smits
Post by vintagewang
on
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
commodity hardware. It provides simple pub-sub semantics over
topics,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
guaranteed at-least-once delivery of messages, automatic cursor
management for
Post by Bryan Call
subscribers, and cross-datacenter replication.
== Proposal ==
Pub-sub messaging is a very common design pattern that is
increasingly
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
found
Post by Bryan Call
in distributed systems powering Internet applications. These
applications
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
provide real-time services, and need publish-latencies of 5ms on
average
Post by Sijie Guo
Post by Raphael Bircher
and
Post by Bryan Call
no more than 15ms at the 99th percentile. At Internet scale,
these
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
applications require a messaging system with ordering, strong
durability, and
Post by Bryan Call
delivery guarantees. In order to handle the “five 9’s” durability
requirements
Post by Bryan Call
of a production environment, the messages have to be committed on
multiple
Post by Bryan Call
disks or nodes.
Pulsar has been developed at Yahoo to address these specific
requirements by
Post by Bryan Call
providing a hosted service supporting millions of topics for
multiple
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
tenants.
Post by Bryan Call
The current incarnation of Pulsar has been open-sourced under
Apache
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
license
Post by Bryan Call
in September 2016 and it is the direct evolution of systems that
were
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
developed at Yahoo since 2011.
We believe there is currently no other system that provides a
multi-tenant
Post by Bryan Call
hosted messaging platform capable of supporting a huge number of
topics
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
while
Post by Bryan Call
maintaining strict guarantees for durability, ordering and low
latency.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Current solutions would require to run multiple individual
clusters
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
with
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
additional operational work and capacity overhead.
Since the open sourcing of Pulsar, the development has been done
exclusively
Post by Bryan Call
on the public Github repository and two major releases were
shipped
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
(1.15 and
Post by Bryan Call
1.16), along with multiple minor ones. Several other companies
have
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
expressed
Post by Bryan Call
interest in the project and its future direction.
== Rationale ==
Pulsar is a platform that is built on top of several other Apache
projects. In
Post by Bryan Call
particular, Apache BookKeeper is used to store the data and
Apache
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
ZooKeeper
Post by Bryan Call
is used for coordination and metadata storage. Pulsar is also
interoperable
Post by Bryan Call
out of the box with Apache Storm, to provide an easy to use
stream
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
processing
Post by Bryan Call
solution.
We want to establish a community outside the scope of initial
core
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
developers
Post by Bryan Call
at Yahoo and we believe that the Apache Foundation is a great fit
and
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
long-
Post by Bryan Call
term home for Pulsar, as it provides an established process for
community-
Post by Bryan Call
driven development and decision making by consensus. This is
exactly
Post by vintagewang
Post by Raphael Bircher
the
Post by Sijie Guo
Post by Raphael Bircher
model
Post by Bryan Call
we want to adopt for future Pulsar development.
== Initial Goals ==
The initial goals will be to move the existing codebase to Apache
and
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrate with the Apache development process. Furthermore, we
plan
Post by Pierre Smits
Post by vintagewang
for
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
incremental development, and releases along with the Apache
guidelines.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
== Current Status ==
Pulsar has been in service at large scale for more than 2 years
at
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo. In
Post by Bryan Call
this time around 60 different applications were integrated with
Pulsar.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Other
Post by Bryan Call
companies are evaluating it as well and have been contributing
code
Post by Pierre Smits
Post by vintagewang
to
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
project.
=== Meritocracy ===
We value meritocracy and we understand that it is the basis to
form
Post by Pierre Smits
Post by vintagewang
an
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
open
Post by Bryan Call
community that encourages multiple companies and individuals to
contribute and
Post by Bryan Call
get invested in the project future. We will encourage and monitor
participation and make sure to extend privileges and
responsibilities
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
all
Post by Bryan Call
contributors.
=== Community ===
We have validated, through the interest demonstrated by Pulsar
users
Post by vintagewang
at
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo,
Post by Bryan Call
that a reliable hosted pub-sub messaging platform represent a
very
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
important
Post by Bryan Call
building block for web-scale distributed applications. We believe
that
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
many
Post by Bryan Call
companies can benefit by applying the same model and that
bringing
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Pulsar to
Post by Bryan Call
Apache will get the community to grow stronger.
=== Core Developers ===
Pulsar has been initially developed at Yahoo and received
significant
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
contributions from Yahoo Japan. After having open-sourced the
project
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
there
Post by Bryan Call
have been contribution from developers from several external
companies.
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Alignment ===
Pulsar builds upon other Apache projects such as ZooKeeper and
BookKeeper,
Post by Bryan Call
along with a number of other Apache libraries. We have already
integrated with
Post by Bryan Call
Storm and we envision to integrate with multiple other systems in
the
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
streaming and big data space.
== Known Risks ==
=== Orphaned Products ===
Yahoo has been doing most of the development and, given that many
internal
Post by Bryan Call
platforms depends on Pulsar, it is heavily invested in the long
term
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
success
Post by Bryan Call
of the the project. Yahoo has a long history participating in
open-source
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
projects, and has been also a long time contributor to the Apache
community.
Post by Bryan Call
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open
source
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
process and
Post by Bryan Call
several of them are committers on other Apache projects. We will
be
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
actively
Post by Bryan Call
working with experienced Apache community members to improve our
project.
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Homogenous Developers ===
The initial committers are employed by large companies including
Yahoo,
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo!
Post by Bryan Call
Japan, Salesforce and MercadoLibre. We hope to grow the community
and
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
include additional committers based on their contributions to the
project.
Post by Bryan Call
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both
salaried
Post by Pierre Smits
Post by vintagewang
time
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
and on
Post by Bryan Call
volunteer time, after hours. The majority of initial committers
are
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
paid
Post by Sijie Guo
Post by Raphael Bircher
by
Post by Bryan Call
their employer to contribute to this project. However, they are
all
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
passionate
Post by Bryan Call
about the project, and we are confident that the project will
continue
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
even if
Post by Bryan Call
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely
dependent
Post by Pierre Smits
Post by vintagewang
and
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrated with BookKeeper and ZooKeeper and Storm. There are
ongoing
Post by vintagewang
Post by Raphael Bircher
to
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
integrate with other projects such Apache Spark. We look forward
to
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
collaborating with those communities, as well as other Apache
communities.
Post by Bryan Call
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is
the
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
next
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
logical step for the Pulsar project after open-sourcing the code
in
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
2016. This
Post by Bryan Call
proposal is not for the purpose of generating publicity. Rather,
we
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
want
Post by Sijie Guo
Post by Raphael Bircher
to
Post by Bryan Call
make sure to create a very inclusive and meritocratic community,
outside
Post by Sijie Guo
Post by Raphael Bircher
the
Post by Bryan Call
umbrella of a single company. Yahoo has a long standing history
of
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
contributing to Apache projects and the Pulsar developers and
contributors
Post by Bryan Call
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing
Pulsar,
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that
we
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
would
Post by Bryan Call
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under
Apache
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
License
Post by Bryan Call
v2.0 and the copyright is assigned to Yahoo. All the
contributions
Post by Pierre Smits
Post by vintagewang
from
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
external parties have been received under Apache style CLA. If
Pulsar
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
fulfills
Post by Bryan Call
and passes the conditions for being an Incubator project in the
ASF,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Yahoo
Post by Bryan Call
will transition the source code ownership to the Apache Software
Foundation
Post by Bryan Call
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are
distributed
Post by Sijie Guo
Post by Raphael Bircher
under
Post by Bryan Call
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections
for
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Java,
Post by Bryan Call
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty,
DataSketches,
Post by Bryan Call
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient,
Jetty,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
SnakeYAML
Post by Bryan Call
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI,
Codec,
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
subscriptions)
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
Post by Bryan Call
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
------------------------------------------------------------
---------
org
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
Post by Sijie Guo
Post by Raphael Bircher
------------------------------------------------------------
---------
org
Post by Pierre Smits
Post by vintagewang
Post by Raphael Bircher
------------------------------------------------------------
---------
Liang Chen
2017-05-19 19:36:11 UTC
Permalink
+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-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
Bryan Call
2017-05-22 23:04:39 UTC
Permalink
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
Post by 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.
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 ...
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 of the development and, given that many internal
platforms depends on Pulsar, it is heavily invested in the long term success
of the the project. Yahoo has a long history participating in open-source
projects, and has been also a long time contributor to the Apache community.
=== Inexperience with Open Source ===
Many Pulsar contributors are already familiar with the open source process and
several of them are committers on other Apache projects. We will be actively
working with experienced Apache community members to improve our project.
=== Homogenous Developers ===
The initial committers are employed by large companies including Yahoo, Yahoo!
Japan, Salesforce and MercadoLibre. We hope to grow the community and to
include additional committers based on their contributions to the project.
=== Reliance on Salaried Developers ===
It is expected that Pulsar development will occur on both salaried time and on
volunteer time, after hours. The majority of initial committers are paid by
their employer to contribute to this project. However, they are all passionate
about the project, and we are confident that the project will continue even if
no salaried developers contribute to the project.
=== Relationships with Other Apache Products ===
As mentioned in the Rationale section, Pulsar is closely dependent and
integrated with BookKeeper and ZooKeeper and Storm. There are ongoing to
integrate with other projects such Apache Spark. We look forward to
collaborating with those communities, as well as other Apache communities.
=== An Excessive Fascination with the Apache Brand ===
We are applying to the Incubator process because we think it is the next
logical step for the Pulsar project after open-sourcing the code in 2016. This
proposal is not for the purpose of generating publicity. Rather, we want to
make sure to create a very inclusive and meritocratic community, outside the
umbrella of a single company. Yahoo has a long standing history of
contributing to Apache projects and the Pulsar developers and contributors
understand the implication of making it an Apache project.
== Documentation ==
* Pulsar code base: https://github.com/yahoo/pulsar
* Pulsar documentation: https://github.com/yahoo/pulsar/blob
/master/docs/Documentation.md
* Blog post: [[https://yahooeng.tumblr.com/post/150078336821/
open-sourcing-pulsar-pub-sub-messaging-at-scale|Open-sourcing Pulsar,
Pub-sub Messaging at Scale]]
== Initial Source ==
https://github.com/yahoo/pulsar. This is the exact codebase that we would
migrate to the Apache Software Foundation.
== Source and Intellectual Property Submission Plan ==
The Pulsar source code in Github is currently licensed under Apache License
v2.0 and the copyright is assigned to Yahoo. All the contributions from
external parties have been received under Apache style CLA. If Pulsar fulfills
and passes the conditions for being an Incubator project in the ASF, Yahoo
will transition the source code ownership to the Apache Software Foundation
via the Software Grant Agreement.
== External Dependencies ==
To the best of our knowledge, all of Pulsar dependencies are distributed under
Apache compatible licenses.
=== External dependencies licensed under Apache License 2.0: ===
Athenz, JCommander, HPPC - High Performance Primitive Collections for Java,
FasterXML Jackson, Caffeine Async Cache, GSon, Guava, Netty, DataSketches,
Joda-time, Jna Java Native Access, Lz4-java, AsyncHttpClient, Jetty, SnakeYAML
=== ASF Projects: ===
BookKeeper, ZooKeeper, Storm, Log4J, Commons (BeanUtils, CLI, Codec,
Collections, Configuration, Digester, IO, Lang, Lang3, Logging)
=== Others: ===
* Protobuf (3-clause BSD)
* JLine (BSD License)
* Jersey (CDDL - Version 1.1)
* HdrHistogram (BSD License)
* RocksDB-JNI (3-clause BSD)
* SLF4J API (MIT)
== Required Resources ==
=== Mailing lists ===
=== Git Repository ===
* https://git-wip-us.apache.org/repos/asf/incubator-pulsar
=== Issue Tracking ===
* JIRA Pulsar (PULSAR)
== Initial Committers ==
== Affiliations ==
* Matteo Merli - Streamlio
* Joe Francis - Yahoo
* Rajan Dhabalia - Yahoo
* Sahaya Andrews Albert - Yahoo
* Maurice Barnum - Yahoo
* Ludwig Pummer - Yahoo
* Jai Asher - Yahoo
* Siddharth Boobna - Salesforce
* Nozomi Kurihara - Yahoo! Japan
* Yuki Shiga - Yahoo! Japan
* Masakazu Kitajo - Apple
* Sebastián Schepens - Mercado Libre
* Brad McMillen - Yahoo
* Bobbey Reese - Yahoo
== Sponsors ==
=== Champion ===
* Bryan Call
=== Nominated Mentors ===
* Dave Fisher
* Jim Jagielski
* P. Taylor Goetz
* Francis Liu
=== Sponsoring Entity ===
* The Apache Incubator PMC
---------------------------------------------------------------------
To unsubscribe, e-mail: general-***@incubator.apache.org
For additional commands, e-mail: general-***@incubator.apache.org
Continue reading on narkive:
Loading...