Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2018-11-22 03:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

2018 | 2017 | 2016 | 2015 | 2014 | 2013 | 2012 | 2011 | 2010 | 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 | 2002 | 2001 | 2000 | 1999 | Pre-organization meetings

Pulsar

21 Nov 2018 [Matteo Merli / Roman]

Report was filed, but display is awaiting the approval of the Board minutes.

17 Oct 2018 [Matteo Merli / Brett]

## Description:

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.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
  - The project has graduated as TLP on Sep. 19th.
  - The community has been following the steps for graduation to update code and website
  - 3 talks on were presented at ApacheCon NA 2018
  - 1 talk was presented at Strata NY in September
  - Community is preparing to release Apache Pulsar 2.2.0. This will be
    the first release after graduation. Biggest features for this release are :
     * Support for interactive SQL querying
     * Added more builtin connectors for Pulsar IO

## Health report:
  - There is healthy grow in the community
  - Activity on the Slack channel has increased considerably. People
    are encouraged to move long discussions and proposals to dev@ and
    @users lists.
  - Several new developers have joined the community providing new
    feature proposals that were discussed with the community and
    finally contributed to the project. We plan to start discussion on
    committer/PMC pipeline soon.

## PMC changes:

 - Currently 23 PMC members
 - No new PMC added in the last month -- All existing PPMC member have joined the PMC

## Committer base changes:

 - Currently 23 committers
 - No new committers added in the last month

## Releases:

  - 2.1.1-incubating was released on Sep. 19th

## Mailing list activity:

 - Activity on the mailing lists remains high with a mixture of new users,
   contributors, and deeper more experienced users and contributors sparking
   discussion and questions and filing bugs or new features.

 - users@pulsar.apache.org:
    - 63 subscribers - 30 emails sent to list in Sep (59 in Aug)

 - dev@pulsar.apache.org:
    - 69 subscribers - 193 emails sent to list in Sep (182 in Aug)


## GitHub activity:

 - 182 PR were merged in the last 1 month
 - 51 Issues were created and 45 closed in the last 1 month

19 Sep 2018

Establish the Apache Pulsar Project

 WHEREAS, the Board of Directors deems it to be in the best interests of
 the Foundation and consistent with the Foundation's purpose to establish
 a Project Management Committee charged with the creation and maintenance
 of open-source software, for distribution at no charge to the public,
 related to a highly scalable, low latency messaging platform running on
 commodity hardware.

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

 RESOLVED, that the Apache Pulsar Project be and hereby is responsible
 for the creation and maintenance of software related to a highly
 scalable, low latency messaging platform running on commodity hardware;
 and be it further

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

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

 * Boyang Jerry Peng <jerrypeng@apache.org>
 * Brad McMillen <bradtm@apache.org>
 * David Fisher <wave@apache.org>
 * Francis Christopher Liu <toffer@apache.org>
 * Hiroyuki Sakai <hrsakai@apache.org>
 * Ivan Brendan Kelly <ivank@apache.org>
 * Jai Asher <jai1@apache.org>
 * Jia Zhai <zhaijia@apache.org>
 * Jim Jagielski <jim@apache.org>
 * Joe Francis <joef@apache.org>
 * Ludwig Pummer <ludwigp@apache.org>
 * Masahiro Sakamoto <massakam@apache.org>
 * Masakazu Kitajo <maskit@apache.org>
 * Matteo Merli <mmerli@apache.org>
 * Nozomi Kurihara <nkurihar@apache.org>
 * P. Taylor Goetz <ptgoetz@apache.org>
 * Rajan Dhabalia <rdhabalia@apache.org>
 * Sahaya Andrews <andrews@apache.org>
 * Sanjeev Kulkarni <sanjeevrk@apache.org>
 * Sebastián Schepens <sschepens@apache.org>
 * Siddharth Boobna <sboobna@apache.org>
 * Sijie Guo <sijie@apache.org>
 * Yuki Shiga <yushiga@apache.org>

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

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

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

 Special Order 7C, Establish the Apache Pulsar Project, was
 approved by Unanimous Vote of the directors present.

19 Sep 2018

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.

Pulsar has been incubating since 2017-06-01.

Most important issues to address in the move towards graduation:

 None

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 Earlier in June there have been few discussions on the private list
 regarding communications regarding Pulsar that were not coming from
 PPMC or that were not respecting the ASF policies.  Clarifications
 followed between PPMC members, mentors and interested parties to
 ensure the mistakes were made in good faith and, in particular, to
 make sure everyone was fully has full understanding of ASF
 policies. There was no other branding related issue after the first
 occurrence.

How has the community developed since the last report?

 The community added 8 new contributors that submitted pull-requests
 which were merged into master.

 The number of users approaching the team on the Slack channel has
 kept steadily increasing since the last report. Many users have
 actively deployed. Pulsar for evaluation and production use cases.

 Different meetups were organized by project members and hosted by
 Yahoo in Sunnyvale and Yahoo Japan in Tokyo. We have presented
 Pulsar's introductions, updates on the state of the projects,
 deep-dives and hands-on tutorial, including recorded podcasts.

 One talk on Pulsar was presented at one at OSCon in July and there
 are several scheduled talks: 2 at ApacheCon in September, and 2
 others at Strata New York in September.

 Since the last report the number of weekly-active-users on the Slack
 channel has increased from 53 to 88.

How has the project developed since the last report?

 28 authors have pushed 494 commits to master in the last 3 months.

 The project has made the its seventh release since joining the
 Apache Incubator (2.1.0-incubating on Aug 2nd).

 This release introduced these new features:

  * Pulsar IO: A connector framework for moving data in and out of
    Apache Pulsar leveraging Pulsar Functions runtime.
  * A number of builtin connectors: (Aerospike, Cassandra, Kafka,
    Kinesis, RabbitMQ, Twitter)
  * Tiered Storage: An extension in Pulsar segment store to offload
    older segments into long term storage (e.g. HDFS, S3). S3 support
    is supported in 2.1 release.
  * Stateful function: Pulsar Functions is able to use State API for
    storing state within Pulsar.
  * Pulsar Go Client
  * Avro and Protobuf Schema support

 Community is actively working on a bug-fix release
 (2.1.1-incubating) and on the next milestone, 2.2 release for which
 the biggest feature will be support for SQL within Pulsar.

 Since June, 5 new PIPs (Pulsar Improvement Proposals) for
 major feature/changes, have been submitted to the wiki and
 discussed in the mailing list.

   PIP 23: Message Tracing By Interceptors
   PIP 22: Pulsar Dead Letter Topic
   PIP 21: Pulsar Edge Component
   PIP 20: Mechanism to revoke TLS authentication
   PIP 19: Pulsar SQL

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [X] Nearing graduation
 [ ] Other:

Date of last release:
 2018-08-02, 2.1.0-incubating

When were the last committers or PPMC members elected?

 2018-06-11 - Ivan Kelly
 2018-06-11 - Jia Zhai

Signed-off-by:

 [X](pulsar) Dave Fisher
    Comments: Looking forward to the graduation resolution.
 [X](pulsar) Jim Jagielski
    Comments:
 [X](pulsar) P. Taylor Goetz
    Comments: Good report. At the urging of mentors, Pulsar completed a
    maturity model evaluation, which I think worked well. They also dealt
    with the branding issue fairly well after realizing how important such
    issues are to the Foundation.
    Currently moving toward graduation, which I support.
 [ ](pulsar) Francis Liu
    Comments:

IPMC/Shepherd notes:

21 Mar 2018

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.

Pulsar has been incubating since 2017-06-01.

Two most important issues to address in the move towards graduation:

 1. Grow the community with new Committers/PPMC members.
 2. Complete the Podling name search tasks

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

 None

How has the community developed since the last report?

 The community added 6 new contributors that submitted pull-requests which
 were merged into master.

 There has been a sharp increase in users approaching the team on the Slack
 channel with many questions on getting started, clarifications,
 troubleshooting. While developers use Slack for informal chatting, the
 predominant usage of Slack has be users support. We have created a tool to
 create daily email digests of the conversation and post it on dev@ and user@
 lists, to comply with ASF policy of. We are also extracting the most
 recurrent questions/answer from Slack and plan to add an FAQ section on the
 website, together with improving documentation in the areas that seemed more
 difficult to users.

 Project members from several companies have organized or participated in
 several meetups, presenting Pulsar's introductions, deep-dives and hands-on
 tutorial, including recorded podcasts. We have several scheduled talks on
 Pulsar at various conferences (such as Strata San Jose on March 8th).


How has the project developed since the last report?

 22 authors have pushed 536 commits to master in the last 3 months.

 The project has made the its third and fourth releases since joining the
 Apache Incubator (1.21.0-incubating on Dec 17th and 1.22.0-incubating on Mar
 6th). Project members are actively working on next milestone, 2.0 release
 that will include several new features including:
  * Topic compaction
  * Redesigned type-safe API with schema support
  * Lightweight compute support

 Overall, since December, 7 new PIPs (Pulsar Improvement Proposals) for major
 feature/changes, have been submitted to the wiki and discussed in the
 mailing list.

 Since the last report the number of weekly-active-users on the Slack channel
 has increased from 27 to 53.


How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [ ] Community building
 [X] Nearing graduation
 [ ] Other:

Date of last release:

 2017-12-13, 1.21.0-incubating
 2018-03-06, 1.22.0-incubating

When were the last committers or PPMC members elected?

 2018-01-19 - Sijie Guo

Signed-off-by:

 [X](pulsar) Dave Fisher
    Comments: They have the release cycle down pretty well. Building community.
 [X](pulsar) Jim Jagielski
    Comments: I would say that the project is still building community and doing so extremely well.
 [X](pulsar) P. Taylor Goetz
    Comments: I would have checked the "Community Building" box, but the podling is doing very well.
 [ ](pulsar) Francis Liu
    Comments:

20 Dec 2017

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.

Pulsar has been incubating since 2017-06-01.

Three most important issues to address in the move towards graduation:

 1. Grow the community with new Committers/PPMC members.
 2. Set up a test cluster to be able to run system tests
 3. Improve release process by having more committers taking part in releases

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None


How has the community developed since the last report?

The community added 5 contributors. There is a healthy discuss on issues related
to development, tools and processes among the community members.
There has been a good number of questions asked by users on the Slack channel
where there are around 33 weekly active users.


How has the project developed since the last report?

18 authors have pushed 150 commits to master in the last 3 months.

The project has made the its second release in the Apache Incubator on October 13th.
The next release (1.21-incubating) is being voted right now in the dev mailing list.
Several design documents with improvement proposals have been submitted to the
wiki and discussed in the mailing list.


How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [X] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 2017-10-13, 1.20.0-incubating

When were the last committers or PPMC members elected?

None


Signed-off-by:

 [X](pulsar) Dave Fisher
    Comments: Seems like the podling is engaging new contributors mostly through slack channel.
              We will need to make sure that enough information is archived by either discussion on dev@ or
              in some other way. They are on their fourth RC in the current release and are doing things correctly.
 [X](pulsar) Jim Jagielski
    Comments: Agreed. Need to push more actual conversation to the dev@ list
 [X](pulsar) P. Taylor Goetz
    Comments: I share the sentiment of other mentors. Would like to more dev@ list traffic vs. slack.
 [ ](pulsar) Francis Liu
    Comments:

20 Sep 2017

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.

Pulsar has been incubating since 2017-06-01.

Three most important issues to address in the move towards graduation:

 1. Grow the community with new Committers/PPMC members.
 2. Set up a test cluster to be able to run system tests
 3. Improve release process by having more committers taking part in releases

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None

How has the community developed since the last report?

The community added 2 contributors. There is a healthy discuss on issues related
to development, tools and processes among the community members.


How has the project developed since the last report?

8 authors have pushed 69 commits to master in the last 30 days.
The project has made the first release from the Apache Incubator on August 9th.
The next release is planned for mid-September. Several design documents with
improvement proposals have been submitted to the wiki and discussed in the
mailing list.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

 [ ] Initial setup
 [ ] Working towards first release
 [X] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 2017-08-09, 1.19.0-incubating

When were the last committers or PPMC members elected?

<none>

Signed-off-by:

 [X](pulsar) Dave Fisher
    Comments: Project is moving towards a second release
 [ ](pulsar) Jim Jagielski
    Comments:
 [x](pulsar) P. Taylor Goetz
    Comments: Pulsar seems to be doing well.
 [ ](pulsar) Francis Liu
    Comments:

16 Aug 2017

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.

Pulsar has been incubating since 2017-06-01.

Three most important issues to address in the move towards graduation:

 1.Make an Apache Release
 2.Set up a test cluster to be able to run system tests
 3.Grow the community with new Committers/PPMC members.


Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

 None

How has the community developed since the last report?

 The community added  one contributor. There is a healthy discuss on issues related to development, tools and processes among the community members.

How has the project developed since the last report?

 6 authors have pushed 21 commits to master and 31 commits to all branches.
 The first release from the incubator is in process. A Release Candidate is up for vote,  scheduled to close on Aug 3. The project has completed setting up its website and project documentation. The community has added a slack
 channel.

How would you assess the podling's maturity?

 The podling is progressing well on its way to it's first Apache release (1.19.0-incubating). There is good participation in governance and in contributions.


How would you assess the podling's maturity?

Please feel free to add your own commentary.

 [ ] Initial setup
 [x] Working towards first release
 [x] Community building
 [ ] Nearing graduation
 [ ] Other:

Date of last release:

 2017-06-17, v 1.18

When were the last committers or PPMC members elected?


Signed-off-by:

 [X](pulsar) Dave Fisher
    Comments: Note v1.18 was a Github release of pre-incubation code. A release vote was just sent to general@incubator.
 [X](pulsar) Jim Jagielski
    Comments:
 [X](pulsar) P. Taylor Goetz
    Comments: Also note that the download page has a note to the effect that the 1.18 release isn't an
              Apache release. The message could be worded better, but at least it is there.
 [ ](pulsar) Francis Liu
    Comments:

19 Jul 2017

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.

Pulsar has been incubating since 2017-06-01.

Three most important issues to address in the move towards graduation:

  1.Finish onboarding the PPMC. We have 11 of 16 fully in place. With two more
    close to setup.
  2.Make an Apache release
  3.Grow the community with new Committers/PPMC members.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

None

How has the community developed since the last report?

This is the first report. All but one of the 16 initial Committers have
participated in one way or another. The existing Pulsar Github was moved to
an Apache Github/GitBox setup. Development discussions are happening on the
dev list.


How has the project developed since the last report?

The project cut a v1.18 release with the old organization just before
conversion. The SGA has been received, the code has switched to
org.apache.pulsar and the license/copyright and headers modified to Apache.

10 authors have pushed 82 commits to the project in the last 30 days.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [x] Initial setup
  [x] Working towards first release
  [ ] Community building
  [ ] Nearing graduation
  [ ] Other:

 Good progress for the first month.

Date of last release:

  2017-06-17,  v1.18

When were the last committers or PPMC members elected?

No one has been added in the last 30 days.

Signed-off-by:

  [X](pulsar) Dave Fisher
     Comments: The project is getting started. Very good so far.
  [x](pulsar) Jim Jagielski
     Comments:
  [x](pulsar) P. Taylor Goetz
     Comments: The project is off to a good start.
  [x](pulsar) Francis Liu
     Comments: