Masakari is always evolving its processes to ensure productive communication between all members of our community easily.
Masakari follows most of the generally adopted norms for OpenStack projects. You can get more details here:
If you are new to Masakari, please read this first:
OK, so you are new to Masakari, and you have been given a feature to implement. How do I make that happen?
You can get most of your questions answered here:
But let's put a Masakari specific twist on things...
We track bugs here:
If you fix an issue, please raise a bug so others who spot that issue can find the fix you kindly created for them.
Also before submitting your patch it's worth checking to see if someone has already fixed it for you (Launchpad helps you with that, at little, when you create the bug report).
To understand this question, we need to understand why blueprints and specs are useful.
But here is the rough idea:
If you are unsure, please ask PTL or one of the other masakari-core on IRC.
So you need your blueprint approved? Here is how:
Got any more questions? Contact samP or one of the other masakari-core who are awake at the same time as you. IRC is best as you will often get an immediate response, if they are too busy send him/her an email.
When feature freeze hits, any patches for blueprints that are still in review get a procedural -2 to stop them merging. In Masakari a blueprint is only approved for a single release. To have the -2 removed, you need to get the blueprint approved for the current release (see How do I get my blueprint approved?).
First and foremost - address any -1s and -2s! A few tips:
Eventually you should get some +1s from people working through the review queue. Expect to get -1s as well. You can ask for reviews within your company, 1-2 are useful (not more), especially if those reviewers are known to give good reviews. You can spend some time while you wait reviewing other people's code - they may reciprocate and you may learn something (
Why do code reviews when I'm not core? <why_plus1>).
If you've waited an appropriate amount of time and you haven't had any +1s, you can ask on IRC for reviews. Please don't ask for core review straight away, especially not directly (IRC or email). Core reviewer time is very valuable and gaining some +1s is a good way to show your patch meets basic quality standards.
Once you have a few +1s, be patient. Remember the average wait times. You can ask for reviews each week in IRC, it helps to ask when cores are awake.
It helps to apply correct tracking information.
Again, it helps to apply correct tracking information. For blueprint-only features:
For blueprint and spec features, do everything for blueprint-only features and also:
If it's not a priority, your blueprint/spec has been approved for the cycle and you have been patient, you can raise it during the Masakari meeting. The outcome may be that your spec gets unapproved for the cycle, so that priority items can take focus. If this happens to you, sorry - it should not have been approved in the first place, Masakari team bit off more than they could chew, it is their mistake not yours. You can re-propose it for the next cycle.
If it's not a priority and your spec has not been approved, your code will not merge this cycle. Please re-propose your spec for the next cycle.