On 08.06.2015, at 20:07, Kohsuke Kawaguchi <[email protected]> wrote:
> As a rule of thumb, I'd like to reduce us blocking people who are interested > in contributing, so we should grant the commit access in parallel to > suggesting to talk to the current maintainer. I disagree as well. There's a huge difference between admitting a new plugin into the jenkinsci org, and adding new developers/maintainers to an existing plugin. This policy will only make existing maintainers quit when they come back from a two week vacation and their plugin is completely broken by a new developer who wasn't as familiar with it as he thought, and asked for commit access instead of opening a PR. If the plugin is actively maintained, we should ask new contributors to open PRs instead of immediately granting commit access. _That_ should be our rule of thumb. (Not relevant to this plugin of course, as we have confirmation that the existing maintainer is okay with handing over ownership, but it needed to be mentioned.) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5B26B418-0412-406D-9661-D61BE3379942%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
