Merge pull request creativecommons#68 from akmadian/master

Add more information regarding proposal selection, and mentor availability to GSoC "General Information" page.

Author: kgodey

content/gsoc-2019/contents.lr

@@ -27,11 +27,27 @@ Here are short bios of each of our 2019 mentors. Please use first names or Slack
 
 ## Proposal review criteria
 
+Proposal quality is very important, code and community contributions help for different reasons. 
+We are hoping that GSoC will lead to long term contributions to CC, and we see being involved in the community as a sign 
+of general interest in our work. Any code contributions are good for first purposes, contributions to CC repos also 
+show a general interest in our work so they count for both.
+
 We do not have formal guidelines for reviewing proposals, but here are a few things we consider:
 * **Quality of the proposal**: This is the most important thing. A good proposal includes attention to detail, externally measurable milestones, consideration for future maintainability and community involvement, and a demonstration of your skills.
 * **Community involvement**: One of our major goals for GSoC is to build an active development community and attract long-term contributors. Engaging in the community, whether it's asking questions, helping other students, contributing code, filing bugs, or whatever else, is a good sign that you're actually interested in our work and our projects.
 * **Communication skills and initiative**: These are essential to completing a successful project. Things we look for (among others): asking specific and detailed questions, following up on conversations, making sure to read available resources before asking questions, being patient and responding to critical feedback well.
-* **Code contributions**: We appreciate seeing your code, it gives us confidence that you have the skills necessary to implement your proposal. Code samples that are not related to CC projects are fine too.
+* **Code contributions**: We appreciate seeing your code, it helps us gauge your ability to orient yourself to a new codebase, as well as giving us confidence that you have the skills necessary to implement your proposal. Code samples that are not related to CC projects are fine too.
+
+However, this is all relative. As is said above, we do not have any formal guidelines. 
+If you have a great proposal, but haven't contributed to any CC repos, you still have a good shot.
+
+## Project slots
+
+Google assigns Creative Commons (and all GSoC organizations) a fixed number of project slots. This means that there may be `n` 
+proposals on the project ideas page, but CC may only be allocated enough project slots to support `< n` projects. 
+The number of project slots allocated to each GSoC organization varies by year. 
+
+You can find more information about the slot allocation process in [the GSoC mentor guide][GSoC-Slot-Allocation].
 
 ## History
 
@@ -43,3 +59,5 @@ CC participated in Google Summer of Code seven previous times. See below for mor
 * [Google Summer of Code 2010](https://www.google-melange.com/archive/gsoc/2010/orgs/creativecommons)
 * [Google Summer of Code 2012](https://www.google-melange.com/archive/gsoc/2012/orgs/cc)
 * [Google Summer of Code 2013](https://www.google-melange.com/archive/gsoc/2013/orgs/cc)
+
+[GSoC-Slot-Allocation]: https://google.github.io/gsocguides/mentor/selecting-students-and-mentors#the-formal-process