I will not enter into debating the long list of grievances here, though I thought I needed to clarify at least 2 points:
1. You can ask any questions and direct any feedback to the PMC (and if you're not happy with the response you can take it all the way up to the ASF Board), but personal attacks are not OK here 2. I don't think it's good looking when you're reacting to people disagreeing with you by claiming they either are incompetent or have some hidden agenda. Perhaps trying to understand why they disagreed with you would be more helpful. Matteo -- Matteo Merli <matteo.me...@gmail.com> On Tue, Mar 5, 2024 at 7:22 PM Kalwit S <skalwit...@gmail.com> wrote: > Congratulations Asaf. > > Btw, does the Apache project have any promotion criteria for committers? I > looked at Asaf's commits at > https://github.com/apache/pulsar/commits?author=asafm and found that 99% > of the commits are simple documentation changes and 1% are related to PIP > monitoring. Most of the PIP monitoring involves adding plugins to existing > metrics APIs. He has also contributed to the PIP reviews, but his > contribution is more philosophical rather than technical. Most of his > comments are comparing Pulsar to other projects, rather than focusing on > the internal insights that Pulsar brings to the table. Our team has been > running production traffic using Apache Pulsar for over a year now. We have > tried several different versions of Pulsar (which we have to constantly > upgrade due to unknown issues in live production traffic) and have never > seen a stable version of Pulsar. Our team has also tried to submit multiple > enhancements and also PIP, but most of them are bogged down by reviewers > who are very new to Pulsar, might not understand messaging correctly, or > don’t find such enhancements useful for their usecases. > I would say that most of these reviewers are brand new to Pulsar, and > almost all of them are from the same company that is also the provider of > Pulsar. The same company controls Pulsar, prevents others from > contributing, and avoids having non-pulsar committers. This is why we > wanted to replace our existing Kafka cluster with Pulsar but we see no > difference in Pulsar provider and Confluent because Pulsar is also largely > controlled by one provider and this company's reviewers are not well-versed > in such systems. > In addition, we can see that almost all the reviewers are from the same > company, and PIP approval requires 3+ votes, which means only specific > reviewers belonging to one company participate and because of that, no one > can promote their improvements without the approval of the provider > company. The Pulsar community needs to break away from the monopolies of > the provider companies, start focusing on stable releases, and let other > companies make their enhancements to meet their requirements, and > experienced contributors or Pulsar creators should be active to prevent > unfairness in the community. > > On Tue, Mar 5, 2024 at 3:31 PM Kalwit S <skalwit...@gmail.com> wrote: > > > Congratulations.! > > > > > > On Tue, Feb 20, 2024 at 8:50 AM Lari Hotari <lhot...@apache.org> wrote: > > > >> The Apache Pulsar Project Management Committee (PMC) has invited > >> Asaf Mesika https://github.com/asafm to become a committer and we > >> are pleased to announce that he has accepted. > >> > >> Welcome and Congratulations, Asaf Mesika! > >> > >> Please join us in congratulating and welcoming Asaf onboard! > >> > >> Best Regards, > >> > >> Lari Hotari > >> on behalf of the Pulsar PMC > >> > > >
