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
On 1/21/20 11:34 AM, 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.
The blog post was not clear about dist-git / src.fedoraproject.org other than this change affecting package maintainers. What is the projected impact on this service as it relates to Pagure sustainability?
While the analysis make sense, as principal actor of one of our platform migration for the same reason (we leave Zanata because it's not core to Red Hat), it doesn't makes me comfortable to see github as an alternative.
Github doesn't fit with the values of pur community.
council-discuss@lists.fedoraproject.org