Here is a proposal Steve was talking about:
https://docs.google.com/document/d/1i4q0MxORDjZ99X_sbczXid4AZnS049bbjITj_IKEnpc/edit#heading=h.qhay327tmakk
Again, we create a special experts group to analyse and discuss all possible pros and cons in Jakarta Config. CN4J is not technical by its nature. I see no point in discussing it twice in different places.
-- Dmitry
Steve,
Can you also add your doc here so that we can discuss and agree on the common goals and nongoals with both proposals?
Thanks
Emily
Hi Emily,
Dmitry and I also put together an alternative document to your and Scott’s proposals so if people insist this goes to a CN4J discussion then both documents would need to be given equal precedence.
Btw CN4J is not a decision making body just a coordination forum.
Steve
We already had this discussion on Jakarta EE Platform meeting and tried to discuss it on one of CN4J meetings with the following conclusion:
1. CN4J meetings are not for technical discussions.
I think some fundamental goals/ non goals as laid out in the google
doc should be agreed on at CN4J meetings. Once we have some guidance, it will be much easier to answer some questions or agree on some actions based on that. By the way, I have no intention to discuss the internal
functionalities of MP Config here, as demonstrated in the google doc.
2. We will create Jakarta Config project and invite there all interested parties including MicroProfile Config committers. The first task for this group is to carefully analyse MP Config and decide which parts
of it should be moved to Jakarta which are not. It may be agreed that the whole MP Config should be moved without any changes, it can be agreed that MP Config suits Jakarta EE only partially. I don’t know the answer yet and not making
any assumptions. It’s what Jakarta Config project will decide the open way. Java package and Maven coordinates will also be part of this discussion. As you mentioned, Jakarta Config is in creation review now. I expect it to be created at the beginning
of June. That time the project group will start working. We all will be happy to discuss your and Scott proposal there.
I think we need to agree on some basic principles first and then work on the technical aspects in Jakarta EE. For instance, Jakarta EE will not be able to ask MicroProfile Config to freeze. Therefore, I feel CN4J
is the place to discuss the roadmap for the spec that affects both Jakarta EE and MicroProfile.
3. When the analysis and discussion is finished, Jakarta Config team will come out with the final plan.
As some of you might be aware, Jakarta
Config Creation Review was created recently by Dimtry (Thanks Dimtry!). The plan is to work with the MicroProfile Config team to define Jakarta Config to be included in Jakarta Core Profile.
The next step is to work out the content of Jakarta Config. From the recent survey done by Reza, it seems majority votes went to move MicroProfile Specs to Jakarta EE (see here for
the survey result blog written by Reza). The top 2 choices are either updating MicroProfile Namespace or keeping the existing MicroProfile namespace.
The community voice is very important to us, but I would also like to gather some consensus from Working group members to agree on the final direction as this impacts both MicroProfile and the Jakarta community.
We need to agree on a solution working for both MicroProfile and Jakarta. With this, I would like to start the discussion of moving MicroProfile Config to Jakarta EE and rebrand to be Jakarta Config 1.0 without updating
namespace and then the future development will evolve in Jakarta EE and any new classes and packages can still use org.eclipse.microprofile.*.
Here is the proposal that
Scott and I put together. Let's start this conversation on the mailing list first. If necessary, we can schedule a call to discuss further. Please share your thoughts here.
_______________________________________________
cn4j-alliance mailing list
cn4j-alliance@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cn4j-alliance
_______________________________________________
cn4j-alliance mailing list
cn4j-alliance@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cn4j-alliance
--
--
_______________________________________________
cn4j-alliance
mailing list
cn4j-alliance@xxxxxxxxxxx
To
change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.com/v3/__https://dev.eclipse.org/mailman/listinfo/cn4j-alliance__;!!GqivPVa7Brio!KsjQSEtRhLrL_WuplZN7DUlXkeC44V2IaDDrUt5G0L43HM6ATESs8owMy0wesMYanoxm$
|