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?
