On Mon, Mar 14, 2022 at 3:08 PM 'Cyrille Le Clerc' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > It's a great idea to allow the syslog-java-client to progress migrating it to the Jenkins Community. I'm fully supportive. > The MIT License should make it easy.
Thank you for the quick reply! In that case, I think we can proceed with the transfer without the two-week waiting period. Based on my reading of Transferring a repository <https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository>, the owner on the source side (i.e., CloudBees-community) needs to initiate the transfer to the target side (i.e., jenkinsci), and the owner on the target side needs to accept the transfer within one day. I am not a GitHub organization owner on either side, but I assume there will be no issue accepting the transfer on the target side. So I think the next step is to initiate the transfer on the source side. Once the transfer has been completed in GitHub, I can create a PR for repository-permissions-updater <https://github.com/jenkins-infra/repository-permissions-updater> to grant Cyrille Le Clerc and myself initial GitHub and Artifactory permissions. If desired, I can then update the build to use the Jenkins project's build and release processes to complete the transition. -- 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/CAFwNDjpEWiKaRYcHAEJPMZ%3DtE%3DOPZYEd61pbeCgPujc0sg9c8w%40mail.gmail.com.
