GSoC 2019: Student Expectations

Here's what we expect of students that Creative Commons is mentoring. If you have any questions, concerns, or feedback, we encourage you to talk to your mentor or one of the organization admins. There are no stupid questions!

During the application process

  • Read the official GSoC student guide and the GSoC FAQ.
  • Review our Project Ideas 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 to write a draft proposal.
  • It is a good idea to learn about what Creative Commons does to provide context to your proposal. Some resources:
  • 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 successful contributions to our projects will help us get a sense of your work and is highly recommended (the more the better!). Please follow the guidelines in Contributing Code to find issues to work on and submit a successful pull request.

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 or two and post it to the CC technical blog.
  • Attend your weekly check-in with your mentor and any other meetings.
  • 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.

At all times

Follow our Code of Conduct.

Back to top