- 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
Forge evaluations done by other Free Software organizations¶
The FSF is currently evaluating forges to compliment their Savannah servers: https://www.fsf.org/blogs/sysadmin/coming-soon-a-new-site-for-fully-free-collaboration
FSF 2020 forge evaluation page on the LibrePlanet wiki: https://libreplanet.org/wiki/FSF_2020_forge_evaluation
December 4th, 2020 update: "The FSF forge is still a work in progress. Since our last update, summer intern Amin Bandali deployed a testing instance of SourceHut, one of many possible programs for the forge." https://www.fsf.org/bulletin/2020/fall/updates-from-the-fsf-tech-team
Possible forges for Replicant¶
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
- Completely integrated mailing list, build, todo, hub, and git repositories. Organizations/groups coming eventually.
- Simple user export of data
- AGPLv3, committed to free software philosophies and open source communities https://sourcehut.org/blog/2019-10-23-srht-puts-users-first/
- Also has wiki/manpage support, a paste service, and a dispatch service.
- Trisquel/Parabola installations would both work with minimal fuss: https://man.sr.ht/packages.md
- Alpine Linux is the most supported distribution, and doesn't meet RYF certification.
- Email setup can be a bit more complicated than alternatives, but it's fine if one is familiar with email concepts - SPF/DKIM/etc
- Drew maintains that sourcehut is "in alpha stage" - he goes over what that means here: https://sourcehut.org/alpha-details
Relevant email from the libreplanet-dev email list about how the Sourcehut CI can optionally be adapted to provide CI support for other forges, like Pagure and Gitea: https://lists.libreplanet.org/archive/html/libreplanet-dev/2021-01/msg00001.html