On Fri, 17 Sept 2021 at 09:51, Leigh Griffin <lgriffin@redhat.com> wrote:

Hey everyone,

This came up on the call yesterday to open a discussion about where we should host our code and I'd like to open it up here for transparency on the path forward. We have a lot of options in this sphere and all are Git based. 

Historically, CentOS SIGs had their code hosted at https://git.centos.org/.  That's wired up to the CentOS Account system so users can login seamlessly. Some SIGs have opted to host on Github as well and use their own Github profile (which is not connected to their CentOS account). 

Currently, CentOS Stream is being built in the open at gitlab.com/redhat/centos-stream where community contributors can create a Gitlab account and interact with CentOS Stream. Gitlab is not currently wired into the CentOS Account system and the team is working to get that integration on the  gitlab.com/CentOS project (which is currently dormant). 

The suggestion put forward by Pierre-Yves Chibon, who is leading the effort within Red Hat on creating the services and infrastructure for the SIG, is to base ourselves on Gitlab. We can create a gitlab.com/redhat/automotive-sig project and mirror it at gitlab.com/centos/automotive-sig so we can show people where we will work once we've resolved the authentication question. The drawback is the need to use a gitlab.com account, which, in time, we can merge into the CentOS Account when the integration is completed. The key benefit of having us base our code on Gitlab is the closeness to Stream from a codebase perspective and the potential to use similar tools and approaches as their development workflow. 

While no formal decision on where the overall CentOS SIGs will host their code in the future has been made, the presence of Stream on Gitlab is potentially future proofing us against a migration.

Well won't we possibly have to do a migration even if we are on gitlab? [From /redhat/ to /centos/ ?]

My experience of migrations is that people do better on BIG migrations rather than small ones. If you have them go from gitlab.com/X to gitlab.com/Y they are going to stick to X  to the point that Y rarely gets traction. [Even similar names have the same issue. Going from github.com to gitlab.com, people will keep going back to github because their fingers keep typing it long after they should have learned something new.] I would suggest a bigger migration where naming and any searches in scripts for say 'git.we_knew_this_was_temporary_in_2019.com'** to 'gitlab.com/centos' is easier to find. 

** not valid dns hostname.

 

Does the community have a strong preference for where we should base our repos? I'm going to suggest we leave this topic percolate for a week to have some dialog on the best path forward and then create our presence on the source forge of choice.

Thanks,

Leigh

--

Leigh Griffin

Senior Engineering Manager

Red Hat Waterford

Communications House

Cork Road, Waterford City

lgriffin@redhat.com    
M: +353877545162     IM: lgriffin

@redhatjobs   redhatjobs @redhatjobs  

_______________________________________________
CentOS-automotive-sig mailing list
CentOS-automotive-sig@centos.org
https://lists.centos.org/mailman/listinfo/centos-automotive-sig

--

Stephen Smoogen, Red Hat Automotive

Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren

_______________________________________________
CentOS-automotive-sig mailing list
CentOS-automotive-sig@centos.org
https://lists.centos.org/mailman/listinfo/centos-automotive-sig