![](https://seccdn.libravatar.org/avatar/a4139df10120ce151e457fd1faff018d.jpg?s=120&d=mm&r=g)
On 8/16/22 18:45, Vojtěch Zeisek wrote:
Dne pondělí 15. srpna 2022 17:50:10 CEST, Jacob Michalskie napsal(a):
On Mo, Aug 15 2022 at 15:47:46 -0000, doug demaio wrote:
Questions Rephrased: 1. Should we begin to think about alternatives to source code hosting services like GitHub and GitLab?
I logged in and it looks like "light version of GitLab". Why not. I then wonder what is <https://gitlab.opensuse.org/> ...? And then there seems to be empty <https://gitlab.com/openSUSE> ... Ehhh... Why do we need all this, and <https://github.com/openSUSE/> and I-don't-know-what-else...? R
The github namespace is actively used to develop a significant portion of openSUSE's software (build.opensuse.org is designed for distributing software not creating it). The board made the choice to register the gitlab group, not because we had any plans to use it but rather it was much simpler to hold it then risk someone else taking it and then have to deal with the process of gaining access back due to the fact that we (well SUSE) owns the trademark. egardless this important issue, this distribution of code elsewhere (not mentioning <https://bugzilla.opensuse.org/> and <https://build.opensuse.org/> - where to report which issue is always confusing for me) is terrible messy. I really think we should have *one* location, preferably hosted by openSUSE, regardless what it is. One of the main issues here is someone needs to volunteer to maintain such infra, for a long time there was no such people willing to do so and we had nothing now code.opensuse.org exists but I don't believe it was strictly implemented to replace all our existing github projects. Another fundamental pillar of openSUSE is that we empower our teams to choose what works best for them including code platforms, so if a team decided that they wished to migrate there git repos from github to gitlab or anything else including something self hosted then we have nothing preventing them from doing such. SUSE has a policy of putting any open source code that it would welcome community contributions to under the openSUSE namespace on github (And open code its not really looking for contributions to under the SUSE namespace). At the end of the day what SUSE does is up to them but it always encourages employees to upstream any code they do on SUSE's behalf to the best possible upstream so some openSUSE teams moving wouldn't cause issues from that perspective. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B