Yeah, that text could probably be improved; this is covered in more
detail later in the document:
https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Makingchangestoexistingplugins
Unfortunately there's also other places where the communication on this
topic isn't necessarily consistent, e.g.:
https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories
Indeed, pull requests and new maintainers are welcome, but this is
something that comes up often on this mailing list, and the first step
is always to get in touch with the existing maintainers. People get
busy, forget about pull requests, go on holiday, or indeed stop working
on a plugin. So you can imagine it may not be appreciated when somebody
starts committing (or releasing) new code :)
I don't think it makes much sense for somebody to have plugin commit
access if they believe there's no maintainer. Without a maintainer to
review code and unit tests, ensure that breaking configuration changes
are not introduced, and fully test and release new plugin versions,
there's not too much point in just committing code.
According to the wiki page, it seems there are a few people you could
ask for review, including the most recently active one "maselvaraj":
https://wiki.jenkins-ci.org/display/JENKINS/Mesos+Plugin
Regards,
Chris
> --
> 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
jenkinsci-de...@googlegroups.com
> <mailto:
jenkinsci-de...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/jenkinsci-dev/05e06ff0-efc1-4029-ba49-3bafb8196789%40googlegroups.com
> <
https://groups.google.com/d/msgid/jenkinsci-dev/05e06ff0-efc1-4029-ba49-3bafb8196789%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit
https://groups.google.com/d/optout.