Updated Google Summer of Code 2016 (markdown)
parent
5932d5522e
commit
358d45fe14
|
@ -20,7 +20,7 @@ Keep in mind that mentoring is about providing guidance to help you solve your t
|
|||
|
||||
# Contribution Guidelines
|
||||
1. Join the development mailinglist at https://lists.riseup.net/www/subscribe/openkeychain
|
||||
2. Read the [README](https://github.com/openpgp-keychain/openpgp-keychain/blob/master/README.md), especially the notes about coding style
|
||||
2. Read the [README](https://github.com/openpgp-keychain/openpgp-keychain/blob/master/README.md), especially the notes about coding styles
|
||||
3. Fork OpenKeychain and contribute code (the best part ;) )
|
||||
4. If you have questions ask on the mailinglist, or in #openkeychain on irc.freenode.net!
|
||||
5. Open a pull request on Github. We will help with occurring problems and merge your changes back into the main project.
|
||||
|
@ -30,7 +30,7 @@ We require one accepted patch (pull request) from each potential GSoC student, b
|
|||
The reason for this requirement is that you can show us that you have succeeded in building OpenKeychain, and that you have understood a little piece of OpenKeychain's code and are able to improve it.
|
||||
This requirement is based on the "two patches" rule applied by projects such as Inkscape and Subsurface.
|
||||
|
||||
To make it easier for you to get started, we picked some (hopefully) easy issues for this purpose: https://github.com/openpgp-keychain/openpgp-keychain/issues?labels=simple-one-patch&page=1&state=open
|
||||
To make it easier for you to get started, we picked some (hopefully) easy issues for this purpose: https://github.com/openpgp-keychain/openpgp-keychain/issues?labels=help-wanted&page=1&state=open
|
||||
|
||||
Keep in mind that mentoring is about providing guidance to help you solve your task, but we don't want to keep holding your hand all the way. It's important for us to know that you can code and solve technical challenges on your own, while also maintaining a constructive dialogue of relevant design decisions with us.
|
||||
|
||||
|
|
Loading…
Reference in New Issue