This document provides information about contributing to the Pinax project. It discusses why Pinax is an important project, when the next releases will occur, who the core developers are, where to find resources and communicate, how to get involved by reviewing tickets, writing documentation, developing apps/themes, and translating materials. The document encourages joining the Pinax community during an upcoming sprint.

1. how to
contribute
to
James Tauber
DjangoCon 2009

2. why
when
who
where
how
what

3. why
• very active community
• cutting edge of issues around packaging,
translation, conventions
• scaffolding for re-usable apps
• rapidly developing (certain types of) Django
sites
• gateway drug to Django and Python

4. when
• 0.7 out this week
• 0.8 and 0.9 starting during the sprints!

5. who
• Core Devs
• James Tauber
• Brian Rosner
• Jannis Leidel
• Danny Greenfeld
• 35 contributors
• 108 members of pinax-core-dev list
• 336 users on code.pinaxproject.com
• 403 watchers on github
• 649 members of pinax-users list

6. where
• pinax-core-dev on google groups
• http://groups.google.com/group/pinax-core-dev
• #pinax-dev on freenode irc
• http://code.pinaxproject.com/
• http://github.com/pinax/pinax/

7. how
• get Pinax installed
• join the pinax-core-dev mailing list
• hang out in #pinax-dev on freenode
• familiarize yourself with the wiki and task
tracking system on
code.pinaxproject.com (CPC)
• (if you will be contributing code,
documentation or media) familiarize
yourself with git and GitHub

8. how (cpc)
• task tracker
• wiki
• pastebin
• ‘new’ vs ‘accepted’
• ‘fix needs review’
• ‘resolved’ vs ‘closed’

9. how (github)
• get account github.com
• fork pinax (and/or appropriate apps)
• pip install -e
• include task number in commit message
• indicate in task when fix pushed with link to
commit
• bug us in #pinax-dev

10. what (1/2)
• review tickets
• review documentation
• write new documentation
• write HOWTOs
• write translations
• write tests
• write a tutorial on your blog
• make a screen cast
• debug existing code

11. what (2/2)
• enhance existing apps (best done in
coordination with app developer)
• develop new django apps to include in Pinax
• develop new themes (templates / css /
media)
• develop new sample/starter projects (either
using existing apps or as scaffolding for a
new django app)

12. translations
• get familiar with Django I18N/L10N
• http://bit.ly/django-i18n
• translate the external apps we use
• look for app on
http://www.transifex.net/
and get app developer to add it if not
there
• the 0.8 branch

13. Join Us
During Sprint
(even if just in
#pinax-sprint on freenode)