GoNeeded.com

Sitting on my flight back from the mentor summit at Google HQ seems to boost my writing power. Although I wanted to get some coding done, I’m mainly writing E-Mail. But I digress, cause I wanna take the chance to summarize a couple of ideas and compile a list of lesson learned items which floated around in the various sessions. Btw. it was an awesome event and I’m really grateful that I could attend it as an Eclipse rep.

Application review phase:

• Get the applications in a lot earlier to have a longer review period

• Assign mentors and students based on technical but also on social grounds

• Have direct, non text base communication (if possible video)

• Find a hook to the reptilian brain (imprinting) to understand how the student ticks

• If you as a mentor are euphoric about the student and the application, let somebody else do a review as well. The review process should be unbiased

• Most successful apps came from the student!!!

• Check how many alterations have been done to the app. The more alterations there are, the more thought has been given by the candidate

• Let the candidate take an entry level test if his/her abilities aren’t known to the reviewer

Community building:

• It should be mandatory to hang out on IRC, IM or whatever communication form is most common. In our case it is probably IRC

• After accepting the students and assigning them to their mentor, do a big group introduction. Again, it shouldn’t be text based

• Have the formal things done fast. It is really frustrating to wait weeks for commit access to the SoC repository

Monitoring and rating progress:

• Define precise project deliverables upfront, though they might change over time

• Frequent checkins should be mandatory. If there is no checkin in a week, find out what’s going on

• Have a transparent review process by providing check-in statistics (DASH/CIA/…)

• Sidenote: Expand DASH to not just monitor CVS/SVN but to also gather statistics about contributions out of Bugzilla, newsgroups and mailinglists…

• Let the student take the test driven development model

After the term ends:

• If all deliverables have been successfully solved by the student, have some follow up tasks in the pocket to keep the student involved with the project. In the end she/he should become a permanent contributor/committer

This collection is certainly far from being complete. This said, the moment the official session notes will be made available, I will add a link to this post. They are currently kept in the non public GSoC wiki.

Chris Aniszczyk: Eclipse's Google Summer of Code 2007 Results
Wayne Beaton: We need help for Summer of Code
Notes on Book Shopping from a Tech Bibliophile
Releng: Build Workshop 2: Build Harder
Nick Boldt: EclipseCON 2008: News from the collective
Wayne Beaton: 12 steps
Jonas Boner: The Power of Sockets and Dynamic Proxies
Remy Suen: How to contribute to Eclipse projects…

This is a small personal project i have been working on for a while. It is for my FBLA competition in March. All it really is a billing system.

Lights Out was originally (at least to my knowledge) a handheld electronic puzzle game by Tiger Electronics. I decided to implement this game in Java/Swing and add lots of cool features that could not possibly be done in the handheld game including: *

To Facilitate and speed GUI development involving java swing. How many times have you been feeling frustrated after spending hours and hours trying to choose the right LayoutManager and making it to work the way you want it to be. How many times have yo

Small applet which gives to stat-companies the possibility to find out how long someone was on a web-page just before he left the specific web. This is the only way to do so, at the moment of this writing.

A Multyclient tchat program: This program is created in java ; I have allready done the non opensource program but i'm expecting this one to be better. Feel free to send Remarks

My intention for creating Software Engineering Techniques is mainly educational. I will post source code I've written or will write that may be useful for others who need to "see" how things can be done rather than just reading references.

This Software is a small web-based project-management tool I have written to support my student research project at the university for cooperative education Stuttgart. It is written in Java/Jsp and MySQL. The main features are: managing projects, create c

Project is out-of-date and have been closed.

CloneSweeper is a Minesweeper clone written entirely in Java. It was done mostly to improve my understanding of the Java language after 1 semester of OOP in college.

An editor and styler written fully in java...this is my first project in java check it out....it has got many features..................