| Re: [ee4j-pmc] Help needed with the Jakarta EE Specification Scope Statements |
That makes sense. So the scope of a specification is effectively a subset of the scope of a specification project, and is updated/changed through the normal project scope change process.
Where do we record "decisions" such as this? Should this be in the operations document?
Wayne Beaton wrote on 5/7/19 8:12 PM:
I'm thinking that the scope field in each specification project's PMI page can be used to hold both the project scope and the specification scope.
e.g.
The Jakarta Mail project provides the specification document, API, and TCK for the Jakarta Mail specification.
Jakarta Mail provides a platform-independent and protocol-independent framework to build mail and messaging applications.
Specification projects that own multiple specifications can just list them each as separate paragraphs.
Ideally, these scope statements should also appear early and distinctly in future specification documents as well.
Wayne
On Tue, May 7, 2019 at 3:53 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
I think I asked this somewhere else but never got an answer..._______________________________________________
The Eclipse project pages record the scope for a project, and the EDP defines a process for changing the scope of a project.
Where is the scope for a specification recorded, independent of the scope for the project that produces the specification, and what's the process for changing the scope of a specification? I assume this isn't already covered by the EDP since the whole concept of a "specification" is new with Jakarta EE.
Ivar Grimstad wrote on 5/7/19 9:10 AM:
Hi all,
The EE4J PMC is looking for help with producing scope statements for the Jakarta EE Specifications in order to be able to convert the current project to Jakarta EE specification projects. This is a necessary step to be able to ship Jakarta EE 8!
Super short definition of scope statements- The scope statement must be aspirational rather than attempt to capture any particular state at any particular point-in-time.- A scope statement must not focus on the work planned for any particular version of the specification, but rather, define the problem space that the specification is intended to address.
The work with scope statements is tracked in our GitHub organization:
Not that it is the scope of the specification we are looking for, not the project itself as the GitHub issues state (if anyone knows how to bulk change a bunch of GitHub issues, please go ahead...).A specification project's scope will typically be to produce the specification document, API JAR and TCK for the specification.
Thanks for your help!
This message is also posted on the Jakarta EE Platform Developer Discussions mailing list.
Ivar
_______________________________________________ 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
--
Wayne Beaton
Director 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
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.