Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Jakarta EE Specification names and scope statements
Let's kindly not add Slack. Email is already bad enough. Don't need the additional noise.

Reza Rahman
Principal Program Manager
Java on Azure

Please note views expressed here are my own as an individual community member and do not represent the views of my employer.

Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone

-------- Original message --------
From: "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
Date: 5/31/19 5:35 AM (GMT-05:00)
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>
Subject: Re: [ee4j-pmc] Jakarta EE Specification names and scope statements

+1 on not joining Slack as the last thing I need is another “inbox” in my life.

 

Steve

 

From: ee4j-pmc-bounces@xxxxxxxxxxx <ee4j-pmc-bounces@xxxxxxxxxxx> On Behalf Of Markus KARG
Sent: 31 May 2019 10:00
To: 'EE4J PMC Discussions' <ee4j-pmc@xxxxxxxxxxx>
Subject: Re: [ee4j-pmc] Jakarta EE Specification names and scope statements

 

Ivar,

 

thank you for this clear request. I will fix the open issues ASAP for JAX-RS so we can hold the PMC's deadline.

 

Unfortunately I need to tell you that I won't join Slack. I am participating in lots of open source projects and all of them work great just by using email. So I hope that the PMC still will use the EF's usual technology to communicate with the project members and Slack is just an *additional* means.

 

-Markus

 

 

From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Ivar Grimstad
Sent: Freitag, 31. Mai 2019 08:56
To: EE4J PMC Discussions
Subject: [ee4j-pmc] Jakarta EE Specification names and scope statements

 

Based on the request from the Jakarta EE Specification Committee, the EE4J PMC is reaching out to everyone involved in the EE4J projects.

 

The work with defining the Jakarta EE specification names and scope statements has been going on for a couple of months. The tracking can be found here:

 

https://github.com/orgs/eclipse-ee4j/projects/11

https://github.com/orgs/eclipse-ee4j/projects/10

 

We will need the proposed project names and scope statements by June 7/2019. Please close the related issue when the project team has come to a conclusion. For those scope statements that are not complete by the deadline, the PMC will create the names and statements on behalf of the projects.

 

The lack of activity on the request for help with the name change and creating of scope statements is a major concern for the EE4J PMC. A consequence may be that we will have to revisit the composition of the unresponsive projects.

 

The Jakarta EE 8 release is very much dependant on the specification names and scope statements changes. To plan out the release schedule and the release date we need to ensure this work is completed in order to engage in the Release review.

 

These are the specifications where there is no or little, progress regarding scope statements:

 

  • Common Annotations
  • Concurrency Utilities
  • EJB
  • Enterprise Security
  • _expression_ Language
  • Interceptors
  • JACC
  • JASPIC
  • JAX-WS
  • JCA
  • JAX-B
  • JSTL
  • JTA
  • Stable APIs
    • Platform Management
    • Platform Application Deployment
    • XML Registries
    • JAX-RPC
    • Enterprise Web Services

 

A Slack Workspace JakartaEE Development is created for collaboration and communication on the Jakarta EE related projects. Can you all please join? Here is the link

 

Ivar - on behalf of the EE4J PMC

 

Back to the top