Conditional on getting *API* and *SPI* changes reviewed by me, +1. Once you've demonstrated confidence on evolution of the API & SPI I'll be overjoyed to release my veto, but as a critical plugin I believe it would be remiss on my behalf to not supervise a transition.
Changes that do not affect either the API or the SPI method signatures, go for it! On Mon, 24 Jun 2019 at 15:29, Matt Sicker <[email protected]> wrote: > It's hard for me to send this email, but yes, I'd like to help > maintain this plugin. I've been working on some improvements to the > user-scoped credentials features lately, and this plugin falls into my > general category of security-related plugins that I've been working > with more frequently. > > -- > Matt Sicker > Senior Software Engineer, CloudBees > -- *Stephen Connolly* Principal Software Engineer CloudBees, Inc. [image: CloudBees-Logo.png] <http://www.cloudbees.com> E: [email protected] Twitter: @connolly_s <https://twitter.com/connolly_s> <https://cloudbees.com/devops-world/san-francisco> <https://cloudbees.com/devops-world/san-francisco> DevOps World | Jenkins World <https://cloudbees.com/devops-world/san-francisco> August 12-15 :: San Francisco, CA December 2-5 :: Lisbon, Portugal *Use promotional code CBPROD20 to get a 20% discount* -- 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/CAKa4YOpc1faVGZv808K5Zeh80ys3JrwE6_7PxRMMDqA9Raff%2Bg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
