On Mon, Feb 07, 2022 at 09:56:32PM +0100, Neels Hofmeyr wrote:
On Sat, Feb 05, 2022 at 09:57:29PM +0100, Harald Welte wrote:
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.
All projects I work on are on gerrit. Does that mean I will not even notice that gitea was introduced?
indeed, for you it won't make a difference, I guess. At least not as long as you always clone your repos from gerrit and not from git.sysmocom.de.
Will I need to do anything on the gitea UI, other than creating a new repository once every other year, if at all?
nope.
Is it going to be gerrit on the one side, and gitea on the other, so that there are two "classes" of git repositories with different workflows required for each?
We already have that fragmentation today: Some repositories use gerrit, others not. Think of rtl-sdr, osmo-fl2k, gmr, ...
We clearly did not want to make the use of gerrit mandatory for those projects/ maintainers that don't want the related overhead.
I don't personally have a reason to change anything, I see infrastructure fragmentation as something worth avoiding, and I don't particularly yearn for more web UI, but fine if it makes someone else's day.
Today, most of the new git repositories, new ssh keys, etc to git.osmocom.org are added by me, and with gitea that won't be neccessary anymore. Admittedly, it's not a lot, but I think it's better to give more control to the program/project maintainers rather than the sysadmin of the server.
I did oppose adopting gerrit back in the days, and gerrit has indeed been a huge help in code review
Agreed.