So You Want to Contribute…¶
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 Trove.
Communication¶
IRC channel: #openstack-trove
Mailing list’s prefix: [trove]
Currently, we don’t have team meeting given we have a small group of core reviewers and their timezones, the situation may change in the future.
Contacting the Core Team¶
The list of current Trove core reviewers is available on gerrit.
New Feature Planning¶
Talk to the team via IRC (meeting) or ML (with [trove] prefix) about the feature requested. We will discuss if a spec is needed based on the implementation complexity and the installation/configuration/upgrade/user-facing impacts.
If a spec is need, a patch needs to be submitted to trove-specs repo before the code being reviewed.
Code implementation and review
Task Tracking¶
We track our tasks in Storyboard
If you’re looking for some smaller, easier work item to pick up and get started on, search for the ‘low-hanging-fruit’ tag.
Reporting a Bug¶
You found an issue and want to make sure we are aware of it? You can do so on Storyboard.
Getting Your Patch Merged¶
Due to the small number of core reviewers of the Trove project, we only need
one +2 before Workflow +1.
Project Team Lead Duties¶
All common PTL duties are enumerated here in the PTL guide.
