Discource-C
/
discourse
mirror of https://github.com/discourse/discourse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated GSoC Application Guide (markdown)

Erlend Sogge Heggen 2016-02-17 21:10:54 +01:00
parent 340f11bfd8
commit 5d12d87b5a
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
GSoC-Application-Guide.md

@ -3,12 +3,19 @@
Send your application starting March 10, 2014. Before you apply, do the following: Send your application starting March 10, 2014. Before you apply, do the following:
* **Can you join?** Check out [Google’s FAQ](https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation) and see if you’re eligible for the GSoC. Also make careful note of the [GSoC timeline](https://developers.google.com/open-source/gsoc/timeline) in your calendar. * **Can you join?** Check out [Google’s FAQ](https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation) and see if you’re eligible for the GSoC. Also make careful note of the [GSoC timeline](https://developers.google.com/open-source/gsoc/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. * **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")“. * **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)](https://github.com/discourse/discourse/wiki/GSoC-2016-Ideas-List) you want to work on. Feel free to `@mention` the username of relevant mentors listed in the ideas list to get their attention. * **What’s your idea?** Decide which [idea(s)](https://github.com/discourse/discourse/wiki/GSoC-2016-Ideas-List) you want to work on. 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 a firm understanding of key Discourse concepts before you apply to any Discourse project. Browse the source code, especially the parts relevant to your project idea(s), and be sure you’ll be capable of integrating your idea into the existing project. * **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 a firm understanding of key Discourse concepts before you apply to any Discourse project. Browse the source code, especially the parts relevant to your project idea(s), and be sure you’ll be capable of integrating your idea into the existing project.
* **Familiarise yourself with Git & GitHub** You should be familiar with common Git workflows before GSoC starts. * **Familiarise yourself with Git & GitHub** You should be familiar with common Git workflows 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. * **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!** 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 will however provide plenty of feedback on scope during the application phase. * **Setting the scope is your job!** 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 will however provide plenty of feedback on scope during the application phase.
## Personal Details Brief ## Personal Details Brief