Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Servlet API kickoff
I do have a few answers while we wait for the Specification Committee.
Every project gets a dev list. All project committers should subscribe to it. This is the primary means by which the Eclipse Foundation systems will connect with the project team to, for example, inform committers of an ongoing committer election. It's called servlet-dev because the id of the project is ee4j.servlet. It would be great if project teams could use this channel for project-related discussions, but other public channels can also be used. 

Please avoid private channels for project-related communication.
  • Do we keep everything on github?
The EE4J projects have opted to use GitHub, so the webmaster can help you create repositories in the eclipse-ee4j organization as needed. You can also use GitHub Issues, pull requests, etc.
  • Who has commit access to the repo? Why can’t we see who has access?
All project committers have commit access to the repo. 
  • How is the TCK going to be managed? Where will the resources be provided from?
AFAIK, the TCK is being contributed in its entirety to the Eclipse Jakarta EE TCK project. The PMC has stated, however, that they'd like to have the TCKs separated and aligned with their respective API projects.
  • What should the copyright headers be? Can we change them?
The existing headers are, AFAIK, correct. You should have no need to change them. There's more help regarding documentation here.

HTH,

Wayne


On Mon, Jun 11, 2018 at 5: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?
  • 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?

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




--
Wayne Beaton
Director of Open Source Projects
The Eclipse Foundation

Back to the top