[Issue 13220][blog] Publishing a community blog for Pulsar's 10k+ GitHub Stars milestone#13438
[Issue 13220][blog] Publishing a community blog for Pulsar's 10k+ GitHub Stars milestone#13438alicebi-streamnative wants to merge 4 commits intoapache:masterfrom
Conversation
|
@alicebi-streamnative:Thanks for your contribution. For this PR, do we need to update docs? |
|
This post mixes StreamNative news with Apache Pulsar news. |
|
@dave2wave I think Alice already updated the PR before you made the comment. |
|
I see where she removed the links in the second commit which is a good first step. But it will still be confusing about things like FunctionMesh and KoP. Those are great, but they are StreamNative product. For vendor products to be in Apache Pulsar Blog Posts, blog authors need to get input from others and become equitable to the whole ecosystem. That's vendor neutrality. |
| # Get Involved | ||
|
|
||
| * Pulsar 2.8.1 was released in September 2021. [Download it now](https://pulsar.apache.org/en/download/) and try it out! | ||
| * Join the [Pulsar community on Slack](https://apache-pulsar.herokuapp.com/). |
There was a problem hiding this comment.
I think we should mention subscribing to the users or dev mailing lists (in addition to the joining the slack group), as those are the official ways to get involved in the community.
There was a problem hiding this comment.
Note that a reference to https://pulsar.apache.org/en/contact/ would include all of the ways to get connected to the community.
There was a problem hiding this comment.
I have added a CTA to the mailing lists. Thanks!
|
|
||
|  | ||
|
|
||
| The number of contributors overtime is another metric for measuring community engagement. The chart below shows that the number of Pulsar contributors accelerated when Pulsar became a top-level Apache project and the growth rate has continued into 2021. |
There was a problem hiding this comment.
"overtime" should be two words
There was a problem hiding this comment.
Thank you catching that!
|
|
||
| Pulsar 2.8 (released in June 2021) introduced many major updates. The Pulsar Transaction API was added to support atomicity across multiple topics and enable end-to-end exactly-once message delivery guarantee for streaming jobs. Replicated subscriptions was added to enhance Pulsar’s geo-replication. With this feature, a consumer can restart consuming from the failure point in a different cluster in case of failover. | ||
|
|
||
| ## 2. Function Mesh - Simplifying Complex Streaming Jobs in the Cloud |
There was a problem hiding this comment.
what is this ? it looks like it is a StreamNative product.
I agree that we can cite this, but then we should have some space to tell about other recently released projects in the Pulsar ecosystem.
The same applies to the other products cited below
Anonymitaet
added
blog
doc-not-needed
|
@dave2wave |
|
|
||
| ## 3. Protocol Handlers | ||
|
|
||
| Protocol handlers, such as MQTT-on-Pulsar (MoP), allow Pulsar to interact with applications built on other messaging platforms, lowering the barrier to Pulsar adoption. MoP enables MQTT applications to leverage Pulsar’s infinite event stream retention with BookKeeper and tiered storage. |
There was a problem hiding this comment.
I see you removed KoP because it's a project from a Pulsar vendor (StreamNative). But MoP is also a StreamNative project.
dave2wave
left a comment
dave2wave
left a comment
There was a problem hiding this comment.
Please remove MQTT-on-Pulsar.
|
The pr had no activity for 30 days, mark with Stale label. |
|
The pr had no activity for 30 days, mark with Stale label. |
|
The source of blog has been moved to https://github.com/apache/pulsar-site/tree/main/site2/website-next/blog. |
9 participants
Master Issue: #<13220>
Motivation
Publishing a community blog to celebrate Pulsar's 10k+ GitHub Stars milestone.
Modifications
*Created a new file in https://github.com/apache/pulsar/tree/master/site2/website/blog *
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If
yeswas chosen, please highlight the changesDocumentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?
doc-required(If you need help on updating docs, create a doc issue)
no-need-doc(Please explain why)
doc(If this PR contains doc changes)