- Fully free software
- Low resource usage
- Workflow requirements:
- Have the ability to tell users, from within the forge how to send patches to the mailing list
- Friendly upstream that can accept patches for integrating it with a mailing based workflow.
- Code base where integrating a mailing list based workflow is not too hard to do
- Have it packaged in a distribution we can use in the FSF VMs to reduce maintenance cost
We used gitlab before and we had resource usage issues. The VM went out of RAM because of that.
From our FOSDEM 2020 report that is not yet released:
It also hide buttons, which is awful for users as they don't understand what is going on.
- The buttons seem to be greyed out when they cannot be used This is much better than Gitlab where the buttons like "Send pull request" completely disappear if the feature is deactivated. Having button like that disappearing is really bad as users struggle to understand what they are doing wrong and can't contribute, when in fact the feature is simply deactivated without any way that shows it.
- It's possible to create a theme that replaces the Pull Requests tab with a link (for instance the link could point to a page that explains how to send patches to the mailing list). src.fedoraproject.org uses that to replace the Issues tab with a link to Red Hat's Bugzilla
- There is some interest in bridging a mailing based workflow to pagure: https://pagure.io/pagure/issue/15
Contacts: #pagure on Freenode and/orthe email@example.com mailing list