Synchronized build

Author: lektor-bot

gsoc-2019/index.html

@@ -108,13 +108,23 @@ <h2 id="mentors">Mentors</h2><p>Here are short bios of each of our 2019 mentors.
 <li><a href="https://creativecommons.org/author/sclachar/">Sophine Clachar</a> (<code>Sophine</code> on Slack)</li>
 <li><a href="https://creativecommons.org/author/timidcreativecommons-org/">Timid Robot Zehta</a> (<code>Timid Robot</code> on Slack)</li>
 </ul>
-<h2 id="proposal-review-criteria">Proposal review criteria</h2><p>We do not have formal guidelines for reviewing proposals, but here are a few things we consider:</p>
+<h2 id="proposal-review-criteria">Proposal review criteria</h2><p>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.</p>
+<p>We do not have formal guidelines for reviewing proposals, but here are a few things we consider:</p>
 <ul>
 <li><strong>Quality of the proposal</strong>: 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.</li>
 <li><strong>Community involvement</strong>: 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.</li>
 <li><strong>Communication skills and initiative</strong>: 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.</li>
-<li><strong>Code contributions</strong>: 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.</li>
+<li><strong>Code contributions</strong>: 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.</li>
 </ul>
+<p>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.</p>
+<h2 id="project-slots">Project slots</h2><p>Google assigns Creative Commons (and all GSoC organizations) a fixed number of project slots. This means that there may be <code>n</code> 
+proposals on the project ideas page, but CC may only be allocated enough project slots to support <code>&lt; n</code> projects. 
+The number of project slots allocated to each GSoC organization varies by year.</p>
+<p>You can find more information about the slot allocation process in <a href="https://google.github.io/gsocguides/mentor/selecting-students-and-mentors#the-formal-process">the GSoC mentor guide</a>.</p>
 <h2 id="history">History</h2><p>CC participated in Google Summer of Code seven previous times. See below for more information about our projects and participation for each year.</p>
 <ul>
 <li><a href="https://developers.google.com/open-source/gsoc/2006/#cc">Google Summer of Code 2006</a></li>