Difference between revisions of "Python3/SprintPycon2014"
(→Requirements) |
(→Requirements) |
||
| Line 25: | Line 25: | ||
* Basic knownledge of OpenStack: [http://devstack.org/ install DevStack] | * Basic knownledge of OpenStack: [http://devstack.org/ install DevStack] | ||
* Subscribe to Launchpad and OpenStack projects, sign the CLA (can be done during the sprint) | * Subscribe to Launchpad and OpenStack projects, sign the CLA (can be done during the sprint) | ||
| − | + | ** [https://www.openstack.org/join/register/ Join The OpenStack Foundation: Individual Member (Free)] | |
| − | + | ** [https://login.launchpad.net/+new_account Launchpad: new account] | |
| − | |||
== Document == | == Document == | ||
Revision as of 07:51, 31 March 2014
Enovance organizes a sprint to Port OpenStack to Python 3 during 4 days: between April, 14 (Monday) and April, 17 (Thursday).
Contents
What
The ultimate goal is to port the whole OpenStack project to Python 3. The goal of the sprint is to send patches to port as much code as possible, OpenStack and OpenStack dependencies.
Who
Anyone knowing Python and OpenStack can participate!
When
April, 14 (Monday) and April, 17 (Thursday).
The next major release of OpenStack is "Icehouse", scheduled for April, 17.
Where
Montreal, at Pycon Montreal 2014.
Requirements
- Bring a laptop
- Good knownledge of Python
- Basic knownledge of OpenStack: install DevStack
- Subscribe to Launchpad and OpenStack projects, sign the CLA (can be done during the sprint)
Document
- Python 3 wiki page
- OpenStack Style Guidelines
- Documentation of the six module
- Port Python 2 code to Python 3
- Status of the OpenStack port to Python 3
- Use the new asyncio module and Trollius in OpenStack
- Why should OpenStack move to Python 3 right now?
Sync
Any change in OpenStack must be carefully reviewed. Don't expect to see your changes commited immediatly, you will probably have to discuss with the "core developers" of each project to enhance your patch, to make it fit the coding style of the project.
If you want to work on a component (ex: neutron, nova, etc.), please write the component name with your name below:
- <component>: <developer name>
