In the past period of time, we have initiated several discussions with
other companies and Pulsar community developers, and improved the project
as follows:

As you can see, there are one license [1], one SECURITY file [2], CI
workflows[3], and more commits in the last two weeks [4].
there are one best practice part[5] and execution plan [6].

Secondly, maintaining this repo requires Pulsar PMC's care. now there are
two PMC members who support to maintain it. [7]


[1] license file:
https://github.com/StevenLuMT/pulsar-java-contrib?tab=License-1-ov-file
[2] SECURITY file:
https://github.com/StevenLuMT/pulsar-java-contrib?tab=security-ov-file
[3] CI workflows:
https://github.com/StevenLuMT/pulsar-java-contrib/pull/8/checks
[4] commits in the last two weeks:
https://github.com/StevenLuMT/pulsar-java-contrib/commits/stable/
[5] best practice:
https://github.com/StevenLuMT/pulsar-java-contrib/tree/stable/pulsar-client-common-contrib/src/main/java/org/apache/pulsar/client/api/impl
[6] execution plan:
https://github.com/StevenLuMT/pulsar-java-contrib/issues/7
[7] VOTE for PIP-367:
https://lists.apache.org/thread/td0j8l1c3l93nny0m5smnsdmb91j1n2y

On Sat, Aug 3, 2024 at 5:25 PM xiangying meng <xiangy...@apache.org> wrote:

> Hi all, I want to start a vote on PIP-367: Propose a Contributor
> Repository for Pulsar
>
> You can find the proposal at https://github.com/apache/pulsar/pull/23061
> and
> the discussion thread at
> https://lists.apache.org/thread/75y70j6pqw15271b0tq8j637tb02mrwo
>
> The vote will stay open for at least 48 hours.
>
> BR,
> Xiangying
>

Reply via email to