On Tue, 21 Jan 2020 at 22:32, Michael Catanzaro <mcatanz...@gnome.org> wrote:
> On Tue, Jan 21, 2020 at 4:04 pm, Neal Gompa <ngomp...@gmail.com> wrote: > > And any discussion of GitHub isn't going to involve self-hosted, it's > > going to involve GitHub.com, which means we're talking about losing > > more of our independence as a project. This is one of those things > > that I'm not sure is a wise move. > > Well since we have a request for requirements: I propose requirements > #1 and #2 are to be self-hosted and open source. I'm suspect the Fedora > community would be outraged if we fail to meet either requirement. > > So if we can agree on that much, then we can avoid wasting time by > including GitHub in the list of options. That would bring us to a > choice between GitLab CE and Pagure. (Are there any other serious > options?) > Thanks for actually proposing some requirements :-). In my opinion there are 2 different use cases : - pagure.io : For me the requirements here is to provide a place for community members to host there projects. And project here can mean anything it can be actual source code, documentation, or just a README with some info about a team or like many team have just a ticket tracker. Once of the strong requirement is that whatever the solution is it needs to integrate with Fedora Account System and user should be able to use Single Sign On. Regarding the use case where a team wants to have a issue tracker and maybe a README to give details about how to contribute to that team I think teams.fedoraproject.org should be the prefered solution, for the second where people want to host a git project (code, documentation, book, etc ...) I don't think this needs to be solved by the Fedora community, there are many options (free and non free, as in freedom) which have dedicated infrastructure and dedicated teams running this type of service. - dist-git (src.fedoraproject.org): This is a different use case, since here the solution needs to integrate with the rest of the infrastructure. the list of requirements here will be more specific for example it needs to be able to integrate with Fedora FAS but also to have the FAS group synced, branch ACLs, a way to integrate with release-monitoring, a way to integrate with bugzilla, a way to integrate with fedora-messaging (RabbitMQ), .... In general I think most of the integration with our infrastructure can be done with any solution either using the solution APIs or plugins system. After we need to compare the cost of developing and maintaining these pieces of glue to integrate everything against the current situation. > Michael > > _______________________________________________ > 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 >
_______________________________________________ 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
