Core developer introduction

From Creative Commons
Revision as of 15:02, 11 July 2011 by Christopher Webber (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
  • cc.licenserdf
  • cc.engine
  • cc.i18n
  • cc.api
  • cc.deedscraper

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.

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