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 [email protected].
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 via email to