Skip to main content

Extracurricular Activities at PyCon 2007

At PyCon this year we are having a significant number of activities besides the keynotes and talks. One group of those are the birds-of-a-feather gatherings being held in the evenings.

The Python community consists of a number of smaller communities and we're encouraging them to hold meetings, dinners and other activities at PyCon this year. The organizers have tried to leave room in the busy schedule for these to happen and of course for some non-Python social BoFs as well.

Here are the BoFs with which you have the opportunity to get involved:
  • Python in Education
  • Python in Science
  • Healthcare and Python
  • A Content Repository Standard for Python
  • Jython Development
  • Django
  • Pylons Web Framework
  • Trac Users and Developers
  • Keysigning Party
  • Tech that Runs the Python Conference
  • Users of Bazaar Version Control/Launchpad
  • Buildbot Users and Developers
  • Python Advocacy Community Forum
  • Texas Regional Unconference Dinner Meet
  • PyGame Programming/Playing Clinic
  • Board Game Socials
  • Bowling
  • Climbers
You can check them out at:

http://us.pycon.org/TX2007/BoF

The room/offsite schedule is listed at the bottom of that page but many of the groups have not yet declared when and where they are meeting. Nudges are welcome.

The other set of activities at PyCon are the 4-days of code sprints held at the end of the conference. A sprint is a focused development session, in which developers gather in a room and focus on building a particular subsystem. A sprint is organized with a coach leading the session. The coach sets the agenda, tracks activities, and keeps the development moving. The developers will sometimes work in pairs using the Extreme Programming (XP) pair programming approach.

The sprints that have announced so far are:
  • Work towards Zope 3.4 release
  • Fun Educational Software for "Playful Learning"
  • PyCon-Tech: Improve the convention software
  • Zope 3 Learner's Circle
  • Python Job Board
  • Django
  • Trac
  • Jython
  • Docutils: squash bugs & add features
  • TurboGears
  • Write a Game
  • Create a Win32 version of MySQLdb under Python 2.5
  • SchoolTool & CanDo
Sprint coaches should plan for an introductory session on Sunday afternoon or Monday morning, to help attendees get started. This might involve helping them to get SVN or CVS installed and checking out the development tree, talking about the software's architecture, or planning what the four-day sprint will try to accomplish.

You can read more at:

http://us.pycon.org/TX2007/Sprinting

and even add your name to particular sprint wiki pages, to encourage them to happen.

See you later this week. Get plenty of sleep beforehand, you won't get much at PyCon this year!

Jeff Rush
PyCon Co-Chair

Comments

tercumenette said…
This comment has been removed by a blog administrator.

Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. PyCon is made by you, so we need you to share what you’re working on, how you’re working on it, what you’ve learned, what you’re learning, and so much more.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
Who should write a proposal? Everyone! If you’re reading this post, you should write a proposal. PyCon is about uniting and building the Python community, and we won’t advance as an open community if we’re not open with each other about what we’ve learned throughout our time in it. It isn’t about being the smartest one in the room, so we don’t just pick all of the expert talks. It’s about helping everyone move together. “A rising tide lifts all boats,” if you will.

We…

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…