first draft, adapted from jmonkeyengine.org/gsoc/application-guide
Erlend Sogge Heggen
parent
e758a1912b
commit
18ec1368c8
|
|
@ -0,0 +1,70 @@
|
|||
# How to Apply
|
||||
|
||||
Send your application starting March 10, 2014. Before you apply, do the following:
|
||||
|
||||
* **Can you join?** Check out [Google’s FAQ](http://www.google-melange.com/document/show/gsoc_program/google/gsoc2014/help_page#1._Are_there_any_age_restrictions_on "http://www.google-melange.com/document/show/gsoc_program/google/gsoc2014/help_page#1._Are_there_any_age_restrictions_on") and see if you’re eligible for the GSoC. Also make careful note of the [GSoC timeline](https://www.google-melange.com/gsoc/events/google/gsoc2014 "GSoC 2014 timeline") in your calendar.
|
||||
* **Are you joining for the right reasons?** Read “[Reasons why you shouldn’t hack on open source projects](http://blog.codecombat.com/reasons-why-you-shouldnt-hack-on-open-source-projects)” carefully. If you’re not passionate about what we’re doing, the work will suffer.
|
||||
* **Let’s avoid rookie mistakes**. Read “[DOs and DON’Ts of GSoC (for students)](http://google-opensource.blogspot.no/2011/03/dos-and-donts-of-google-summer-of-code.html "DOs and DON")“.
|
||||
* **What’s your idea?** Decide which [idea(s)](http://hub.jmonkeyengine.org/soc/2014-ideas/ "2014 Ideas") you want to work on. Optionally, you suggest an idea of your own. We’d prefer it if you discuss your ideas out in the open in our [User Code & Projects](http://hub.jmonkeyengine.org/c/user-code-projects "User Code & Projects board") board. Feel free to `@mention` the username of relevant mentors listed in the ideas list to get their attention.
|
||||
* **Orientate yourself.** Have you contributed to Discourse before, made a pull request or a plugin? Some projects demand greater expertise than others. In any case, make sure that you have **read the [Beginner Tutorials](http://wiki.jmonkeyengine.org/doku.php/jme3#tutorials_for_beginners "jME3 Beginner Tutorials")** and that you have a firm understanding of key Discourse concepts before you apply to any Discourse project. Browse the Discourse source, especially the parts relevant to your project idea, and be sure you’ll be capable of integrating your idea into the existing project.
|
||||
* **Familiarise yourself with version control.** You should be familiar with the SVN or Git (preferred) workflow before GSoC starts.
|
||||
* **Draft your application (see template below).** Feel free to type up drafts for different ideas and ask us which one has the highest chance of succeeding: Create your draft on the forum if you’d like, or type it up on an external site like your blog or a GitHub gist and share a link to it on the forum or PM the relevant mentors.
|
||||
* **Setting the scope is your job!** A lot of the project briefs on our ideas list have not taken the GSoC timeline carefully into account. It is your responsibility to cut down or expand upon an idea so that it’s both challenging but also completely feasible within 4 months. We however provide plenty of feedback on scope during the application phase.
|
||||
|
||||
## Personal Details Brief
|
||||
|
||||
**Mandatory**
|
||||
|
||||
* **Name:** _Your_Name_Here_
|
||||
* **Nickname:** _@Your_Hub_Username_Here_
|
||||
* **Email:** _[name@domain.com](mailto:name@domain.com)_
|
||||
* **Country, language & timezone:** _E.g. “Germany, German, GMT+1″_
|
||||
* **School Name & Study:** _The name of your university and field of study._
|
||||
* **Preferred IDE:** _NetBeans, Eclipse or other?_
|
||||
|
||||
**Optional**
|
||||
|
||||
* **Skype ID or GTalk/Jabber:** _SkypeID or [name@gmail.com](mailto:name@gmail.com) (for IM and voice chats)._
|
||||
* **Personal Website:** _[http://yourdomain.tld](http://yourdomain.tld/ "http://yourdomain.tld") (if applicable)_
|
||||
* **Phone number:** _For emergencies only. __If all contact methods fail because you are in an internet-free zone at some point, we can try your phone. Enter your phone number (with country code) here._
|
||||
|
||||
# Application Template
|
||||
|
||||
## Synopsis
|
||||
|
||||
_Give us the “[elevator pitch](http://en.wikipedia.org/wiki/Elevator_pitch "elevator pitch")“. You have 30 seconds to tell us what you are going to make, why we will like this project, and to convince us that you are qualified to do it! (You might want to write this section last)_
|
||||
|
||||
## Deliverables
|
||||
|
||||
_Provide a summary of what this project will add to the engine. Example: “Once this [4-month] project is done, Discourse users will be able to do [the following cool new things: ...]” . Just as importantly: What do you expect to NOT do during these 4 months of work? i.e. what is out of scope._
|
||||
|
||||
## Project Details
|
||||
|
||||
_Scope: List the main features of the project, and detail their scope (which features do you expect will require the most and least amount of work?) and the coding approach you’ll take._
|
||||
|
||||
_Implementation: Explain in detail how you’re planning to implement each of your deliverables. _
|
||||
|
||||
_Anticipated challenges: Identify challenges or risks to the success of the project, such as the project being incomplete by the end of the GSoC term. How do you intend to detect these risks early on? How do you plan to mitigate the challenges?_
|
||||
|
||||
_Groundwork: What have you done so far with this idea: Include any work or research on this project you have already started. Has something similar been tried before, and how was it different from your approach? Summarise what you’ve discussed with other developers so far and where you’ll be going from there._
|
||||
|
||||
## Project Schedule
|
||||
|
||||
_How long will the project take? When can you begin work? How many hours are you going to work on this a week? Include an estimated timeline of the project with mini-milestones. Consider your school/vacation/work/life commitments that conflict with your project schedule, and please explain how you plan to compensate for them._
|
||||
|
||||
## Experience
|
||||
|
||||
_What is your experience using and developing Discourse or other similar applications? What about RoR/Ember.js programs? Have you worked like this before (remote team work, timezone difference, deadlines)? Are you comfortable communicating technical development in English?_
|
||||
|
||||
---
|
||||
|
||||
> Tip: Don’t just rely on the GSoC mentors to review your application in depth; they will only turn back a proposal if they find it fundamentally lacking. Instead, ask a technical colleague or friend to review it carefully and provide critical feedback.
|
||||
|
||||
## Example Proposals:
|
||||
|
||||
* [Blender Proposal](http://wiki.blender.org/index.php/User:Apinzonf/Gsoc2013/proposal "Blender example GSoC proposal").
|
||||
* [WordPress Proposal](http://www.mertyazicioglu.com/2013/05/02/gsoc-2013-proposal-enhance-profiles-wordpress-org/)
|
||||
|
||||
# After Submitting Your Application
|
||||
|
||||
After you’ve applied, check on your application at the GSoC site once or twice a day. **Answering your mentor’s questions timely is very important.** Discourse mentors will leave notes on your application if they need more information or have additional questions about your proposal that they need answered before making a decision. If they leave a note and you don’t respond, it’s not their job to track you down. There will be many applications, so making sure you stay on top of your application will help you compete for the spots we have to fill. Google will announce the accepted students [on their site](http://www.google-melange.com/gsoc/homepage/google/gsoc2014 "http://www.google-melange.com/gsoc/homepage/google/gsoc2014").
|
||||
Loading…
Reference in New Issue