Contributing¶
For general information on contributing to OpenStack, please check out the contributor guide to get started. It covers all the basics that are common to all OpenStack projects: the accounts you need, the basics of interacting with our Gerrit review system, how we communicate as a community, etc.
Below will cover the more project specific information you need to get started with compute-hyperv.
Communication¶
We recommend using the standard communication channels, such as the OpenStack mailing list or IRC channels. The official IRC channel (#openstack-hyper-v) is not archived at the moment, so we recommend using #openstack-dev.
Please include one of the following tags when using the OpenStack mailing list:
- winstackers
- windows
- hyper-v
Feel free to reach out to the Winstackers PTL or other core members.
Contacting the Core Team¶
The Winstackers core team is composed of:
- Lucian Petrut <lpetrut@cloudbasesolutions.com> (lpetrut)
- Claudiu Belu <cbelu@cloudbasesolutions.com> (claudiub)
- Alessandro Pilotti <apilotti@cloudbasesolutions.com> (apilotti)
New Feature Planning¶
If you want to propose a new feature, we recommend filing a blueprint and then contacting the core team.
Once the feature is approved, please propose the patches on Gerrit, following the Openstack contributor guide.
Reporting a Bug¶
You found an issue and want to make sure we are aware of it? You can do so on Launchpad. More info about Launchpad usage can be found on OpenStack docs page.
Getting Your Patch Merged¶
Changes proposed to compute-hyperv generally require two Code-Review +2 votes from
compute-hyperv core reviewers before merging. In case of trivial patches and urgent
bug fixes, this rule is sometimes ignored.
