Dan Čermák <dan.cermak@xxxxxxxxxxxxxxxxxxx> writes: > Rahul Sundaram <metherid@xxxxxxxxx> writes: > >> Hi >> >> On Fri, Jan 31, 2020 at 10:46 AM Pierre-Yves Chibon wrote: >> >>> >>> Welcome to our lives! >>> If it was mathematically possible to go above 100% that's how much >>> agreement you >>> would have from us. >>> >> >> If Red Hat is using Pagure internally, it is really odd to discuss >> replacing Pagure with something else. The only viable replacement is >> Gitlab which is a open code project written in a language that isn't a >> strong fit for Fedora. Red Hat should be assigning more resources >> (development & infrastructure) to add the features needed to extend Pagure >> going forward and reduce the burden on the CPE team. Has CPE leadership >> considered talking internally about that? > > I have to second this: why are we even *having* this discussion, when > Pagure is used internally at RedHat and thus RedHat will require some > form of maintenance anyway? Why is then the RedHat CPE team pushing to > move away from Pagure, especially to Gitlab? Which albeit being a great > platform, is written in Ruby and there's a lot less Ruby devs in the > Fedora community than Python devs. I have to apologize, this was far too harsh. What I wanted to say is the following: wouldn't it be mutually beneficial for RedHat, Fedora and specifically the CPE Team too, that someone¹ takes over maintenance of Pagure since it's used by us all and there appear to be enough people that want to continue using it? Cheers, Dan ¹: Yeah, I know that this is actually the tricky part to find this someone…
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx