Login Register

Student FAQs

This page will serve as a list of questions and answers about Dojo's Summer of Code in 2008. We'll flesh this out a bit more over the next couple of weeks. Add any questions or comments to this page and we'll roll them in, or get in touch with Rob.

Google's FAQ on the summer of code is the definitive answers around how the programme will work overall, we'll focus on the Dojo-specific bits here.

Why Dojo?

  • We're a vibrant and active project, that is used by some really big companies as well as thousands of other developers around the world.
  • Our goal is to be the Javascript toolkit of choice for anybody building applications of any size. This means there is tonnes of scope for new work in many areas.
  • In 2007, we released 1.0 after some major refactoring - the codebase is clean and documented, and there are clearly defined areas for you to work in. We take being professional seriously around issues like internationalization, accessibility, and cross-browser support.
  • Lots of people are paid to work on Dojo, including many of our committers. Its not just a hobby (but it is fun!)
  • We've done Summer of Code twice before, in 2006 and 2007 - we're learning and improving each time.
  • We have some very well-known developers involved with Dojo and we're picky about our mentors - you'll be learning from the best.

What does Dojo require in a SoC application?

  • In addition to all the normal stuff...
  • Read the GSoC wiki page "Advice for Students".
  • Some references (work or study) who we will get in touch with.
  • To make yourself available for a phone/skype call so we can get to know you.
  • To complete our coding test so we can see which areas you're strong in.

What does Dojo expect?

  • At least once a week you'll need to post a blog update on what you've achieved, problems you've encountered, and what's coming up. The other people in the Dojo community want to hear what you're working on!
  • You'll work for us full-time over the summer, not try to squeeze us around another job. If you have exam commitments or something else, you must be upfront about it, and have a plan for how to make them co-exist successfully.
  • You'll sign a Contributors License Agreement - we need to make sure our IP is clean and we take it very seriously.
  • You'll follow our coding style guide - other people may have to maintain your work in future, so it needs to fit in.
  • We have a team meeting at 3pm PST on Wednesdays - if you're in a semi-compatible time zone you must be there. The other developers want to get to know you and hear what you're doing.
  • Our mentors are all volunteers and are doing this because they want to help - you need to respect and listen to them.

What can I expect as a student?

  • Two mentors assigned to each student. This allows you to get different perspectives and ideas and not be left in the lurch if the mentor is unavailable for a few days.
  • To learn from some of the leading Javascript developers in the world. The Dojo devs are a friendly bunch, get to know us!
  • A responsive SoC Admin (Rob) who you can always contact with questions or problems, and who will treat you fairly.

Other stuff

How many students/projects will you take?
We don't know at this stage. In 2007 we accepted 4 applications, ideally it will be more this year. It depends on Dojo getting accepted into GSoC, how many quality applicants there are to Dojo, how many mentors we have available, and how many projects Google is able to fund through the programme.

More questions?

Add a comment here or head to the forum.

Coding test is up

We've added the details for the coding test we want our student applicants to do - have a read.

What should an application look like?

Below is the text we've added to the Google application, and also have a read of this topic in the forum.

Your application should include the following: your project proposal (including goals, milestones, priorities, perceived risks), why you'd like to complete this particular project, and the reason you're the best individual to do so. Your proposal should also include details of your academic, industry, and/or open source development experience, and other details as you see fit.

In addition...

1. Write about the experiences developing software that you've been most enthusiastic about (whether personal, professional, academic, or open-source).

2. Please provide a name and a phone number/Skype/email for some who Dojo can talk to about your software development experience - this might be a supervisor, tutor, or manager.

3. Do you consider this your full-time job over summer or are there other committments you know about now which could conflict with SoC?

4. Have you applied for or done Google Summer of Code before? If so, tell us how it went.

5. Make sure you've read and understand our Student FAQs (http://www.dojotoolkit.org/book/summer-code-2008/student-faqs)

6. Send us the results of the Dojo coding exercise (http://www.dojotoolkit.org/book/summer-code-2008/dojo-coding-test)