Hi Harald, everyone,
Unfortunately I haven't had the opportunity to actively work on anything
osmocom for quite a while now, however I think I can contribute a few ยข
on this one.
I have been using Gitea for about a year now, and I am generally very
happy with it. It even includes some collaborative features, like
project boards (
https://github.com/go-gitea/gitea/pull/8346). It has a
few annoying bugs or issues, like #17808 when creating new pages in the
wiki (
https://github.com/go-gitea/gitea/issues/17808), or the lack of a
"cancel" button to return while modifying a page.
I have also used the integration of accounts with LDAP, which worked
well, except when I realized that I hadn't created any administrator
account prior to that; but this could be solved with Gitea's own CLI tool.
About the repo URLs, I suppose you could host Gitea at eg
gitea.osmocom.org, and put redirections in place on
git.osmocom.org. A
default page with instructions about how to reach Gitea could be
configured there, until enough URL rewriting rules are identified and
put in place.
In the meantime, HTH,
-- khorben
On 05/02/2022 21:57, Harald Welte wrote:
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/ --
khorben