eclipse/microprofile-evolution-process

For the evolution of new ideas

Eclipse MicroProfile

This repository is no longer the active process for submitting feature ideas for Eclipse MicroProfile.

Please see https://wiki.eclipse.org/MicroProfile/FeatureInit for details of the current process.

microprofile-evolution-process's Issues

Need to clean up evolution-process per IP review

Our process documentation still references the microprofile.io site in several locations. We need to clean these up per the IP review:
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=12628

2. The microprofile-evolution-process-master/process.md references
   contributing to https://microprofile.io/community/#contributing. I believe
   you'll want to amend necessary URLs as required as this could be confusing.
   Yes, agree. We've been finding several of these ourselves and have been
   correcting some of them as we go along. We are also undergoing a massive
   update to this "evolution process", so much of this might be removed.

URLS Generally

3. It seems certain URLs remain pointing to the original project as above.
   Please advise if the content has received a pass to update URLs as expected?
   Not sure what you mean by "receiving a pass"? We will still have some
   URLs pointing back at the microprofile.io site, but we shouldn't be relying or
   depending on these URLs for any specific content. It's more to recognize that
   microprofile.io is a viable and useful portal for our efforts.

Third Party Content:

4. The /microprofile-evolution-process-master/NOTICE.md indicates the work is
   derived from the Swift Evolution Process and adapted to suit.... That
   statement would indicate the inclusion of Third Party Content. A Third Party
   CQ is required.
   Again, we're in the process of revamping our processes, so this particular
   statement about Swift might go away. Also, please be aware that this repo is
   only to document our process for developing MicroProfile content. This is not
   part of our deliverables, per se. These processes help us develop our
   deliverables. So, even this derived usage of the Swift Evolution Process is
   not really Third Party Content. There is nothing "real", just processes.

Since we're in the process of redefining and simplifying our process, we should clean these items up at the same time.

We should replace the term "core team" in the process doc

As John mentioned, "core team" should be changed.

One option would be to use Eclipse approved committers:
https://projects.eclipse.org/projects/technology.microprofile/who

Define a way to form a working group

In the proposal process, we get some number of people to get to write a proposal. After the proposal is written, we sometimes get more people interested in a project.

We should add some details about how to join these discussions.

Create proposal for OpenAPI v3

Create proposal for OpenAPI v3 Java specification.

Document our voting requirements

https://groups.google.com/forum/#!topic/microprofile/tTEaf2uBnt4

In this topic, our rules around votes for evolution changes are discussed. Whatever the outcome, this ticket is to document those rules within the evolution process itself.

Add label "proposal" to the Monitoring PR #12

Hi, microprofile org members, can anyone of you add the label "proposal" to the PR #12 to follow the agreed eveolution process?

Please also confirm on the mailing list topic or a new topic that the review is started, with estimated deadline for the review.

//cc @karianna @AndyGee @dblevins @tveronezi @Emily-Jiang @smillidge @kenfinnigan

Close the evolution repo issues to maintainers

Community should not use the github issues to submit proposals

Review the template for new proposals

Based on FT hangout on 12 April 2017

come up with canonical URL paths we use for swagger, liveness checks, readiness checks etc

It'd be nice to come up with some conventions for microprofile apps that make them easy to automatically tool when its ran on a container platform like kubernetes.

For example if we had canonical paths for exposing the swagger metadata, we could annotate the Deployment automatically via the fabric8 maven plugin (see this issue fabric8io/fabric8-maven-plugin#645).

Similarly it'd be nice to have a canonical URL path for liveness and readiness checks
http://kubernetes.io/docs/user-guide/liveness/
so that we can automatically add good liveness & readiness probes when deploying a microprofile app on kubernetes fabric8io/fabric8-maven-plugin#645

Fix link

Replace content of 00001-config.md to something more fitting.

This is a follow up of #41.

00001-config.md is linked from https://jcp.org/en/jsr/detail?id=382, Section 3, first link:

Is it possible to a) change the deep link of the JSR (contradiction to Cool URIs don't change) or b) to add the outdated link to the deep linked file https://github.com/eclipse/microprofile-evolution-process/blob/master/proposals/0001-config.md?

Reservation file for MP proposal numbers?

I ran into an issue when I created the proposal for MicroProfile 1.1. I just looked at the "proposals" subdirectory and saw the next logical number was 0005. But, because of other in-flight proposals, this number was already in use by the JWT proposal. So, how can someone know what the proper proposal number should be?

My suggestion is to just create a top-level file that can easily be updated with the MP proposal number along with the title of the proposal. As new proposals arise, we could update that file so that everyone can see at a glance all of the proposal numbers and associated titles.

I'm open to other ideas. I'm just looking for something simple so that future proposals don't hit the same problem that I did. Thanks.

The config proposal needs to me moved

Proposal go into the proposals subfolder. @Emily-Jiang can you move the proposal there?