Poppy/Developer - Getting Started
- Read the Developer's Guide on how to contribute
- Understand how the Poppy API is architected
- Read the Poppy Wiki
- Learn how the Stevedore framework works
- Learn how Pecan WSGI framework works
- Make frequent and small commits and patches.
- Add unit tests and functional tests for your code - we want 100% code coverage.
- Run "tox" before submitting patches. This will run all the tests locally and help identify issues before hitting the Jenkins servers.
- Learn the terms used in Poppy - .
- Poppy follows OpenStack guidelines.
- Must support py26,py27,py33,pypy,pep8.
- Any third party library used must be available via the Pypi server.
Participating in the process
- Join the #openstack-poppy channel where the team hangs out and participate in design discussions
- Join and participate in the weekly Poppy meeting every Thursday : Meetings/Poppy
- Contribute Blueprints for potential features that you think need to be incorporated into the Poppy API
- Contribute to implementing Blueprints
- Contribute to fixing Bugs
- Tackle some of the low hanging fruit