Mirrors
/
open-keychain
mirror of https://github.com/open-keychain/open-keychain.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Google Summer of Code 2015 (markdown)

Dominik Schürmann 2015-02-12 14:59:11 +01:00
parent e21b33d037
commit 3d5783b56e
1 changed files with 8 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Google-Summer-of-Code-2015.md

@ -11,15 +11,16 @@ OpenKeychain can be installed from [Google Play](https://play.google.com/store/a
# Prerequisites # Prerequisites
* Be a student enrolled at a university * Be a student enrolled at a university
* Solid understanding of Java
# Contribution Guidelines # Contribution Guidelines
1. Join the development mailinglist at http://groups.google.com/d/forum/openpgp-keychain-dev 1. Join the development mailinglist at http://groups.google.com/d/forum/openpgp-keychain-dev
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 style
3. Fork OpenKeychain and contribute code (the best part ;) ) 3. Fork OpenKeychain and contribute code (the best part ;) )
4. If you have questions ask on the mailinglist! 4. If you have questions ask on the mailinglist!
5. Open a pull request on Github. I will help with occurring problems and merge your changes back into the main project. 5. Open a pull request on Github. We will help with occurring problems and merge your changes back into the main project.
I am happy about every code contribution and appreciate your effort to help us developing OpenKeychain! We are happy about every code contribution and appreciate your effort to help us developing OpenKeychain!
# "One patch" rule # "One patch" rule
We require one accepted patch (pull request) from each potential GSoC student, before accepting the student for GSoC participation. We require one accepted patch (pull request) from each potential GSoC student, before accepting the student for GSoC participation.
@ -32,24 +33,20 @@ I sorted out some probably easy issues and tagged them: https://github.com/openp
1. Have one patch accepted in OpenKeychain (see "one patch" rule) 1. Have one patch accepted in OpenKeychain (see "one patch" rule)
2. Lookout for interesting ideas on this page and choose multiple according to the time you expect to work on them. You can also propose your own ideas 2. Lookout for interesting ideas on this page and choose multiple according to the time you expect to work on them. You can also propose your own ideas
3. Tell us about your plans on the mailinglist 3. Tell us about your plans on the mailinglist
4. [Apply officially on the Google Summer of Code page](https://www.google-melange.com/gsoc/homepage/google/gsoc2015) (**Registration opens on March 16, 2014, 7 p.m. UTC.**) 4. [Apply officially on the Google Summer of Code page](https://www.google-melange.com/gsoc/homepage/google/gsoc2015) (**Registration opens on March 16, 2015, 7 p.m. UTC.**)
4. For accepted students participating in the Summer of Code, we encourage to open a blog and write about your progress.
# Evaluation # Evaluation
GSoC has two formal evaluation points, at the mid-term and at the end. These evaluations determine if you receive the stipend from Google. In order to receive a pass for the evaluations you will need to show adequate progress toward your project's goals. GSoC has two formal evaluation points, at the mid-term and at the end. These evaluations determine if you receive the stipend from Google. In order to receive a pass for the evaluations you will need to show adequate progress toward your project's goals.
To help you meet your goals and so that your mentor can better evaluate your progress you need to: To help you meet your goals and so that your mentor can better evaluate your progress you need to:
* Have frequent, public discussions of your progress. (Don't rely on just your mentor for advice.) * Track your progress and milestones on our [issue tracker](https://github.com/open-keychain/open-keychain/issues).
* Have a public OpenKeychain fork for your code to which you commit regularly. * Participate in discussions on our mailinglist
* Give weekly status reports for example via a blog. * Have a public OpenKeychain branch for your code to which you commit regularly. To this end, you will be granted write access to our repository after we accept your first pull request.
* You are encouraged to write blog posts for [our website](http://www.openkeychain.org).
For the final pass, you will normally be required to merge your code into OpenKeychain master.
Remember: we want you to succeed and we'd like you to stick around. Remember: we want you to succeed and we'd like you to stick around.
(based on [Subsurface's wiki page](http://trac.hohndel.org/wiki/Subsurface_GSOC_2014_Idea_List))
# Ideas # Ideas
## Improve keyserver support ## Improve keyserver support