Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Fwd: Re: [ee4j-pmc] Servlet API kickoff


On Mon, Jun 11, 2018 at 5:12 AM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxxxxxxxxxxxxx> wrote:

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 --------
Subject: Re: [ee4j-pmc] Servlet API kickoff
Date: Mon, 11 Jun 2018 11:55:14 +0200
From: Mike Milinkovich <mike.milinkovich@eclipse-foundation.org>
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>


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. 

On Jun 11, 2018, at 11:36 AM, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:

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.

For now, I have put the minutes of the meeting in the github wiki for the project.

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?
If I remember correctly, we decided that the API, document and other artifacts (e.g. xml schemas) are all products of the Specification Group.  The TCK is by a seperate group (either one combined or all seperate) and that there is no reference implemention; only specification implemenations of which their may be many. 
 
  • Can we make ammendments to the 4.0 javadoc and specification in our initial releases?  Ie can this be a maintenance release?
Until we have a contributor agreement that adequately covers IPR, the specification of anything should remain as informal as possible.  Also, in the case of the Servlet Specification owned by the JCP, I don't think we can use that in the new Jakarta EE Servlet specification, can we?   If memory serves, the new specification would need to produced from scratch - although it can embody the same specifications as the original as long as (a) it doesn't infringe copyright and (b) all contributors agree (see my first point about a contributor agreement).
  • What rules will our EG operate under?  IETF style?
  • Is there an EE4J architect?
I could be wrong, but I do not think that an EE4J Architecture Council has been established, but perhaps it should be. Also, I feel strongly that the Architecture Council needs to be split into a Jakarta EE Council and an Eclipse Council. 
  • 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?

cheers


--
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc

_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee


Back to the top