Am Sun, 28 Feb 2021 16:14:55 +0100 schrieb Wolfgang Denk via Xenomai xenomai@xenomai.org:

Hi all,

In message 621240.1614155458@gemini.denx.de I wrote:

...

We have to move all public projects off gitlab.denx.de to a new gitlab instance; the new host name is then source.denx.de . We are fully aware that this will cause inconveniences, and I can only assure you that we try hard to keep these as limited as possible.

# Details

Around noon on Saturday, 2021-02-27, we will freeze all public repositories on gitlab.denx.de. They will still be readable/ cloneable but any attempt to push new commits after this point will fail.

We will then copy them over to the now host, source.denx.de . All custodian accounts will also be transferred, the same login credentials from gitlab.denx.de will work on source.denx.de .

The URLs for the repositories will stay the same, except of course for the host name. So, for example, the U-Boot mainline repository will then be hosted at

https://source.denx.de/u-boot/u-boot.git

We will install redirects to forward HTTP accesses from the old repository URLs to the new host. This should make the transition mostly transparent, but does not cover everything. The following needs to be taken care of manually:

• Update the SSH URI for pushing to the repositories. Just replace gitlab.denx.de with source.denx.de . We will transfer all the SSH-keys to the new host so nothing else should be needed.

• Make sure you're logging in on source.denx.de . Access to gitlab.denx.de will no longer work!

• CI runners connected to gitlab.denx.de need to be re-registered with source.denx.de .

The new host should hopefully be operational sometime on Sunday, 2021-02-28. We will send a further announcement once everything is back up and running.

As far as we were able to test it, the move has been completed and is fully functional again. All public project are now on the new gitlab instance source.denx.de

One fun side-effect is that pulling via ssh also does not work anymore. Because it seems account have been fully deleted. This mail did not make it to my inbox because it was only sent to a list i happen to read sometimes. It would have been nice to receive my own copy with me actually in "To:". Would have saved me a bit of time trying to understand what is wrong. Luckily i remembered the "New developer accounts on source.denx.de" mail from last week, where that URL seemed strange when i first read it.

I do not understand why this is not just gitlab (proper) or github. I hope this discussion was held with the communities of the affected projects involved. While being disruptive i would suggest for Xenomai to move away from denx. For the git side of the operations. To be more open and welcoming to users/contributers etc.

regards, Henning

If you should experience any problems, please do not hesitate to ask Harald Seiler hws@denx.de, he will try to help you.

Thanks for your patience!

Best regards,

Wolfgang Denk

Am Wed, 10 Mar 2021 08:56:48 +0100 schrieb Wolfgang Denk wd@denx.de:

Dear Henning,

In message 20210308083457.76db0c20@md1za8fc.ad001.siemens.net you wrote:

...

I do not understand why this is not just gitlab (proper) or github. I hope this discussion was held with the communities of the affected projects involved. While being disruptive i would suggest for Xenomai to move away from denx. For the git side of the operations. To be more open and welcoming to users/contributers etc.

Are you positively sure that moving to any otherhosting environment will have any positive effect on how the Xenomai community works?

I am not sure. But i would be willing to give it a try. Sitting on a platform that is open to everyone means we might see "stars", "fork-relationships" etc. We might have to close issues and MRs with ever repeating ... "please use ML". But at that point you are already talking to someone who used the easy collaboration effects to drive-by/random interact. And chances are high you get them onto the ML, we see this in other projects where we keep PRs and issues enabled even though we do not "use them".

We use the very same setup for U-Boot as well, which has a _much_ bigger and _much_ more active community. We have regular releases every 3 months, and most releases include commits from >200 developers from >30 employers. And the CI setup for U-Boot is in no respect (number of supported architectures / processors / boards / tool chains) less challenging than what you do in Xenomai, on contrary. Not to mention the development rate - U-Boot sees > 20 commits per day in mainline.

Xenomai does not have such a strong community, a point that needs to improve. Putting it on a social coding platform (probably in addition), where people can socialize could help. In a private gitlab social interaction is pretty limited, especially with a strict bouncer rejecting people that are invited to the party ;).

CI/CT needs mean a hoster is more than a storage of code, and also means that more stakeholders need access. Many public hosters give compute+storage away for free. Plus free code-coverage, style checking with commercial tools ... Good stuff. Stuff that any project can benefit from, just put a "mirror fork" on github, no offense to the main hoster ... they can stay.

Sorry, but I don't buy your "more open and welcoming to users/contri- buters" comment. THe existing environment has proven to work fine for a FOSS community project.

Maybe you know now.

regards, Henning

Best regards,

Wolfgang Denk