Further to yesterday's MP technical call, there was a consensus to standardize the way of creating new specifications. In this year's MicroProfile Technical Goals, the community
expressed the desire to work on new proposals of adopting new technologies such as OpenTelemetry, gRPC, etc. How to proceed with this?
If you (proposer) are already active in the MicroProfile community, lazy consensus applies.
If you (proposer) are not yet active in the MicroProfile community, consensus is required. Those not yet active are highly encouraged to leverage the
sandbox as a great way to show the essence of ideas.
It seems like adding an extra barrier to new proposers. Besides, what happens if no consensus is reached. This seems one -1 will stop a proposal going forward, which contradicts with our voting policy of supermajority.
With these concerns, we discussed in the meeting with some initial suggestions:
Step 1: Start immediately via `microprofile-sandbox` repository
Create a distinct sub-directory
Submit as many PRs as you need to explore the ideas behind the proposal
No approvals or prior notification required.
The `microprofile-sandbox` has an intentional zero bar to entry to capture ideas when time permits, from anyone, even if not yet active in the MicroProfile community.
When ready, proceed to the next step.
Any form of contribution on any topic is allowed in the `microprofile-sandbox`. Moving from the `microprofile-sandbox` is at will or upon request of the MicroProfile community.
Step 2: Create Project Creation Plan
Create an issue under microprofile-wg with the label of Plan Creation Review and then send it to this WG to start a ballot. If it passes the ballot with a super majority, a new
project will be created under microprofile.