Google Summer of Code 2009 Mentors
We also need some volunteers to be mentors. Being a mentor will require a significant amount of time and effort. How much is hard to say, but I think everyone can take a good guess considering each would be assisting someone (probably new to Enlightenment) with a "project" which would be more than just a patch. If you are interested in mentoring please add your name below. Please include with your name, your proclaimed area of expertise, as well as any other area you would be willing to mentor in. If your areas overlap with other developers that is a "Good Thing", as one of the things we are responsible for is "a plan for dissapearing developers"
- raster - Carsten Haitzler
- k-s - Gustavo Sverzut Barbieri [Evas, Ecore_Evas, Edje, ETK] (Media Players, Embedded Systems, Optimizations)
- KainX - Michael Jennings
- vtorri - Vincent Torri [ Evas, Ecore, Ecore_Evas, Edje, Win32 (!) ]
- cedric - Cedric BAIL [ Eet, Evas, Ecore_Evas, Edje, SDL ] (Embeded Systems, Optimizations)
- RbdPngn - Nathan Ingersoll [Ewl]
- mekius - Nick Hugart
- Sachiel - Ivan Briano
- ravenlock - Eric Schuele [ Backup ]
- Ryback_ - Ulisses Furquim [ Backup ]
- pfritz - Peter Wehrfritz [ EWL Backup ]
In addition to your time... there are a few other things a mentor needs to provide, have, or contribute. Here is a "Mentor's Checklist":
- Must be an active Enlightenment developer with SVN commit privileges
- Must have a Google Account
- Must commit to being available from April 15th - August 11th.
- Please identify a "backup mentor" in case you unexpectedly become unavailable.
- Must set measurable project milestones for the purposes of student evaluations
Here is a great article on how to be a good mentor (written by a previous SoC mentor). Please take a few minutes. I think we can all get something out of it.
More good tips on mentoring. (These from Google)
