This is an old revision of the document!
How to run Google Summer of Code
Before application
- Check with core@ etc to make sure there is no reason not to apply
- Get committers to add new ideas to SummerOfCodeIdeas and remove old ones
- Solicit ideas from public, add suitable ideas
- Make sure any projects done in previous years has been removed
- Find a backup admin. We can't apply without one.
- Co-ordinate with the Foundation, they may wish to assist with any part of the process
Writing application
- Copy/paste from previous years for a good starting point
When accepted
- Create wiki pages for new year
- Advertise!
- Update PDF publicity flyer
- Advertise on twitter, facebook, etc. Get FreeBSD Foundation, @FreeBSDHelp, @freebsd, committers etc to retweet
- News item on FreeBSD home page
- Post to -announce, hackers, etc
- The Foundation may well be able to offer help to promote
- Get committers to sign up as mentors
When applications open
- Most of the previous section applies
- Start commenting on proposals.
- Note that a lot of students submit right on the deadline, try to discourage this (they can edit submitted proposals right until the deadline anyway)
After applications close
- Comment on proposals. Try to tease out missing information from students
- Create judging spreadsheet, share with people who have signed up as mentors
- Keep requesting for mentors to help judge and/or willing to actually mentor. Update the mentors email alias.
- Make sure slot numbers are decided and entered before the slot allocation deadline
- Assign mentors to proposals where possible
After slot allocation
- Choose top proposals with mentors
- If a very good project doesn't have a mentor, find one if possible
- Any project without a mentor listed cannot be accepted after this point