On 22.03.2016, at 14:42, Sergei Egorov <[email protected]> wrote: > For me, it's too early but if you think that it's fine to include it under > jenkinsci in the current state then I don't mind. Yet I want to control > development of it for now and keep pull request model for it, I hope you > understand :)
We try hard to not interfere with plugin maintainers who want to keep strict control over their plugin development (a CONTRIBUTING.md helps as well). If you respond within two weeks or so to PRs there never should be a situation in which we'd even _ask_ you whether someone else should become co-maintainer. However, if you ever lose interest in the plugin or circumstances prevent you from working on it further, we as the Jenkins project have a way forward if someone volunteers to take over. Note that you can release the plugin to the experimental update center by releasing a version something-alpha-something or something-beta-something, e.g. 1.0-beta-1, making the plugin available to a less Java-proficient audience while . Some explanation on this is here: http://jenkins-ci.org/content/experimental-plugins-update-center -- 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/D225785D-A87C-422A-B9E2-8637C2D60B9C%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
