Closed benoitc closed 3 years ago
I have no issues going to gitlab what so ever. I generally prefer it. The only hitch is what you already stated, which is maintenance, and I would agree, it's generally automatic. We would have to back up to vultr object storage, in addition to image snapshots.
There's only one thing I would not want us to maintain and that is a CI server. I don't think we really have a strong need for that, erlef website aside, but I do think we need a solid solution for that if we're on gitlab. This is an area I don't have any experience in, in that anytime I've run my own gitlab I've always run my own gitlab-ci server in conjunction with it, but that was part of my job 😁
Do you have any thoughts on this?
interresting to read : https://about.gitlab.com/blog/2020/09/08/gnome-follow-up/
I should look out the IT budget numbers for Eclipse but I think they have more than a handful of full-time IT guys. I think we need to stay in SaaS land for the time being
closing issue. no action since awhile.
Following their move in Europe, the Eclipse foundation have also setup a Gitlab service to host all the repositories. It will comes in addition to their Github :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=537913
They are mainly doing it to open the Eclipse projects for more people and keep the control on the sources supported by the foundation.
Coming with this idea of using the Foundation to host and maintain orphaned Erlang projects I was thinking that Gitlab would perfectly fit. This could be done in addition to github and synchronize between the services if needed.
Also this is not the only foundation to have choosen that path. Kde, Gnome are also doing it.
Pro:
Cons:
Notes
Copying and mirroring our current Github to Gitlab is straight forward. I propose the following agenda:
Anyway let's discuss and raise the Pros/Cons about it in comments there.