Intro for Developers

The Website League runs on a lot of different software, mostly adopted from the existing Fediverse and ActivityPub ecosystems.

Where to Contribute

The primary repository for all of the projects we've adopted is hosted on gitlab:

https://gitlab.com/website-league

For every repository here, wl-stable is the branch we recommend node operators use. If you want a change to be shared across the league, your goal should be to submit a gitlab merge request to one of these repositories.

This also means you don't need to be a node operator, or even a steward, to contribute! Though, before recommending a patch be adopted everywhere, it may help to contact a node operator directly to test your changes in production.

What to Contribute

If you're fixing a technical issue, bug, or generally useful feature: consider submitting it to the upstream project, and then merging into wl-stable from there. This way, everyone benefits, and we can minimize the work league contributors need to provide to keep your patch alive.

If you're making a change to specific node to provide a local-only feature, you can do that in a local branch that doesn't need to be in wl-stable. If you're making a change that other league users might appreciate, but doesn't fit within the mission of the wider fediverse, submit it to wl-stable, and then merge afterward to pick it up. In other words: Start as far upstream as you can, and let the patch flow downstream.

For each feature, start by making a local feature branch. The best patches are small, self-contained, and easy for an outside observer to review, but a bad patch is better than no patch! A maintainer will look at your patch and provide feedback.

Thank you for contributing to the Website League.