Merge pull request creativecommons#17 from creativecommons/student_success_page

Updated GSoC information.

Author: kgodey

assets/static/favicon.ico

@@ -4,7 +4,7 @@ title: Technology at Creative Commons
 ---
 body:
 
-Creative Commons has been building free software for over a decade to support our [mission](https://creativecommons.org/about/mission-and-vision/) of maximizing digital creativity, sharing, and innovation. Our projects come in all sizes and shapes, from simple static websites to providing a fast and relevant search interface to the billion-plus Creative Commons works currently available on the internet. Our engineering team is fairly small and spread thin, so we're really appreciative of volunteers who help us build or test our software.
+**[Creative Commons](https://creativecommons.org/)** has been building free software for over a decade to support our mission of maximizing digital creativity, sharing, and innovation. Our projects come in all sizes and shapes, from simple static websites to providing a fast and relevant search interface to the billion-plus Creative Commons works currently available on the internet. Our engineering team is fairly small and spread thin, so we're really appreciative of volunteers who help us build or test our software.
 
 ### Getting Involved
 

content/contents.lr

@@ -10,6 +10,8 @@ body:
 
 Take a look at the Creative Commons website to learn more about what we do. Also look at our GitHub organization and our developer community website to get a sense of the code and projects we work on. Making a successful contribution to one of our projects will help us get a sense of your work and is highly recommended.
 
+Read our [Student Expectations](/gsoc-2019/student-expectations) guide.
+
 ### Applying
 
 Your proposal must be submitted through the [Google Summer of Code website](https://summerofcode.withgoogle.com/dashboard/). It is a good idea to submit drafts and get feedback from CC mentors before you submit your final proposal.

content/gsoc-2019/application-instructions/contents.lr

@@ -4,6 +4,23 @@ title: Google Summer of Code 2019
 ---
 body:
 
-Creative Commons is applying to be a mentoring organization for [Google Summer of Code 2019](https://summerofcode.withgoogle.com/).
+Creative Commons has been selected as a mentoring organization for [Google Summer of Code 2019](https://summerofcode.withgoogle.com/)! 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.
 
-Check out our [Project Ideas](/gsoc-2019/project-ideas/all) and [Application Instructions](/gsoc-2019/application-instructions)!
+For more information about what Creative Commons as a whole does, please check out the ["What we do" page on our organization website](https://creativecommons.org/about/). 
+
+### First Steps
+
+If you are a student interested in submitting a proposal to CC, start by checking out our [Project Ideas](/gsoc-2019/project-ideas/all) page and finding an idea that interests you and joining our [Slack or developer mailing list](/community).
+
+Before you submit a proposal, read our [Application Instructions](/gsoc-2019/application-instructions) and [Student Expectations](/gsoc-2019/student-expectations) to get an idea of what we are looking for from students.
+
+### History
+
+CC participated in Google Summer of Code seven previous times. See below for more information about our projects and participation for each year.
+* [Google Summer of Code 2006](https://developers.google.com/open-source/gsoc/2006/#cc)
+* [Google Summer of Code 2007](https://developers.google.com/open-source/gsoc/2007/#cc)
+* [Google Summer of Code 2008](https://developers.google.com/open-source/gsoc/2008/#cc)
+* [Google Summer of Code 2009](https://www.google-melange.com/archive/gsoc/2009/orgs/cc)
+* [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)

content/gsoc-2019/contents.lr

@@ -0,0 +1,32 @@
+_model: page
+---
+title: GSoC 2019: Student Expectations
+---
+body:
+
+#### During the application process
+
+* Read the [official GSoC student guide](https://google.github.io/gsocguides/student/).
+* Review our [Project Ideas](/gsoc-2019/project-idea/all) and ask questions about projects you're potentially interested in on our `#cc-gsoc` Slack channel or developer mailing list.
+* Once you've decided on a project, follow our [Application Instructions](/gsoc-2019/application-instructions) to write a draft proposal.
+* Get feedback from the primary mentor associated with the project you're proposing before you submit a final application.
+* If you're proposing a project that's not on our official ideas list, please talk to our mentors to see if there is anyone interested in mentoring that project before you put any work into the proposal.
+
+#### During the community bonding period
+
+* Continue to plan your project with your mentor and the community.
+* Define communication channels and set up a weekly check-in with your mentor.
+* Set up your computer and development environment.
+* Familiarize yourself with the development process at Creative Commons (pull requests, code review).
+* Introduce yourself to the members of CC's engineering team.
+
+#### During the work period
+
+* Work 30-40 hours per week (or agree on a different plan with your mentor ahead of time).
+* Push code to GitHub frequently. Commit early and often.
+* Be available on Slack whenever you are working and post at least once a (work)day to talk about what you're working on that day.
+* Write a short update on your work every week and post it either to a personal blog or the CC developers mailing list.
+* Attend your weekly check-in with your mentor.
+* Be proactive about asking for help, especially when you're stuck.
+* Ensure that you're on track to delivering your project at the end of the work period. If you're not on track, talk with your mentor to come up with a new plan for the project well before the deadline.
+* Let your mentor and the organization admins know when you are going to be unavailable. If something sudden comes up, let us know.

content/gsoc-2019/student-expectations/contents.lr

@@ -1,5 +1,6 @@
 <!doctype html>
 <meta charset="utf-8">
+<link rel="shortcut icon" type="image/x-icon" href="{{ '/static/favicon.ico'|url }}">
 <link href="https://stackpath.bootstrapcdn.com/bootstrap/4.2.1/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-GJzZqFGwb1QTTN6wy59ffF1BuGJpLSa9DkKMp0DgiMDm4iYMj70gZWKYbI706tWS" crossorigin="anonymous">
 <link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro" rel="stylesheet">
 <link rel="stylesheet" href="{{ '/static/style.css'|url }}">
@@ -42,6 +43,7 @@
                   <div class="dropdown-menu" aria-labelledby="navbarDropdown">
                     {% for href, title in [
                       ['/gsoc-2019/project-ideas/all', 'Project Ideas'],
+                      ['/gsoc-2019/student-expectations', 'Student Expectations'],
                       ['/gsoc-2019/application-instructions', 'Application Instructions'],
                     ] %}
                       <a class="dropdown-item" href="{{ href|url }}">{{ title }}</a>