Hi,

recently we have received quite a bit of patches for various parts of amaroK. Contribution is good, it's vital for the project. Patches are bad though. amaroK development is CVS-based, and this is the form of contribution we prefer.

Often it will happen that people submit patches to our mailing list, and they'll just get ignored. This is because we're lacking the time and motivation to actually apply and test all these patches. Please, if you want to contribute something, get access to KDE-CVS, announce what you plan to change on the mailing list, and then commit it yourself. This way you can document the commit in the CVS-log, and also maintain and change your patch afterwards.

Getting CVS access is so easy and painless! Read this FAQ for instructions:

http://developer.kde.org/documentation/other/developer-faq.html#q1.8

So you wouldn't have a problem if I got myself CVS access and i added patches for amarok?

seb wrote:

So you wouldn't have a problem if I got myself CVS access and i added patches for amarok?

Get access, man

Hi.

I agree.

The handbook should be changed to reflect this, as it now states
"Then either submit a patch to the mailing list, or..."

see
http://amarok.kde.org/component/option, ... v_faq.html
in section 4.

/wef