To be honest, I didn't really have energy to read all of the thread, by skimming it, I would like to add my thoughts w.r.t. the path forward.
I really like the idea of having a RedHat/Fedora/CentOS provided an supported GitLab. But as we plan to ahe gitlab as the alternative to pagure as both gitforge and distgit, this sounds like two projects, with two distinct pilots and testing periods and re-evaluation. What I really want to be mindful are sunk-cost fallacies and unknown-unknowns. So we need to be able to say "we tried but we need more resources" or even "we tried but it is not working out and we are pulling the plug". We might get to a point where we'd see that GitLab is a great forge, but we drastically underestimated resources to actually support migration to use it as a new dist-git. I have been through a plan to replace an established but under-staffed/under-developed tool at RedHat. As a QE at RedHat, I have been through a switch from our TestCaseManagementSystem to Polarion. These days we mostly use it as an excellent example how not to replace tools in your company :D There was almost no pilot, limited testing-period, and little support for people attempting to migrate, especially as we were starting to see how the tool didn't fit the volume of test-cases we wanted to store there. I have a fair degree of trust that we will introduce GitLab in a more reasonable way :-) Adam
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
