Tison, can we mark this repo as suggested?

On Tue, Aug 8, 2023 at 12:24 PM Matteo Merli <matteo.me...@gmail.com> wrote:

> Thanks Tison,
>
> I fully agree that we should have a clear representation of the actual
> status of the Helm chart, so that users can have the correct expectation.
>
> In particular I think we should have this Helm chart to provide basic
> functionality out of the box and serve as a template/example on top of
> which one can tweek to its specific needs for productions environments.
>
> Since this thread got started, there was no one stepping up, so I guess
> your prevision was also correct :) and reinforces the idea that we
> should reduce a bit the scope and expectation for this Helm chart.
>
>
> --
> Matteo Merli
> <matteo.me...@gmail.com>
>
>
> On Wed, Jul 19, 2023 at 11:26 AM tison <wander4...@gmail.com> wrote:
>
>> Hi Pulsar devs and users,
>>
>> The pulsar-helm-chart[1] was initially developed in the main repo[2] and
>> later moved to its own repo in 2018[3].
>>
>> During the past years, it gets little attention on both development or
>> maintenance, while the Pulsar ecosystem has grown multiple alternatives to
>> distributed pulsar deployment via helm charts or Kubernetes operators -
>>
>> 1. https://github.com/streamnative/charts
>> 2. https://github.com/streamnative/pulsar-operators
>> 3. https://github.com/streamnative/terraform-helm-charts
>> 4. https://github.com/datastax/pulsar-helm-chart
>> 5. https://github.com/datastax/kaap
>>
>> Almost all of the ecosystem projects have better maturity than the
>> upstream
>> one. Although, we in the upstream still recommend the pulsar-helm-chart as
>> the "official" helm chart among the README[4] and docs[5].
>>
>> Of course, it's by-defined the "official" one. But such an advertisement
>> can mislead Pulsar users to choose a half-unmaintained project over better
>> implemented and maintained projects.
>>
>> The upstream community, when it doesn't have the bandwidth to maintain the
>> repo, doesn't have to take the place of an official helm chart. And I saw
>> a
>> pull request proposing to update the README of pulsar-helm-chart[6].
>>
>> I approved that PR and understand that our community makes decisions on
>> mailing lists. Thus, here is the discussion thread to roll up the project
>> status for pulsar-helm-chart.
>>
>> My suggestion is -
>>
>> 1. Accept the PR to update README reflecting the project status and remove
>> the "official" advertisement. It is not wrong, but it can mislead our
>> users
>> as described above.
>> 2. Correspondingly update the word in the docs on the Pulsar website.
>>
>> There can be some arguments that we can pick up the project again and
>> develop and maintain it - this is good.
>>
>> However, generally talk is cheap and real effort is slow to apply. I
>> totally appreciate anyone who is willing to maintain the
>> pulsar-helm-chart,
>> but let's do not block the description updates by such an argument.
>> Instead, update the description, and change it back when the development
>> and maintenance really happen. It also reflects the low traffic during the
>> past few years.
>>
>> Looking forward to your feedback :)
>>
>> Best,
>> tison.
>>
>> [1] https://github.com/apache/pulsar-helm-chart
>> [2]
>> https://github.com/apache/pulsar/tree/master/deployment/kubernetes/helm
>> [3] https://github.com/apache/pulsar-helm-chart/graphs/contributors
>> [4]
>>
>> https://github.com/apache/pulsar-helm-chart/blob/73fe688a439c3ab9b56f2d249f16505292391f4b/README.md
>> [5] https://pulsar.apache.org/docs/3.0.x/deploy-kubernetes/
>> [6] https://github.com/apache/pulsar-helm-chart/pull/367
>>
>

Reply via email to