projects / mediagoblin.git / blame
| Commit | Line | Data |
|---|---|---|
| 5a40e1ec WKG |
1 | ==================== |
| 2 | Contributing HOWTO | |
| 3 | ==================== | |
| 4 | ||
| 5 | We're super glad you want to contribute! | |
| 6 | ||
| 7 | There are a variety of ways you can help us and become part of the | |
| 8 | team. We're not just looking for coders! We're also looking for | |
| 9 | documentation writers, users, testers, evangelists, painters, bakers, | |
| 10 | candle-stick makers... | |
| 11 | ||
| 12 | However, if you are a coder and you're looking to code, check out the | |
| 13 | :ref:`hacking-howto`. | |
| 14 | ||
| 15 | The rest of this chapter talks about different things we need your | |
| 16 | help with. | |
| 17 | ||
| 18 | **File bugs** | |
| 19 | ||
| 20 | Filing bugs is an important part of any project. For more | |
| 21 | information on filing bugs, see :ref:`filing-bugs`. | |
| 22 | ||
| 23 | ||
| 24 | **Translate GNU MediaGoblin** | |
| 25 | ||
| 26 | Knowing more than one language is an important skill. If you are | |
| 27 | multi-lingual and are interested in translating GNU MediaGoblin, | |
| 28 | see :ref:`translating`. | |
| 29 | ||
| 30 | FIXME - add additional things here | |
| 31 | ||
| 32 | ||
| 33 | .. _filing-bugs: | |
| 34 | ||
| 35 | File bugs | |
| 36 | ========= | |
| 37 | ||
| 38 | GNU MediaGoblin uses a bug tracker called `Redmine | |
| 39 | <http://www.redmine.org>`. | |
| 40 | ||
| 41 | The bug tracker is at http://bugs.foocorp.net/ and bugs go in the | |
| 42 | ``GNU mediagoblin`` project. | |
| 43 | ||
| 44 | FIXME - how to file a good bug report | |
| 45 | ||
| 46 | ||
| 47 | .. _translating: | |
| 48 | ||
| 49 | Translate GNU MediaGoblin | |
| 50 | ========================= | |
| 51 | ||
| 52 | FIXME - need to write this | |
| 53 | ||
| 54 | ||
| 55 | Where to go when you get stuck | |
| 56 | ============================== | |
| 57 | ||
| 58 | FIXME - need to write this |