[ADMIN] Welcome to Servlet 4.0 on groups.io

Edward Burns

Welcome to Servlet 4.0 on groups.io. I'll take this opportunity to
resend the originial first message from jsr369-experts@..., and
I'll update the references.

On Wed, 24 Sep 2014 07:45:03 -0700, Edward Burns <edward.burns@...> said:
EB> Hello Volunteers,
EB> This message is sent to all members of servlet-spec, including
EB> observers, but this message is really intended for Expert Group members.
EB> Note that only JCP Expert Group (EG) members may subscribe to
EB> jsr369-experts, and therefore only EG members may post to this list.

EB> Introduction

EB> Hello and welcome to the JSR-369 Expert Group for developing version
EB> 4.0 of the Servlet specification. If you're a veteran of past Servlet
EB> JSRs, thanks for coming back again, we're very glad to have you. If
EB> you're new to Servlet spec development, welcome! We look forward to
EB> more fresh ideas. My name is Ed Burns. Shing-wai Chan and I will be
EB> your co-spec leads for this JSR.

EB> Goals

EB> As stated on our JSR [1], the primary goal of this JSR is to expose
EB> support for the upcoming IETF standard HTTP/2 to users of the Servlet
EB> API. A secondary goal is to refresh the Servlet API with to achieve
EB> compliance with new features in HTTP 1.1 as well as responding to
EB> community input. The


EB> list will be used for technical discussions in JSR-369.

EB> Getting to know each other

EB> I know some of you from previous JSRs, but others are new. I'd like
EB> for everyone to share their


EB> user name. If you don't have
EB> one, please get one. We'll add everyone to the servlet-spec project.
EB> Please reply to this email, including where you live, who you
EB> represent, anything else you'd like to say and, optionally, a picture
EB> or a link to a picture of yourself.

EB> Platform

EB> Servlet 4.0 is included in the the Java EE 8 platform schedule and
EB> will depend on Java EE 8 and JavaSE 8.

EB> Rights and Responsibilities

EB> Based on lessons we've learned from past JSRs, we think it would be
EB> useful to lay out some rights and responsibilites of the JSR-369 Spec
EB> Lead and EG members.

EB> * Your rights as a JSR-369-EG member

EB> - Timely response to emails

EB> - The issues you raise get dealt with and not fall on the floor

EB> - Be informed of schedule milestones and release plans as soon as
EB> possible.

EB> - Have expectations set realistically, for example, the EG needs to
EB> be made aware that the JCP process can take a long time between
EB> when the actual spec discussion work is done, and when it is
EB> final. During that time, we are going through JCP process steps,
EB> working on the TCK and polishing the RI, writing the
EB> documentation, integrating it into the release vehicle, and
EB> qualifying it with third party products.

EB> - Have access to quality tools for distributed collaborative
EB> development. For example, the issue tracker, wiki, and shared
EB> file space at


EB> * Your responsibilities as an EG Member

EB> - Be active in email discussions

EB> - On the rare occasions when we specifically ask for a VOTE, such
EB> as whether or not we declare that we've hit a JCP milestone, cast
EB> one.

EB> - Conduct all email in a professional manner, no flaming

EB> - Follow email discussion guidelines in this message

EB> - Stay within the scope of the JSR

EB> - Respect the spec lead's final call on the schedule for the JSR.

EB> * Our rights as spec leads

EB> - The authority to make the final call on the schedule for the JSR,
EB> after sincerely considering EG input

EB> - The authority to make executive decisions to settle deadlocks

EB> - The authority to shut down threads that are digressions.

EB> - The authority to break up email messages into separate threads to
EB> aid discussion.

EB> * Our responsiblities as spec leads

EB> - All new discussion threads receive a response within two days
EB> from Shing-wai or I, barring planned absences.

EB> - All discussion threads managed. If appropriate, they are
EB> associated with an issue-tracker issue.

EB> - See that each discussion thread is summarized and labeled as
EB> CLOSED when the discussion is resolved.

EB> - Keep the spec document up-to-date as issues are resolved

EB> Process

EB> All official spec discussion will happen on


EB> This list is archived at [2]. We used the archive heavily in past
EB> JSRs, so please test that you can access the archive.

EB> Please send all mail in ASCII, not HTML. If you must, non ASCII
EB> attachments are ok, but generally it's better to put that sort of
EB> thing as an attachment to an issue in the issue-tracker.

EB> As mentioned above, everyone needs a


EB> user id. We'll be using the servlet-spec [3] project. We'll use
EB> the servlet-spec issue tracker for all issues [4].

EB> We may have occasional conference calls if the need arises.

EB> Reference Implementation and TCK

EB> The official reference implementation for JSR-369 is being developed
EB> out in the open on the


EB> project called glassfish. The TCK
EB> will be developed by Oracle internally.

EB> Email practices

EB> We will use the following conventions, used in previous iterations of
EB> the JavaServer Faces expert groups.

EB> The subject line of All core discussion threads will be prefixed by
EB> [jsr369-experts][TargetVersion-IssueNumber-ShortName].
EB> TargetVersion is optional and is assumed to be Servletv4.0 if
EB> omitted. Having this convention covers us if we end up talking
EB> about something targeted at Servletv4.1. IssueNumber is the issue
EB> number in the servlet-spec issue tracker. ShortName is a WikiWord
EB> that enables us to look at the email subject line and quickly recall
EB> the topic of the thread. For example, Subject: "[43-XMLSchema]
EB> Status"

EB> If you want to originate a thread, send it to the EG prefixed by
EB> [NEW] in the subject line. If we see the need for an issue tracker
EB> issue, we'll put it in the issue tracker, re-subject the email to be
EB> prefixed with [IssueNumber-ShortName], and discussion will continue
EB> on that thread, NOT the thread with [NEW] in the title.

EB> Put [ADMIN] at the start of the subject line for all schedule and
EB> administrative related emails.

EB> I am open to other suggestions about how to best conduct the EG
EB> discussions over email.

EB> Next Steps

EB> As you may know, next week is JavaOne 2014. Shing-wai and I are
EB> attending, as well as Greg Wilkins.

EB> We are having a face-to-face meeting, with conference call as well,
EB> the first day of JavaOne. It is a shared meeting with the JSF EG.

EB> Date: Monday 29 September 2014

EB> Time:

EB> 14:00 San Francisco

EB> 17:00 New York

EB> 23:00 Vienna

EB> Phone number:

EB> +1 866 682 4770

EB> Conference code: 7821409

EB> Access code: 2323

EB> If you are calling in from a country other than the U.S.A., please
EB> reply to me only with the country you will be calling from and I'll
EB> hopefully have a toll-free number for you in that country.

EB> Again, welcome, and we look forward to collaborating in the coming
EB> months!

[1] http://www.jcp.org/en/jsr/detail?id=369

[2] https://javaee.groups.io/g/servlet-spec/

[3] https://github.com/javaee/servlet-spec/

[4] https://github.com/javaee/servlet-spec/issues/

| edward.burns@... | office: +1 407 458 0017