| Re: [jakarta.ee-spec.committee] Werner's comment |
Having additional candidates for the process is great. Is this specific to MicroProfile? If so, than I think it should remain in the MP project. They have their own process for specifications. If its not MP specific and can complement the Jakarta EE platform than I would support adding it as a candidate.On Wed, Aug 29, 2018 at 4:31 PM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> wrote:All,
Werner added a comment to the draft minutes of our meeting today. I cannot keep it as part of the minutes since we did not discuss it on the call, but I thought it was pertinent so wanted to capture it for everyone via this email:
Create a plan to deliver a draft Specification Process for CodeOne/EclipseCon
Creating a draft from scratch may not work there, but in the EG discussion Emily sounded very interested to also migrate the non-final Config JSR to Jakarta EE, see: https://dev.eclipse.org/mhonarc/lists/configjsr-experts/msg00059.html If what was discussed for JNoSQL applies to a future version of the Config Spec, then it would end up with at least 2 package name spaces. Migrating it now before it even entered MavenCentral could avoid that.