Hi Akram, I have noticed that the repo was renamed to https://github.com/jenkinsci/jenkins-automation-operator . We briefly discussed the potential renaming at the previous Cloud Native SIG meeting, but AFAICT there was no finalized decision. Although the maintainers have admin permissions and can rename repos, naming agreements are a part of the hosting process. So it would be great to agree on the name here.
The code has not been pushed there yet as well. I highlighted this issue to Vibhav at the last Cloud Native SIG meeting on Nov 20, and IIUC there was a plan to move the code to the new upstream shortly. P.S: It highlights the importance of the formal hosting process. Although it does not prevent from all issues, it helps to ensure that everyone is on the same page. BR, Oleg On Thursday, November 12, 2020 at 2:22:42 PM UTC+1 Oleg Nenashev wrote: > Hi Daniel, > > I agree that I bypassed a few steps in the Hosting process for this repo. > I am happy to discuss why in another channel, but please be sure it is not > about "anyone". > If you or other Hosting team members want me to revert my actions, I will > do so. > > Best regards, > Oleg > > > On Thu, Nov 12, 2020 at 1:34 PM Daniel Beck <db...@cloudbees.com> wrote: > >> >> >> On Thu, Nov 12, 2020 at 12:07 PM Oleg Nenashev <o.v.ne...@gmail.com> >> wrote: >> >>> Since this is a request for a new repo creation (not a fork/move) && >>> there is a consensus here, I do not see a particular need. A HOSTING ticket >>> would be useful to understand the desired permissions, but we can figure it >>> out as we go. >>> >> >> So are you saying that anyone can circumvent hosting processes by asking >> for a new repo "to push existing code"? Because that's what I'm hearing. >> >> (FWIW we stopped doing this several years ago because we customize repos >> in the ircbot code, set up permissions – which you've already noticed is a >> problem now – and apply some other custom defaults. Plus having empty repos >> around that never got populated for months or years is also not great.) >> >> -- >> > You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Developers" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-dev/oAWCXDbgcG4/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> jenkinsci-de...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BtmogApuyJkNET8gmV0sr8%2Bs3og3x8NSw%3DJrV3o7CAPg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BtmogApuyJkNET8gmV0sr8%2Bs3og3x8NSw%3DJrV3o7CAPg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/94d497ad-fca6-44f7-bdd5-79f3f84a4557n%40googlegroups.com.
