How to become a regular KLearnNotes2 developer?

What does it mean to be a 'regular developer?

Well, it just means that you have write access to kln2 CVS tree.

If you plan to make a very specific, small correction to kln2 sources, please just do it and submit a patch. If you face any problems e.g. with understanding kln2 sources - send a message to kln2-devel mailing list or directly to Marek - I will try to answer asap.

On the other hand, if you would like to and find time to get involved for longer, participate in decisions about kln2 future etc. you are very much welcome to become a kln2 developer. It is especially important to use CVS if few people make changes in the same file - you may incorporate subsequent changes made by others and allow them to adjust their code to the changes made by you. Otherwise merging two big changes at once maybe quite a hard task.

Note:

This is an open, volunteer based project. It has few important consequences:

I do understand that it is something additional to your "normal" life; you may have exams to pass or have a busy season at work etc. Therefore, even if I suggest something for you to code it's perfectly alright if you'd rather not do it (even if you accepted the task at first).
But this means it is your responsibility to keep me informed. If you face any problems with the code - ask me. If you have some external reasons for delays -please, please let me know.
This is also the reason why I try to make as little suggestions as possible. In general self-assigned tasks are done more effectively - if you see the problem yourself, you have a clearer view how to approach it and better motivation to solve it. If you have any idea of what you would like to do - just drop me a mail. Usually such suggestions are willingly accepted.
My suggestions will be usually just send to kln2-devel. Whoever has time and finds it interesting to follow one of them is welcome to volunteer.

If you want to become a regular kln2 developer. here is how you should start:

1. verify that you are able to get and compile latest kln2 sources

See section about CVS usage and compilation requirements. If you face any problems write for help to kln2-devel or report it as a compilation bug.

2. go through kln2 source docs

- without looking into details, just to see what's there. If you don't have experience with qt I suggest the following order:

sound setup window (how does qt work in practice?)
- run kln2 and see how this window looks like
- read part of docs about MIDI_setup class
- read midi_setup.h and midi_setup.cpp (again: without much detail)
random objects
Exercise class and its derivatives
other classes/files without much detail

3. go through kln2-devel mailing list archive

and subscribe to it (it is really low traffic). Note, that messages appear in the archive with approximately two weeks delay. Therefore, after subscribing you should still check out the archives in a week or two to see if you haven't missed something.

4. find a little task and code it

see page on submitting patches for some hints. KEEP IT LITTLE! Otherwise the code you are patching may change before you end coding ... :(

5. create a sourceforge account

if you don't have one.

6. send to me:

the patch
some info about you (do you have experience with programming and music? - if you just want to learn you are welcome too! :)
some suggestions about which part of kln2 development you would like to be involved in.

Published on: 2004-05-08 (1084 reads)

[ Go Back ]