ApacheCon is Coming 9-12 Sept. 2019 - Las Vegas The Apache Software Foundation
Apache 20th Anniversary Logo

Community-led development "The Apache Way"

Apache Support Logo

This was extracted (@ 2020-09-29 22: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.

Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).

Pulsar

16 Sep 2020 [Matteo Merli / Patricia]

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

17 Jun 2020 [Matteo Merli / Justin]

==============================

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

## Project Activity:
  - 2.5.1 was released on May 10th 2020
  - 2.5.2 was released on May 19th 2020
  - Pulsar Client Go 0.1.0 was released on Apr 2nd 2020
  - Pulsar Client Node 1.1.0 was released on Feb 17th 2020

  - The project has released 2.5.2 in May that included fixes in the
    stable 2.5.x branch.

  - Several improvement proposals have been submitted:
     * PIP 65: Adapting Pulsar IO Sources to support Batch Sources
     * PIP 64: Introduce REST endpoints for producing, consuming and
               reading messages
     * PIP 63: Readonly Topic Ownership Support
     * PIP 62: Move connectors, adapters and Pulsar Presto to separate
               repositories
     * PIP 61: Advertised multiple addresses
     * PIP 60: Support Proxy server with SNI routing

  - First Pulsar Summit conference is being held on June 17th and 18th
    2020. This has been rescheduled as a virtual conf from the
    in-person event that was earlier scheduled for March 2020.
    Many Pulsar committers and PMC members are participating along with
    several users presenting on their experiences and their journeys
    in the Pulsar adoption.

  - On Jun 26th, at Spark AI Summit, Matteo and Karthik are presenting on
    "Apache Pulsar: The Next Generation Messaging and Queuing System

  - Next release 2.6.0 is being voted
  - The seconds released for Pulsar Go client (0.1.1) is being voted.

## Health report:
  - There is healthy grow in the community, several users are starting to
    become contributors to the project and engaging more and more with
    the community.

## Membership Data:
  - There are currently 32 committers and 24 PMC members in this project.
  - The Committer-to-PMC ratio is 4:3.

  - Community changes, past quarter:
    * No new PMC members. Last addition was Penghui Li on 2019-09-16.
    * Daniel Blankensteiner was added as committer on 2020-03-19
    * Yijie Shen was added as committer on 2020-05-08


## Community Health:

 - 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:
    - 152 subscribers (+12 from March 2020) - 45% increase in traffic in
      the past quarter (194 emails compared to 133):

 - dev@pulsar.apache.org:

    - 196 subscribers (+22 from March 2020) - 46% increase in traffic in
      the past quarter (609 emails compared to 417):


## Slack activity:
  * 1990 Members (1673 in March 2020)
  * 258  Active weekly users (234 in March 2020)


## GitHub activity:

 - 767 commits in the past quarter (23% increase)
 - 116 code contributors in the past quarter (30% increase)
 - 5660 Stars (up from 5218 in March 2020)
 - 483 PRs opened on GitHub, past quarter (9% increase)
 - 290 issues opened on GitHub, past quarter (-18% decrease)
 - 231 issues closed on GitHub, past quarter (-1% decrease)

18 Mar 2020 [Matteo Merli / Daniel]

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.

## Project Activity:
  - The project has released 2.5.0 in December that included Highlights
    include:
     * [PIP-41] Introduce Protocol Handler API
  * [PIP-45] Pluggable metadata interface
  * [PIP-44] Separate schema compatibility checker for producer and consumer
  * [PIP-43] Producer send messages with different schema
  * [PIP-51] Introduce sticky consumer
  * [PIP-38] Support batch receive in java client.
  * [PIP-52] Add support of dispatch throttling relative to publish-rate
  * Upgraded to ZooKeeper 3.5
  * Upgraded to BookKeeper 4.10.0
  * HDFS offloader for Pulsar tiered storage
  - Work is underway for next release 2.6.0
  - Pulsar NodeJS client library 1.1.0 was released on Feb 18th.

  - Several improvement proposals have been submitted:
     * PIP 59: gPRC Protocol Handler
     * PIP 58: Support Consumers Set Custom Retry Delay
     * PIP 57: Improve Broker's Zookeeper Session Timeout Handling
     * PIP 56: Python3 Migration
     * PIP 55: Refresh Authentication Credentials
     * PIP 54: Support acknowledgement at batch index level
     * PIP 53: Contribute DotPulsar to Apache Pulsar
     * PIP 52: Message dispatch throttling relative to publish rate

  - Several talk on Pulsar were presented at conferences and meetups, in US,
    Europe and China, both by Pulsar committer/PMC members as well as other
    members of the community. Non-exhaustive list:
     * A Pulsar meetup was held on Jan 15 in Toronto. Cory Darby gave a talk
       about
       "RIP Apache Kafka, long live Apache Pulsar" and Tamer A shared about
       "Pulsar in Action, getting your hands dirty with Pulsar".
     * Apache IoTDB X Apache Pulsar meetup was held on Jan 4 in Beijing. Jia
       Zhai from StreamNative shared about "Apache Pulsar: from messaging
       system to event streaming platform". Besides, Guangning E from
       StreamNative gave a talk about
       "How to connect Apache Pulsar to IoTDB with Pulsar IO".
     * Pulsar Summit SF was initially scheduled for Apr 28th though due to
       current situation it has been postponed to a TBD date after summer.

  - Work is ongoing for next release (2.6.0) and for to reach the first
    release for the native Go client library.

## Community Health:
  - There is healthy growth in the community, several users are starting to
    become contributors to the project and engaging more and more with
    the community.

## Membership Data:
  - There are currently 30 committers and 24 PMC members in this project.
  - The Committer-to-PMC ratio is 5:4.

  - Community changes, past quarter:
   * No new PMC members. Last addition was Penghui Li on 2019-09-16.
   * No new committers. Last addition was Liu Yu on 2019-11-28.

## Releases:

  - 2.5.0 was released on Dec. 6th 2019
  - Pulsar-client-node 1.1.0 was released on Feb. 18th 2020

## 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:
    - 140 subscribers (+10 from Dec 2019) - 137 emails sent to list in
last 3 months

 - dev@pulsar.apache.org:
    - 174 subscribers (+21 from Dec 2019) - 425 emails sent to list in
last 3 months

## Slack activity:
  * 1673 Members (1311 in Dec 2019)
  * 234 Active weekly users (160 in Dec 2019)

## GitHub activity:

 - 438 PRs from 88 contributors (+11) were merged in the last 3 months
 - 278 Issues were created and 165 closed in the last 3 months
 - 5218 Stars (up from 4608 in Dec 2019)

18 Dec 2019 [Matteo Merli / Shane]

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

## Project Activity:
  - The project has released 2.4.2 in December and it is in the process
    of releasing the next feature release 2.5.0.
    Highlights include:
     * [PIP-41] Introduce Protocol Handler API
* [PIP-45] Pluggable metadata interface
* [PIP-44] Separate schema compatibility checker for producer and consumer
* [PIP-43] Producer send messages with different schema
* [PIP-51] Introduce sticky consumer
* [PIP-38] Support batch receive in java client.
* [PIP-52] Add support of dispatch throttling relative to publish-rate
* Upgraded to ZooKeeper 3.5
* Upgraded to BookKeeper 4.10.0
* HDFS offloader for Pulsar tiered storage

  - Several talk on Pulsar were presented at conferences and meetups,
in US, Europe
    and China, both by Pulsar committer/PMC members as well as other members of
the community. Non-exaustive list:
* Pulsar meetup in Shanghai on Nov. 20th
* Query Pulsar Streams using Apache Flink at Flink Forward Berlin by Sijie Guo
     * Apache Pulsar - Flexible Pub-Sub and Compute backed by durable
log storage
   at IEEE Big Data - Real-time streaming workshop by Matteo Merli
* Go in Pulsar by Xiaolong Ran at Github meetup
* Stream processing with Apache Pulsar by Bruno Bonnin
* Scalable logs processing with Pulsar at Paris Data Eng by Alexandre Duval and
   Quentin Adam
* Apache Pulsar 101: architecture, concepts & benchmark at Devoxx BE by Quentin
   Adam and Steven Le Roux

  - The first release of Pulsar Manager was released on Nov. 25th

  - Work is ongoing for next release (2.6.0) and for to reach the first release
    for the native Go client library.

## Community Health:
  - There is healthy grow in the community, several users are starting to
    become contributors to the project and engaging more and more with
    the community.
  - Activity on the Slack channel is still high, many first time users come
    to ask questions while getting started. There are 160 weekly active users
    on the channel, up from 148 in Sep.

## Membership Data:

 - Currently 24 PMC members
 - No new PMC members added since last report.
 - Last PMC member added:
   - Penghui Li - Sep 10th

 - Currently 30 committers
 - 2 committers were added since last report
   - Guangning E - Oct 8th
   - Liu Yu - Dec 3rd

## Releases:

  - 2.4.2 was released on Dec. 4th 2019

## 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:
    - 130 subscribers (+9 from Sep 2019) - 205 emails sent to list in
last 3 months

 - dev@pulsar.apache.org:
    - 153 subscribers (+18 from Sep 2019) - 390 emails sent to list in
last 3 months

## Slack activity:
  * 1311 Members (1041 in Sep 2019)
  * 160 Active weekly users (148 in Sep 2019)

## GitHub activity:

 - 339 PRs from 71 contributors were merged in the last 3 months
 - 278 Issues were created and 165 closed in the last 3 months
 - 4608 Stars (up from 4130 in Sep 2019)

18 Sep 2019 [Matteo Merli / Rich]

## 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 released 2.4.0 in June and a subsequent patch release
    2.4.1 in August. This was a very big release that included many new
    features and improvements. Highlights include:
     * Key-Shared Subscription type
     * Delayed message delivery
     * Negative acknowledgments
     * Replicated subscriptions
     * Kerberos authentication
     * Go functions
     * Schema versioning

  - Conferences talk on Pulsar
    * 5 Pulsar talks were presented at Apache Con NA 2019
      - Using Apache Pulsar to Provide Real-Time IoT Analytics on the Edge by
        David Kjerrumgaard
      - Life beyond Kafka with Apache Pulsar - Alvaro Santos Andrés
      - Building Zhaopin's enterprise event bus based on Apache Pulsar by Jia
        Zhai and Penghui Li
      - Interactive querying of streams using Apache Pulsar - Boyang Jerry
        Peng
      - Serverless Event Streaming with Pulsar Function: Use Cases and Best
        Practices by Xiaolong Ran
    * Two talks are scheduled for Strata NY in September:
      - Posttransaction processing using Apache Pulsar at Narvar, by Karthik
        Ramasamy
      - How Orange Financial combats financial fraud over 50M transactions a
        day using Apache Pulsar, by Sijie Guo
    * One talk is scheduled for Flink Forward Berlin in October:
      - Query Pulsar Streams using Apache Flink by Sijie
    * One keynote on Pulsar at the "Workshop on Real-time & Stream Analytics"
      at IEEE Big Data conference in Dec will be presented by Matteo Merli
    * Several Pulsar specific meetups were held in China, Japan and US. Other
      talks on Pulsar were also hosted in other meetups.

  - Work is ongoing for next release (2.5.0) for which we plan to include:
    * Transactional API
    * Ruby Client
    * Pulsar manager UI
    * Kafka protocol handler
  - Since last report sever PIPs (Pulsar improvement proposals) were
    submitted:
    * PIP 38: Batch Receiving Messages
    * PIP 39: Namespace Change Events
    * PIP 40: Pulsar Manager
    * PIP 41: Pluggable Protocol Handler
    * PIP 42: KoP - Kafka on Pulsar
    * PIP 43: producer send message with different schema
    * PIP 44: Separate schema compatibility checker for producer and consumer

  - New client libraries have seen signifant work:
    * NodeJS client: https://github.com/apache/pulsar-client-node
    * Native Go client: https://github.com/apache/pulsar-client-go
    * Ruby
    * C# https://github.com/danske-commodities/dotpulsar
    * F# https://github.com/fsharplang-ru/pulsar-client-dotnet

## Health report:
  - There is healthy grow in the community, several users are starting to
    become contributors to the project and engaging more and more with the
    community.
  - Activity on the Slack channel is still high, many first time users come to
    ask questions while getting started. There are 148 weekly active users on
    the channel, up from 103 in June.

## PMC changes:

 - Currently 24 PMC members
 - 1 new PMC member added since last report:
   - Penghui Li - Sep 10th

## Committer base changes:

 - Currently 28 committers
 - 4 committers were added since last report
   - Jennifer Huang - Jun 24th
   - Ali Ahmed - Jul 25th
   - Fangbin Sun - Jul 25th
   - Xiaolong Ran - Jul 25th

## Releases:

  - 2.4.0 was released on Jun. 30th 2019
  - 2.4.1 was released on Aug. 30th 2019

## 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:
    - 121 subscribers (+18 from Jun 2019) - 110 emails sent to list in last 3
      months

 - dev@pulsar.apache.org:
    - 135 subscribers (+27 from Jun 2019) - 290 emails sent to list in last 3
      months

## Slack activity:
  * 1041 Members
  * 148 Active weekly users

## GitHub activity:

 - 328 PRs from 60 contributors were merged in the last 3 months
 - 261 Issues were created and 165 closed in the last 3 months
 - 4130 Stars (up from 3540 in June 2019)

19 Jun 2019 [Matteo Merli / Danny]

## 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 released 2.3.2 in May. This was a bug fix release for the
    2.3 branch.
  - 5 Pulsar talks are being presented at Apache Con NA 2019
      - Using Apache Pulsar to Provide Real-Time IoT Analytics on the Edge by
        David Kjerrumgaard
      - Life beyond Kafka with Apache Pulsar - Alvaro Santos Andrés
      - Building Zhaopin's enterprise event bus based on Apache Pulsar by Jia
        Zhai and Penghui Li
      - Interactive querying of streams using Apache Pulsar - Boyang Jerry
        Peng
      - Serverless Event Streaming with Pulsar Function: Use Cases and Best
        Practices by Xiaolong Ran
  - Several meetups either centered on Pulsar or with Pulsar presentations, in
    China, US and France.
  - Community is working toward 2.4.0 release for mid-June. Highlights for
    this release will include:
     - Kerberos authentication
     - Negative Acknowledgment
     - Key-Shared Subscription type
     - Replicated Subscriptions
     -
  - Since last report sever PIPs (Pulsar improvement proposals) were
    submitted:
    * PIP 37: Large message size handling in Pulsar
    * PIP 36: Max Message Size
    * PIP 35: Improve topic lookup for topics that have high number of
      partitions
    * PIP 33: Replicated subscriptions

## Health report:
  - There is healthy grow in the community
  - Activity on the Slack channel is still high, many first time users come to
    ask questions while getting started. There are 110 weekly active users on
    the channel.

## PMC changes:

 - Currently 23 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Sahaya Andrews on Wed Sep 19 2018

## Committer base changes:

 - Currently 24 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Penghui Li at Fri Dec 07 2018
 - There are 4 new committers currently being voted

## Releases:

  - 2.3.1 was released on April 12th 2019
  - 2.3.2 was released on May 30th 2019

## 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:
    - 103 subscribers (+9 from March 2019) - 103 emails sent to list in last 3
      months

 - dev@pulsar.apache.org:
    - 108 subscribers (+11 from March 2018) - 241 emails sent to list in last
      3 months


## GitHub activity:

 - 464 PR from 66 contributors were merged in the last 3 months (up from 386
   PRs and 47 contributors)
 - 231 Issues were created and 161 closed in the last 3 months

20 Mar 2019 [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 released 2.3.0 in February. This was a very big release
    that included many new features and improvements. Highlights include:
     * Kubernetes support in Pulsar functions
     * New Pulsar IO connectors: Change data capture with Debezium, MongoDB,
       Elastic Search, HBase and local files source and sink.
     * Token based authentication
     * Schema support in Python client library
     * Function state API in Python
  - Several meetup and conferences talk on Pulsar
    * Two talks are scheduled for Strata SF in March:
      - How Zhaopin.com built its enterprise event bus using Apache Pulsar
        from Sijie and Penghui
      - Reducing stream processing complexity using Apache Pulsar Functions
        from Jowanza Joseph and Karthik Ramasamy
  - A patch release (2.3.1) is being prepared to address all the issues
    reported in 2.3.0 release
  - Work is ongoing for next release (2.4.0), scheduled for end of March
    for which we plan to include:
    * NodeJS client library
    * Negative acknowledgments
    * Replicated subscription state
    * Kerberos authentication plugin
  - Since last report several PIPs (Pulsar improvement proposals) were
    submitted:
    * PIP 32: Go Function API, Instance and LocalRun
    * PIP 31: Transaction Support
    * PIP 30: change authentication provider API to support mutual
      authentication
    * PIP 28: Pulsar Proxy Gateway Improvement
    * PIP 29: One package for both pulsar-client and pulsar-admin
    * PIP 26: Delayed Message Delivery

## Health report:
  - There is healthy grow in the community
  - Activity on the Slack channel is still high, many first time users come to
    ask questions while getting started. There are 103 weekly active users on
    the channel, up from 92 in November.

## PMC changes:

 - Currently 23 PMC members
 - No new PMC added since last report

## Committer base changes:

 - Currently 24 committers
 - Last committer added: Penghui Li - Dec 7th

## Releases:

  - 2.2.1 was released on Dec. 31st 2018
  - 2.3.0 was released on Feb. 20th 2019

## 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:
    - 94 subscribers (+10 from Dec 2018) - 103 emails sent to list in last 3
      months

 - dev@pulsar.apache.org:
    - 97 subscribers (+17 from Dec 2018) - 241 emails sent to list in last 3
      months


## GitHub activity:

 - 386 PR from 47 contributors were merged in the last 3 months (up from 131)
 - 197 Issues were created and 125 closed in the last 3 months

19 Dec 2018 [Matteo Merli / Ted]

## 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.
  - Several meetup and conferences talk on Pulsar
    * Ivan Kelly has presented Pulsar at BigData Spain on Nov 15th
    * A Pulsar intro talk was presented at LeadDevAustin
    * Apache Pulsar meetup scheduled for Dec 15th in Shanghai
      with talk from several members of community
    * Sijie and Jia will present "Unifying the Batch and Stream Elastic Processing
      with Apache Pulsar and Apache Flink" at Flink Forward in Beijing on Dec 20th.
  - A patch release (2.2.1) is being prepared to address all the issues reported
    in 2.2.0 release
  - Work is ongoing for next release (2.3.0), scheduled for end of December for which
    we plan to include:
    * Apache BookKeeper 4.9.0
    * Schema support for C++ and Python
    * Token based authentication

## Health report:
  - There is healthy grow in the community
  - Activity on the Slack channel is still high, many first time users come
    to ask questions while getting started. There are 103 weekly active users
    on the channel, up from 92 in November.
  - Several new developers have joined the community providing new
    feature proposals that were discussed with the community and
    finally contributed to the project. We have voted one new committer and we
    plan to start discussion on more committers/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 24 committers
 - 1 Committer added in the last month (Penghui Li - Dec 7th)

## Releases:

  - 2.2.0 was released on Oct. 24th

## 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:
    - 84 subscribers (+5 from Nov 2018) - 32 emails sent to list in Nov (35 in Oct)

 - dev@pulsar.apache.org:
    - 80 subscribers (+5 from Nov 2018) - 40 emails sent to list in Nov (99 in Oct)


## GitHub activity:

 - 144 PR from 24 contributors were merged in the last 1 month (up from 131)
 - 57 Issues were created and 52 closed in the last 1 month

21 Nov 2018 [Matteo Merli / Roman]

## 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.
  - 1st Pulsar meetup in Beijing on Oct 20th was very well attended
  - Community has released Apache Pulsar 2.2.0. This has been the first
    release after graduation. Biggest features for this release are :
     * Pulsar Java Client Interceptors
     * Integration of functions and io with schema registry
     * Dead Letter Topic
     * Apache Flink Source connector
     * JDBC Sink Connector
     * HDFS Sink Connector
     * Google Cloud Storage Offloader
  - Work is ongoing for next release (2.3.0) for which we plan to include:
    * Apache BookKeeper 4.9.0
    * Schema support for C++ and Python
    * Token based authentication

## Health report:
  - There is healthy grow in the community
  - Activity on the Slack channel is still high, many first time users come to
    ask questions while getting started. There are 92 weekly active users on
    the channel.
  - 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.2.0 was released on Oct. 24th

## 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:
    - 79 subscribers (+16 from Oct 2018) - 35 emails sent to list in Oct (30
      in Sep)

 - dev@pulsar.apache.org:
    - 75 subscribers (+6 from Oct 2018) - 99 emails sent to list in Sep (193
      in Sep)


## GitHub activity:

 - 131 PR from 26 contributors were merged in the last 1 month
 - 60 Issues were created and 45 closed in the last 1 month

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: