All the information in this section, except the Description, will be made public if the proposal is accepted. After you submit your proposal you will be able to make edits to all the fields below, assign Co-Authors, attach files, and communicate with the reviewers. Durring the review process other authors will be able to see this information to help foster communication between like proposals. Just because there are multiple proposals on a subject does not mean that only one will be accepted. See the Call for Proposals for detailed instructions.
The first impression reviewers and attendees will have of your talk is its title. Some media such as the printed schedule will only have the talk title. Panel discussions should have a title with the prefix 'Panel: '
If you wish a different duration than those listed, leave a comment to that effect on the submitted proposal. Panel discussions must be 45min long.
advocacy agile ajax animation archiving artificial intelligence ast best-practices biology business business case case study cli cloud computing command line tools community community sites complexity concurrency core coroutines coverage databases digital libraries distributed django documentation dotnet easy easy to develop ecommerce education eggs embedding engineering extensions fast fast web presence finance games geography geospatial gis google spreadsheets graphics gui gui automation handheld html ide implementations inkscape integration intergration introspection ironpython javascript jython k-12 language laser legal library mailman maps mashup metaprogramming multimedia network nevow object orientation online databse packaging panel parsing paste performance plone podcasting preservation project py3k pyblosxom pylons pypy python newbie roundup science security shell software spreadsheets storage subversion svg system administration technique testing text turbogears tutorial twisted unicode university usability user interfaces web web cam web development web framework web services web-archiving wsgi wxpython zope
Examples: games, software development, testing, web framework
This summary will be included in the talks listing, the schedule, and conference materials. The summary is pre-formated text. Newlines and indenting is preserved. Any links discovered will be made clickable. (i.e. google.com, http://www.example.com/foo/)
The detailed description is for the purpose of reviewing the proposal. Only reviewers, authors, and organizers will see it. Portions may be extracted for the website.
Be sure to include the following:
*italic*, **bold**, ``literal`` Title ===== A block quote is just indented text Subtitle -------- :: preformatted code block for code and the like
italic, bold, literal
A block quote is just indented text
preformatted code block for code and the like
http://python.org/ `Python <http://python.org/>`_ `Python PEP index`_ .. _Python PEP index: http://www.python.org/dev/peps/
http://python.org/
Python
Python PEP index
Cancel