> > > Can't we let people do what they want instead of forcing people to deal > with code they don't want to. We are actively harming jenkins community by > overly policing plugins. > > A thousand times this. I was about to say "you can, there's no need to fork into jenkinsci, just release from your own repository".
Then I stumbled upon https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites Can someone point me to when the decision - This will be forked into the Jenkins organisation <https://github.com/jenkinsci>, which will become the canonical source repo was made and accepted by the community? I think it's hugely wrong-headed (I.E: actively bad and against the spirit that attracted me to Jenkins in the first place). There's no technical reason for it. -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPYP83S%2Bp8LtmKgkbSEeMiY-9pb%3Dtx8q95HErC8mZJsdNsm%3DGQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
