mirror of https://github.com/laurent22/joplin.git
updated ## Recommended steps
- replaced Development by Features in `4. Come up with project that you're interested in and discuss it in [Features category](https://discourse.joplinapp.org/c/features)` -pull/2653/head
parent
a17e01793e
commit
9b562276f3
|
@ -61,7 +61,7 @@ First of all, please read the above referenced resources and the [GSoC FAQ](http
|
|||
1. Join the [Joplin Forum](https://discourse.joplinapp.org), introduce yourself in a structured manner, share your GitHub username, and meet your fellow developers in the [GSoC category](https://discourse.joplinapp.org/c/gsoc). The subject of the topic shall contain your username, e.g. _Introducing \<username>_.
|
||||
2. Read Student proposal guidelines and the [GSoC Student Manual](https://developers.google.com/open-source/gsoc/resources/manual#student_manual)
|
||||
3. Take a look at the [list of ideas](https://joplinapp.org/gsoc2020/ideas.html). You can have you own idea added by posting it in the [Features category](https://discourse.joplinapp.org/c/features)
|
||||
4. Come up with project that you're interested in and discuss it in [Development category](https://discourse.joplinapp.org/c/development)
|
||||
4. Come up with project that you're interested in and discuss it in [Features category](https://discourse.joplinapp.org/c/features)
|
||||
5. Write a first draft and get someone to review it
|
||||
6. Remember: you must link to work such as commits in your proposal. A private place will be created wihtinn the forum for that purposes.
|
||||
7. Read [How to write a kickass proposal for GSoC](http://teom.org/blog/kde/how-to-write-a-kick-ass-proposal-for-google-summer-of-code/)
|
||||
|
|
Loading…
Reference in New Issue