...
...
| Table of Contents |
|---|
| Info |
|---|
The purpose of an OpenMBEE Enhancement Proposal (OEP) is to introduce any major change to OpenMBEE. This is required in order to balance the need to support new features, use cases, while avoiding accidentally introducing half thought-out interfaces that cause needless problems when changed. |
...
What are the "public interfaces" of the project? All of the following are public interfaces that people build around:
TODO
Proposal lifecycle
| Info |
|---|
Prerequisites
If you have trouble accessing any of the above, please contact openmbee [at] gmail [dot] com |
Discuss
Most proposals start with an idea. If you have an idea of how OpenMBEE could improve, we encourage you to send a Slack message to an email to openmbee [at] googlegroups [dot] com with a subject starting with [DISCUSS]. This email thread will allow you to gather early feedback. We encourage you to start a Draft document on this wiki or share a Google Document with the mailing list detailing your proposal. Use AIP the OEP template here to file provide details on your proposal.
...
Anyone is welcome to propose a new Improvement improvement to AirflowOpenMBEE. You will need to request edit access to the Confluence page in order to create your AIP OEP document. You can do so by sending an email with your Wiki ID to dev@airflow.apache.org details to openmbee [at] gmail [dot] com and request permission.
| Create from Template | |||||
|---|---|---|---|---|---|
|
|
Vote
Once you or someone else feels like there’s a rough consensus on the idea and there’s no strong opposition, you can move your proposal to the Vote phase. For this you will send a new email to the dev list with the subject starting with [VOTE]. This phase follows a vote on code modifications for Apache projects as described here. Remember to link the discussion thread to your AIP and ideally also to this vote email. And don’t forget to link the AIP to the email as well.
...