I am +1000 on the transfer goal, instead of forking. I am quite bothered TBH by the immense amount of fork links that are still present on many (most?) plugins in our GH org. I believe that it sends quite a misleading message especially to new contributors.
We indeed need to be very careful and automate ideally everything, because to be allowed to transfer repo, AFAIR one needs to be admin. And in the past, we've had someone even *delete* the https://github.com/jenkinsci-transfer organization after the transfer had been done, thinking this was a one-off one... On top of the fact PRs against forked repositories are simply ignored in one's statistics (granted, not everybody cares about this, but I think this can be important for some people, possibly more juniors, who want to join the pleasant and the useful to grow their résumé). Le jeu. 29 août 2019 à 11:48, Oleg Nenashev <[email protected]> a écrit : > As long as the transfer process is automated, +100 for that. > It should also help to avoid issues when contributor companies request > hosting but then continue development in their own repos (no > finger-pointing in this thread). > > On Wednesday, August 28, 2019 at 8:58:13 PM UTC+2, Gavin Mogan wrote: >> >> > Which would be a downside I think. >> >> Oh I thought that was the intention >> >> Yea for sure a downside >> >> On Wed, Aug 28, 2019 at 11:56 AM Jesse Glick <[email protected]> >> wrote: >> >>> On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers >>> <[email protected]> wrote: >>> > That would break the fork linkage >>> >>> Which would be a downside I think. Also the current method forces you >>> to remember to delete your own account’s clone so the @jenkinsci one >>> does not appear as a fork of it. >>> >>> Also you would lose any existing issues, PRs, etc. >>> >>> The repository transfer operation seems like the most intuitive and >>> least problematic approach. >>> >>> -- >>> 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/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/cc66f864-4acc-4cc0-b79f-71d918f3fe37%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/cc66f864-4acc-4cc0-b79f-71d918f3fe37%40googlegroups.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6dOhyxLosHF78nGcas27okKPx2tjjno-E-5iYJ-M3Thw%40mail.gmail.com.
