Amarok/Development/Join: Difference between revisions
< Amarok | Development
mNo edit summary |
mNo edit summary |
||
| Line 31: | Line 31: | ||
You might also want to keep an eye on: | You might also want to keep an eye on: | ||
* [https:// | * [https://blogs.kde.org/authors/amarok/ Amarok Blog] | ||
* [https://planet.kde.org Planet KDE] | * [https://planet.kde.org Planet KDE] | ||
* [https://dot.kde.org dot.KDE] | * [https://dot.kde.org dot.KDE] | ||
[[Category:Amarok]] | [[Category:Amarok]] | ||
Latest revision as of 11:41, 1 June 2024
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
- KDE Bug Tracker - search for "Amarok" (also listed under "Products")
- KDE Gitlab instance for submitting patches
- IRC channels on libera.chat:
- Mailing Lists:
- Amarok calendar - events and release schedule
- An outdated list of 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
- 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: