The first suggestion is great. Knowing the structure of the program greatly helps when trying to understand individual parts, gives an idea of context.
Personally I've been able to find some small tasks to do as an introduction to programming, but keeping a list of such tasks for anybody to easily pick up could definitely help catching stray developers. At the moment, I don't have any ideas of my own, but I'll think about it. How about asking some other projects about what they do? /Oliver On Wed, Apr 2, 2008 at 5:25 AM, Greywhind <[EMAIL PROTECTED]> wrote: > The first suggestion I would make involves the code itself. While > much of it is rather self-explanatory and quite clean, it can still > be overwhelming for new developers who do not know where to start or > what to look for. Therefore, I recommend that we include a simple > explanation of the basic file structure and a very brief description > of the contents of each code file in a "DEVELOPERREADME.txt" or some > such document. We should also make sure there are ample comments in > the code itself, explaining each class and method and even pointing > out other code files that are related to the class. > > Another useful tool for new developers is the bug tracker on > Sourceforge.net. We should have a prominent link to it, and perhaps a > category there related to "introductory tasks" that can be > accomplished by programmers who are just learning the intricacies of > the project. > > Please respond with feedback or your own ideas on getting new > developers started. > > - Greywhind<http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel> >
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
