Spec Committee Agenda April 3rd, 2019

[Werner Keil <werner.keil@xxxxxxx>]

Probably the Steering Committee, but I also don’t see the Spec Committee to Play a Management role for individual specs or a platform.

 

Werner

 

Sent from Mail for Windows 10

 

From: Bill Shannon
Sent: Tuesday, April 9, 2019 19:44
To: Jakarta specification committee; Kevin Sutter
Subject: Re: [jakarta.ee-spec.committee] Review for approval: SpecificationCommittee Meeting Minutes April 3rd, 2019

 

I don't think the Spec Committee is project managing any of this.  Project management belongs to the PMC or the individual projects, doesn't it?

And it wasn't clear to me what the Spec Committee would be updating on the TCK or Compatible Implementations tabs.  The Spec Committee is not producing or managing any of these items, with the exception of the TCK process work that David is leading.

Kevin Sutter wrote on 4/5/19 10:23 AM:

Hi,

Looking at the actions from last week's meeting...

>  ACTION for all other owners is to update their tabs prior the next call, in particular TCK, Compatible Implementations

 

I looked at the spreadsheet and I am not planning to track the minute detail of every implementation like has been outlined on the Compatible Implementation tab. I plan to track some major milestones for each Compatible Implementation, but I don't plan to track every individual technology (ie. JSON-B, Servlet, JPA, etc) for every potential implementation per the current spreadsheet.

 

But, before I make these type of changes to the spreadsheet, I wanted to voice that opinion. I think tracking only the major milestones is consistent with what we have been discussing in regards to Compatible Implementations. That is, we as a Spec (or Steering) Committee are not interested in project managing the Glassfish project. Just like I'm sure we don't want to project manage Open LIberty, or Wildfly, or TomEE, or Payara, or.... Those details should be left up to the individual teams that are responsible for those implementations.

 

Make sense?

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter

 

 

----- Original message -----
From: Tanja Obradovic <tanja.obradovic@xxxxxxxxxxxxxxxxxxxxxx>
Sent by: jakarta.ee-spec.committee-bounces@xxxxxxxxxxx
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Cc:
Subject: [jakarta.ee-spec.committee] Review for approval: Specification Committee Meeting Minutes April 3rd, 2019
Date: Fri, Apr 5, 2019 11:00 AM
 

HI All,

can you please review for the approval of the meeting minutes from this week?

As for some the link to the document works better,providing that also. 

 

Spec Committee Agenda April 3rd, 2019

Attendees (present in bold):

Kenji Kazumura - Fujitsu, Michael DeNicola

Dan Bandera - IBM, Kevin Sutter, Alasdair Nottingham, BJ Hargrave

Bill Shannon - Oracle, Ed Bratt, Dmitry Kornilov, Jim Wright, Will Lyons

Steve Millidge - Payara, Arjan Tijms

Scott Stark - Red Hat, Mark Little, Antoine Sabot-Durand

David Blevins - Tomitribe, Richard Monson-Haefel, Jean-Louis Monterio

Ivar Grimstad - PMC Representative

Alex Theedom - Participant Member

Werner Keil - Committer Member

Eclipse Foundation: Wayne Beaton, Tanja Obradovic, Paul Buck, Mike Milinkovich

•         

Past business / action items

 

       

                

•                 

Approval of Meeting min March 27th

                

                

•                 

Will be reviewed next call

               

        

        

•         

Jakarta EE Spec - JESP process

 

       

                

•                 

Vote on JESP v1.0

 

               

                        

•                         

Richard communicated it is +1 from Tomitribe

                       

                        

•                         

Wayne will communicate by EOD the results

                       

                

                

                

•                 

Draft: Jakarta EE Specification Process v1.0

               

                

•                 

Specializing the EFSP for Jakarta EE

                

                

•                 

JESP operational document

               

        

        

•         

Jakarta EE 8 release

 

       

                

•                 

Please refer to the spreadsheet document summarizing activities related to Jakarta EE 8 release and Jakarta EE 9 planning

 

                

                        

•                         

We reviewed and updated the Specification Tab

                       

                        

•                         

ACTION for all other owners is to update their tabs prior the next call, in particular TCK, Compatible Implementations

                       

                

                

        

        

 

Many Thanks,

Tanja

 

--

Tanja Obradovic

Jakarta EE Program Manager | Eclipse Foundation, Inc.

Twitter: @TanjaEclipse

Eclipse Foundation: The Platform for Open Innovation and Collaboration

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee

 

_______________________________________________

jakarta.ee-spec.committee mailing list

jakarta.ee-spec.committee@xxxxxxxxxxx

To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee