On Tuesday, 21 January 2020 17:34:37 CET Leigh Griffin wrote: > Hey Everyone, > > On behalf of the CPE team I want to draw the communities attention to a > recent blog post which you may be impacted by: > https://communityblog.fedoraproject.org/git-forge-requirements/ > > We will be seeking input and requirements in an open and transparent manner > on the future of a git forge solution which will be run by the CPE team on > behalf of the Fedora Community. This mail is being sent to the devel, > mindshare and council-discuss lists for maximum visibility on a BCC to > allow each list have their own views. Please forward it to any other list > you may feel is relevant to maximise the exposure. > > Thanks in advance, > Leigh Quote: >At the same time, integrations that already exist in Pagure may need to be created for another git forge, which is a cost as well. This also needs to be fully considered by the team as part of the requirement gathering. We just got Release-monitoring integration in Pagure, how would that be implemented in a new forge? What man-hours are you ready to commit to this new forge that can't equally be equally be committed to Pagure? At least with Pagure, we have people who know the codebase, would it be that easy to do custom integration with Git{hub,lab}? GitHub is also, as far as I know, not free; wouldn't that be in contradiction with Fedora mission-statement to use it over a free alternative? Best regards, Robert-André _______________________________________________ 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
