Thanks for the pointer. I feel like I'm only really going to know
what a good scope statement is after reviewing a bunch of scope
statements. I took a crack at it for Jakarta Mail, but I don't know
if I did it right! :-)
Do we want to request that the Project Leads for each of the
Specification Projects send a draft scope statement to the
Specification Committee, which will collect them together and review
them all at once, sending feedback to the Project Leads? (Although
the Specification Projects don't really exist yet because we haven't
converted some of the existing projects into Specification
Projects.)
Or do you feel like you can review them one at a time as they come
in? (Maybe Wayne can do that, but I can't!)
I guess we're supposed to use the
project
tracker to know what's ready for review.
It sounds like we need to vote on each scope statement. How are we
going to keep track of which scope statements have been approved?
Meeting minutes? Closing the corresponding issues?
In addition to the Specification Committee approving the new scope
statements, do the projects also need to go through a formal Eclipse
process to update the scope for a project? If so, how will we track
that that's been done?
As usual, I'm just trying to understand what the process is for
getting to an approved set of scope statements for our projects.
Finally, I have to ask once again...
Will the TCKs be part of the Spec Projects (when they're eventually
split out of the CTS, or like Jakarta Mail are already separate)?
Or will they have to be in a different project, e.g., because
they'll need to use a different license?
Last I heard, they needed to be separate, but I'd like
confirmation. (The Jakarta Mail TCK will need to be moved, for
example.)