It’s an ongoing debate in one of the projects I work with if we should move to a more forge oriented development process. For all it’s faults email does provide a good record of discussion as well as evidence of review.
Forge is a newish term for systems like github, gitlab, forgejo, gitea, etc that provide source control, project management, issues, and discussion features for projects.
And more to the point, Forge is a free, open-source server that allows players to install and run Minecraft mods. It was designed with the intent to simplify compatibility between community-created game mods for Minecraft: Java Edition.
It sounds like maybe OP and their crew were maintaining Minecraft compatibility via e-mail prior to the release of Forge.
We use GitLab for hosting and CI as well as the issue tracker. Just the patch workflow goes over email although we have considered just maintainers submitting pull requests once the review and tags have been collected on list.
A lot of the more senior maintainers find the process of patch review in the webui suboptimal compared to email.
It’s an ongoing debate in one of the projects I work with if we should move to a more forge oriented development process. For all it’s faults email does provide a good record of discussion as well as evidence of review.
I’ve not heard of this before, and a search finds a lot about Minecraft?
Forge is a newish term for systems like github, gitlab, forgejo, gitea, etc that provide source control, project management, issues, and discussion features for projects.
And more to the point, Forge is a free, open-source server that allows players to install and run Minecraft mods. It was designed with the intent to simplify compatibility between community-created game mods for Minecraft: Java Edition.
It sounds like maybe OP and their crew were maintaining Minecraft compatibility via e-mail prior to the release of Forge.
Wait does that mean comment thread OP isn’t using any of those things?
It’s not uncommon for older projects to use plain git, patch files, and email groups. Linux kernel development still gets done that way every day.
Ah right. I thought you meant that there was no project management or revision system. That does make more sense
The project management capabilities of GitLab are pretty nice, for what my opinion is worth.
Then Sourcehut is built around email, so that might be a good middle ground.
We use GitLab for hosting and CI as well as the issue tracker. Just the patch workflow goes over email although we have considered just maintainers submitting pull requests once the review and tags have been collected on list.
A lot of the more senior maintainers find the process of patch review in the webui suboptimal compared to email.