[Adium-devl] Summer of Code, start your engines!

Chris Forsythe chris at growl.info
Thu Apr 12 12:10:34 UTC 2007


Hey folks,

    In case anyone missed it, the slots for Google Summer of Code have 
been decided. We're currently waiting on one application which may have 
a conflict to be resolved, and then David will be making announcements 
on the blog. This conflict is something which is good for the student, 
and Google has been made aware of the situation. It's personal, but not 
in a bad way, so nobody worry about it that doesn't have to. :) We have 
six slots either way.

    Mentors, please contact your assigned student ASAP. Last year we had 
some communication problems that I would like to avoid this year. If any 
students do not have contact information for their mentors, please 
contact me ASAP.

    Mentors, please get your students to subscribe to this mailing list. 
Also, they need to get a trac account created. Send me the trac username 
and I will grant them some additional rights on trac.

    I'd like to propose the following items:

- Updates from students every 2 weeks as to the progress of their 
project. This is so that it will be easier to tell if a project is 
starting to have problems, so that we can be proactive rather than 
reactive. Reports either in the biweekly irc meetings or via the mailing 
list should be sent either by the student or mentor, preferably the student.
- Branches named after project names and not student names.
- No SoC specific mailing list. These people are part of our project 
now, I do not mind the extra traffic on adium-devl, I'm hoping everyone 
else will not mind it either, it should be low volume.
- Keeping the SoC blog and the main blog together. Basically, getting 
everyone to sign up for blogger is what this boils down to, and then 
prefixing the subject of a post with "SoC-Project Name". This goes along 
with the last suggestion, keeping everyone on the same page and working 
within our already setup infrastructure could be beneficial.

    I'm sure there are other items we can come up with, but basically I 
think this would make things a tad more cohesive this year. Thoughts?

Chris




More information about the devel mailing list