Improved Contributing Code page and linked to it from Student Expectations page.

Author: kgodey

content/contributing-code/contents.lr

@@ -10,19 +10,27 @@ body:
 
 Here's a list of [all our current projects](/projects). We do all of our development on GitHub and are generally open to pull requests. We would especially like help with reviving projects that CC's engineering team does not have the time to actively work on (such as [our WordPress plugin](https://github.com/creativecommons/creativecommons-wordpress-plugin) and [license chooser widget](https://github.com/creativecommons/LicenseChooser.js)). We're also looking to improve our documentation and increase our automated test coverage across pretty much all our projects.
 
-We are working on making sure all of our projects are documented, licensed, and have self-contained contribution guidelines. Until we finish that work, follow the checklist below before writing any code.
+We are working on making sure all of our projects are documented, licensed, and have self-contained contribution guidelines. Until we finish that work, follow the guidelines below before writing any code.
 
-**Make sure that the project is ready for contribution**
+### Check for contribution readiness
 
-If the repository has no license file, code of conduct, or is missing basic documentation, please create a GitHub issue attached to that repository to set those up. We will prioritize adding these files to repositories towards which people show active interest in contributing.
+We do not accept contributions to projects without licenses. We're working on adding licenses to all our repositories but we will prioritize ones in which there is an active interest in contribution. If the repository you want to contribute to has no license file (or is missing other infrastructure such as basic documentation), please create a GitHub issue attached to that repository asking us to set those up.
 
-**Make sure your change will be accepted**
+### Working on open GitHub issues
 
-* If you want to work on an open GitHub issue tagged "help wanted" or "good first issue", comment on it to indicate that you're working on it (so that no one else does) and submit a pull request when you're ready. No other steps are needed.
-* If you want to work on an open GitHub issue without those tags, comment on it to ask if help is desired.
-    * Indications that it may not be available to work on are that it was created very recently, it already has someone assigned to it, or it is in a project whose name starts with "Active".
-* If you want to work on something that there is no GitHub issue for, either create an issue and ask there whether a pull request will be accepted for that change or propose the change in [one of our community forums](/community) before creating the ticket.
-    * 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.
+We track all our work via the GitHub issues associated with each repository and they are a good way to find things to work on. The first step is to check the labels on the issue and follow the appropriate steps below.
+
+**If the issue is labeled "help wanted" or "good first issue"**, comment on it to indicate that you're working on it (so that no one else does) and submit a pull request when you're ready. No other steps are needed.  
+* Here's a list of [all issues labeled "good first issue"](https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
+* Here's a list of [all issues labeled "help wanted"](https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
+
+**If it does not have either of those labels**, comment on it to ask if help is desired. If you receive a response that tells you to go ahead and work on it, comment on it to indicate that you're working on it (so that no one else does) and submit a pull request when you're ready.
+
+### Proposing something new
+
+If you want to work on something that there is no GitHub issue for, then propose the change in [one of our community forums](/community) 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.
+
+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.
 
 When in doubt, ask a question on [one of our community forums](/community).
 
@@ -36,15 +44,15 @@ In general, we'd like any new projects to use Python, WordPress/PHP, and/or Java
 
 No matter what kind of project you're working on, these are good guidelines to follow
 
-**Code**
+### Code
 
 * Write comprehensive and robust tests that cover the changes you've made in your work.
 * Follow the appropriate code style standards for the language and framework you're using (e.g. PEP 8 for Python).
 * Write readable code – keep functions small and modular and name variables descriptively.
 * Document your code thoroughly.
 * Make sure all the existing tests pass.
 
-**Pull requests**
+### Pull requests
 
 * Use the format specified in pull request template for the repository if there is one.
 * Describe your change in detail. Too much detail is better than too little.

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

@@ -13,6 +13,7 @@ Here's what we expect of students that Creative Commons is mentoring. If you hav
 * 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.
+* Making a successful contribution to one of our projects will help us get a sense of your work and is highly recommended. Please follow the guidelines in [Contributing Code](/contributing-code) to find issues to work on and submit a successful pull request.
 
 ## During the community bonding period