| Re: [ee4j-pmc] Note to Project Leads regarding the specification project process |
----- Original message -----
From: Ivar Grimstad <ivar.grimstad@xxxxxxxxx>
Sent by: ee4j-pmc-bounces@xxxxxxxxxxx
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Cc:
Subject: Re: [ee4j-pmc] Note to Project Leads regarding the specification project process
Date: Wed, Apr 24, 2019 2:46 AM
Amelia, Markus,Eclipse projects do have the notion of project leads. They are not bosses in any sense and don't have any more power than the committers.BUT they have responsibilities, and that is what Wayne asking for. One of those responsibilities is to join the PMC mailing list to take part in the information being sent there. Another one is to encourage committers to engage in the process.If a project lead, elected or appointed, isn't fulfilling their responsibilities, they can be replaced according to the Eclipse Development Process (https://www.eclipse.org/projects/dev_process/#4_6_2_PL).Please help focus on the important part here, which is to move this thing forward. It is not helpful criticizing every initiative that is being made. Note that Wayne said "We need all project leads to engage in this process with the EE4J PMC and your project team", which in my world means to discuss with committers. NOT deciding anything without discussions. I don't see anything controversial in this.IvarOn Tue, Apr 23, 2019 at 10:26 PM Amelia Eiras <aeiras@xxxxxxxxxxxxx> wrote:+1 to Markus’ feedback._______________________________________________When I read the msg with Leads on it, it bothers me to no end.OSS doesn’t have bosses, it has Contributors. I recommend Leads gets dropped and Stewards gets added instead.It seems wasteful to even consider using that word during this process. — We know better, lets show it via actions. :) end of feedback!On Apr 23, 2019, at 1:23 PM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:_______________________________________________Concern: The existing project leads are mostly not elected but simply taken over from the JCP (hence, from Oracle), so their input not necessarily covers the opinion of the majority of the committers. Hence some questions should be discussed among the committers, not among the projects leads, or there should be project lead elections first.-MarkusFrom: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Wayne Beaton
Sent: Dienstag, 23. April 2019 22:20
To: EE4J PMC Discussions
Subject: [ee4j-pmc] Note to Project Leads regarding the specification project processAs 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.As part of this, we are required to change the names of the specifications (and corresponding specification projects), and provide scope statements for each of the specifications. The provided links have more information.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 BeatonDirector of Open Source Projects | Eclipse Foundation, Inc.
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc