Hi, On Thu, May 10, 2012 at 9:37 AM, Stefan Bodewig <bode...@apache.org> wrote: > On 2012-05-10, Jukka Zitting wrote: >> However, the one thing I am a bit worried about is that I couldn't >> tell when was the last time you added a new committer to the team. > > Never.
OK. >> Your contribution report [1] shows some people who've contributed lots >> of patches but aren't committers yet. What's up with that? > >> [1] >> https://issues.apache.org/jira/secure/ConfigureReport.jspa?versionId=-1&issueStatus=all&selectedProjectId=12310290&reportKey=com.sourcelabs.jira.plugin.report.contributions%3Acontributionreport&Next=Next > > Many of those contributions happened before Lucene.NET re-entered > incubation, the people have been let down back then and never came back > when Lucene.NET came back to life. That's a good reminder of the importance of bringing in new committers when you can. Without a constant stream of new people a project will eventually lose steam as existing committers lose interest or become otherwise occupied for whatever other reason. > Is there a way to get a contribution report for the last year only or > something similar? Filtering by version likely won't cut it. AFAICT it's not possible by default, though someone with enough Jira skills would likely be able to create such a report. > Of the top ten people some already are committers (Digy and Prescott) > and only two other names ring a bell (I haven't been involved with > Lucene.NET prior to becoming a mentor). Many contributions to > Lucene.NET are one-off contributions and so far almost all contributors > have been content with discussing their issues in JIRA. Unfortunately. OK, thanks for the background. I've been involved with quite a few podlings with similar problems in attracting longer-term contributors. In my experience the best way to solve that problem is to change your mindset of expecting most such people to be just one-off contributors. If you instead treat them as your next new committers and engage with them as peers, many (though of course not all) will respond in kind and actually become more involved. Many developers, especially from commercial backgrounds, tend to treat such contributors as just users reporting a problem. A typical interaction goes like "What's the problem? Do you have a test case? OK, let me fix it (when I get around to it)." A better approach is something like "What's the problem? OK, here are some pointers to the relevant bits in code. How do you think this should be fixed?" BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
