On Monday, 25 August 2014, Slide <[email protected]> wrote: > There have been a couple times recently where someone from Cloudbees has > made changes to email-ext without consulting with me as the maintainer of > email-ext. Just recently tfennelly made a change to the parent pom version > with no consultation. I consider this to be unacceptable. > > Any changes to plugins should go through the plugin maintainers (through > PR's is fine), regardless if it is a plugin that is heavily used in the > enterprise Clousebees offerings. >
I think it would be really good if plugin maintainers put a "contributing" section in the README in the Git repo. With 1000+ plugins it gets hard to remember the rules of the different maintainers. Perhaps the above proposal is something that we should bring to the board. We could then put in place tooling to track whether there is a contribution section and nag the corresponding maintainers > > I'm planning on reverting the changes made, as the policy for email-ext is > to track the LTS version of Jenkins, not the latest. > > -- > 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] > <javascript:_e(%7B%7D,'cvml','jenkinsci-dev%[email protected]');> > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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]. For more options, visit https://groups.google.com/d/optout.
