Fwd: [op25-dev] RFC: migrating git.osmocom.org to gitea?

Hi Harald, Thanks for the email and the continued support of the OP25 project. I don't seem to have permissions to the original ticket. Moving to gitea looks great and the additional features look very handy. Cheers, Matt [image: image.png] ---------- Forwarded message --------- From: Harald Welte &lt;laforge(a)osmocom.org&gt; Date: Sun, 6 Feb 2022 at 08:01 Subject: [op25-dev] RFC: migrating git.osmocom.org to gitea? To: &lt;openbsc(a)lists.osmocom.org&gt; Cc: &lt;simtrace(a)lists.osmocom.org&gt;rg>, &lt;tetra(a)lists.osmocom.org&gt;rg>, < osmocom-sdr(a)lists.osmocom.org&gt;gt;, &lt;op25-dev(a)lists.osmocom.org&gt;rg>, < baseband-devel(a)lists.osmocom.org&gt; Hi all! [please follow-up-to the openbsc(a)lists.osmocom.org mailing list, if there is any discussion, we don't want to drag it over tons of mailing lists in parallel] Some weeks ago, I created https://osmocom.org/issues/5397 but it seems nobody noticed the ticket or had any comments to it. So let me post this as RFC here on the mailing list: In the past, we had a gitolite/gitosis setup, which was fine in the early days of git, but it means that people cannot easily create new repositories, see who has permissions, and we cannot delegate ownership. Even updating SSH keys requires manual interaction of a sysadmin like me. I would therefore suggest to migrate git.osmocom.org to gitea[1] This would allow the following features: * users can self-create any number of personal repositories (like gitlab/github) * we can create 'organizations' along the line of reasonably independent osmocom member projects like op25, who can then manage their own repos/permissions/... * gitea can link to redmine wiki and redmine issue trackers (rather than using its own built-in) For those repositories hosted in gerrit (mainly CNI), we would still keep git.osmocom.org a read-only mirror, like we do it right now. For those repositories not hosted in gerrit, users/projects could then accept merge requests in gitea. Coupling this with 3rd party authentication via github/gitlab/etc should make it easier for the occasional contributor to submit changes. There is a downside, of course; A lot of repo URLs have to change. Most of our current repositories are at git.osmocom.org/project.git while gitea follows a git.osmocom.org/organization/project.git scheme. I'm not sure there is any way to help to mitigate this... Any thoughts, comments? [1] https://gitea.io/ -- - Harald Welte &lt;laforge(a)osmocom.org&gt; http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)