TwistedSprint
This wiki is in the process of being archived due to lack of usage and the resources necessary to serve it — predominately to bots, crawlers, and LLM companies. Edits are discouraged.
Pages are preserved as they were at the time of archival. For current information, please visit python.org.
If a change to this archive is absolutely needed, requests can be made via the infrastructure@python.org mailing list.
Twisted Sprint
Twisted is too big and there are too many small groups of people who want to work on different things for a "Twisted Sprint" to be meaningful. There will be several mini-sprints involving improvements to the Twisted code base and related projects.
Potential mini-sprints
This is only a list of possibilities; if you can think of anything else that might belong here, or if you definitely plan on organizing your own Twisted mini-sprint, put it up here.
The 2.0 release: for planning and explaining details of Twisted's future architecture.
Twisted.web2: help with an enlightened rewrite of Twisted's HTTP server and client
Nevow: a powerful new templating and rendering engine for use with (or without) Twisted web servers
LivePage: bi-directional, realtime calling between Python in the backend and JavaScript in the front-end; enhance API available to Python to manipulate the browser, and add SSL support.
Participants
Please add your name if you plan on coming to a Twisted-related sprint! If you don't know which mini-sprints you want to take part in, at least just put it at the end of this page.
Alex Levy (mesozoic)
- James Knight (foom) - heading up web2.
- Ed Rahn
- Jeff Rush
Kragen Sitaker (maybe)
- Kartic Krishnamurthy (Tuesday). Level - Beginner. Not sure which mini-sprint to participate in.
- your name here