| Re: [jakarta.ee-spec.committee] BALLOT: Approval to restructure as specification projects (round two) |
Greetings Specification Committee...
Here is the second round of conversions from regular Eclipse Projects into Specification Projects. I've grouped five projects into this first Restructuring Review.
The purpose of a Restructuring Review is to change the nature of a project. Since the Eclipse Foundation Specification Process (EFSP) does not specifically deal with the notion of restructuring, I'm following the Eclipse Development Process (EDP). While we are not strictly creating a new project, we are in a manner of thinking, creating new Specification Projects from the existing ones. With this in mind, I am treating this as a Creation Review from the perspective of the Specification Committee approval requirement.
I have created a Restructuring Review record that provides the high level details of the intention. I've pasted it below for your quick review and for posterity. In all cases, I've included the scope statement for the specification itself; the specification project's scope will be to "provide the specification document and supporting technical artifacts" for the corresponding specification.
The review documentation includes links to GitHub Issues that provide more details regarding what will change.
Here is the project list:We will rename the "Eclipse Jakarta EE Platform" project to "Jakarta EE Platform" and convert it into a specification project with this project/specification scope statement:
The Jakarta EE Platform project provides the specification document, and related technical artifacts for the Jakarta EE Platform Full Profile, Jakarta EE Platform Web Profile, and Jakarta Managed Beans Specifications.
The Jakarta EE Platform Full Profile defines the aggregation and integration of the full collection of Jakarta EE specifications.
The Jakarta EE Platform Web Profile defines the aggregation and integration of the subset of Jakarta EE specifications related to the development of web applications.
The Jakarta Managed Beans specification defines a set of basic services for container-managed objects with minimal requirements, otherwise known under the acronym “POJOs” (Plain Old Java Objects).
We will rename "Eclipse Project for JTA" project to "Jakarta Transactions" and convert it into a specification project with this project/specification scope statement:
Jakarta Transactions defines a standard that allows the demarcation of transactions and the transactional coordination of XA-aware resource managers as described in the X/Open XA-specification and mapped to the Java SE XAResource interface within Java applications.
We will rename "Eclipse Project for JMS" project to "Jakarta Messaging" and convert it into a specification project with this project/specification scope statement:
Jakarta Messaging describes a means for Java applications to create, send, and receive messages via loosely coupled, reliable asynchronous communication services.
We will rename "Eclipse Project for JSON-B" project to "Jakarta JSON Binding" and convert it into a specification project with this project/specification scope statement:
Jakarta JSON Binding defines a binding framework for converting Java objects to and from JSON documents.
We will rename "Eclipse Project for Servlet" project to "Jakarta Servlet" and convert it into a specification project with this project/specification scope statement:
Jakarta Servlet defines server-side handling for HTTP requests and responses.
We will rename "Eclipse Project for JSP" project to "Jakarta Server Pages" and convert it into a specification project with this project/specification scope statement:
Jakarta Server Pages defines a template engine for web applications that supports mixing of textual content (including HTML and XML) with custom tags, _expression_ language, and embedded Java code, that gets compiled into a Jakarta Servlet.
We will rename "Eclipse Project for Concurrency Utilities" project to "Jakarta Utilities" and convert it into a specification project with this project/specification scope statement:
Jakarta Concurrency defines a framework for leveraging concurrency in application components without compromising container integrity while still preserving the Jakarta EE Platform's fundamental benefits.
We will rename "Eclipse Project for JSTL" project to "Jakarta Standard Tag Library" and convert it into a specification project with this project/specification scope statement:
Jakarta Standard Tag Library defines a framework and simple tags for Jakarta Server Pages that provide support for common, structural tasks such as iteration and conditionals, tags for manipulating XML documents, internationalization tags, and SQL tags.
We will rename "Eclipse Project for JAXB" project to "Jakarta XML Binding" and convert it into a specification project with this project/specification scope statement:
Jakarta XML Binding defines an API and tools that automate the mapping between XML documents and Java objects.
We will rename "Eclipse Project for EJB" project to "Jakarta Enterprise Beans" and convert it into a specification project with this project/specification scope statement:
Jakarta Enterprise Beans defines an architecture for the development and deployment of component-based business applications.
I hereby request that the Specification Committee vote to approve the conversion as described above of these existing projects into Specification Projects under the supervision of the Jakarta EE Working Group.--
Please respond to this note with:
+1 to approve;
-1 to reject; or
0 to abstain.
If you do choose to reject or abstain, I would appreciate a short (one or two sentence) explanation.
I will interpret a single vote as applying to all of the listed projects. You may also vote for each project individually (if, for example, you'd like to register different votes for each projects).
I will document the results of this vote on a per-project basis.
Thanks,
WayneWayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.