PyCon-Tech

the python behind pycon.

THIS PAGE HAS BEEN REPLACED! Please go to the new Trac and Wiki for PyCon-Tech

Note: this is a work in progress, please ignore the incredibly bad spelling.

As PyCon grows, so does the software used to manage the convention. Long-term talk materials and audio are managed in Zope. Documentation and information is managed in the wiki. Specialized short term applications are currently developed in Django. There is also PyCon-Tech mailing list.

There are a number of applications under development or need to be written for PyCon07 and we are actively looking for volunteers to help out. No prior experience is needed.

Goals

Mission statements make me ill, but there are some goals for this project which should be kept in mind.

1. Software for PyCon
   It's obvious, but it's the most important and overriding goal. At the end of the day we need software to help manage the convention. Features and convention sometimes need to bend or break to meet this goal.
2. Give back to the community
   PyCon is a convention by, for, and of the community, and so is the code written for it. Applications such as the attendee map, scheduling, and even registration should be designed in a generic way so that others in the community can learn from it and use it to their own ends. This will take many years to get right, but it is a goal to keep in mind.
3. Show what python can do
   It is important to showcase the power of the language and varied ways in which it can be used to solve real world problems.

PyCon-Tech ShowMeDo Series

1. Introduction
2. Integrating Django and PHP
3. Schedule App Part 1 (comming soon)
4. Schedule App Part 1a (comming soon)

Overview

At the core, there are a set of tasks for managing the convention:

• Talk/Tutorial Proposal and Review
• Sponsorship sign-up
• Registration
• Scheduling
• Survey
• Talk Material, Audio, and Video Management

Currently only a few of these are managed with the help of python software applications. We are looking for people to work on the core applications, write helper scripts, write documentation, etc. There are many small short term jobs as well as work which does not need to be done until PyCon08. No experience is reqired.

Getting Started

Anonymous SVN Access

• svn co https://svn.python.org/conference/django/trunk/ pycon-tech

Required Software

• Subversion
  Windows SVN 1.4.0 Installer
• Python2.4
  Windows Python2.4.4 Install
• psycopg2
  Windows psycopg2-2.0.5.1 for Python2.4 Install
• PIL
  Windows PIL 1.1.5 for Python2.4 Install
• Django, docutils, and Dojo are NOT REQUIRED!
  The exact revisions of these packages are managed in the PyCon-Tech
  SVN repository via the svn:externals property. You will get these
  packages when you get the pycon-tech source code. We are currently
  running with the dev trunk of both projects.

Optional Software

• ElementTree?/cElementTree (used by some custom tools)
• postgresql 8.14
• Zope
• PMWiki?/PHP
• Some form of SSH (for commit access)
  Which works with subversion and a public/private key pair.
  Cygwin and PuTTY (install) have been tested on windows.

PyCon-Tech SVN Repository (For Commit Access)

Anonymous Access

https://svn.python.org/conference/django/trunk/

Commit Access

You will need to e-mail your public SSH key to pycon@python.org for access.

SVN URL

svn+ssh://conference@svn.python.org/django/trunk

Cygwin Example

Mya@miyu /c $ svn co svn+ssh://conference@svn.python.org/django/trunk pycon-tech
. . . . . . . . . . . . . . . . . . . 8< ommiting verbose output >8 . . . . . . . . . . . . . . . . . . .
Mya@miyu /c $ export PYTHONPATH=c:/pycon-tech
Mya@miyu /c $ cd pycon-tech
Mya@miyu /c/pycon-tech $ ls
django docutils pycon
Mya@miyu /c/pycon-tech $ python pycon/manage.py runserver
Validating models...
0 errors found.

Django version 0.96-pre, using settings 'pycon.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CTRL-BREAK.

Bugs/Requests

Currently bugs and feature requests are being managed in this wiki under the PyConTechBugs page. At some point we should move this over to the python.org bug system under a PyCon-Tech project.