This was extracted (@ 2024-10-16 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.
WARNING: these pages may omit some original contents of the minutes.
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).
Report was filed, but display is awaiting the approval of the Board minutes.
No report was submitted.
## 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.
## Project Status:
- There are no issues requiring board attention at this time.
## Project Activity:
- 3.3.1 was released on August 1st 2024
- 3.2.4 was released on August 1st 2024
- 3.0.6 was released on August 1st 2024
- 3.3.0 was released on June 5th 2024
- Pulsar C++ releases:
- 3.5.1 on April 1st 2024
- Pulsar Python releases:
- 3.5.0 was released on April 13th 2024
- Pulsar Go releases:
- 0.13.1 was released on August 9th 2024
- 0.13.0 was released on July 22nd 2024
- Pulsar reactive client:
- 0.5.6 was released on June 16th 2024
- Pulsar NodeJS client:
- 1.11.1 was released on July 8th 2024
- 1.11.0 was released on April 18th 2024
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-344: Correct the behavior of the public API pulsarClient
.getPartitionsForTopic(topicName)
PIP-345: Optimize finding message by timestamp
PIP-346: Add a simplified configuration file for Pulsar
PIP-347: Extend LTS release process to client SDKs
PIP-349: Add additionalSystemCursorNames ignore list for TTL check
PIP-353: Improve transaction message visibility for peek-messages
PIP-360: Add admin API to display Schema metadata
PIP-366: Support to specify different config for Configuration and Local
Metadata Store
- Pulsar has reached 661 contributors on the main Github repo
(It was 639 contributors in April 2024)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter, 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (5 years ago)
There are currently 84 committers and 43 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
* No new PMC members. Last addition was Baodi Shi on 2024-04-11.
* Jie Chen was added as committer on 2024-06-19
* WenZhi Feng was added as committer on 2024-07-02
## 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:
- 44% decrease in traffic in the past quarter (17 emails compared to 30)
- dev@pulsar.apache.org:
- 28% decrease in traffic in the past quarter (431 emails compared to 591)
## Slack activity:
- 10375 Members (10071 in April 2024)
- 125 Active weekly users (124 in April 2024)
## GitHub activity:
- 741 commits in the past quarter (-40% decrease)
- 90 code contributors in the past quarter (-34% change)
- 451 PRs opened on GitHub, past quarter (-25% change)
- 428 PRs closed on GitHub, past quarter (-24% change)
- 174 issues opened on GitHub, past quarter (-24% change)
- 95 issues closed on GitHub, past quarter (-55% change)
No report was submitted.
No report was submitted.
## 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.
## Project Status:
- Security Advisories
The project has created 8 different security advisories
* 2024-03-12 CVE-2022-34321 Improper Authentication for Pulsar Proxy
Statistics Endpoint
* 2024-03-12 CVE-2024-27135 Improper Input Validation in Pulsar Function
Worker allows Remote Code Execution
* 2024-03-12 CVE-2024-27317 Pulsar Functions Worker's Archive Extraction
Vulnerability Allows Unauthorized File
Modification
* 2024-03-12 CVE-2024-27894 Pulsar Functions Worker Allows Unauthorized File
Access and Unauthorized HTTP/HTTPS Proxying
* 2024-03-12 CVE-2024-28098 Improper Authorization For Topic-Level Policy
Management
* 2024-02-07 CVE-2023-51437 Timing attack in SASL token signature
verification
* 2023-12-20 CVE-2023-37544 Improper Authentication for WebSocket Proxy
Endpoint Allows DoS
All the supported versions of Pulsar have already available patch releases
with fixes for all the issues.
## Project Activity:
- 3.2.0 - Feb 05 2024
- 3.2.1 - Mar 08 2024
- 3.1.2 - Jan 02 2024
- 3.1.3 - Mar 08 2024
- 3.0.3 - Mar 09 2024
- 2.11.3 - Jan 03 2024
- 2.11.4 - Mar 08 2024
- 2.10.6 - Mar 07 2024
- Pulsar C++ releases:
- No releases
- Pulsar Python releases:
- 3.4.0 - Jan 3 2024
- Pulsar Go releases:
- 0.12.0 - Jan 28 2024
- 0.12.1 - Mar 8 2024
- Pulsar reactive client:
- 0.5.2 - Jan 15 2024
- 0.5.3 - Feb 20 2024
- Pulsar NodeJS client:
- 1.10.0 - Feb 6 2024
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-327: Support force topic loading for unrecoverable errors
PIP-328: Add a topicDeleteProtectionEnable configuration option.
PIP-329: Strategy for maintaining the latest tag to Pulsar docker images
PIP-330: getMessagesById gets all messages
PIP-331: Replace configuration
brokerServiceCompactionPhaseOneLoopTimeInSeconds with
brokerServiceCompactionPhaseOneReadTimeoutInSeconds
PIP-332: peek messages from topic subscription with offset value
PIP-334: Create a new admin API: pck (Pulsar Consistency Checker).
PIP-335: Oxia metadata plugin
PIP-336: WASM Support for pulsar-function-java
PIP-337: SSL Factory Plugin to customize SSL Context and SSL Engine
generation
PIP-338: Add default lookup listener and fix inconsistency with listener's
usage between different protocols
PIP-339: Introducing the --log-topic Option for Pulsar Sinks and Sources
PIP-341: Pluggable client metrics tracker interface
PIP-342: Support OpenTelemetry metrics in Pulsar client
PIP-343: Use picocli instead of jcommander
PIP-344: Correct the behavior of the public API
pulsarClient.getPartitionsForTopic(topicName)
PIP-345: Optimize finding message by timestamp
PIP-346: Add a simplified configuration file for Pulsar
- Pulsar has reached 644 contributors on the main Github repo
(It was 639 contributors in December 2023)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter, 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (5 years ago)
There are currently 82 committers and 41 PMC members in this project.
The Committer-to-PMC ratio is 2:1.
Community changes, past quarter:
* David Jensen was added to the PMC on 2024-02-07
* Asaf Mesika was added as committer on 2024-02-20
* Kiryl Valkovich was added as committer on 2024-02-26
## 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:
- 206% increase in traffic in the past quarter (46 emails compared to 15)
- dev@pulsar.apache.org:
- 5% increase in traffic in the past quarter (622 emails compared to 592
## Slack activity:
- 10189 Members (10071 in Dec 2023)
- 142 Active weekly users (140 in Dec 2023)
## 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.
## Project Status:
- There are no issues requiring board attention at this time.
- Responses to the feedback questions:
1. Could you please explain what this pulsar-private repo is all
about? We wanted to have a look, but don't seem to have
access to it.
The repository was created in order for PMC member to review changes
to address security fixes for Pulsar. In general there is a private
discussion that can end up in creating a CVE. In the same way, we
want to make sure we have a fix reviewed and ready to be released
by the time the CVE is published. The repository itself is just a
copy of Pulsar repo, all the PMC members do have access and can
create pull-request for private reviews.
2. You say both that you invited 8 new committers
and that there are no new committers. Can you clarify?
The 8 committers number was a mistake. I carried over the number from
the precedent quarter.
## Project Activity:
- 3.0.2 was released on December 7th 2023
- 3.1.1 was released on October 28th 2023
- 2.11.2 was released on July 18th 2023
- Pulsar C++ releases:
- 3.4.2 on Dec 12th 2023
- Pulsar Python releases:
- 3.3.0 was released on August 29th 2023
- Pulsar Go releases:
- 0.11.1 was released on November 7th 2023
- Pulsar reactive client:
- 0.5.1 was released on December 16th 2023
- Pulsar NodeJS client:
- 1.9.0 was released on July 10th 2023
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-276: Add metric `pulsar_topic_load_times`
PIP-275: Introduce topicOrderedExecutorThreadNum to deprecate
numWorkerThreadsForNonPersistentTopic in configuration
PIP-278: Support pluggable topic compaction service
PIP-280: Refactor CLI for measurement units (time and byte)
PIP-279: Reformat property in generateResponseWithEntry
PIP-281: Add notifyError method on PushSource
PIP 289: Secure Pulsar Connector Configuration
PIP-293: Delete config `disableBrokerInterceptors`
PIP-290: Provide a way to implement WSS E2E encryption and not need to
expose the private key to the WebSocket Proxy
PIP-264: Enhanced OTel-based metric system
PIP-297: Support terminating Function & Connector with the fatal exception
PIP-277: Add `current` option in the Clusters list cmd
PIP-301: Introduce LoadBalanceResources to unify the load-date CRUD
PIP-286: Make the TopicCompactionService to support find entry based
on publishTime or index
PIP-299: Stop dispatch messages if the individual acks will be lostin the
persistent storage
PIP-307: Optimize Bundle Unload(Transfer) Protocol for ExtensibleLoadManager
PIP-302: Introduce refreshAsync API for TableView
PIP-298: Consumer supports specifying consumption isolation level
PIP-307: Support subscribing multi topics for WebSocket
PIP-305: Customize DNS servers to use for Pulsar Client
PIP-300: Add custom dynamic configuration for plugins
PIP-318: Don't retain null-key messages during topic compaction
PIP-312: Use StateStoreProvider to manage state in Pulsar Functions
endpoints
PIP-303: Add optional parameters for getPartitionedStats
PIP-315: Configurable max delay limit for delayed delivery
PIP-320: OpenTelemetry Scaffolding
PIP-300: Add custom dynamic configuration for plugins
PIP-322: Pulsar Rate Limiting Refactoring
PIP-313: Support force unsubscribe using consumer api
- Pulsar has reached 639 contributors on the main Github repo
(It was 623 contributors in June 2023)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter, 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (5 years ago)
There are currently 80 committers and 40 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
* Daniel Blankensteiner was added to the PMC on 2023-11-19
* Yubiao Feng was added to the PMC on 2023-11-07
* David Jensen was added as committer on 2023-11-22
* Yan Zhao was added as committer on 2023-11-06
* Chris Bono was added as committer on 2023-11-18
* Vineeth Polamreddy was added as committer on 2023-10-09
## 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:
- 44% decrease in traffic in the past quarter (17 emails compared to 30)
- dev@pulsar.apache.org:
- 3% decrease in traffic in the past quarter (613 emails compared to 627)
## Slack activity:
- 10071 Members (9807 in June 2023)
- 143 Active weekly users (212 in June 2023)
## GitHub activity:
- 741 commits in the past quarter (-40% decrease)
- 90 code contributors in the past quarter (-34% change)
- 451 PRs opened on GitHub, past quarter (-25% change)
- 428 PRs closed on GitHub, past quarter (-24% change)
- 174 issues opened on GitHub, past quarter (-24% change)
- 95 issues closed on GitHub, past quarter (-55% change)
No report was submitted.
No report was submitted.
No report was submitted.
## 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.
## Project Status:
- There are no issues requiring board attention at this time.
## Project Activity:
- 3.0.0 was released on May 2nd 2023
This was the first LTS release and the first time the Pulsar community
committed to a specific scheduled date plan.
- 2.10.4 was released on April 18th 2023
- 2.9.5 was released on April 19th 2023
- 2.11.1 was released on April 18th 2023
- Pulsar C++ releases:
- 3.2.0 on May 15th 2023
- Pulsar Python releases:
- 3.2.0 was released on June 4th 2023
- Pulsar reactive client:
- 0.3.0 was released on April 26th 2023
- Pulsar NodeJS client:
- 1.8.2 was released on April 20th 2023
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-260: Client consumer filter received messages PIP Stale
PIP-261: Restructure Getting Started section
PIP-262: A limitation for the max size of ack records to persistent PIP
Stale
PIP-264: Enhanced OTel-based metric system
PIP-265: PR-based system for managing and reviewing PIPs
PIP-266: Support batch deletion of tenants, namespaces, topics, and
subscriptions using input files and regex in Pulsar CLI
PIP-267: Support multi-topic messageId deserialization to ack messages
PIP-266: Support batch deletion of tenants, namespaces, topics, and
subscriptions using input files and regex in Pulsar CLI
PIP-268: Add support of topic stats/stats-internal using client api
PIP-269: Add an epoch of cursor to discard outdated reading
PIP-270 Add config to set metadata size threshold for compression.
PIP-271: Add broker health check status into prometheus metrics
PIP-272: Add stateStorageConfig to WorkerConfig
PIP-274: Add metric prefix for topic_load_times
- Pulsar has reached 623 contributors on the main Github repo
(It was 604 contributors in March 2023)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter, 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (4 years ago)
There are currently 75 committers and 37 PMC members in this project.
The Committer-to-PMC ratio is roughly 5:3.
Community changes, past quarter:
* Qiang Zhao was added to the PMC on 2023-03-28
* No new committers. Last addition was Yuri Mizushima on 2023-02-22.
There are though several discussions and open votes for new committers.
## 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:
- 25% decrease in traffic in the past quarter (72 emails compared to 96):
- dev@pulsar.apache.org:
- 16% increase in traffic in the past quarter (1062 emails compared to 914)
## Slack activity:
- 9807 Members (9672 in March 2023)
- 222 Active weekly users (212 in December 2022)
## GitHub activity:
- 823 commits in the past quarter (-23% change)
- 95 code contributors in the past quarter (-14% change)
- 525 PRs opened on GitHub, past quarter (-21% change)
- 518 PRs closed on GitHub, past quarter (-18% change)
- 239 issues opened on GitHub, past quarter (-23% change)
- 337 issues closed on GitHub, past quarter (27% increase)
## 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.10.3 was released on January 3rd 2023
- 2.9.4 was released on January 4th 2023
- 2.11.0 was released on January 10th 2023
- The PMC has approved a new models of Long Term Support, LTS releases
PIP-175: https://github.com/apache/pulsar/issues/15966
The next release will be 3.0 and it's scheduled for May 2nd
- Pulsar C++ releases:
- pulsar-client-cpp 3.1.1 on January 27th 2023
- pulsar-client-cpp 3.1.2 on February 15th 2023
- Pulsar Python releases:
- 3.0.0 was released on December 26th 2022
- 3.1.0 was released on March 13th 2023
- Pulsar reactive client:
- 0.2.2 was released on February 6th 2023
- Pulsar NodeJS client:
- 1.8.0 was released on January 4th 2023
- 1.8.1 was released on March 6th 2023
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-231: Add metric for topic load failed
PIP-232: Introduce thread monitor to check if thread is blocked for long
time.
PIP-234: Support using shared thread pool across multiple Pulsar client
instance
PIP-235: Add metric for subscription backlog size
PIP-236: Record schema in the request and carry to the broker when
subscribing with AUTO_CONSUME schema.
PIP-237: Make PulsarAdmin accessible in SinkContext and SourceContext
PIP-238: Change the aggregatePublisherStatsByProducerName config default to
true
PIP-239: MAX RECONSUME TIMES per Message
PIP-240: A new API to unload subscriptions
PIP-242: Topic name restrictions
PIP-243: Register Jackson Java 8 support modules by default
PIP-244: Refactor ByteBuf release method
PIP-245: Make subscriptions of NonPersistentTopic non-durable
PIP-246: Improved PROTOBUF_NATIVE schema compatibility checks without using
avro-protobuf
PIP-247: Notifications for partitions update
PIP-248: Add metrics for backlog quota event
PIP-249: Pulsar website redesign
PIP-250: Add proxyVersion to CommandConnect
PIP-251: Add snapshot stats in TransactionBufferStats
PIP-252: Configurable compact topic retention
PIP-253: Expose ProducerStats for deadLetterProducer & retryLetterProducer
in java client
PIP-254: Support configuring client version with a description suffix
PIP-255: Support for Idempotent Commit and Abort.
PIP-256: Building Great Developer Experience with API Content
PIP-257: Add Open ID Connect Support to Server Components
PIP-258: Deprecation of the consumer subscribeTopicMode configuration
PIP-255: Assign topic partitions to bundles by round robin
PIP-259: Make the config httpMaxRequestHeaderSize of the pulsar web server
to configurable
- Pulsar has reached 604 contributors on the main Github repo
(It was 594 contributors in December 2022)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter, 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (4 years ago)
There are currently 75 committers and 36 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:3.
Community changes, past quarter:
* Bo Cong was added to the PMC on 2023-01-12
* Nicolò Boschi was added to the PMC on 2023-01-19
* Yunze Xu was added to the PMC on 2022-12-28
* Baodi Shi was added as committer on 2023-01-17
* Tao Jiuming was added as committer on 2023-01-30
* Yuri Mizushima was added as committer on 2023-02-22
* Yubiao Feng was added as committer on 2023-02-07
## 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:
- 25% decrease in traffic in the past quarter (72 emails compared to 96):
- dev@pulsar.apache.org:
- 16% increase in traffic in the past quarter (1062 emails compared to 914)
## Slack activity:
- 9672 Members (9536 in December 2022)
- 212 Active weekly users (218 in December 2022)
## GitHub activity:
- 1052 commits in the past quarter (-26% decrease)
- 111 code contributors in the past quarter (-16% change)
- 654 PRs opened on GitHub, past quarter (-29% change)
- 623 PRs closed on GitHub, past quarter (-46% change)
- 307 issues opened on GitHub, past quarter (-21% change)
- 257 issues closed on GitHub, past quarter (-79% change)
## 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.10.2 was released on October 27th 2022
- 2.8.4 was released on October 4th 2022
- The team is working on releasing next feature version 2.11.0 and 2.9.4
- Pulsar C++ client has been moved to its own dedicated repository
and now has a release schedule independent from main Pulsar repo.
We have performed 2 releases:
- pulsar-client-cpp 3.0.0 on November 10th 2022
- pulsar-client-cpp 3.1.0 on December 12th 2022
- Similarly, Python client has also moved to a separate repo and the
first release is being prepared.
- Pulsar reactive client has also made the first release, 0.1.0 on
December 11th 2022.
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-202: Support latency quantile metric for pulsar read and write PIP Stale
PIP-203: Enable read-only partition, add read and write control for a single
partition
PIP-205: Reactive Java client for Apache Pulsar
PIP-207: Add clientStats API for ProxyStats
PIP-210: Retry producing on next partition if possible when a partition is
not available
PIP-211: Introduce offload throttling
PIP-215: Configurable TopicCompactionStrategy for StrategicTwoPhaseCompactor
and TableView
PIP-216: Support subscription backlog metrics in message counts
PIP-217: LoadShedding Strategy Improment
PIP-218: Consumer batchReceive() single partition every receive
PIP-219: Support full scan and trim ledger
PIP-220: TransferShedder (Only for PIP-192 New Broker Load Manager )
PIP-221: Make TableView support TTL
PIP-222: Add CommandPartitionedTopicMetadata metrics
PIP-223: Add metrics for all Rest Endpoints
PIP-224: Introduce TopicMessageId for consumer's MessageId related APIs
PIP-225: Pulsar Functions fetch parameters from local config file.
PIP-226: Add JWKS support for AuthenticationProviderToken
PIP-227: New API for closing the consumer after waiting for the job to
complete
PIP-228: Refactor Information Architecture of Pulsar Client Documentation
PIP-229: Add a common interface to get fields of the MessageIdData
PIP-230: Modify MessageIdImpl and BatchMessageIdImpl compareTo(MessageId o)
method
- Pulsar has reached 594 contributors on the main Github repo
(It was 572 contributors in June 2022)
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter, 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (4 years ago)
There are currently 71 committers and 33 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:5.
Community changes, past quarter:
* Haiting Jiang was added to the PMC on 2022-10-17
* Christophe Bornet was added as committer on 2022-09-28
* Qiang Huang was added as committer on 2022-10-11
* Lin Chen was added as committer on 2022-11-10
* Zili Chen was added as committer on 2022-11-09
* Cong Zhao was added as committer on 2022-11-19
## 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:
- 25% decrease in traffic in the past quarter (72 emails compared to 96):
- dev@pulsar.apache.org:
- 16% increase in traffic in the past quarter (1062 emails compared to 914)
## Slack activity:
- 9536 Members (8339 in June 2022)
- 218 Active weekly users (232 in September 2022)
## GitHub activity:
- 1434 commits in the past quarter (-6% decrease)
- 131 code contributors in the past quarter (-8% change)
- 913 PRs opened on GitHub, past quarter (-21% change)
- 1163 PRs closed on GitHub, past quarter (6% increase)
- 383 issues opened on GitHub, past quarter (-23% change)
- 1249 issues closed on GitHub, past quarter (219% increase)
## 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.10.1 was released on July 15th 2022
- 2.9.3 was released on July 19th 2022
- 2.7.5 was released on September 3rd 2022
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-201 : Extensions mechanism for Pulsar Admin CLI tools
PIP 198: Standardize PR Naming Convention using GitHub Actions
PIP-195: New bucket based delayed message tracker
PIP-194: Pulsar client: seek command add epoch
PIP-193: Sink preprocessing Function
PIP-192: New Pulsar Broker Load Balancer
PIP-191: Support batched message using entry filter
PIP-190: Simplify documentation release and maintenance strategy
PIP-189: No batching if only one message in batch
PIP-188: Cluster migration or Blue-Green cluster deployment support
in Pulsar
PIP-187: Add API to analyse a subscription backlog and provide a
accurate value
PIP-186: Introduce two phase deletion protocol based on system topic
PIP-184: Topic specific consumer priorityLevel
PIP-183: Reduce unnecessary REST call in broker
PIP-182: Provide new load balance placement strategy implementation for
ModularLoadManagerStrategy
PIP-181: Pulsar Shell
PIP-180: Shadow Topic, an alternative way to support readonly topic
ownership
PIP-179: Support the admin API to check unknown request parameters
PIP-178: Multiple snapshots for transaction buffer
PIP-177: Add the classLoader field for SchemaDefinition
PIP-176: Refactor Doc Bot
- Pulsar has reached 572 contributors on the main Github repo
(It was 538 contributors in June 2022)
- The Pulsar Summit 2022 was held in San Francisco on Aug 18th 2022. It
was the first edition to be held in presential form.
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (4 years ago)
There are currently 66 committers and 32 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:4.
Community changes, past quarter:
* Michael Marshall was added to the PMC on 2022-07-25
* Guo Jiwei was added to the PMC on 2022-08-17
* Xiaoyu Hou was added as committer on 2022-08-17
* Jun Ma was added as committer on 2022-08-29
* Kai Wang was added as committer on 2022-07-28
* Neng Lu was added as committer on 2022-07-06
* Zixuan Liu was added as committer on 2022-06-24
## 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:
- 25% decrease in traffic in the past quarter (72 emails compared to 96):
- dev@pulsar.apache.org:
- 16% increase in traffic in the past quarter (1062 emails compared to 914)
## Slack activity:
- 8339 Members (7320 in June 2022)
- 232 Active weekly users (246 in June 2022)
## GitHub activity:
- 1471 commits in the past quarter (-8% decrease)
- 127 code contributors in the past quarter (-23% change)
- 1138 PRs opened on GitHub, past quarter (+9% change)
- 1050 PRs closed on GitHub, past quarter (+12% change)
- 487 issues opened on GitHub, past quarter (+4% change)
- 378 issues closed on GitHub, past quarter (+36% increase)
## 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.10.0 was released on April 13th 2022
- 2.9.2 was released on April 8th 2022
- 2.8.3 was released on March 21st 2022
- Pulsar Client Go 0.8.1 was released on March 15th 2021
- Pulsar Client Node 1.6.0 was released on Match 10th 2022
- We continue to have a very high number of "Pulsar Improvement
Proposal" getting submitted, discussed and voted by the
community:
PIP-175: Extend time based release process
PIP-174: Provide new implementation for broker dispatch cache
PIP-173: Create a built-in Function implementing the most common basic
transformations
PIP-172: Introduce the HEALTH_CHECK command in the binary protocol
PIP-171: Expose SubscriptionProperties to the Consumer interface
PIP-168: Support zero-copy of NIC to NIC on Proxy
PIP-170: LTS Releases
PIP-167: Make it Configurable to Require Subscription Permission
PIP-166: Function add MANUAL delivery semantics
PIP-161: Exclusive Producer: new mode ExclusiveWithFencing
PIP-165: Auto release client useless connections
PIP-163: Add lowWaterMark check before appending entry to TB
PIP-160: ManagedLedger decorator for batch append enties
PIP-159: Reuse transaction buffer reader
PIP-162: Enable system topic by default
PIP-158: Split client TLS transport encryption from authentication
PIP-157: Bucketing topic metadata to allow more topics per namespace
PIP-156: Build and Run Pulsar Server on Java 17
PIP-155: Drop support for Python2 lifecycle/stale
PIP 154: Max active transaction limitation for transaction coordinator
lifecycle/stale
PIP-152: Support subscription level dispatch rate limiter setting.
PIP-153: Optimize metadataPositions in MLPendingAckStore
PIP-151: Use the system topic to store the bundle load data lifecycle/stale
- Pulsar has reached 538 contributors on the main Github repo
(It was 472 contributors in December 2021)
- The community has released a new updated pulsar.apache.org website, with
improved look and documentation structure.
- The Pulsar Summit 2022 will be held in San Francisco on Aug 18th 2022. It
will be the first edition to be held in presential form.
## Health report:
- There is healthy growth in the community, and several users are starting
to become contributors to the project and engage more and more with
the community. In this quarter 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (4 years ago)
There are currently 61 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is roughly 2:1.
Community changes, past quarter:
* No new PMC members. Last addition was Lari Hotari on 2022-01-16.
* Dezhi Liu was added as committer on 2022-05-24
* Qiang Zhao was added as committer on 2022-05-03
* Nicolò Boschi was added as committer on 2022-04-25
* Xiangying Meng was added as committer on 2022-06-01
* Ruguo Yu was added as committer on 2022-03-23
* Gavin Gao was added as committer on 2022-04-04
* Zike Yang was added as committer on 2022-03-22
## 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:
- 25% decrease in traffic in the past quarter (72 emails compared to 96):
- dev@pulsar.apache.org:
- 16% increase in traffic in the past quarter (1062 emails compared to 914)
## Slack activity:
- 7320 Members (6248 in March 2022)
- 246 Active weekly users (220 in March 2022)
## GitHub activity:
- 1593 commits in the past quarter (-11% decrease)
- 127 code contributors in the past quarter (-23% change)
- 980 PRs opened on GitHub, past quarter (-12% change)
- 896 PRs closed on GitHub, past quarter (-16% change)
- 443 issues opened on GitHub, past quarter (-9% change)
- 308 issues closed on GitHub, past quarter (12% increase)
## 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:
- In the feedback from the last report it was asked to comment on the issues
discussed in
https://lists.apache.org/thread/r768j1xqs43p7dmp15xb6nh98pzl7d45. In the
discussion there was feedback about a blog post published by StreamNative
that was containing ambiguous wording when describing the StreamNative
Ambassador program. The blog post, the tweet and the pages it linked to
were immediately updated to remove any ambiguity and to comply with the
spirit of Apache Way and with the appropriate trademark guidelines.
## Project Activity:
- 2.9.0 was released on November 25th 2021
- 2.9.1 was released on December 20th 2021
- 2.8.2 was released on December 20th 2021
- Pulsar Client Go 0.8.0 was released on February 15th 2021
- Pulsar Client Node 1.5.0 was released on December 20th 2021
- After a more formal process to discuss Pulsar Improvement Proposal was
introduced in the previous quarter, there has been a very significant
uptick in new proposals that were discussed and voted by the community:
PIP 112: Generate Release Notes Automatically
PIP 113: Update Pulsar Website Design & Content PIP
PIP 116: Create Pulsar Writing Style Guide
PIP 117: Change Pulsar Standalone defaults
PIP-118: Do not restart brokers when ZooKeeper session expires
PIP-119: Enable consistent hashing by default on KeyShared dispatcher
PIP-120: Enable client memory limit by default
PIP-121: Pulsar cluster level auto failover
PIP-122: Change loadBalancer default loadSheddingStrategy to
ThresholdShedder
PIP-123: Introduce Pulsar metadata CLI tool
PIP-124: Create init subscription before sending message to DLQ
PIP-126: Support custom and pluggable consumer selector
PIP 129: Introduce intermediate state for ledger deletion
PIP-130: Apply redelivery backoff policy for ack timeout
PIP 131: Resolve produce chunk messages failed when topic level
maxMessageSize is set
PIP 132: Include message header size when check maxMessageSize for
non-batch message on the client side. PIP
PIP 133: Pulsar Functions Add API For Accessing Other Function States
PIP-135: Include MetadataStore backend for Etcd
PIP-136: Sync Pulsar policies across multiple clouds
PIP-137: Pulsar Client Shared State API
PIP-138: Use NarClassLoaderManager to manage all NarClassLoader.
PIP-139: Support Broker send command to close producer/consumer.
PIP-140: Normalize system topic naming rule.
PIP 141: Pulsar BOM
PIP-142: Increase default numHttpServerThreads value to 200 to prevent
Admin API unavailability
PIP-143: Support split bundle by specified boundaries
PIP-144: Making SchemaRegistry implementation configurable
PIP-145: Improve performance of regex subscriptions
PIP-146: ManagedCursorInfo compression
PIP-148: Create Pulsar client release notes
- Pulsar has reached 500 contributors on the main Github repo
(It was 472 contributors in December 2021)
- Next release 2.10.0 is in the process of 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. In this quarter 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (3 years ago)
There are currently 54 committers and 30 PMC members in this project.
The Committer-to-PMC ratio is 9:5.
Community changes, past quarter:
Community changes, past quarter:
- Lari Hotari was added to the PMC on 2022-01-16
- Aloys Zhang was added as committer on 2022-01-25
- Andrey Yegorov was added as committer on 2022-03-07
- Haiting Jiang was added as committer on 2022-01-19
- ZhangJian He was added as committer on 2021-12-31
- Li Li was added as committer on 2021-12-23
## 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:
- 25% decrease in traffic in the past quarter (72 emails compared to 96)
- dev@pulsar.apache.org:
- 16% increase in traffic in the past quarter (1062 emails compared to 914)
## Slack activity:
- 6248 Members (5510 in December 2021)
- 220 Active weekly users (223 in December 2021)
## GitHub activity:
- 795 commits in master in the past quarter (was 1256)
- 121 code contributors in the past quarter (was 113)
- 1068 PRs opened on GitHub, past quarter (9% increase)
- 1022 PRs closed on GitHub, past quarter (12% increase)
- 473 issues opened on GitHub, past quarter (17% increase)
- 270 issues closed on GitHub, past quarter (42% increase)
## 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.8.1 was released on September 10th 2021
- Pulsar Client Go 0.7.0 was released on November 15th 2021
- Pulsar Client Node 1.4.1 was released on October 8th 2021
- We have added a more formal process and guidelines for contributors
for adding new features and signficant changes.
There were several improvement proposals discussed this quarter,
* PIP-111: Add messages produced by Protocol Handler When checking
maxMessagePublishBufferSizeInMB
* PIP 110: Topic metadata
* PIP 108: Add method to help user judge if consumer queue has message PIP
* PIP 107: Introduce the chunk message ID PIP
* PIP 106: Broker extensions to provide operators of enterprise-wide
clusters better control and flexibility
* PIP 105: Support pluggable entry filter in Dispatcher
- Pulsar has reached 472 contributors on the main Github repo
(It was 452 contributors in September 2021)
- The first edition on Pulsar Summit EU was on October 6th,
and the 2nd edition of Pulsar Summit Asia will be on January 15.
- Next release 2.9.0 has went through 4 release candidates and has
been finally approved. Release notes and website updates are
ongoing, before the official announcement.
## 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. In this quarter 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (3 years ago)
There are currently 49 committers and 29 PMC members in this project.
The Committer-to-PMC ratio is roughly 7:4.
Community changes, past quarter:
Community changes, past quarter:
- David Kjerrumgaard was added as committer on 2021-09-30
- Liu Yu was added to the PMC on 2021-11-30
- Michael Marshall was added as committer on 2021-12-02
- Guo Jiwei was added as committer on 2021-10-28
- Marvin Cai was added as committer on 2021-11-14
## 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:
- 28% decrease in traffic in the past quarter (67 emails compared to 92)
- dev@pulsar.apache.org:
- 1% increase in traffic in the past quarter (876 emails compared to 863)
## Slack activity:
- 5510 Members (4393 in September 2021)
- 223 Active weekly users (252 in September 2021)
## GitHub activity:
- 1256 commits in the past quarter (no change)
- 113 code contributors in the past quarter (-22% change)
- 929 PRs opened on GitHub, past quarter (14% increase)
- 865 PRs closed on GitHub, past quarter (13% increase)
- 380 issues opened on GitHub, past quarter (-19% change)
- 182 issues closed on GitHub, past quarter (-25% change)
## 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.7.3 was released on July 27th 2021
- 2.8.0 was released on June 12th 2021
- 2.8.1 was released on September 10th 2021
- Pulsar Client Go 0.6.0 was released on July 25th 2021
- Pulsar Client Node 1.4.0 was released on August 2nd 2021
- Pulsar Client Node 1.3.1 was released on September 17th 2021
- There were a lot of improvement proposals discussed this quarter:
* PIP 104: Add new consumer type: TableView
* PIP 101: Add seek by index feature for consumer
* PIP 100: Pulsar pluggable topic factory
* PIP 97: Asynchronous Authentication Provider
* PIP 95: Smart Listener Selection with Multiple Bind Addresses
* PIP 94: Support level increment delay for ReconsumerLater interface
* PIP 93: Transaction performance tools
* PIP 92: Topic policy across multiple clusters
* PIP 91: Separate lookup timeout from operation timeout
* PIP 90: Expose broker entry metadata to the client
* PIP 89: Structured document logging
* PIP 88: Replicate schemas across multiple
* PIP 87: Pulsar Website Redesign
* PIP 86: Pulsar Functions: Preload and release external resources
- Pulsar has reached 452 contributors on the main Github repo (10%
increase since June 2021 when there were 408 contributors)
- The second edition of Pulsar Summit North America was held on
June 16, 17 2021, the first edition on Pulsar Summit EU was on October 6th,
and the 2nd edition of Pulsar Summit Asia will be on November 20-21.
- There were several talks on Pulsar at ApacheCon and other virtual
conferences and new meetups dedicated to Pulsar were created.
- Next release 2.9.0 is in preparation and expected to be ready
within a week.
## 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. In this quarter 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (3 years ago)
There are currently 46 committers and 28 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- Hang Chen was added to the PMC on 2021-08-01
- Enrico Olivelli was added to the PMC on 2021-08-01
- Lin Lin was added to the PMC on 2021-07-28
- David Kjerrumgaard was added as committer on 2021-09-30
- Rui Fu was added as committer on 2021-08-09
## 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:
- 4% increase in traffic in the past quarter (94 emails compared to 90)
- dev@pulsar.apache.org:
- 19% increase in traffic in the past quarter (921 emails compared to 769)
## Slack activity:
- 4393 Members (3256 in June 2021)
- 252 Active weekly users (496 in June 2021)
## GitHub activity:
- 1066 commits in the past quarter (-8% decrease)
- 121 code contributors in the past quarter (-10% change)
- 730 PRs opened on GitHub, past quarter (-12% change)
- 670 PRs closed on GitHub, past quarter (-16% change)
- 422 issues opened on GitHub, past quarter (1% increase)
- 213 issues closed on GitHub, past quarter (-11% change)
No report was submitted.
## 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.6.4 was released on June 2nd 2021
- 2.7.2 was released on May 11th 2021
- 2.7.1 was released on March 18th 2021
- Pulsar Client Go 0.5.0 was released on May 13th 2021
- There were 3 improvement proposals discussed this quarter:
* PIP 83 : Pulsar client: Message consumption with pooled buffer
* PIP 84 : Pulsar client: Redeliver command add epoch.
* PIP 85 : Add Schema Information to Message in Java Client API
- Pulsar has reached 408 contributors on the main Github repo (8%
increase since December 2020 when there were 375 contributors)
- The serie of by-weekly virtual community meetings for committers
and community members that was started in the past quarter is
still going strong. In both meetings, there are always healthy
discussions on the current issues in the project, new proposals
and ideas bounced with other developers. The participation is
open to anyone and the minutes of these meetings are posted the
dev@ mailing list.
- The second edition of Pulsar Summit North America is scheduled
for next week, June 16, 17 2021. The agenda includes 5 keynotes
and 33 talks, divided in 3 tracks: Deep dive, Use cases and
Ecosystem.
- Next release 2.8.0 is being voted. There have been 2 release
candidates and since the community has found few issues in the
latest build, we are working to prepare a 3rd release
candidate.
## 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. In this quarter 8 contributors were invited as
committers to the project.
## Membership Data:
Apache Pulsar was founded 2018-09-18 (2.5 years ago)
There are currently 44 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 3:2.
Community changes, past quarter:
- No new PMC members. Last addition was Jennifer Huang on 2020-10-25.
- Addison Higham was added as committer on 2021-04-20
- Bo Cong was added as committer on 2021-03-22
- Chris Kellogg was added as committer on 2021-04-20
- Enrico Olivelli was added as committer on 2021-03-16
- Yuto Furuta was added as committer on 2021-05-06
- Lari Hotari was added as committer on 2021-05-02
- Ran Gao was added as committer on 2021-03-23
- Yunze Xu was added as committer on 2021-05-13
## 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:
- 72% increase in traffic in the past quarter (128 emails compared to 74)
- dev@pulsar.apache.org:
- 10% increase in traffic in the past quarter (759 emails compared to 685)
## Slack activity:
- 3256 Members (2650 in March 2021)
- 496 Active weekly users (220 in March 2021)
## GitHub activity:
- 963 commits in the past quarter (-12% change)
- 123 code contributors in the past quarter (8% increase)
- 732 PRs opened on GitHub, past quarter (7% increase)
- PRs closed on GitHub, past quarter (3% increase)
- issues opened on GitHub, past quarter (-5% change)
- issues closed on GitHub, past quarter (-9% change)
## 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.6.3 was released on January 26th 2021
- Pulsar Client Go 0.4.0 was released on March 4th 2021
- This quarter there has been a marked increase of new proposals and very
healthy discussions around them in the community:
* PIP 82: Tenant and namespace level rate limiting
* PIP 81: Split the individual acknowledgments into multiple entries
* PIP 80: Unified namespace-level admin API
* PIP 79: Reduce redundant producers from partitioned producer
* PIP-78: Reduce redundant producers from partitioned producer
* PIP 77: Contribute Supernova to Apache Pulsar
* PIP 76: Streaming Offload
* PIP 75: Replace protobuf code generator
* PIP 74: Pulsar client memory limits
- Pulsar has reached 375 contributors on the main Github repo (11% increase
since December 2020)
- The project has started a series of by-weekly virtual community meetings
for committers and community members to discuss new proposals, technical
issues, or seek assistance on PRs. There are 2 meetings, on in afternoon
(Pacific time) to accommodate Asia and US timezones and the other in
morning (PT) to accommodate Europe and US contributors. The minutes of
these meetings are posted the dev@ mailing list.
- The second edition of Pulsar Summit North America has been announced for
June 16, 17 2021. The call for presentation is closing on March 26th.
- Next release 2.8.0 is still being worked on and expected to be released
within the current month of March.
## 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:
Apache Pulsar was founded 2018-09-18 (2.5 years ago)
There are currently 36 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:7.
Community changes, past quarter:
No new PMC members. Last addition was Jennifer Huang on 2020-10-25.
- Lin Lin was added as committer on 2020-12-24
- Yong Zhang was added as committer on 2021-01-20
## 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:
- 34% decrease in traffic in the past quarter (74 emails compared to 111)
- dev@pulsar.apache.org:
- 1% decrease in traffic in the past quarter (685 emails compared to 686)
## Slack activity:
- 2650 Members (2428 in December 2020)
- 220 Active weekly users (1997 in December 2020)
## GitHub activity:
- 1061 commits in the past quarter (-8% decrease)
- 112 code contributors in the past quarter (-8% decrease)
- 648 PRs opened on GitHub, past quarter (-2% decrease)
- 631 PRs closed on GitHub, past quarter (-3% decrease)
- 399 issues opened on GitHub, past quarter (4% increase)
- 235 issues closed on GitHub, past quarter (-8% decrease)
## 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.7.0 was released on November 25th 2020
- 2.6.2 was released on November 9th 2020
- Pulsar Client Go 0.3.0 was released on November 17th 2020
- Pulsar Manager 0.2.0 was released on September 30th 2020
- Several improvement proposals have been submitted:
* PIP 73: Configurable data source priority for message reading
* PIP 71: Pulsar SQL migrate SchemaHandle to presto decoder
* PIP 70: Introduce lightweight broker entry metadata
- Pulsar has reached 337 contributors on the main Github repo (10% increase
since September 2020)
- First Pulsar Summit Asia was held on November 28-29 2020. There were
3 tracks and 50+ presentation with a mix of English and Mandarin
sessions presentations
Many Pulsar committers and PMC members participated along with
broader Pulsar Asian community.
- Next release 2.8.0 is being worked on and it's expected to be ready
by the end of January 2021.
## 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:
Apache Pulsar was founded 2018-09-18 (2 years ago)
There are currently 34 committers and 25 PMC members in this project.
The Committer-to-PMC ratio is roughly 9:7.
Community changes, past quarter:
- Jennifer Huang was added to the PMC on 2020-10-25
- Hang Chen was added as committer on 2020-10-21
## 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:
- 21% decrease in traffic in the past quarter (115 emails compared to 144)
- dev@pulsar.apache.org:
- 54% increase in traffic in the past quarter (899 emails compared to 583)
## Slack activity:
- 2428 Members (2223 in September 2020)
- 197 Active weekly users (320 in September 2020)
## GitHub activity:
- 1107 commits in the past quarter (45% increase)
- 122 code contributors in the past quarter (12% increase)
- 621 PRs opened on GitHub, past quarter (3% increase)
- 619 PRs closed on GitHub, past quarter (10% increase)
- 365 issues opened on GitHub, past quarter (-7% decrease)
- 244 issues closed on GitHub, past quarter (-10% decrease)
## 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.6.0 was released on June 17th 2020
- 2.6.1 was released on Aug 28th 2020
- Pulsar Client Go 0.2.0 was released on Aug 26th 2020
- Pulsar Client Node 1.2.0 was released on Aug 12th 2020
- Several improvement proposals have been submitted:
* PIP 69: Schema design for Go client
* PIP 68: Exclusive Producer
* PIP 67: Pulsarctl - An alternative tools of pulsar-admin
* PIP 66: Pulsar Function Mesh
- Pulsar has reached 307 contributors on the main Github repo
- First Pulsar Summit conference was 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.
- Pulsar Summit Asia will replicate the same format, while targeting
the APAC community. The conference will take place in virtual form
on Nov. 28-29th and the CFP is now open.
- Next release 2.7.0 is being worked on and it's expected to be ready
for mid October.
- The seconds release fof Pulsar-Manager (0.2.0) 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:
- Apache Pulsar was founded 2018-09-18 (2 years ago)
- There are currently 33 committers and 24 PMC members in this project.
- The Committer-to-PMC ratio is roughly 4:3.
- Community changes, past quarter:
* No new PMC members. Last addition was Penghui Li on 2019-09-16.
* Huanli Meng was added as committer on 2020-09-01
## 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:
- 19% decrease in traffic in the past quarter (152 emails compared to 187)
- dev@pulsar.apache.org:
- 54% increase in traffic in the past quarter (899 emails compared to 583)
## Slack activity:
- 2223 Members (1990 in June 2020)
- 320 Active weekly users (250 in June 2020)
## GitHub activity:
- 621 commits in the past quarter (-32% decrease)
- 86 code contributors in the past quarter (-24% decrease)
- 514 PRs opened on GitHub, past quarter (-2% decrease)
- 475 PRs closed on GitHub, past quarter (-11% decrease)
- 344 issues opened on GitHub, past quarter (12% increase)
- 241 issues closed on GitHub, past quarter (-1% decrease)
==============================
## 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)
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)
## 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)
## 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)
## 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
## 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
## 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
## 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
## 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
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.
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:
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:
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:
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:
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:
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: