{"thread":{"id":"60644","subject":"Git mirror at gitlab","startedAt":"2023-12-21T11:36:38Z","lastAt":"2024-03-31T07:27:05Z","messageCount":23,"participants":["Olliver Schinagl","Patrick Steinhardt","Phillip Wood","Junio C Hamano","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"485926","messageId":"2a833bfc-a075-4e78-ae6c-270f5198d498@schinagl.nl","threadId":"60644","inReplyTo":null,"subject":"Git mirror at gitlab","fromName":"Olliver Schinagl","fromEmail":"oliver@schinagl.nl","sentAt":"2023-12-21T11:30:02Z","receivedAt":"2023-12-21T11:36:38Z","isPatch":false,"sender":{"key":"oliver@schinagl.nl","avatar":"https://gravatar.com/avatar/abb8ef5f9b23563b7703a4114da6f9bd6e7f6d7e8e0296677547b20ff7740c56?d=mp&s=160"},"body":"Hey list,\n\nFor years, I wanted (tried, but time) to run the mirror for git on \ngitlab. Actually, the original idea was to run a docker container ([0] \n10k+ pulls :p)\n\nI initially set this up via docker build containers, where docker hub \nwould pull my mirror of the git repo. My mirror, because I added a \nDockerfile which was enough for docker to do its trick. I was planning \n(time ..) on submitting this upstream to the list, but never did. \nBecause of me not doing that, I had to manually (I was even too lazy to \nscript it) rebase the branch. Docker then did some changes to their \nbusiness, where the docker builds where not possible anymore.\n\nSo then I figured, I'll do the same on gitlab and push it to the docker \nhub. Thus I setup a mirror on gitlab [1], with the idea to work there on it.\n\nAgain, I never got around to finalize this work, mostly because the \ndocker container 'just worked' for pretty much everything. After all, \ngit is very stable overal.\n\nSo very interestingly, last month commit 0e3b67e2aa25edb (\"ci: add \nsupport for GitLab CI\") landed, which started to trigger pipeline jobs!\n\nSadly, this only worked for 3 builds, as that's when the minutes ran out :)\n\nSo one, I would very much like to offer the registered names (cause they \nare pretty nice in name) to here, so people can use and find it.\n\nTwo, hopefully get Patrick Steinhardt to help out to get unlimited \nminutes and storage on the repo :)\n\nThree, see what the opinion of people here is on this. I'll do the work \nto get the dockerfile (now containerfile, we're inclusive after all) \nmerged, and the CI file updated to create, store (and push to docker \nhub) the generated containers.\n\nThanks,\nOlliver\n\n[0]: https://hub.docker.com/r/gitscm/git\n[1]: https://gitlab.com/gitscm/git\n\nP.S. I'm not subscribed, so please keep me in the CC :)\n"},{"id":"485927","messageId":"ZYQl_G-S4vQibHWn@framework","threadId":"60644","inReplyTo":"2a833bfc-a075-4e78-ae6c-270f5198d498@schinagl.nl","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2023-12-21T11:48:12Z","receivedAt":"2023-12-21T11:48:18Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Dec 21, 2023 at 12:30:02PM +0100, Olliver Schinagl wrote:\n> Hey list,\n> \n> For years, I wanted (tried, but time) to run the mirror for git on gitlab.\n> Actually, the original idea was to run a docker container ([0] 10k+ pulls\n> :p)\n> \n> I initially set this up via docker build containers, where docker hub would\n> pull my mirror of the git repo. My mirror, because I added a Dockerfile\n> which was enough for docker to do its trick. I was planning (time ..) on\n> submitting this upstream to the list, but never did. Because of me not doing\n> that, I had to manually (I was even too lazy to script it) rebase the\n> branch. Docker then did some changes to their business, where the docker\n> builds where not possible anymore.\n> \n> So then I figured, I'll do the same on gitlab and push it to the docker hub.\n> Thus I setup a mirror on gitlab [1], with the idea to work there on it.\n> \n> Again, I never got around to finalize this work, mostly because the docker\n> container 'just worked' for pretty much everything. After all, git is very\n> stable overal.\n> \n> So very interestingly, last month commit 0e3b67e2aa25edb (\"ci: add support\n> for GitLab CI\") landed, which started to trigger pipeline jobs!\n> \n> Sadly, this only worked for 3 builds, as that's when the minutes ran out :)\n> \n> So one, I would very much like to offer the registered names (cause they are\n> pretty nice in name) to here, so people can use and find it.\n\nNot to throw a wrench into this, but are you aware of the official\nGitLab mirror at https://gitlab.com/git-vcs/git? I myself wasn't aware\nof this mirror for a rather long time.\n\nI also wondered whether we want to have https://gitlab.com/git/git as we\ndo on GitHub. I don't think anybody registered it, but it is blocked\nfrom being registered as far as I can tell. Maybe we block the namespace\nout of caution, I dunno. I can certainly check in with our SREs in case\nit is something the Git project would like to own.\n\n> Two, hopefully get Patrick Steinhardt to help out to get unlimited minutes\n> and storage on the repo :)\n\nI'm sure we can do something here, but I'd rather aim to do this for the\nofficial mirror which currently is the one I mentioned above. If the\nproject is interested in running builds on GitLab then I'm happy to\ncoordinate.\n\nAlso Cc Ævar, who is the current owner of the mirror. Would it be\npossible to add myself as a second owner to the project? This might help\nsetting up the CI infrastructure. But please, if anybody disagrees with\nme being added as an owner here I encourage you to say so.\n\n> Three, see what the opinion of people here is on this. I'll do the work to\n> get the dockerfile (now containerfile, we're inclusive after all) merged,\n> and the CI file updated to create, store (and push to docker hub) the\n> generated containers.\n\nI don't really have much of an opinion here and will leave it to others\nto discuss.\n\nThanks!\n\nPatrick\n\nPS: As most other folks I'll be OOO during holidays, so I may only\n    answer sporadically.\n\n> Thanks,\n> Olliver\n> \n> [0]: https://hub.docker.com/r/gitscm/git\n> [1]: https://gitlab.com/gitscm/git\n> \n> P.S. I'm not subscribed, so please keep me in the CC :)\n"},{"id":"485979","messageId":"1D1CDDF3-E0D2-4059-9C9A-796145AB6E24@schinagl.nl","threadId":"60644","inReplyTo":"ZYQl_G-S4vQibHWn@framework","subject":"Re: Git mirror at gitlab","fromName":"Olliver Schinagl","fromEmail":"oliver@schinagl.nl","sentAt":"2023-12-22T14:06:08Z","receivedAt":"2023-12-22T14:06:50Z","isPatch":false,"sender":{"key":"oliver@schinagl.nl","avatar":"https://gravatar.com/avatar/abb8ef5f9b23563b7703a4114da6f9bd6e7f6d7e8e0296677547b20ff7740c56?d=mp&s=160"},"body":"Hey Patrick,\n\nOn December 21, 2023 12:48:12 p.m. GMT+01:00, Patrick Steinhardt <ps@pks.im> wrote:\n>On Thu, Dec 21, 2023 at 12:30:02PM +0100, Olliver Schinagl wrote:\n>> Hey list,\n>> \n>> For years, I wanted (tried, but time) to run the mirror for git on gitlab.\n>> Actually, the original idea was to run a docker container ([0] 10k+ pulls\n>> :p)\n>> \n>> I initially set this up via docker build containers, where docker hub would\n>> pull my mirror of the git repo. My mirror, because I added a Dockerfile\n>> which was enough for docker to do its trick. I was planning (time ..) on\n>> submitting this upstream to the list, but never did. Because of me not doing\n>> that, I had to manually (I was even too lazy to script it) rebase the\n>> branch. Docker then did some changes to their business, where the docker\n>> builds where not possible anymore.\n>> \n>> So then I figured, I'll do the same on gitlab and push it to the docker hub.\n>> Thus I setup a mirror on gitlab [1], with the idea to work there on it.\n>> \n>> Again, I never got around to finalize this work, mostly because the docker\n>> container 'just worked' for pretty much everything. After all, git is very\n>> stable overal.\n>> \n>> So very interestingly, last month commit 0e3b67e2aa25edb (\"ci: add support\n>> for GitLab CI\") landed, which started to trigger pipeline jobs!\n>> \n>> Sadly, this only worked for 3 builds, as that's when the minutes ran out :)\n>> \n>> So one, I would very much like to offer the registered names (cause they are\n>> pretty nice in name) to here, so people can use and find it.\n>\n>Not to throw a wrench into this, but are you aware of the official\n>GitLab mirror at https://gitlab.com/git-vcs/git? I myself wasn't aware\n>of this mirror for a rather long time.\nNot a wrench at all, and no, I didn't know. How old is it though :p could be that git-vcs was created cause I owned gitscm :)\n\n\nI had chosen gitscm to match the official site, git-scm.org. the hyphen I left out because afaik it wasn't allowed on docker hub.\n\n>\n>I also wondered whether we want to have https://gitlab.com/git/git as we\n>do on GitHub. I don't think anybody registered it, but it is blocked\n>from being registered as far as I can tell. Maybe we block the namespace\n>out of caution, I dunno. I can certainly check in with our SREs in case\n>it is something the Git project would like to own.\nYeah couldn't figure out who it was either ... hence gitscm.\n\nSadly gitlab doesn't support aliases :) I'm more then happy to hand over the space. Whatever name is decided to be best.\n\n>\n>> Two, hopefully get Patrick Steinhardt to help out to get unlimited minutes\n>> and storage on the repo :)\n>\n>I'm sure we can do something here, but I'd rather aim to do this for the\n>official mirror which currently is the one I mentioned above. If the\n>project is interested in running builds on GitLab then I'm happy to\n>coordinate.\n>\n>Also Cc Ævar, who is the current owner of the mirror. Would it be\n>possible to add myself as a second owner to the project? This might help\n>setting up the CI infrastructure. But please, if anybody disagrees with\n>me being added as an owner here I encourage you to say so.\n>\n>> Three, see what the opinion of people here is on this. I'll do the work to\n>> get the dockerfile (now containerfile, we're inclusive after all) merged,\n>> and the CI file updated to create, store (and push to docker hub) the\n>> generated containers.\n>\n>I don't really have much of an opinion here and will leave it to others\n>to discuss.\n>\n>Thanks!\n>\n>Patrick\n>\n>PS: As most other folks I'll be OOO during holidays, so I may only\n>    answer sporadically.\n>\n>> Thanks,\n>> Olliver\n>> \n>> [0]: https://hub.docker.com/r/gitscm/git\n>> [1]: https://gitlab.com/gitscm/git\n>> \n>> P.S. I'm not subscribed, so please keep me in the CC :)\n"},{"id":"486116","messageId":"ZY1YYtoIw4dIpZ6Q@tanuki","threadId":"60644","inReplyTo":"1D1CDDF3-E0D2-4059-9C9A-796145AB6E24@schinagl.nl","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2023-12-28T11:13:38Z","receivedAt":"2023-12-28T11:13:44Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Dec 22, 2023 at 03:06:08PM +0100, Olliver Schinagl wrote:\n> Hey Patrick,\n> \n> On December 21, 2023 12:48:12 p.m. GMT+01:00, Patrick Steinhardt <ps@pks.im> wrote:\n> >On Thu, Dec 21, 2023 at 12:30:02PM +0100, Olliver Schinagl wrote:\n> >> Hey list,\n> >> \n> >> For years, I wanted (tried, but time) to run the mirror for git on gitlab.\n> >> Actually, the original idea was to run a docker container ([0] 10k+ pulls\n> >> :p)\n> >> \n> >> I initially set this up via docker build containers, where docker hub would\n> >> pull my mirror of the git repo. My mirror, because I added a Dockerfile\n> >> which was enough for docker to do its trick. I was planning (time ..) on\n> >> submitting this upstream to the list, but never did. Because of me not doing\n> >> that, I had to manually (I was even too lazy to script it) rebase the\n> >> branch. Docker then did some changes to their business, where the docker\n> >> builds where not possible anymore.\n> >> \n> >> So then I figured, I'll do the same on gitlab and push it to the docker hub.\n> >> Thus I setup a mirror on gitlab [1], with the idea to work there on it.\n> >> \n> >> Again, I never got around to finalize this work, mostly because the docker\n> >> container 'just worked' for pretty much everything. After all, git is very\n> >> stable overal.\n> >> \n> >> So very interestingly, last month commit 0e3b67e2aa25edb (\"ci: add support\n> >> for GitLab CI\") landed, which started to trigger pipeline jobs!\n> >> \n> >> Sadly, this only worked for 3 builds, as that's when the minutes ran out :)\n> >> \n> >> So one, I would very much like to offer the registered names (cause they are\n> >> pretty nice in name) to here, so people can use and find it.\n> >\n> >Not to throw a wrench into this, but are you aware of the official\n> >GitLab mirror at https://gitlab.com/git-vcs/git? I myself wasn't aware\n> >of this mirror for a rather long time.\n> \n> Not a wrench at all, and no, I didn't know. How old is it though :p\n> could be that git-vcs was created cause I owned gitscm :)\n> \n> I had chosen gitscm to match the official site, git-scm.org. the\n> hyphen I left out because afaik it wasn't allowed on docker hub.\n\nNo idea when exactly this mirror was created. The first mention of it in\nthe \"What's cooking\" report is in December 2020, 489058b80d (What's\ncooking (2023/12 #05), 2023-12-27).\n\n> >I also wondered whether we want to have https://gitlab.com/git/git as we\n> >do on GitHub. I don't think anybody registered it, but it is blocked\n> >from being registered as far as I can tell. Maybe we block the namespace\n> >out of caution, I dunno. I can certainly check in with our SREs in case\n> >it is something the Git project would like to own.\n> \n> Yeah couldn't figure out who it was either ... hence gitscm.\n> \n> Sadly gitlab doesn't support aliases :) I'm more then happy to hand\n> over the space. Whatever name is decided to be best.\n\nI don't particularly mind the name we ultimately settle with. The most\npragmatic choice would likely be to stick with what we already have.\nIdeally, all the others would then be created as forks of the official\none so that they point back to it. Like this, users can learn about the\ncanonical location of the official GitLab-hosted mirror more easily.\n\nIn any case, regardless of which location it is going to be, I certainly\nagree that having CI jobs running for it would be great. Folks here at\nGitLab are mostly on vacation though, but I'll take care of this once\nthey are back and once Ævar has responded so that I can get access to\nthe current official mirror.\n\nPatrick\n"},{"id":"486120","messageId":"733be0c6-24bf-453f-b539-ac2226955b5f@gmail.com","threadId":"60644","inReplyTo":"ZY1YYtoIw4dIpZ6Q@tanuki","subject":"Re: Git mirror at gitlab","fromName":"Phillip Wood","fromEmail":"phillip.wood123@gmail.com","sentAt":"2023-12-28T14:50:31Z","receivedAt":"2023-12-28T14:50:34Z","isPatch":false,"sender":{"key":"phillip.wood@dunelm.org.uk","avatar":null},"body":"On 28/12/2023 11:13, Patrick Steinhardt wrote:\n> On Fri, Dec 22, 2023 at 03:06:08PM +0100, Olliver Schinagl wrote:\n>> Hey Patrick,\n>>\n>> On December 21, 2023 12:48:12 p.m. GMT+01:00, Patrick Steinhardt <ps@pks.im> wrote:\n>>> On Thu, Dec 21, 2023 at 12:30:02PM +0100, Olliver Schinagl wrote:\n>>> Not to throw a wrench into this, but are you aware of the official\n>>> GitLab mirror at https://gitlab.com/git-vcs/git? I myself wasn't aware\n>>> of this mirror for a rather long time.\n>>\n>> Not a wrench at all, and no, I didn't know. How old is it though :p\n>> could be that git-vcs was created cause I owned gitscm :)\n>>\n>> I had chosen gitscm to match the official site, git-scm.org. the\n>> hyphen I left out because afaik it wasn't allowed on docker hub.\n> \n> No idea when exactly this mirror was created. The first mention of it in\n> the \"What's cooking\" report is in December 2020, 489058b80d (What's\n> cooking (2023/12 #05), 2023-12-27).\n\nI think Ævar set it up towards the end of 2018 [1]. I think he used it \nto do some testing using the gcc compile farm [2]\n\nBest Wishes\n\nPhillip\n\n[1] https://lore.kernel.org/git/87k1mecj96.fsf@evledraar.gmail.com/\n[2] https://lore.kernel.org/git/875zwm15k2.fsf@evledraar.gmail.com/\n"},{"id":"486907","messageId":"Zad1S3vCuv4KYIzx@tanuki","threadId":"60644","inReplyTo":"ZYQl_G-S4vQibHWn@framework","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-01-17T06:35:55Z","receivedAt":"2024-01-17T06:37:16Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Dec 21, 2023 at 12:48:12PM +0100, Patrick Steinhardt wrote:\n> On Thu, Dec 21, 2023 at 12:30:02PM +0100, Olliver Schinagl wrote:\n> > Hey list,\n> > \n> > For years, I wanted (tried, but time) to run the mirror for git on gitlab.\n> > Actually, the original idea was to run a docker container ([0] 10k+ pulls\n> > :p)\n> > \n> > I initially set this up via docker build containers, where docker hub would\n> > pull my mirror of the git repo. My mirror, because I added a Dockerfile\n> > which was enough for docker to do its trick. I was planning (time ..) on\n> > submitting this upstream to the list, but never did. Because of me not doing\n> > that, I had to manually (I was even too lazy to script it) rebase the\n> > branch. Docker then did some changes to their business, where the docker\n> > builds where not possible anymore.\n> > \n> > So then I figured, I'll do the same on gitlab and push it to the docker hub.\n> > Thus I setup a mirror on gitlab [1], with the idea to work there on it.\n> > \n> > Again, I never got around to finalize this work, mostly because the docker\n> > container 'just worked' for pretty much everything. After all, git is very\n> > stable overal.\n> > \n> > So very interestingly, last month commit 0e3b67e2aa25edb (\"ci: add support\n> > for GitLab CI\") landed, which started to trigger pipeline jobs!\n> > \n> > Sadly, this only worked for 3 builds, as that's when the minutes ran out :)\n> > \n> > So one, I would very much like to offer the registered names (cause they are\n> > pretty nice in name) to here, so people can use and find it.\n> \n> Not to throw a wrench into this, but are you aware of the official\n> GitLab mirror at https://gitlab.com/git-vcs/git? I myself wasn't aware\n> of this mirror for a rather long time.\n> \n> I also wondered whether we want to have https://gitlab.com/git/git as we\n> do on GitHub. I don't think anybody registered it, but it is blocked\n> from being registered as far as I can tell. Maybe we block the namespace\n> out of caution, I dunno. I can certainly check in with our SREs in case\n> it is something the Git project would like to own.\n\nCircling back on this topic: https://gitlab.com/git is unfortunately\ntaken, so it's out of question. I'd say the most pragmatic thing to do\nwould thus be to retain the already-existing location of the official\nmirror at GitLab.\n\nI'm still trying to reach Ævar so that we can collaborate and set up CI\nfor that mirror.\n\nPatrick\n"},{"id":"491119","messageId":"ZfwY_h70OeuRT7mk@tanuki","threadId":"60644","inReplyTo":"Zad1S3vCuv4KYIzx@tanuki","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-21T11:24:46Z","receivedAt":"2024-03-21T11:24:54Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Wed, Jan 17, 2024 at 07:35:55AM +0100, Patrick Steinhardt wrote:\n> On Thu, Dec 21, 2023 at 12:48:12PM +0100, Patrick Steinhardt wrote:\n> > On Thu, Dec 21, 2023 at 12:30:02PM +0100, Olliver Schinagl wrote:\n> > > Hey list,\n> > > \n> > > For years, I wanted (tried, but time) to run the mirror for git on gitlab.\n> > > Actually, the original idea was to run a docker container ([0] 10k+ pulls\n> > > :p)\n> > > \n> > > I initially set this up via docker build containers, where docker hub would\n> > > pull my mirror of the git repo. My mirror, because I added a Dockerfile\n> > > which was enough for docker to do its trick. I was planning (time ..) on\n> > > submitting this upstream to the list, but never did. Because of me not doing\n> > > that, I had to manually (I was even too lazy to script it) rebase the\n> > > branch. Docker then did some changes to their business, where the docker\n> > > builds where not possible anymore.\n> > > \n> > > So then I figured, I'll do the same on gitlab and push it to the docker hub.\n> > > Thus I setup a mirror on gitlab [1], with the idea to work there on it.\n> > > \n> > > Again, I never got around to finalize this work, mostly because the docker\n> > > container 'just worked' for pretty much everything. After all, git is very\n> > > stable overal.\n> > > \n> > > So very interestingly, last month commit 0e3b67e2aa25edb (\"ci: add support\n> > > for GitLab CI\") landed, which started to trigger pipeline jobs!\n> > > \n> > > Sadly, this only worked for 3 builds, as that's when the minutes ran out :)\n> > > \n> > > So one, I would very much like to offer the registered names (cause they are\n> > > pretty nice in name) to here, so people can use and find it.\n> > \n> > Not to throw a wrench into this, but are you aware of the official\n> > GitLab mirror at https://gitlab.com/git-vcs/git? I myself wasn't aware\n> > of this mirror for a rather long time.\n> > \n> > I also wondered whether we want to have https://gitlab.com/git/git as we\n> > do on GitHub. I don't think anybody registered it, but it is blocked\n> > from being registered as far as I can tell. Maybe we block the namespace\n> > out of caution, I dunno. I can certainly check in with our SREs in case\n> > it is something the Git project would like to own.\n> \n> Circling back on this topic: https://gitlab.com/git is unfortunately\n> taken, so it's out of question. I'd say the most pragmatic thing to do\n> would thus be to retain the already-existing location of the official\n> mirror at GitLab.\n> \n> I'm still trying to reach Ævar so that we can collaborate and set up CI\n> for that mirror.\n> \n> Patrick\n\nI still have not been able to reach Ævar until now. Unless somebody else\nhas a way to contact him directly we at GitLab are wondering how to\ncontinue. Two options:\n\n  - Collaborate with our support folks at GitLab to add a new owner to\n    the mirror. In theory we have this option, but none of us at GitLab\n    feel that it is the right course of action. It feels too hostile and\n    overreaching.\n\n  - Set up a new official mirror hosted on GitLab and change the URLs\n    that we advertise. We may want to use the one set up by Olliver\n    (https://gitlab.com/gitscm/git), but in that case I'd want us to\n    transfer ownership to people of the community that have been working\n    on the project for a long time. We can also use an alternate URL,\n    I'm happy to take proposals.\n\nIt would certainly be great to set up ownership of whatever solution we\narrive at such that it's more distributed across the community so that\nwe don't have a single point of failure in the future. Also, I don't\nwant us at GitLab to be the sole owners of the mirror, so I have been\nwondering how the other mirrors are set up and whom we should add to any\nsuch mirror.\n\nIn any case, once things are arranged I will collaborate with our\nsupport folks to get free CI minutes for the new mirror.\n\nPatrick\n"},{"id":"491159","messageId":"xmqqy1aba6i6.fsf@gitster.g","threadId":"60644","inReplyTo":"ZfwY_h70OeuRT7mk@tanuki","subject":"Re: Git mirror at gitlab","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-03-21T16:34:25Z","receivedAt":"2024-03-21T16:34:30Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n>> Circling back on this topic: https://gitlab.com/git is unfortunately\n>> taken, so it's out of question. I'd say the most pragmatic thing to do\n>> would thus be to retain the already-existing location of the official\n>> mirror at GitLab.\n\nhttps://gitlab.com/git/ sems to give us 404, though.\n\n> I still have not been able to reach Ævar until now. Unless somebody else\n> has a way to contact him directly we at GitLab are wondering how to\n> continue.\n\nGit @ SFC has heard from avarab@gmail.com on Nov 29, 2023 but I do\nnot recall any more recent communications X-<.\n\n> It would certainly be great to set up ownership of whatever solution we\n> arrive at such that it's more distributed across the community so that\n> we don't have a single point of failure in the future. Also, I don't\n> want us at GitLab to be the sole owners of the mirror, so I have been\n> wondering how the other mirrors are set up and whom we should add to any\n> such mirror.\n\nDistribution, yes.  I do not think we mind if the set of volunteer\nowners end up to be all GitLab folks, but aiming for diversity is\ngood.\n\n> In any case, once things are arranged I will collaborate with our\n> support folks to get free CI minutes for the new mirror.\n\nWonderful.\n\nThanks.\n"},{"id":"491180","messageId":"E5C00398-536B-4CE5-AB25-FE7FCD55CCD8@schinagl.nl","threadId":"60644","inReplyTo":"xmqqy1aba6i6.fsf@gitster.g","subject":"Re: Git mirror at gitlab","fromName":"Olliver Schinagl","fromEmail":"oliver@schinagl.nl","sentAt":"2024-03-21T22:27:07Z","receivedAt":"2024-03-21T22:33:25Z","isPatch":false,"sender":{"key":"oliver@schinagl.nl","avatar":"https://gravatar.com/avatar/abb8ef5f9b23563b7703a4114da6f9bd6e7f6d7e8e0296677547b20ff7740c56?d=mp&s=160"},"body":"Hey all,\n\nOn March 21, 2024 5:34:25 p.m. GMT+01:00, Junio C Hamano <gitster@pobox.com> wrote:\n>Patrick Steinhardt <ps@pks.im> writes:\n>\n>>> Circling back on this topic: https://gitlab.com/git is unfortunately\n>>> taken, so it's out of question. I'd say the most pragmatic thing to do\n>>> would thus be to retain the already-existing location of the official\n>>> mirror at GitLab.\n>\n>https://gitlab.com/git/ sems to give us 404, though.\n>\n\nThat seems tot indicatie this is a user, not a group (gitlab is more advanced then github), but I could be wrong. In both cases the user has set this to private.\n\nMy guess is, someone set this up as a bot-user or something the like. Maybebgitlab could check activity (internally and confidentially) and see if the user would want to talk. But I admit is a bit hostile. Other we have no way of reaching out.\n\n\nAs for my mirror, I started my mail with I'd me more then happy to transfer ownership. The name I post cked as a reference to git-scm.org, and never intended to keep it for myself. As I initially wrote, I was just slow and lazy to sort thongs out ;)\n\nI will transfer and relinquish any and all control of the group once I know to whom.\n\nOlliver\n\n>> I still have not been able to reach Ævar until now. Unless somebody else\n>> has a way to contact him directly we at GitLab are wondering how to\n>> continue.\n>\n>Git @ SFC has heard from avarab@gmail.com on Nov 29, 2023 but I do\n>not recall any more recent communications X-<.\n>\n>> It would certainly be great to set up ownership of whatever solution we\n>> arrive at such that it's more distributed across the community so that\n>> we don't have a single point of failure in the future. Also, I don't\n>> want us at GitLab to be the sole owners of the mirror, so I have been\n>> wondering how the other mirrors are set up and whom we should add to any\n>> such mirror.\n>\n>Distribution, yes.  I do not think we mind if the set of volunteer\n>owners end up to be all GitLab folks, but aiming for diversity is\n>good.\n>\n>> In any case, once things are arranged I will collaborate with our\n>> support folks to get free CI minutes for the new mirror.\n>\n>Wonderful.\n>\n>Thanks.\n"},{"id":"491196","messageId":"ZfzUb9HkZLq1UIed@tanuki","threadId":"60644","inReplyTo":"E5C00398-536B-4CE5-AB25-FE7FCD55CCD8@schinagl.nl","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-22T00:44:31Z","receivedAt":"2024-03-22T00:44:38Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Thu, Mar 21, 2024 at 11:27:07PM +0100, Olliver Schinagl wrote:\n> Hey all,\n> \n> On March 21, 2024 5:34:25 p.m. GMT+01:00, Junio C Hamano <gitster@pobox.com> wrote:\n> >Patrick Steinhardt <ps@pks.im> writes:\n> >\n> >>> Circling back on this topic: https://gitlab.com/git is unfortunately\n> >>> taken, so it's out of question. I'd say the most pragmatic thing to do\n> >>> would thus be to retain the already-existing location of the official\n> >>> mirror at GitLab.\n> >\n> >https://gitlab.com/git/ sems to give us 404, though.\n> >\n> \n> That seems tot indicatie this is a user, not a group (gitlab is more\n> advanced then github), but I could be wrong. In both cases the user\n> has set this to private.\n> \n> My guess is, someone set this up as a bot-user or something the like.\n> Maybebgitlab could check activity (internally and confidentially) and\n> see if the user would want to talk. But I admit is a bit hostile.\n> Other we have no way of reaching out.\n\nI checked with support folks and it is a private group if I remember\ncorrectly. Whatever it was, it's not available right now.\n\n> As for my mirror, I started my mail with I'd me more then happy to\n> transfer ownership. The name I post cked as a reference to\n> git-scm.org, and never intended to keep it for myself. As I initially\n> wrote, I was just slow and lazy to sort thongs out ;)\n> \n> I will transfer and relinquish any and all control of the group once I\n> know to whom.\n\nOkay, thanks, I didn't quite remember :) In any case, unless we get a\nhold of git-vcs/git, we have two viable options:\n\n  - gitvcs/git owned by Olliver.\n\n  - git-scm/git. I just discovered a few hours ago that the git-scm\n    group is owned by Chris, so we can set this one up easily.\n\nI'd personally rather go with the latter, mostly because it matches our\ngit-scm.com domain. I also like it better than the current git-vcs/git\nbecause of that.\n\nSo Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\nadditional owner of that group? I'd be happy to manage the rest from\nthere -- setup of the project, mirroring, CI system and changing our\ndocs to point to the new mirror.\n\nPatrick\n"},{"id":"491227","messageId":"CAP8UFD2LmapWutRpfveL6ChSg8xrCkQXyQaJwHyEp8JA0p_Osw@mail.gmail.com","threadId":"60644","inReplyTo":"ZfzUb9HkZLq1UIed@tanuki","subject":"Re: Git mirror at gitlab","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2024-03-22T10:08:34Z","receivedAt":"2024-03-22T10:08:47Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"(Sorry for initially sending this privately to Patrick.)\n\nOn Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n>\n> On Thu, Mar 21, 2024 at 11:27:07PM +0100, Olliver Schinagl wrote:\n> > Hey all,\n\n> > As for my mirror, I started my mail with I'd me more then happy to\n> > transfer ownership. The name I post cked as a reference to\n> > git-scm.org, and never intended to keep it for myself. As I initially\n> > wrote, I was just slow and lazy to sort thongs out ;)\n> >\n> > I will transfer and relinquish any and all control of the group once I\n> > know to whom.\n>\n> Okay, thanks, I didn't quite remember :) In any case, unless we get a\n> hold of git-vcs/git, we have two viable options:\n>\n>   - gitvcs/git owned by Olliver.\n>\n>   - git-scm/git. I just discovered a few hours ago that the git-scm\n>     group is owned by Chris, so we can set this one up easily.\n\nIt's owned by me and James Ramsay (ex-GitLab). James created it when\nhe was the Gitaly Product Manager and added me as owner.\n\n> I'd personally rather go with the latter, mostly because it matches our\n> git-scm.com domain. I also like it better than the current git-vcs/git\n> because of that.\n>\n> So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n> additional owner of that group?\n\nDone.\n\n> I'd be happy to manage the rest from\n> there -- setup of the project, mirroring, CI system and changing our\n> docs to point to the new mirror.\n\nThanks for doing this!\n"},{"id":"491242","messageId":"Zf2B5oksaJRDH5WT@tanuki","threadId":"60644","inReplyTo":"CAP8UFD2LmapWutRpfveL6ChSg8xrCkQXyQaJwHyEp8JA0p_Osw@mail.gmail.com","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-22T13:04:38Z","receivedAt":"2024-03-22T13:04:45Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n> (Sorry for initially sending this privately to Patrick.)\n> \n> On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n[snip]\n> > I'd personally rather go with the latter, mostly because it matches our\n> > git-scm.com domain. I also like it better than the current git-vcs/git\n> > because of that.\n> >\n> > So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n> > additional owner of that group?\n> \n> Done.\n\nThanks! I've set up the repository at https://gitlab.com/git-scm/git\nnow. I'm coordinating internally to get it signed up for the Open Source\nprogram that we have at GitLab for CI and mirroring functionality.\n\nFor any of the stakeholders in the Git project, please feel free to\nshoot me a message with your GitLab handle so that I can add you to the\ngroup/project.\n\nPatrick\n"},{"id":"491831","messageId":"d9515be6f21a8a95de3319e1046e05606cd91d55.1711723543.git.ps@pks.im","threadId":"60644","inReplyTo":"Zf2B5oksaJRDH5WT@tanuki","subject":"[PATCH 1/2] cook: switch unmaintained GitLab mirror to new URL","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-29T14:47:10Z","receivedAt":"2024-03-29T14:47:18Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"One of the official mirrors for the Git project is hosted at\nhttps://gitlab.com/git-vcs/git. This mirror is only maintained by a\nsingle person (Ævar Arnfjörð Bjarmason) whom we haven't been able to\ncontact for multiple months by now. Thus the mirror is essentially\nunmaintained right now.\n\nGiven the recent introduction of support for GitLab CI into Git in\n0e3b67e2aa (ci: add support for GitLab CI, 2023-11-09) there is interest\nthough to set up CI systems for the GitLab mirror. A new mirror was thus\ncreated on GitLab at https://gitlab.com/git-scm/git that has been signed\nup with the GitLab Open Source program, which gives that project free CI\nminutes. Furthermore, this mirror has multiple owners (Christian Couder\nand myself and we are happy to add more stakeholders) so that we do not\nrun into the same issue in the future.\n\nSwitch over the GitLab mirror URL to the new mirror.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n\nThe new repository has now been registered with the GitLab Open Source\nprogram. It has been configured to mirror [1] and CI pipelines run after\nevery mirror update.\n\nPatrick\n\n[1] https://git.kernel.org/pub/scm/git/git\n\n MaintNotes        | 2 +-\n cook              | 2 +-\n whats-cooking.txt | 2 +-\n 3 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/MaintNotes b/MaintNotes\nindex 919a9dc3fb..774ce56c20 100644\n--- a/MaintNotes\n+++ b/MaintNotes\n@@ -135,7 +135,7 @@ My public git.git repositories are (mirrored) at:\n   https://kernel.googlesource.com/pub/scm/git/git\n   https://repo.or.cz/alt-git.git/\n   https://github.com/git/git/\n-  https://gitlab.com/git-vcs/git/\n+  https://gitlab.com/git-scm/git/\n \n This one shows not just the main integration branches, but also\n individual topics broken out:\ndiff --git a/cook b/cook\nindex e1d9e6aba9..5fb2062574 100755\n--- a/cook\n+++ b/cook\n@@ -398,7 +398,7 @@ With maint, master, next, seen, todo:\n \tgit://repo.or.cz/alt-git.git/\n \thttps://kernel.googlesource.com/pub/scm/git/git/\n \thttps://github.com/git/git/\n-\thttps://gitlab.com/git-vcs/git/\n+\thttps://gitlab.com/git-scm/git/\n \n With all the integration branches and topics broken out:\n \ndiff --git a/whats-cooking.txt b/whats-cooking.txt\nindex bd471c4e78..24e9fc51df 100644\n--- a/whats-cooking.txt\n+++ b/whats-cooking.txt\n@@ -27,7 +27,7 @@ With maint, master, next, seen, todo:\n \tgit://repo.or.cz/alt-git.git/\n \thttps://kernel.googlesource.com/pub/scm/git/git/\n \thttps://github.com/git/git/\n-\thttps://gitlab.com/git-vcs/git/\n+\thttps://gitlab.com/git-scm/git/\n \n With all the integration branches and topics broken out:\n \n-- \n2.44.0\n\n"},{"id":"491830","messageId":"a7ceeee328f1303eeaffe3ef2dc94955e0d2e47f.1711723543.git.ps@pks.im","threadId":"60644","inReplyTo":"Zf2B5oksaJRDH5WT@tanuki","subject":"[PATCH 2/2] cook: update mirror URLs to use HTTPS","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-29T14:47:14Z","receivedAt":"2024-03-29T14:47:19Z","isPatch":true,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"Some of our mirror URLs are listed with the \"git://\" protocol even\nthough all of them actually support \"https://\". There is no good reason\nto prefer the former over the latter. Quite on the contrary, given that\nthe \"https://\" protocol is encrypted it is a safer choice.\n\nUpdate those mirror URLs to use \"https://\" protocols.\n\nSigned-off-by: Patrick Steinhardt <ps@pks.im>\n---\n Announce          | 2 +-\n cook              | 6 +++---\n whats-cooking.txt | 6 +++---\n 3 files changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/Announce b/Announce\nindex 8ac01306e3..db0bedcdb0 100755\n--- a/Announce\n+++ b/Announce\n@@ -113,7 +113,7 @@ cat <<\\EOF\n \n   url = https://git.kernel.org/pub/scm/git/git\n   url = https://kernel.googlesource.com/pub/scm/git/git\n-  url = git://repo.or.cz/alt-git.git\n+  url = https://repo.or.cz/alt-git.git\n   url = https://github.com/gitster/git\n EOF\n \ndiff --git a/cook b/cook\nindex 5fb2062574..b5450936a2 100755\n--- a/cook\n+++ b/cook\n@@ -394,8 +394,8 @@ repositories have only a subset of branches.\n \n With maint, master, next, seen, todo:\n \n-\tgit://git.kernel.org/pub/scm/git/git.git/\n-\tgit://repo.or.cz/alt-git.git/\n+\thttps://git.kernel.org/pub/scm/git/git.git/\n+\thttps://repo.or.cz/alt-git.git/\n \thttps://kernel.googlesource.com/pub/scm/git/git/\n \thttps://github.com/git/git/\n \thttps://gitlab.com/git-scm/git/\n@@ -409,7 +409,7 @@ are not sources, they are published in these repositories for\n convenience (replace \"htmldocs\" with \"manpages\" for the manual\n pages):\n \n-\tgit://git.kernel.org/pub/scm/git/git-htmldocs.git/\n+\thttps://git.kernel.org/pub/scm/git/git-htmldocs.git/\n \thttps://github.com/gitster/git-htmldocs.git/\n \n Release tarballs are available at:\ndiff --git a/whats-cooking.txt b/whats-cooking.txt\nindex 24e9fc51df..14f306df36 100644\n--- a/whats-cooking.txt\n+++ b/whats-cooking.txt\n@@ -23,8 +23,8 @@ repositories have only a subset of branches.\n \n With maint, master, next, seen, todo:\n \n-\tgit://git.kernel.org/pub/scm/git/git.git/\n-\tgit://repo.or.cz/alt-git.git/\n+\thttps://git.kernel.org/pub/scm/git/git.git/\n+\thttps://repo.or.cz/alt-git.git/\n \thttps://kernel.googlesource.com/pub/scm/git/git/\n \thttps://github.com/git/git/\n \thttps://gitlab.com/git-scm/git/\n@@ -38,7 +38,7 @@ are not sources, they are published in these repositories for\n convenience (replace \"htmldocs\" with \"manpages\" for the manual\n pages):\n \n-\tgit://git.kernel.org/pub/scm/git/git-htmldocs.git/\n+\thttps://git.kernel.org/pub/scm/git/git-htmldocs.git/\n \thttps://github.com/gitster/git-htmldocs.git/\n \n Release tarballs are available at:\n-- \n2.44.0\n\n"},{"id":"491838","messageId":"xmqq8r20zz5h.fsf@gitster.g","threadId":"60644","inReplyTo":"d9515be6f21a8a95de3319e1046e05606cd91d55.1711723543.git.ps@pks.im","subject":"Re: [PATCH 1/2] cook: switch unmaintained GitLab mirror to new URL","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-03-29T18:11:22Z","receivedAt":"2024-03-29T18:11:27Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Patrick Steinhardt <ps@pks.im> writes:\n\n> The new repository has now been registered with the GitLab Open Source\n> program. It has been configured to mirror [1] and CI pipelines run after\n> every mirror update.\n\nOK, thanks.\n"},{"id":"491872","messageId":"1d6a282e-afe6-4d43-a61c-d0259131b11c@schinagl.nl","threadId":"60644","inReplyTo":"Zf2B5oksaJRDH5WT@tanuki","subject":"Re: Git mirror at gitlab","fromName":"Olliver Schinagl","fromEmail":"oliver@schinagl.nl","sentAt":"2024-03-30T08:14:47Z","receivedAt":"2024-03-30T08:14:49Z","isPatch":false,"sender":{"key":"oliver@schinagl.nl","avatar":"https://gravatar.com/avatar/abb8ef5f9b23563b7703a4114da6f9bd6e7f6d7e8e0296677547b20ff7740c56?d=mp&s=160"},"body":"On 22-03-2024 14:04, Patrick Steinhardt wrote:\n> On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n>> (Sorry for initially sending this privately to Patrick.)\n>>\n>> On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n> [snip]\n>>> I'd personally rather go with the latter, mostly because it matches our\n>>> git-scm.com domain. I also like it better than the current git-vcs/git\n>>> because of that.\n>>>\n>>> So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n>>> additional owner of that group?\n\nI'll empty out my gitscm group, make it private so that it won't be \naccidentally used and transfer ownership to pks-t. You can then 'do what \nis needed' with the group. Since gitlab doesn't support aliases (yet? \n:p) best to park the namespace.\n\nOlliver\n\n>>\n>> Done.\n> \n> Thanks! I've set up the repository at https://gitlab.com/git-scm/git\n> now. I'm coordinating internally to get it signed up for the Open Source\n> program that we have at GitLab for CI and mirroring functionality.\n> \n> For any of the stakeholders in the Git project, please feel free to\n> shoot me a message with your GitLab handle so that I can add you to the\n> group/project.\n> \n> Patrick\n"},{"id":"491874","messageId":"ZgfK3DoeidDcIaFj@framework","threadId":"60644","inReplyTo":"1d6a282e-afe6-4d43-a61c-d0259131b11c@schinagl.nl","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-30T08:18:36Z","receivedAt":"2024-03-30T08:18:43Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Sat, Mar 30, 2024 at 09:14:47AM +0100, Olliver Schinagl wrote:\n> On 22-03-2024 14:04, Patrick Steinhardt wrote:\n> > On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n> > > (Sorry for initially sending this privately to Patrick.)\n> > > \n> > > On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n> > [snip]\n> > > > I'd personally rather go with the latter, mostly because it matches our\n> > > > git-scm.com domain. I also like it better than the current git-vcs/git\n> > > > because of that.\n> > > > \n> > > > So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n> > > > additional owner of that group?\n> \n> I'll empty out my gitscm group, make it private so that it won't be\n> accidentally used and transfer ownership to pks-t. You can then 'do what is\n> needed' with the group. Since gitlab doesn't support aliases (yet? :p) best\n> to park the namespace.\n> \n> Olliver\n\nBy the way, thanks a ton for being this open and helpful during the\nwhole process. This is greatly appreciated!\n\nPatrick\n"},{"id":"491875","messageId":"f283d6ed-54b6-4bbd-8b14-67c9c8d50a2a@schinagl.nl","threadId":"60644","inReplyTo":"ZgfK3DoeidDcIaFj@framework","subject":"Re: Git mirror at gitlab","fromName":"Olliver Schinagl","fromEmail":"oliver@schinagl.nl","sentAt":"2024-03-30T08:20:22Z","receivedAt":"2024-03-30T08:20:24Z","isPatch":false,"sender":{"key":"oliver@schinagl.nl","avatar":"https://gravatar.com/avatar/abb8ef5f9b23563b7703a4114da6f9bd6e7f6d7e8e0296677547b20ff7740c56?d=mp&s=160"},"body":"On 30-03-2024 09:18, Patrick Steinhardt wrote:\n> On Sat, Mar 30, 2024 at 09:14:47AM +0100, Olliver Schinagl wrote:\n>> On 22-03-2024 14:04, Patrick Steinhardt wrote:\n>>> On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n>>>> (Sorry for initially sending this privately to Patrick.)\n>>>>\n>>>> On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n>>> [snip]\n>>>>> I'd personally rather go with the latter, mostly because it matches our\n>>>>> git-scm.com domain. I also like it better than the current git-vcs/git\n>>>>> because of that.\n>>>>>\n>>>>> So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n>>>>> additional owner of that group?\n>>\n>> I'll empty out my gitscm group, make it private so that it won't be\n>> accidentally used and transfer ownership to pks-t. You can then 'do what is\n>> needed' with the group. Since gitlab doesn't support aliases (yet? :p) best\n>> to park the namespace.\n>>\n>> Olliver\n> \n> By the way, thanks a ton for being this open and helpful during the\n> whole process. This is greatly appreciated!\n\nHey, no problem. I initiated this discussion because I wanted to get to \nthis solution. Just because my mirror is not used doesn't mean I don't \nagree :)\n\nBtw, I can't transfer the group, it's empty, but if I delete it _right \nnow_, you'll have to re-create it, _right_now_ (well within the next 5 \nminutes?).\n\nOlliver\n\n> \n> Patrick\n"},{"id":"491877","messageId":"ZgfWH_smdZ1jXkLO@ncase","threadId":"60644","inReplyTo":"f283d6ed-54b6-4bbd-8b14-67c9c8d50a2a@schinagl.nl","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-30T09:06:39Z","receivedAt":"2024-03-30T09:06:45Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Sat, Mar 30, 2024 at 09:20:22AM +0100, Olliver Schinagl wrote:\n> On 30-03-2024 09:18, Patrick Steinhardt wrote:\n> > On Sat, Mar 30, 2024 at 09:14:47AM +0100, Olliver Schinagl wrote:\n> > > On 22-03-2024 14:04, Patrick Steinhardt wrote:\n> > > > On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n> > > > > (Sorry for initially sending this privately to Patrick.)\n> > > > > \n> > > > > On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n> > > > [snip]\n> > > > > > I'd personally rather go with the latter, mostly because it matches our\n> > > > > > git-scm.com domain. I also like it better than the current git-vcs/git\n> > > > > > because of that.\n> > > > > > \n> > > > > > So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n> > > > > > additional owner of that group?\n> > > \n> > > I'll empty out my gitscm group, make it private so that it won't be\n> > > accidentally used and transfer ownership to pks-t. You can then 'do what is\n> > > needed' with the group. Since gitlab doesn't support aliases (yet? :p) best\n> > > to park the namespace.\n> > > \n> > > Olliver\n> > \n> > By the way, thanks a ton for being this open and helpful during the\n> > whole process. This is greatly appreciated!\n> \n> Hey, no problem. I initiated this discussion because I wanted to get to this\n> solution. Just because my mirror is not used doesn't mean I don't agree :)\n> \n> Btw, I can't transfer the group, it's empty, but if I delete it _right now_,\n> you'll have to re-create it, _right_now_ (well within the next 5 minutes?).\n\nShouldn't it be possible to add me as a secondary owner of the group in\n[1]? From thereon I could \"transfer\" the group by removing you from it.\n\nPatrick\n\n[1]: https://gitlab.com/groups/gitscm/-/group_members\n"},{"id":"491878","messageId":"68563c5e-af74-4300-84c4-a0d75434167f@schinagl.nl","threadId":"60644","inReplyTo":"ZgfWH_smdZ1jXkLO@ncase","subject":"Re: Git mirror at gitlab","fromName":"Olliver Schinagl","fromEmail":"oliver@schinagl.nl","sentAt":"2024-03-30T10:59:51Z","receivedAt":"2024-03-30T10:59:54Z","isPatch":false,"sender":{"key":"oliver@schinagl.nl","avatar":"https://gravatar.com/avatar/abb8ef5f9b23563b7703a4114da6f9bd6e7f6d7e8e0296677547b20ff7740c56?d=mp&s=160"},"body":"On 30-03-2024 10:06, Patrick Steinhardt wrote:\n> On Sat, Mar 30, 2024 at 09:20:22AM +0100, Olliver Schinagl wrote:\n>> On 30-03-2024 09:18, Patrick Steinhardt wrote:\n>>> On Sat, Mar 30, 2024 at 09:14:47AM +0100, Olliver Schinagl wrote:\n>>>> On 22-03-2024 14:04, Patrick Steinhardt wrote:\n>>>>> On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n>>>>>> (Sorry for initially sending this privately to Patrick.)\n>>>>>>\n>>>>>> On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n>>>>> [snip]\n>>>>>>> I'd personally rather go with the latter, mostly because it matches our\n>>>>>>> git-scm.com domain. I also like it better than the current git-vcs/git\n>>>>>>> because of that.\n>>>>>>>\n>>>>>>> So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n>>>>>>> additional owner of that group?\n>>>>\n>>>> I'll empty out my gitscm group, make it private so that it won't be\n>>>> accidentally used and transfer ownership to pks-t. You can then 'do what is\n>>>> needed' with the group. Since gitlab doesn't support aliases (yet? :p) best\n>>>> to park the namespace.\n>>>>\n>>>> Olliver\n>>>\n>>> By the way, thanks a ton for being this open and helpful during the\n>>> whole process. This is greatly appreciated!\n>>\n>> Hey, no problem. I initiated this discussion because I wanted to get to this\n>> solution. Just because my mirror is not used doesn't mean I don't agree :)\n>>\n>> Btw, I can't transfer the group, it's empty, but if I delete it _right now_,\n>> you'll have to re-create it, _right_now_ (well within the next 5 minutes?).\n> \n> Shouldn't it be possible to add me as a secondary owner of the group in\n> [1]? From thereon I could \"transfer\" the group by removing you from it.\n\nDone and done.\n\nI'll remove myself, or you can kick me :( one I know you have \nsuccessfully received ownership. I tried to invite the group git-scm but \nthat couldn't be found, probably you can do that (and then remove \nyourself :p)\n\nWould have been useful to transfer ownership of a group, iirc you do \nthat with repo's as well? Under the hood it could use the invite + \nremove members thing. Though this works.\n\n> \n> Patrick\n> \n> [1]: https://gitlab.com/groups/gitscm/-/group_members\n"},{"id":"491897","messageId":"ZghUu7Ae5PYga-Ji@ncase","threadId":"60644","inReplyTo":"68563c5e-af74-4300-84c4-a0d75434167f@schinagl.nl","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-30T18:06:51Z","receivedAt":"2024-03-30T18:06:59Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Sat, Mar 30, 2024 at 11:59:51AM +0100, Olliver Schinagl wrote:\n> On 30-03-2024 10:06, Patrick Steinhardt wrote:\n> > On Sat, Mar 30, 2024 at 09:20:22AM +0100, Olliver Schinagl wrote:\n> > > On 30-03-2024 09:18, Patrick Steinhardt wrote:\n> > > > On Sat, Mar 30, 2024 at 09:14:47AM +0100, Olliver Schinagl wrote:\n> > > > > On 22-03-2024 14:04, Patrick Steinhardt wrote:\n> > > > > > On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n> > > > > > > (Sorry for initially sending this privately to Patrick.)\n> > > > > > > \n> > > > > > > On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n> > > > > > [snip]\n> > > > > > > > I'd personally rather go with the latter, mostly because it matches our\n> > > > > > > > git-scm.com domain. I also like it better than the current git-vcs/git\n> > > > > > > > because of that.\n> > > > > > > > \n> > > > > > > > So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n> > > > > > > > additional owner of that group?\n> > > > > \n> > > > > I'll empty out my gitscm group, make it private so that it won't be\n> > > > > accidentally used and transfer ownership to pks-t. You can then 'do what is\n> > > > > needed' with the group. Since gitlab doesn't support aliases (yet? :p) best\n> > > > > to park the namespace.\n> > > > > \n> > > > > Olliver\n> > > > \n> > > > By the way, thanks a ton for being this open and helpful during the\n> > > > whole process. This is greatly appreciated!\n> > > \n> > > Hey, no problem. I initiated this discussion because I wanted to get to this\n> > > solution. Just because my mirror is not used doesn't mean I don't agree :)\n> > > \n> > > Btw, I can't transfer the group, it's empty, but if I delete it _right now_,\n> > > you'll have to re-create it, _right_now_ (well within the next 5 minutes?).\n> > \n> > Shouldn't it be possible to add me as a secondary owner of the group in\n> > [1]? From thereon I could \"transfer\" the group by removing you from it.\n> \n> Done and done.\n> \n> I'll remove myself, or you can kick me :( one I know you have successfully\n> received ownership. I tried to invite the group git-scm but that couldn't be\n> found, probably you can do that (and then remove yourself :p)\n> \n> Would have been useful to transfer ownership of a group, iirc you do that\n> with repo's as well? Under the hood it could use the invite + remove members\n> thing. Though this works.\n\nThanks! I've added Christian to this group such that it has a higher bus\nfactor. I guess it should probably have the same owners as the \"git-scm\"\none just in case we ever want to do anything with it. I've also removed\nyou from this group now.\n\nPatrick\n"},{"id":"491913","messageId":"4A3E0E2D-2922-4C90-A306-30A685D11C4D@schinagl.nl","threadId":"60644","inReplyTo":"ZghUu7Ae5PYga-Ji@ncase","subject":"Re: Git mirror at gitlab","fromName":"Olliver Schinagl","fromEmail":"oliver@schinagl.nl","sentAt":"2024-03-30T23:54:12Z","receivedAt":"2024-03-30T23:54:13Z","isPatch":false,"sender":{"key":"oliver@schinagl.nl","avatar":"https://gravatar.com/avatar/abb8ef5f9b23563b7703a4114da6f9bd6e7f6d7e8e0296677547b20ff7740c56?d=mp&s=160"},"body":"\n\nOn March 30, 2024 7:06:51 p.m. GMT+01:00, Patrick Steinhardt <ps@pks.im> wrote:\n>On Sat, Mar 30, 2024 at 11:59:51AM +0100, Olliver Schinagl wrote:\n>> On 30-03-2024 10:06, Patrick Steinhardt wrote:\n>> > On Sat, Mar 30, 2024 at 09:20:22AM +0100, Olliver Schinagl wrote:\n>> > > On 30-03-2024 09:18, Patrick Steinhardt wrote:\n>> > > > On Sat, Mar 30, 2024 at 09:14:47AM +0100, Olliver Schinagl wrote:\n>> > > > > On 22-03-2024 14:04, Patrick Steinhardt wrote:\n>> > > > > > On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n>> > > > > > > (Sorry for initially sending this privately to Patrick.)\n>> > > > > > > \n>> > > > > > > On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n>> > > > > > [snip]\n>> > > > > > > > I'd personally rather go with the latter, mostly because it matches our\n>> > > > > > > > git-scm.com domain. I also like it better than the current git-vcs/git\n>> > > > > > > > because of that.\n>> > > > > > > > \n>> > > > > > > > So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n>> > > > > > > > additional owner of that group?\n>> > > > > \n>> > > > > I'll empty out my gitscm group, make it private so that it won't be\n>> > > > > accidentally used and transfer ownership to pks-t. You can then 'do what is\n>> > > > > needed' with the group. Since gitlab doesn't support aliases (yet? :p) best\n>> > > > > to park the namespace.\n>> > > > > \n>> > > > > Olliver\n>> > > > \n>> > > > By the way, thanks a ton for being this open and helpful during the\n>> > > > whole process. This is greatly appreciated!\n>> > > \n>> > > Hey, no problem. I initiated this discussion because I wanted to get to this\n>> > > solution. Just because my mirror is not used doesn't mean I don't agree :)\n>> > > \n>> > > Btw, I can't transfer the group, it's empty, but if I delete it _right now_,\n>> > > you'll have to re-create it, _right_now_ (well within the next 5 minutes?).\n>> > \n>> > Shouldn't it be possible to add me as a secondary owner of the group in\n>> > [1]? From thereon I could \"transfer\" the group by removing you from it.\n>> \n>> Done and done.\n>> \n>> I'll remove myself, or you can kick me :( one I know you have successfully\n>> received ownership. I tried to invite the group git-scm but that couldn't be\n>> found, probably you can do that (and then remove yourself :p)\n>> \n>> Would have been useful to transfer ownership of a group, iirc you do that\n>> with repo's as well? Under the hood it could use the invite + remove members\n>> thing. Though this works.\n>\n>Thanks! I've added Christian to this group such that it has a higher bus\n>factor. I guess it should probably have the same owners as the \"git-scm\"\n>one just in case we ever want to do anything with it. I've also removed\n\nCould you not just invite the git-scm group and have no members at all?\n\n\n>you from this group now.\n>\n>Patrick\n"},{"id":"491921","messageId":"ZgkQQhW6GegFNqfB@ncase","threadId":"60644","inReplyTo":"4A3E0E2D-2922-4C90-A306-30A685D11C4D@schinagl.nl","subject":"Re: Git mirror at gitlab","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2024-03-31T07:26:58Z","receivedAt":"2024-03-31T07:27:05Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"On Sun, Mar 31, 2024 at 12:54:12AM +0100, Olliver Schinagl wrote:\n> \n> \n> On March 30, 2024 7:06:51 p.m. GMT+01:00, Patrick Steinhardt <ps@pks.im> wrote:\n> >On Sat, Mar 30, 2024 at 11:59:51AM +0100, Olliver Schinagl wrote:\n> >> On 30-03-2024 10:06, Patrick Steinhardt wrote:\n> >> > On Sat, Mar 30, 2024 at 09:20:22AM +0100, Olliver Schinagl wrote:\n> >> > > On 30-03-2024 09:18, Patrick Steinhardt wrote:\n> >> > > > On Sat, Mar 30, 2024 at 09:14:47AM +0100, Olliver Schinagl wrote:\n> >> > > > > On 22-03-2024 14:04, Patrick Steinhardt wrote:\n> >> > > > > > On Fri, Mar 22, 2024 at 11:08:34AM +0100, Christian Couder wrote:\n> >> > > > > > > (Sorry for initially sending this privately to Patrick.)\n> >> > > > > > > \n> >> > > > > > > On Fri, Mar 22, 2024 at 10:41 AM Patrick Steinhardt <ps@pks.im> wrote:\n> >> > > > > > [snip]\n> >> > > > > > > > I'd personally rather go with the latter, mostly because it matches our\n> >> > > > > > > > git-scm.com domain. I also like it better than the current git-vcs/git\n> >> > > > > > > > because of that.\n> >> > > > > > > > \n> >> > > > > > > > So Chris, would you mind adding me (@pks-t, my non-GitLab handle) as an\n> >> > > > > > > > additional owner of that group?\n> >> > > > > \n> >> > > > > I'll empty out my gitscm group, make it private so that it won't be\n> >> > > > > accidentally used and transfer ownership to pks-t. You can then 'do what is\n> >> > > > > needed' with the group. Since gitlab doesn't support aliases (yet? :p) best\n> >> > > > > to park the namespace.\n> >> > > > > \n> >> > > > > Olliver\n> >> > > > \n> >> > > > By the way, thanks a ton for being this open and helpful during the\n> >> > > > whole process. This is greatly appreciated!\n> >> > > \n> >> > > Hey, no problem. I initiated this discussion because I wanted to get to this\n> >> > > solution. Just because my mirror is not used doesn't mean I don't agree :)\n> >> > > \n> >> > > Btw, I can't transfer the group, it's empty, but if I delete it _right now_,\n> >> > > you'll have to re-create it, _right_now_ (well within the next 5 minutes?).\n> >> > \n> >> > Shouldn't it be possible to add me as a secondary owner of the group in\n> >> > [1]? From thereon I could \"transfer\" the group by removing you from it.\n> >> \n> >> Done and done.\n> >> \n> >> I'll remove myself, or you can kick me :( one I know you have successfully\n> >> received ownership. I tried to invite the group git-scm but that couldn't be\n> >> found, probably you can do that (and then remove yourself :p)\n> >> \n> >> Would have been useful to transfer ownership of a group, iirc you do that\n> >> with repo's as well? Under the hood it could use the invite + remove members\n> >> thing. Though this works.\n> >\n> >Thanks! I've added Christian to this group such that it has a higher bus\n> >factor. I guess it should probably have the same owners as the \"git-scm\"\n> >one just in case we ever want to do anything with it. I've also removed\n> \n> Could you not just invite the git-scm group and have no members at all?\n\nIn theory yes. In practice though this could cause us to hit the free\nuser limit in the \"gitscm\" group eventually. This could be fine given\nthat we don't intend to use the group anyway. But I wasn't a 100% sure\nand wanted to double check first before doing that.\n\nPatrick\n"}]}