#4 contributing ?

[Anonymous]

There's a number of very interesting ideas collected in
the feature tracker and I might be interested in
contributing some stuff-I could imagine, other people
would also like to.
So, I wonder what's the best procedure to get actively
involved in kdiff3 development?
Would you provide volunteers with SVN priviledges and
do you accept patches, or rather are there any coding
guidelines?
Also, do you have any sort of roadmap for KDiff3, so
that we don't begin adding stuff that's unlikely to be
added anytime soon?

Thanks

Boris

[Joachim Eibl]

Logged In: YES
user_id=584435

Hi Boris,
Thank you for your mail. You are welcome to help if you want to.
I would also provide you SVN-access if you prefer this and
want to contribute more than a single patch.
As for coding guidelines:
- Indentation is 3 spaces (no tabs).
- Subset of hungarian coding style:
- Membervariables begin with "m_". Global vars with "g_"
- Pointers have prefix "p". Booleans "b" etc.
- Names of classes begin with a capital letter. Variables
and methods are lower case.

But more important is thorough testing.

Regarding the roadmap question: Please be more specific. Do
you wan't to work on a specific feature and be sure it will
make it into a release soon? Then let's discuss it. Or would
you like me to point out topics to work on?

Please send me an email to continue the discussion.
Cheers,
Joachim

[Nobody/Anonymous]

Logged In: NO

hi, thanks for your response and sorry for not getting back
to you earlier (real life commitments), in fact I tried to
compile the latest version from SVN, that's when I noticed
that I had to upgrade my QT/KDE to 4.0, unfortunately this
is something that I won't get to do until holidays, so I'll
check back with you then.

Boris

[Joachim Eibl]

Logged In: YES
user_id=584435

Hi,
At the moment KDE4 isn't required. Only Qt4 is needed.
Cheers,
Joachim