> > the requester would initiate a repository transfer request on Github >
Note that it used to require some additional automation logic, because a contributor cannot just move a project to jenkinsci. It has to happen through an intermediate organization like https://github.com/jenkinsci-transfer we use now. I need to test whether there is a transfer request feature in GitHub and whether we can automate the bot somehow. If so, this is perfect On Wednesday, August 28, 2019 at 5:16:04 PM UTC+2, Matt Sicker wrote: > > Sounds like a good idea. > > On Tue, Aug 27, 2019 at 12:03 PM 'Gavin Mogan' via Jenkins Developers > <[email protected] <javascript:>> wrote: > > > > +1 > > I like the idea of not having to contact support to break the link > > > > > > On Tue, Aug 27, 2019 at 10:01 AM Slide <[email protected] <javascript:>> > wrote: > >> > >> Based on some feedback from various people during plugin hosting > requests, our current method of forking and renaming repositories is not as > desirable as one might hope. I am thinking of creating a JEP to change the > process, but wanted to solicit some feedback before I do so. I would like > to propose that the process be changed as follows: > >> > >> 1) Person/Org submits request to the HOSTING project, but the New > Repository Name field is removed. > >> 2) The normal checks occur, however, now the originating repository > name must follow the rules that we normally used for New Repository Name > (e.g., if a plugin it must end in -plugin, no camelcase, etc). > >> 3) Once the plugin has has completed the review process as it does now > (automated checker and human review) the requester would initiate a > repository transfer request on Github > >> 4) Once the transfer request has been submitted, the ircbot would be > updated such that the "host" command would accept the transfer and setup > the teams on the repository to complete the transfer. > >> > >> This would remove the need for users to break the relationship between > the originating repository and the jenkinsci repository (which would become > the canonical repository). > >> > >> Please let me know your thoughts on this process change idea. If it has > good feedback, I'll submit a JEP to document the process. > >> > >> -- > >> Website: http://earl-of-code.com > >> > >> -- > >> 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:>. > >> To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%40mail.gmail.com. > > > > > > -- > > 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:>. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuGgswR6B%2BC930Sh%3Dm-yzU%3D%3DrD3FA%3DNXh9YXDAXrQaV5Q%40mail.gmail.com. > > > > > > -- > Matt Sicker > Senior Software Engineer, CloudBees > -- 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/a9f09d9d-7c03-4610-993d-c5a448134192%40googlegroups.com.
