Maintainer role clarification

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Maintainer role clarification

nicolas de loof-2
Hi!

Over the years I've been working with Jenkins, I've come to adopt or just patch a few plugins. In some cases, I was only delivering a fix, not really adopting the plugin per-se. Many of them I've been contacted to review  pull requests while I only provided a fix for a customer but don't use by myself, so hardly can maintain. As this might have led to some confusion nowadays, I would like to clarify for future requests that I don't consider myself an active maintainer on any plugin.  So I would like to formally tell the community that anyone can consider "my" plugins ready to be adopted if there isn't already another active maintainer. This typically includes the few docker-*-plugins I've created or maintained past years. Some people using them for production would be better candidate for a maintener role.

I hope this will possibly avoid some loops to provide maintainership to requesters, for plugins that are already de facto without an active maintainer.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznRfyzpnzDx2oTn6Bg8yiZqYuXoWOVt7urQSXJg3jdTMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer role clarification

Oleg Nenashev
Thanks for the clarification Nicolas! It should help with transitions. I had to go through the same during the last year (putting more than 30 plugins for adoption). It hurts sometimes, but it is really required to keep the focus. Thanks a lot for your contributions to the plugins!

I went through the component list in JIRA, and there are few components where you are marked as a lead:
Would you like us to mark all these plugins for adoption and remove you as a default assignee (or change to otheractive maintainers in some components like Docker)?

Best regards,
Oleg


On Thursday, February 21, 2019 at 7:18:50 PM UTC+1, nicolas de loof wrote:
Hi!

Over the years I've been working with Jenkins, I've come to adopt or just patch a few plugins. In some cases, I was only delivering a fix, not really adopting the plugin per-se. Many of them I've been contacted to review  pull requests while I only provided a fix for a customer but don't use by myself, so hardly can maintain. As this might have led to some confusion nowadays, I would like to clarify for future requests that I don't consider myself an active maintainer on any plugin.  So I would like to formally tell the community that anyone can consider "my" plugins ready to be adopted if there isn't already another active maintainer. This typically includes the few docker-*-plugins I've created or maintained past years. Some people using them for production would be better candidate for a maintener role.

I hope this will possibly avoid some loops to provide maintainership to requesters, for plugins that are already de facto without an active maintainer.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e74f423c-44a3-40eb-9a2e-f190f31cac87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer role clarification

Marky Jackson
Thank you Nicolas.
I can help with the AWS credentials plugin and the docker ones if it helps

On Feb 21, 2019, at 3:44 PM, Oleg Nenashev <[hidden email]> wrote:

Thanks for the clarification Nicolas! It should help with transitions. I had to go through the same during the last year (putting more than 30 plugins for adoption). It hurts sometimes, but it is really required to keep the focus. Thanks a lot for your contributions to the plugins!

I went through the component list in JIRA, and there are few components where you are marked as a lead:
Would you like us to mark all these plugins for adoption and remove you as a default assignee (or change to otheractive maintainers in some components like Docker)?

Best regards,
Oleg


On Thursday, February 21, 2019 at 7:18:50 PM UTC+1, nicolas de loof wrote:
Hi!

Over the years I've been working with Jenkins, I've come to adopt or just patch a few plugins. In some cases, I was only delivering a fix, not really adopting the plugin per-se. Many of them I've been contacted to review  pull requests while I only provided a fix for a customer but don't use by myself, so hardly can maintain. As this might have led to some confusion nowadays, I would like to clarify for future requests that I don't consider myself an active maintainer on any plugin.  So I would like to formally tell the community that anyone can consider "my" plugins ready to be adopted if there isn't already another active maintainer. This typically includes the few docker-*-plugins I've created or maintained past years. Some people using them for production would be better candidate for a maintener role.

I hope this will possibly avoid some loops to provide maintainership to requesters, for plugins that are already de facto without an active maintainer.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e74f423c-44a3-40eb-9a2e-f190f31cac87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/14332AC4-4DF6-4AC5-ACB9-D60256E5BE0D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Maintainer role clarification

nicolas de loof-2
In reply to this post by Oleg Nenashev


Le jeu. 21 févr. 2019 à 19:44, Oleg Nenashev <[hidden email]> a écrit :
Thanks for the clarification Nicolas! It should help with transitions. I had to go through the same during the last year (putting more than 30 plugins for adoption). It hurts sometimes, but it is really required to keep the focus. Thanks a lot for your contributions to the plugins!

I went through the component list in JIRA, and there are few components where you are marked as a lead:
Would you like us to mark all these plugins for adoption and remove you as a default assignee (or change to otheractive maintainers in some components like Docker)?

Please do.
I'd like to keep maintainer role on clever-cloud plugin and time-machine-plugin as those are still work in progress on my side.



Best regards,
Oleg


On Thursday, February 21, 2019 at 7:18:50 PM UTC+1, nicolas de loof wrote:
Hi!

Over the years I've been working with Jenkins, I've come to adopt or just patch a few plugins. In some cases, I was only delivering a fix, not really adopting the plugin per-se. Many of them I've been contacted to review  pull requests while I only provided a fix for a customer but don't use by myself, so hardly can maintain. As this might have led to some confusion nowadays, I would like to clarify for future requests that I don't consider myself an active maintainer on any plugin.  So I would like to formally tell the community that anyone can consider "my" plugins ready to be adopted if there isn't already another active maintainer. This typically includes the few docker-*-plugins I've created or maintained past years. Some people using them for production would be better candidate for a maintener role.

I hope this will possibly avoid some loops to provide maintainership to requesters, for plugins that are already de facto without an active maintainer.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e74f423c-44a3-40eb-9a2e-f190f31cac87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznNstONUV2-4QRuGB9z7gu0U5r%3DKhBCCO8doHFyZnwg8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.