Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
MicroProfile/FeatureInit
Contents
Introducing New Ideas to Eclipse MicroProfile
Step 0: (optional) Start immediately via `microprofile-sandbox` repository
- Fork the repository
- Create a distinct sub-directory
- Code
- 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.
Lazy Consensus: Considered accepted with no negative votes.
Step 1: Request a Repository
Send message to Google Group Forum with brief paragraph or two on the idea/proposal and asking for feedback within 72 hrs.
If you are already active in the MicroProfile community, lazy consensus applies.
If you are not yet active in the MicroProfile community, consensus is required. Those not yet active are highly encourage to leverage the sandbox as a great way to show the essence of ideas.
Acceptance results in an appropriate admin requesting a new git repository for the proposal so that work can begin on spec/api/tck.
Once the new repository is created, existing content from `microprofile-sandbox` is migrated to new repository and removed from `microprofile-sandbox`.
Step 2: Collaboration
Proposal goes through community iteration of development, discussion leveraging lazy consensus. Any form of release requires community consensus.