We are listing here things we`ve learned while participating at Google Summer of Code. This page is meant to be useful for the years to come.

2012

  • When XWiki is selected, send an announcement mail with a call-to-participation subject that people could forward to their friends.
  • Write a blog post on xwiki.org (even if you have one in xwiki.com)
  • Keep up the policy documents, they're really precious and show that XWiki is an organization that has some maturity in monitoring GSoC participatns
    • The current student guide is targeting accepted students.
    • Add a section for students that are applying. Mention the things we want from them (communication, etc).
  • Rules for grading student applications (1-5 ratings):
    • 1 star means spam, completely off topic
    • 2 stars means it's on topic (applying for an XWiki project), but very low quality
    • 3-5 stars for grading real proposals, where 5 stars means definitely +1, the student has a good proposal, exchanged some emails on the devs list, has some code written
  • Provide more detailed descriptions for projects and update them once students ask questions on the mailing list. This way we avoid answering to the same questions and we reuse as much as possible the replies from the list.
    • Another (more sloppy but more practical) option is to just add links to markmail thread in the project description so that interested students can easily identify the discussions where the project was mentioned and detailed
  • Make sure to pair proposals with mentors and secondary mentors before the student application period begins. All proposals that have not done so will not be considered.

2011

  • Require code samples from students.
Tags:
Created by Eduard Moraru on 2012/04/09 15:42
   

Get Connected