Whether you are just getting started as an OpenStack contributor or you are a veteran upstream committer, there's always room to improve the efficiency of your workflow.
From writing a blueprint, coding it and submitting patches, you have an environment, tools and procedures you follow.
There is no "right" or "wrong" workflow, that said, is your workflow as efficient as it could be? There is always room for improvement and the aim of this discussion is to try to share our experiences, both good and bad, and make us all productive committers and more successful in the community.
Some of the topics addressed:
- Your development environment? DevStack, OpenStack Ansible, or full distro on a rack of servers?
- Tooling: IDEs, CLI only?
- Testing strategies
- Python venvs
- Best practices for writing blueprints
- Submitting your patches: one big one or lots of little ones?
We will share a couple of unique workflows and look to attendees to share their experiences as well.
The goal here is to share and educate us all a little so all upstream contributors can be:
- More productive - get more done in less time
- Less frustrated - get your blueprints accepted and code committed upstream as painlessly as possible.