Greetings Specification Committee...
Here is the first 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. In the
case of "Eclipse Project for JAX-RS", for example, we are
compelled to change the project id and the name of the
GitHub repository to avoid names that Oracle lays claim to.
Here is the project list:
Eclipse Project for JAX-RS will
be renamed to "Jakarta RESTful Web Services" with the
following specification scope:
Jakarta
RESTful Web Services defines a standard for development of
web services following the Representational State Transfer
(REST) architectural pattern.
Eclipse Project for JSON
Processing will be renamed "Jakarta JSON Processing"
with the following specification scope:
Jakarta
JSON Processing defines a Java(R) based framework for
parsing, generating, transforming, and querying JSON
documents.
Eclipse Project for JAF will
be renamed "Jakarta Activation" with the following
specification scope:
Jakarta
Activation defines a set of standard services to:
determine the MIME type of an arbitrary piece of data;
encapsulate access to it; discover the operations
available on it; and instantiate the appropriate bean to
perform the operation(s).
Eclipse Project for JPA will
be renamed "Jakarta Persistence" with the following
specification scope:
Jakarta
Persistence defines a standard for management of
persistence and object/relational mapping in Java(R)
environments.
Eclipse Project for WebSocket will
be renamed "Jakarta WebSocket" with the following scope:
Jakarta
WebSocket defines how Jakarta based applications create
and manage WebSocket Clients and Servers.
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,
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
