Amarok/Development/Join: Difference between revisions
< Amarok | Development
add a tip for new contributors |
add another tip *sigh* |
||
| Line 1: | Line 1: | ||
Here is a list of important things an Amarok developer should know: | Here is a list of important things an Amarok developer should know: | ||
{{Tip|1=<span style="color:red;">To potential GSoC students:</span> please read all the documentation first before asking questions. We do not have time to teach you the basics, the documentation is there for that, so READ!}} | {{Tip|1=<span style="color:red;">To potential GSoC students:</span> please read all the documentation first before asking questions. We do not have time to teach you the basics, the documentation is there for that, so READ! - | ||
If you want to develop for Amarok, make sure you have a recent KDE and Linux distribution, LTS releases are not suitable for development - And finally Qt4 != Qt5}} | |||
{{Tip | 1=<span style="color:red;">To new contributors:</span> please get in touch with us on the amarok-devel mailing list before starting to implement features, this will spare you some precious time.}} | {{Tip | 1=<span style="color:red;">To new contributors:</span> please get in touch with us on the amarok-devel mailing list before starting to implement features, this will spare you some precious time.}} | ||
Revision as of 12:49, 28 February 2014
Here is a list of important things an Amarok developer should know:
| Tip |
|---|
| To potential GSoC students: please read all the documentation first before asking questions. We do not have time to teach you the basics, the documentation is there for that, so READ! - If you want to develop for Amarok, make sure you have a recent KDE and Linux distribution, LTS releases are not suitable for development - And finally Qt4 != Qt5 |
| Tip |
|---|
| To new contributors: please get in touch with us on the amarok-devel mailing list before starting to implement features, this will spare you some precious time. |
- The Amarok source code
- The API documentation
- KDE Bug Tracker - search for "Amarok" (also listed under "Products")
- KDE Review Board for submitting patches
- IRC channels on freenode:
- Mailing Lists:
- Amarok calendar - events and release schedule
- A list of the current Amarok developers
Other tools:
- HACKING folder in source (a must read!)
- Amarok Architecture Overview in source, a sub-directory of the above
- An introduction to Git
- Junior Jobs - Bugs suitable for people who would like to get involved with Amarok hacking, but aren't sure where to start.
- commit account - Getting a commit account for KDE
- commit filter - sign up to receive emails of all commits to Amarok
- Jenkins continuous integration - The Jenkins continuous integration tool for Amarok
- Fisheye - recent commits and way to browse through Git history (not real-time)
- English Breakfast Network - a static code analyzer for KDE
- Tech Base - A guide to contributing to KDE. Pretty much everything there is also applicable to Amarok.
You might also want to keep an eye on: