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

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…

How to get ready for the PyCon development sprints

[A guest post by Kushal Das, one of the 2016 Sprint Coordinators]So — you have already decided to join in the PyCon development sprints! The sprints run for four days, from Thursday to Sunday after the conference. You do not have to be registered for the conference to attend the sprints! Some teams plan to write code over all four days, while some projects plan a shorter sprint if the organizers cannot stay for all four days.Can you start getting prepared for the sprint ahead of time? Yes!There are several things you can do ahead of time, that can save effort once you arrive at the sprints — and some preparations can even be made at home, before you arrive at PyCon:Have your operating system updated and patched — whether Mac, Windows, or Linux. This eliminates one possible source of problems with getting software up and running.Go ahead and install the version control system that will be used by the projects you are interested in. If you install both git and Mercurial on your computer…

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to https://us.pycon.org/2018/registration/ to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…