Users and reporters are just that, users and reporters.  The development
community, which I think is what Justin is referring to, comprises the
contributors.  Please keep in mind that contributors should encompass not
only code slingers, but people who write documentation, review code, answer
user questions, talk about Pekko at conferences, and otherwise contribute
to the healthy community around the code base.

Pekko might be well served by adding "committers" that do not sling code.

just my 2 cents.


On Sun, Jan 21, 2024 at 1:21 AM kerr <hepin1...@gmail.com> wrote:

> I there are several Chinese developers try to contribution and preparing,
>  and even asking me for an issue for they to take care of.
>  And  GreyPlane
> <
> https://github.com/apache/incubator-pekko/issues?q=is%3Apr+is%3Aopen+author%3AGreyPlane
> >
>   just chips in too, and find a fs2 stream issue and report back when he
> prepare the pull request to pekko
>  and there are some of my friends who was contributes to Akka and I think
> they will shows up in Pekko too.
>
> We have a wechat group, nearly 37 members, which very likely to contributes
> to pekko, and a 200+ people in our dingtalk pekko/akka user group( company
> internal).
>
> and two wechat group 500 + 397 people of scala user group in China, I think
> the most problem for us is the firewall ,sometime we can't push/pull.
>
> IMHO,Pekko/Akka is too stable and mutual to gain any issues reporting and
> contributions, and even roland once said, good software is very hard to
> sell.
>
> Take care everyone, and I have some issue, and recovering too.
>
> So I think for the community size, you should calculates the
> users+reporter+contributors.
>
> 何品
>
>
> Matthew de Detrich <matthew.dedetr...@aiven.io.invalid> 于2024年1月21日周日
> 07:38写道:
>
> > As far as I understand, in order to solve the maven name issue we
> basically
> > need to add the `Apache ` prefix to the name := setting
> > in sbt everywhere.
> >
> > > My main concern is the small community size. Only a couple of people
> > contribute significantly to the project. Also, during incubation, only 2
> > committers and 1 PPMC member have been added, we usually expect a minimum
> > of 3.
> >
> > During the entire history of the project we have actually had 3
> significant
> > contributors (PJ Fanning, He-Pin and myself). However
> > in the past few months specifically we have had a few more frequent
> > contributors, i.e. Samuel Ruesca (who is also in PMC now),
> > Jxnu Liguobin, Roiocam (Andy Chen) and Laglangyue have also made quite a
> > few contributions lately. Ontop of this
> > Nicolas Vollmar historically helped out immensely when it comes to
> reviews.
> > I am quite sure I am also missing others
> > (apologies if so).
> >
> > I am not sure what the bar is for "community size" but I would say I
> > personally had some concerns during and just before Christmas
> > but those were alleviated into the new year (not surprising, a lot of
> > people take a break at Christmas).
> >
> > Point about having 3 added committers is taken, thankfully since we have
> > some new people contributing to me this is looking
> > hopefully positive.
> >
> > On Sun, Jan 21, 2024 at 10:15 AM Justin Mclean <jus...@classsoftware.com
> >
> > wrote:
> >
> > > Hi,
> > >
> > > The names here [1] need to use the “Apache Foo” form, which most Apache
> > > projects do. I would guess it’s the name field in your pom. I bring up
> > the
> > > issue with the Spark project with them.
> > >
> > > Kind Regards,
> > > Justin
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org
> > > For additional commands, e-mail: dev-h...@pekko.apache.org
> > >
> > >
> >
> > --
> >
> > Matthew de Detrich
> >
> > *Aiven Deutschland GmbH*
> >
> > Immanuelkirchstraße 26, 10405 Berlin
> >
> > Alexanderufer 3-7, 10117 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >
> > *m:* +491603708037
> >
> > *w:* aiven.io *e:* matthew.dedetr...@aiven.io
> >
>

Reply via email to