Core developer introduction

From Creative Commons
Revision as of 22:29, 17 April 2013 by Dan Mills (talk | contribs) (Get cc packages set up with zc.buildout)
Jump to: navigation, search


First week or two: getting acclimated

Server / git access

  • Generate SSH key
  • Coordinate with nkinkade about getting on servers
  • Coordinate about getting git access

Get cc packages set up with zc.buildout

Do git checkouts *via ssh* for all of these packages:

  • cc.license
  • license.rdf
  • cc.engine
  • i18n
  • cc.api
  • deedscraper

Configure buildout so it takes less than your lifetime to complete: http://www.cynapse.com/blog/cynin-buildout-low-bandwidth-try-these-settings

You should then set up zc.buildout. For more about what zc.buildout is, let's talk on the phone.

 python bootstrap.py && ./bin/buildout

Get server running

In cc.engine:

 ./bin/paster serve cc.engine.ini --reload

Get cross-package virtualenv working

http://labs.creativecommons.org/2010/03/16/using-virtualenv-and-zc-buildout-together/

This will be important when you have to work on multiple packages that affect each other at once.

Reading materials

You aren't expected to completely grasp all of this immediately.

Some general CC pages you should read:

Backups!

You should have the machine you work on have backups done regularly and automatically. We have some in-house backup machines, but you can backup locally, even to an external drive. You just need to backup your data.

Some of us like using Dirvish for this.

Start working on tickets

EG, with Jon Palecek, we're starting with:

http://wiki.creativecommons.org/Clarity_Project

Talk and pick out the appropriate tickets