Changes

lh says: list of mentors' names good. also some reorg
Line 67: Line 67:     
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
 
===What criteria did you use to select these individuals as mentors? Please be as specific as possible.===
 +
All of our mentors have experience with the Sugar code base and around half of them have been with the project since the beginning - more than 2 years ago. Most have successful mentoring experience (including combined 6 years' experience as successful GSoC mentors) and/or are teachers. All have been active in our software development support community and a regular presence on our support IRC channel.
 +
 
List of mentors:
 
List of mentors:
 
name <gmail account name>
 
name <gmail account name>
Line 80: Line 82:  
#Sayamindu Dasgupta <sayamindu>
 
#Sayamindu Dasgupta <sayamindu>
 
#Austin Appel <scorche15>
 
#Austin Appel <scorche15>
  −
All of our mentors have experience with the Sugar code base and around half of them have been with the project since the beginning - more than 2 years ago. Most have successful mentoring experience (including combined 6 years' experience as successful GSoC mentors) and/or are teachers. All have been active in our software development support community and a regular presence on our support IRC channel.
  −
  −
We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.
      
===What is your plan for dealing with disappearing students?===
 
===What is your plan for dealing with disappearing students?===
Line 91: Line 89:  
===What is your plan for dealing with disappearing mentors?===
 
===What is your plan for dealing with disappearing mentors?===
   −
Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We plan to have secondary (paired mentors) and tertiary (general IRC channel) support for each project as described above, and mentors will also be expected to attend the weekly check-in meetings on IRC.
+
Our mentors have a history of being deeply involved and invested with the project and in constant and reliable contact with the community, so we think it is unlikely that this will happen. We also plan to pair mentors to ensure that there is an experienced "second" associated with each project. If a mentor misses the weekly check-in meetings on IRC, their "backup" will track them down as they temporarily cover for them. Finally, our IRC channel is active 24/7, and we will give all students a list of IRC handles whom they can consult specifically. There is a safety net for any software developer who needs it.  
    
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
 
===What steps will you take to encourage students to interact with your project's community before, during and after the program?===
273

edits