Core developer introduction
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:
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
./bin/paster serve cc.engine.ini --reload
Get cross-package virtualenv working
This will be important when you have to work on multiple packages that affect each other at once.
You aren't expected to completely grasp all of this immediately.
- Read the cc.engine docs/ materials
- Read the RDFa primer: http://www.w3.org/TR/xhtml-rdfa-primer/
- Play with http://creativecommons.org/choose/ and see how the output there has RDFa embedded in it
- ... don't bother reading the RDF primer immediately, let's talk about it on the phone
- Read: http://labs.creativecommons.org/2009/12/18/understanding-the-state-of-sanity-via-whiteboards-and-ascii-art/
- Read: http://labs.creativecommons.org/2010/01/06/caching-deeds-for-peak-performance/
- If you get stuck on git, http://progit.org/book/ is really great.
Some general CC pages you should read:
- All sections on http://creativecommons.org/about
- The FAQ http://wiki.creativecommons.org/FAQ
- The CC0 FAQ http://wiki.creativecommons.org/CC0_FAQ
- The Public Domain Mark FAQ http://wiki.creativecommons.org/PDM_FAQ
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:
Talk and pick out the appropriate tickets