There are still a few plugins hosted in the Jenkins Subversion repository. I am not sure if active changes are being made there. Confusingly, when github.com/jenkinsci was created, we also mirrored those subdirectories as Git repositories. Naturally people have since then submitted GitHub PRs and in some cases pushed to the Git repo while the Subversion repo was active, meaning the plugin is effectively forked. This is a freaking mess.
I think we should simply abandon the Subversion repo, meaning creating a new commit that deletes everything, and then removing write access, and request plugin authors to use GitHub. If they insist on using Subversion (and not via the bridge to Git), they can use some other hosting site, but the plugin should not be considered “hosted on jenkins-ci.org”. Ideally some final check would be done for outstanding changes in svn that did not make it into Git for whatever reason. -- 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/CANfRfr0j2rsHcDmj1X%3DgBFo%2Bb0tKFkFF5DG7B45yyXor%2BYe5vg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
