Synchronized build

Author: lektor-bot

contributing-code/index.html

@@ -143,7 +143,8 @@ <h3 id="working-on-open-issues">Working on open issues</h3><p>We track all our w
 <h3 id="proposing-a-new-issue">Proposing a new issue</h3><p>If you want to work on something that there is no GitHub issue for, then propose the change in <a href="../community">one of our community forums</a> or create a a new GitHub issue associated with the relevant repository amd propose your change there. Be sure to include implementation details and the rationale for the proposed change.</p>
 <p>If the project has a roadmap documented in the README, checking the roadmap to see if the feature is already in our pipeline would be a good first step.</p>
 <p>When in doubt, ask a question on <a href="../community">one of our community forums</a>.</p>
-<h2 id="pull-request-guidelines">Pull request guidelines</h2><ul>
+<h2 id="pull-request-guidelines">Pull request guidelines</h2><p>We aim to review pull requests within three business days.<a href="#footnote-1"><strong>*</strong></a>. If it has been over three business days and you have not received any feedback, feel free to follow up.</p>
+<ul>
 <li>Read and follow the contributing guidelines and code of conduct for the project. Here are screenshots of where to find them for <a href="../contributing-code/first-time-contributor-resources.png">first time contributors</a> and <a href="../contributing-code/previous-contributor-resources.png">previous contributors</a>.</li>
 <li>Use the format specified in pull request template for the repository if one exists.</li>
 <li>Describe your change in detail. Too much detail is better than too little.</li>
@@ -166,6 +167,7 @@ <h3 id="code-guidelines">Code guidelines</h3><ul>
 </ul>
 </li>
 </ul>
+<p><a name="footnote-1"><p class="muted small"><strong>*</strong> CC staff work Monday through Friday and are not available on weekends and national holidays (the specific holidays observed vary based on the person's location). CC is closed between Christmas Eve and New Years' Day every year and for a few days following the CC Global Summit. Also, our availability during events such as the CC Global Summit and our biannual staff meetups is limited.</p></a></p>
 <h2 id="new-projects">New projects</h2><p>We are also open to working on or hosting projects that are related to the Creative Commons licenses or general mission. Our <a href="../gsoc-2019/project-ideas">Google Summer of Code project ideas</a> list is a good place to find ideas we'd like implemented. If you're interested in working on one of them, please propose it in one of our <a href="../community">community forums</a> (you don't need to be a student, anyone is welcome to work on those ideas) and work out implementation details with CC staff members before you write any code. If you want to suggest a new project idea, follow the same process.</p>
 <p>In general, we'd like any new projects to use Python, WordPress/PHP, and/or JavaScript (our framework of choice is Vue.js) so that our team can help review and maintain the project.</p>
 

gsoc-2019/index.html

@@ -89,9 +89,9 @@ <h1 class="page-title pb-3 mb-4">Google Summer of Code 2019</h1>
 
   <p>Creative Commons has been selected as a mentoring organization for <a href="https://summerofcode.withgoogle.com/">Google Summer of Code 2019</a>! Increasing digital collaboration is one of CC’s primary goals as an organization, so we are very excited by the idea of helping students become acquainted with open communities. Working with us is a good opportunity to work on large and impactful technical challenges and acquire new skills, but you'll also learn what it’s like to work for a nonprofit and help advance our mission to legally share knowledge and creativity to build a more equitable, accessible, and innovative world.</p>
 <p>For more information about what Creative Commons as a whole does, please check out the <a href="https://creativecommons.org/about/">"What we do" page on our organization website</a>.</p>
-<h2 id="first-steps">First Steps</h2><p>If you are a student interested in submitting a proposal to CC, start by checking out our <a href="../gsoc-2019/project-ideas/all">Project Ideas</a> page to find an idea that you would like to write a proposal to work on during GSoC. CC mentors are available on <a href="../community">Slack and the developer mailing list</a> to answer questions and provide feedback.</p>
+<h2 id="first-steps">First steps</h2><p>If you are a student interested in submitting a proposal to CC, start by checking out our <a href="../gsoc-2019/project-ideas/all">Project Ideas</a> page to find an idea that you would like to write a proposal to work on during GSoC. CC mentors are available on <a href="../community">Slack and the developer mailing list</a> to answer questions and provide feedback.</p>
 <p>Before you start writing a proposal, read our <a href="../gsoc-2019/application-instructions">Application Instructions</a> and <a href="../gsoc-2019/student-expectations">Student Expectations</a> to get an idea of what we are looking for from students.</p>
-<h2 id="mentors">Mentors</h2><p>Here are short bios of each of our 2019 mentors.</p>
+<h2 id="mentors">Mentors</h2><p>Here are short bios of each of our 2019 mentors. Please use first names or Slack/IRC nicknames to address mentors; we prefer informality.</p>
 <ul>
 <li><a href="https://creativecommons.org/author/aldencreativecommons-org/">Alden Page</a> (<code>aldenpage</code> on Slack)</li>
 <li><a href="https://creativecommons.org/author/brenoferreira/">Breno Ferreira</a> (<code>Breno</code> on Slack)</li>
@@ -100,6 +100,13 @@ <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>
+<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>
+</ul>
 <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>