I have posted some guidelines for our two (2) Google Summer of Code students, Chris and Leandro, here:
http://openjump.org/wiki/show/Summer+of+Code+Student+Guidelines I invite other OpenJUMP programmers to comment on the guidelines. Let me know if something needs to be added or changed. I tried to create guidelines that promote small working modules or chunks of code, rather than a lot of code that doesn't work. (I must admit I follow the later programming style, to my own disadvantage.) I have also created a "summer_of_code" folder in the JPP Subversion Repository at SourceForge for our students to work in. They need to let me know ASAP if they need assistance being set up to access (both read and commit) to our repository. I would also like both of our students to outline a basic plan for their first "module" by next Monday. This can be a very short document. (Only a couple of paragraphs are needed.) Please let me know what your module will accomplish and what classes and interfaces it will contain. I'll review the documents Monday and will provide any suggestions before our students get to work. I'll be looking to Nacho and other Portuguese speakers to help with Leandro! I will then plan on making my first code and documentation review on Friday, April 25th to check on our students progress. Please let me know if you have any questions. The Sunburned Surveyor P.S. - I consolidated our Summer of Code pages here: http://openjump.org/wiki/show/Google+Summer+Of+Code ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
