fuzzyworld-tools / files / server / content / contribute.md
contribute.md
829da61a 2026-10-28 Pavel Safronov | 1 | --- |
| 2 | title: How to contribute | |
| 3 | --- | |
| 4 | ||
| 5 | # How to contribute | |
| 6 | ||
| 7 | Thanks for wanting to help! This site has no accounts, issue tracker or merge requests, so contributions | |
| 8 | arrive by email. Two ways work, both with plain git. | |
| 9 | ||
| 10 | ## 1. Share a branch | |
| 11 | ||
| 12 | Best for anything bigger than a small fix. | |
| 13 | ||
| 14 | 1. Clone the repository: `git clone https://code.fuzzyworld.net/<repo>.git` | |
| 15 | 2. Make your change on a branch, and push that branch to **any** public git host you like | |
| 16 | (GitHub, Codeberg, GitLab, your own server). | |
| 17 | 3. Email the repository URL, the branch name and a short description to | |
| 18 | `contrib-68uq+<repo>@fuzzyworld.net`, using the repository's name in place of `<repo>`. | |
| 19 | ||
| 20 | I fetch the branch, review it locally, and reply by email. | |
| 21 | ||
| 22 | ## 2. Email a patch | |
| 23 | ||
| 24 | Good for small changes. Commit your change, then create a patch file: | |
| 25 | ||
| 26 | ``` | |
| 27 | git format-patch origin/main | |
| 28 | ``` | |
| 29 | ||
| 30 | and attach the `.patch` file(s) to an email to `contrib-68uq+<repo>@fuzzyworld.net`. | |
| 31 | If you use `git send-email`, that address works there too. | |
| 32 | ||
| 33 | ## Bug reports and ideas | |
| 34 | ||
| 35 | No git needed: email `bugs-k7q4+<repo>@fuzzyworld.net`. Many of the apps have a **report** link that fills in the details for you. | |
| 36 | ||
| 37 | ## Before you send | |
| 38 | ||
| 39 | - Check the repository's README (and CONTRIBUTING, if it has one) for how to build and test it. | |
| 40 | - One change per branch or patch, please; it makes review much quicker. | |
| 41 | - By contributing you agree that your change is shared under the repository's license. | |
| 42 | ||
| 43 | [Why there are no merge requests here](/why-i-left-gitlab/) |