I’d like to point any potential Google Summer of Code applicants to a post on DOs and DON’Ts for students over on the Google Open Source blog that I wrote with Lydia Pintscher and Kevin Smith. They’re fellow admins from two other long-time GSoC participants, KDE and the XMPP Standards Foundation. Here’s a quick summary of the points; you’ll have to read the original post for details:
DO | DON’T |
Be on your best behavior. | Make a bad first impression: SMS speech, extremely poor English, rudeness/hostility, etc. |
Read all the documentation, so you submit a useful application. | Submit a useless application. |
Be transparent about other commitments. | Disappear. |
Make Google Summer of Code your top priority. | Hold another major commitment. |
Be realistic about your skills. | Over- or under-rate your abilities. |
Commit and publicize your code frequently. | Make last-minute (or later) code drops. |
Submit code that’s ready to integrate. | Finish the summer with code that’s “almost ready” but will take forever to ship. |
Complete your project design before writing a line of code. | Start coding before finalizing design. |
Use your resources wisely. | Refuse to ask for help. |
Remember that you’re part of a community. | Consider it a solo project, like it often is in college. |