Re: RFC: migrating git.osmocom.org to gitea?

2022-02-07 Thread Pau Espin Pedrol

Hi again,

I now realize this is a thread started in several mailing lists by 
Harald, so it seems I was missing the context with my previous email.


After reading Harald's email, it seems it's about adding gitea while 
still keeping the gerrit+redmine. So I'm fine with, I don't mind it that 
way.



--
- Pau Espin Pedrol  http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte


Re: RFC: migrating git.osmocom.org to gitea?

2022-02-07 Thread Pau Espin Pedrol

Hi,

which use would you like to give to gitea exactly? For wiki/tickets we 
have redmine already, and for submission (code review) we do have 
gerrit. What are you suggesting exactly? Simply have a readonly gitea 
instance to navigate instead of cgit? Or replace redmine + gerrit with 
gitea?


I'd personally oppose to replace redmine + gerrit to gitea, specially 
for the code review part.


--
- Pau Espin Pedrol  http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte


RFC: migrating git.osmocom.org to gitea?

2022-02-05 Thread Harald Welte
Hi all!

[please follow-up-to the open...@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 http://laforge.gnumonks.org/

"Privacy in residential applications is a desirable marketing option."
  (ETSI EN 300 175-7 Ch. A6)