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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdKJLWzcuAAVnmZRwwLvrZyRSC_wYdizp-TYbEMyh-ziQ%40mail.gmail.com.
