Having only non-organization PMC members nominate new committers could un-level the playing field. 1. Many times contributions might not require a contributor to have direct 1:1 discussion with PMC members outside his org. 2. It would give inordinate power/responsibility to the few non-Amazon active PMC members.
Just my 2 cents. Thanks Anirudh On Wed, Mar 6, 2019 at 7:10 AM Isabel Drost-Fromm <isa...@apache.org> wrote: > > > Am 2. März 2019 15:13:23 MEZ schrieb Carin Meier <carinme...@gmail.com>: > >I wanted to kickoff a discussion about community building. There was an > >excellent blog post from the Apache Beam Community on this > >https://blogs.apache.org/comdev/entry/an-approach-to-community-building > > Needless to say I really love that blog post. > > Other than that there are a couple of question you might ask yourself as a > community: > > How easy is it to patriciate as an outsider, how much communication is > happening outside of dev@? > > How explicit are you about how inclusive you want to be? See also > https://youtu.be/LgB1s3buccI > > How explicit are you about where you need help (including and beyond > coding)? > > How explicit are you with downstream users that some of the inner workings > of Apache projects are build around a scratch your own itch casual > contributions that ideally should be rewarded the same way as full-time > contributions ( > https://blogs.apache.org/foundation/entry/success-at-apache-for-love )? > > I think you want to enable as many ppl as possible - typically only ten > percent of your users turn into contributor, of those only ten percent > trend to be repeat contributors... at least in my experience. > > Just some ideas, > Isabel > -- > Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. >