fuzzyworld

fuzzyworld-tools / files / server / content / contribute.md

contribute.md

1.5 KB · history · blame


title: How to contribute

How to contribute

Thanks for wanting to help! This site has no accounts, issue tracker or merge requests, so contributions arrive by email. Two ways work, both with plain git.

1. Share a branch

Best for anything bigger than a small fix.

  1. Clone the repository: git clone https://code.fuzzyworld.net/<repo>.git
  2. Make your change on a branch, and push that branch to any public git host you like (GitHub, Codeberg, GitLab, your own server).
  3. Email the repository URL, the branch name and a short description to contrib-68uq+<repo>@fuzzyworld.net, using the repository's name in place of <repo>.

I fetch the branch, review it locally, and reply by email.

2. Email a patch

Good for small changes. Commit your change, then create a patch file:

git format-patch origin/main

and attach the .patch file(s) to an email to contrib-68uq+<repo>@fuzzyworld.net. If you use git send-email, that address works there too.

Bug reports and ideas

No git needed: email bugs-k7q4+<repo>@fuzzyworld.net. Many of the apps have a report link that fills in the details for you.

Before you send

Why there are no merge requests here

Source
1---
2title: How to contribute
3---
4
5# How to contribute
6
7Thanks for wanting to help! This site has no accounts, issue tracker or merge requests, so contributions
8arrive by email. Two ways work, both with plain git.
9
10## 1. Share a branch
11
12Best for anything bigger than a small fix.
13
141. Clone the repository: `git clone https://code.fuzzyworld.net/<repo>.git`
152. Make your change on a branch, and push that branch to **any** public git host you like
16 (GitHub, Codeberg, GitLab, your own server).
173. 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
20I fetch the branch, review it locally, and reply by email.
21
22## 2. Email a patch
23
24Good for small changes. Commit your change, then create a patch file:
25
26```
27git format-patch origin/main
28```
29
30and attach the `.patch` file(s) to an email to `contrib-68uq+<repo>@fuzzyworld.net`.
31If you use `git send-email`, that address works there too.
32
33## Bug reports and ideas
34
35No 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/)