As discussed on our call today, I'm going to assemble a note to the EE4J project leads about getting engaged in this process.
I'm going to convert the "The process to create the first set of Final Specifications" thread into a blog post and provide a link to it as a starting point for the discussion.
For now, I'd like to avoid debating any specific part of this message in this thread and would instead like you to confirm that that I have the tone right and that I haven't missed anything important: I will send this note directly to the email addresses that we have on file for the project leads and I prefer to use direct email sparingly (so I very much appreciate your help in ensuring that I get it right the first time). The key messages with this are: please engage us on the ee4j-pmc mailing list, and please engage in the name and scope exercise.
After I send this note to the project leads themselves, we'll engage them further on the pmc mailing list.
Later tomorrow, I'll send out something like the following:
--
Greetings EE4J Project Leads.
I'm sending this note to the
EE4J PMC's mailing list with you in blind copy. Some very important discussions regarding the future of the various projects engaged in Jakarta EE specification work are happening now and in the near future on that list. It is important that you be part of that discussion, so if you have not already done so, please join this list and join in the conversation.
We are at a point in the process where it's time to create specification projects as defined by the
Eclipse Foundation Specification Process (EFSP) as a home for specification document development. Where possible and sensible, we will convert the existing "Eclipse Project for ..." projects into specification projects; in cases where this is not possible or sensible, we will create new specification projects.
This is where you come in. We need all project leads to engage in this process with the EE4J PMC and your project team. To that end, the PMC has set up a project board with individual tasks for each project. Please identify the tasks in the
project name board and
project scope board that apply to projects within your purview and engage there. Regarding names, the PMC has posted a
naming standard for your consideration.
If you have questions, connect with the PMC on the EE4J PMC list (and otherwise engage via that public channel).
--
Thoughts? Concerns? Important additions?
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
