I would also add a couple of things: - General evangelism about the project for increasing user / developer interest. Submit talks to apachecon, blog post, cross-post to zk mailing lists, etc. - Create a label for "newbie" issues, and mention this in "How to start Curator development" page. Add a link to the jira search for the issues labeled "newbie". In HBase, this proved useful to referring newcomers a list of smaller issues to pick from. - If an apache project depends on Curator as a vital component, then the developers there will begin to report bugs or add new features that is required for them.
Enis On Wed, Jan 29, 2014 at 9:19 AM, Luciano Resende <[email protected]>wrote: > On Tue, Jan 28, 2014 at 9:49 AM, Jordan Zimmerman <[email protected] > >wrote: > > > Curator needs more active committers. Please don't take this as a > complaint > > against the current committers, I realize that everyone has other > > priorities. This email is meant to open a discussion on how to get more > > active committers for Curator so that it doesn't totally rely on me. I've > > been extremely busy lately and haven't had much time for OSS projects. > The > > good news is that there are a lot of great patches coming in. But, that > > still means I have to manage them. > > > > I'd appreciate any thoughts. > > > > -Jordan > > > > 1) Mentor the folks providing patches to become committers > 2) Work on a roadmap on the dev list, leave open jiras for roadmap tasks > 3) Encourage others to respond to dev list questions (by not jumping to it > very quickly as well) > > ... > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
