I would recommend you look towards what you can do to: A) encourage people who are not coders to contribute. Right now, you only cover coders. Bug management, graphics, documentation, testing, etc. are all necessary.
B) Consider a lower bar towards entry. For example, the SVN project allows anyone who is a committer on another project to commit. I'm not saying that broad but right now, I think you want to encourage people who have high quality but low volume commits still. Regards, KAM -- Kevin A. McGrail VP Fundraising, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 On Sun, Nov 4, 2018 at 7:15 AM Wenli Zhang <[email protected]> wrote: > Hi all, > > As you can see, we have several new contributors making PRs for our > project. > And here we'd like to discuss what criteria is requested for one to become > a committer. > > Here are some of my suggestions to start with: > > 1. We can set a minimum number for required PRs merged or issues > contributed. And we need to discuss the amount for them. How about 3 merged > PRs and 10 issues? > As for the definition of *issues contributed*, I think they should report > to us those issues that they think they've helped or made a progress, and > let us judge. > > 2. I'd suggest candidates send an email for application (maybe to the > private mailing list) and mention the links of their PRs or solved issues > or other contributions (like document fixing, suggestions and etc.). If you > guys agree on this, we shall put a notice about the details on our website > or GitHub about how to apply. > > 3. The quality is even more important, so this should probably also be > assessed by us. > > 4. Another requirement I think necessary is the commitment to contribute, > which may be in the form of making more PRs or fixing document errors, or > answering issue problems. > > 5. After an offline discussion with Dave, Shen Yi and Su Shuang, we think > it is necessary to require those new committers to make PR before their > commits are merged. It's a safer way to make sure our code is at its best > state. > > Please feel free to share your opinions on this topic! > And looking forward to having new committers. :) > > Zhang Wenli > http://zhangwenli.com >
