Hi, I am posting this here to have a public discussion:
As discussed during Jenkins World 2017 we are up for transferring the JenkinsPipelineUnit <https://github.com/lesfurets/JenkinsPipelineUnit> project into Jenkins Organization. We naturally want to make sure that current maintainers and LesFurets Org stay collaborators on the project. One option was expressed by @OlegNenashev, quote : <https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins> > > https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins covers the > hosting process based on forking. In the case of PipelineUnit we would > rather prefer moving the project. Usually we use the following approach: > > 1. We grant you administrative access to the > https://github.com/jenkinsci-transfer organization > > > 1. You move the project to this organization > > > 1. One of Jenkins GitHub org admins (e.g. me or Daniel) moves the > project to jenkinsci org > > Such approach allows to retain issues, stars, followers, etc. There will > be also automatic redirect by GitHub, so previous links from external > sources won't be broken. Let me know how to proceed, Cheers Ozan -- 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/729c5f51-9ca1-4744-ab6c-0248bb4c6c0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
