Becoming involved in Amarok development

[Nikolaj Hald Nielsen]

>  Also, how does one go about getting patches accepted to svn?

The best way to start out is to post svn patches against current trunk
to this list. Make patches by going to the amarok base dir and doing
"svn diff >> DESCRITIVE_NAME.patch". Then someone who is fammiliar
with that area of code will have a look at it and commit it if no
major issues are seen. Do make sure to always update your checkout and
resolve any conflicts before making the patch!

After doing this for a while, until we "get to know you" a little
better, we can look at setting up a write enabled svn account for you.

>  Hopefully I should be able to start doing a bit more on Friday (start
>  of the weekend for me :P). So far I've only been able to find a couple
>  of half-hour sessions to look at this, and I keep getting distracted
>  by other code paths :D.

Sounds really good! We need all the help we can get, as there are so
many cool thing possible with the new Amarok 2 framework. :-)

- Nikolaj