Amarok/Development/Join: Difference between revisions

Revision as of 19:43, 2 March 2013

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!

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:

@@ Line 1: / Line 1: @@
 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!}}
 * [http://quickgit.kde.org/?p=amarok.git&a=summary The Amarok source code]