Apache Logo
The Apache Way Contribute ASF Sponsors

This was extracted (@ 2018-05-16 18: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 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: