Getting involved HOWTO?

[Christian Couder]

Hi,

Tarjei Knapstad wrote:
> 
> At the risk of losing friends, girlfriend, and basically having a life, I
> thought I might spend even more of my time coding, and get (more or less)
> invovled in the KDevelop project.

Welcome on board !

> Some questions arise though:
> 
> 1. Where can I find documentation on KDevelop?
> I cashed out the KDE_2_2_BRANCH from CVS yesterday, and generated the
> doxygen documentation which was far from complete. Another thing I sorely
> miss is some documentation on the design (an UML diagram would be nice).

There is no real documentation on KDevelop 2.0 since we planned for a
long time to drop this branch and work instead on KDevelop 3.0/Gideon.
There is a message that Omid Givi wrote some time ago about starting to
work on KDevelop 3.0/Gideon :
http://lists.kde.org/?l=kdevelop&m=98379930132535&w=2
But I think it's quite outdated.
Instead you should probably get the HEAD branch from CVS and look at the
HACKING, TODO and ChangeLog files.

> 2. What needs to be done? Who currently works on what?
> There should be a proper and up to date bug reporting/handling system on
> the web site. (I've personally installed Mantis, mantisbt.sourceforge.net,
> at the company where I'm currently employed...very nice, allthough I don't
> know how easy it would be to migrate your existing database.) I sincerely
> doubt (hope :-) that the bug stats at the homepage are up to date as some
> bugs have lived for 560 days (!).

Some bugs should be fixed on the KDE_2_2_BRANCH. Any many things can
also be done on the HEAD branch.
You should also subscribe to the kdevelop-devel mailing list and look at
its archive. Bug reports are forwarded on this list.

> 3. Which platforms/compilers should I work with?
> I'm currently using RedHat 7.x and GCC 3.0.1 (as of today :)
> Is this OK? Also, it should be sufficient to compile Qt, kdelibs, and
> kdevelop with Gcc 3.0.x to get things working, right?

I don't know if KDE compiles and then works well with gcc 3.0.1. If it
doesn't then you should perhaps go back to gcc 2.95.x.

> 4. Is there any collection on the discussion regarding the "big plans" for
> Gideon? I have some major suggestions that I will get back to later on.

Did you check the discussions on kdevelop-devel ?

> 5. Where/how should patches be posted/made?
> (At least up until I might prove worthy of CVS write access... :)

Please post them on the lists, then you will not have to wait a long
time before we ask you to get a write CVS account :-)
 
> If you could kindly answer my questions I'll get into some 2.0.1 fixing as
> soon as possible. I'll start out with having a look at the "tree collapse"
> problem which I reported last week.

Good luck and welcome again!

Bye,
Christian.

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«