|
All,
There are some really good questions in here that we could use as
the starting point for an FAQ on our spec requirements document.
-------- Forwarded Message --------
Greg,
All excellent questions :)
The Specification Committee of the Jakarta EE Working Group
is a few days away from publishing an initial document outlining
their thoughts on how the spec process is going to work. Most of
what you’re asking about is their responsibility, not the EE4J
PMC. If you can be patient for just a few more days, it would be
appreciated.
Thanks.
Mike Milinkovich
(m) +1.613.220.3223
Please note new email
address.
All,
Stuart Douglas and I had a kickoff meeting today for
the servlet-api project. The meeting produced more
questions than answers and we realized that we need to
not just go do our own thing and should seek guidance
from the ee4j project to try to follow communal
standards/process etc. as far as possible.
There are lots of question in there, mostly directed
at the ee4j-pmc. Please read the document for a
(little) bit more context, but to ease any replies we
can get in this thread I will list the main questions
for the PMC below:
- Are we also responsible for: the servlet 4.0
document; The relevant xml schemas; The TCK; The
reference implementation?
- Can we make ammendments to the 4.0 javadoc and
specification in our initial releases? Ie can this
be a maintenance release?
- What rules will our EG operate under? IETF style?
- Is there an EE4J architect?
- Do we have/need a mailing list? What is servlet-dev@xxxxxxxxxxx?
Should that be ee4j-servlet-api@xxxxxxxxxxx?
- Do we keep everything on github?
- Who has commit access to the repo? Why can’t we
see who has access?
- How is the TCK going to be managed? Where will the
resources be provided from?
- How is the specification document going to be
managed? Where is the source? What format?
- What are the RI plans? Glassfish? Servlet only? Do
we need one? Who maintains?
- Do we manage our own schemas?
- What should the copyright headers be? Can we
change them?
|
