[jsr-314-open] [ADMIN] Resend of JSR-314 EG email practice

[Dan Allen]

I've put this on the wiki for handy reference:
http://wiki.jcp.org/wiki/index.php?page=JSR-314+Mailinglist+Guidelines (you
can find it by navigating the wiki)

I've taken some liberty in updating the conventions. Please feel free to
revise until we get something that we'll all stick to.

Personally, I don't see a need for all uppercase prefix tags. It's annoying
to type and uppercase is equivalent to yelling online. So I've suggested
lowercase prefixes like [admin], [community], etc.

As for a new idea, I've never liked the [NEW] prefix because all e-mails are
new by nature. Instead, the prefix should suggest the target version. For
instance, [jsf2next] or [jsf3next]. I'm kind of sticking to the twitter
hashtag that we have blasted out about since it's already out there. Again,
feel free to challenge.

I'm sure in time we'll settle into a nice groove.

-Dan

On Mon, Dec 7, 2009 at 1:19 PM, Ed Burns <Ed.Burns at sun.com> wrote:

> Rather than copy and paste the whole email, which may be found at [0],
> I'm only including the bit about our email process.
>
> 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 java.net user id.  We'll be
> using
> EB>   the javaserverfaces-spec-public [5] and javaserverfaces-spec-eg [6]
> EB>   projects.  In the spirit of JCP 2.6, we intend to use the former more
> EB>   than the latter, since the latter is private to EG members only.
> EB>   We'll use the javaserverfaces-spec-public issue tracker for all
> EB>   issues.  Generally only the spec leads will be submitting issues
> here,
> EB>   but you may be asked to submit one yourself for expedience.  We'll
> use
> EB>   the javaserverfaces-spec-eg issue tracker to host the development of
> EB>   the spec document itself.
>
> EB>   We may have occasional conference calls if the need arises.
>
> EB> Reference Implementation and TCK
>
> EB>   The official reference implementation for JSR-314 is being developed
> EB>   out in the open on the java.net project called javaserverfaces.
> EB>   Please let us know if you have a problem with this practice.  The TCK
> EB>   will be developed by Sun internally.
>
> EB> Email practices
>
> EB>   During JSR-127, we used the following conventions, and they seemed
> EB>   to work reasonably well, especially for the purposes of looking back
> EB>   over the archive.
>
> EB>     The subject line of All core discussion threads will be prefixed
> EB>     by [TargetVersion-IssueNumber-ShortName].  TargetVersion is
> EB>     optional and is assumed to be JSFv2.0 if omitted.  Having this
> EB>     convention covers us if we end up talking about something targeted
> EB>     at JSFv2.1 or 3.0.  IssueNumber is the issue number in the
> EB>     javaserverfaces-spec-public issue tracker.  If we need to refer to
> EB>     an issue in the EG private tracker, prefix the number with "EG".
> EB>     ShortName is a WikiWord that enables us to look at the email
> EB>     subject line and quickly recall the topic of the thread.  For
> EB>     example, Subject: "[43-XMLSchema] Status"
>
>
> EB>     If you want to originate a thread, send it to the EG prefixed by
> EB>     [NEW] in the subject line.  If the spec lead sees the need for an
> EB>     issue tracker issue, we'll put it in the issue tracker, re-subject
> EB>     the email to be prefixed with [IssueNumber-ShortName], and
> EB>     discussion will continue on that thread, NOT the thread with [NEW]
> EB>     in the title.
>
> EB>     Put [ADMIN] at the start of the subject line for all schedule and
> EB>     administrative related emails (such as this one).
>
>
> [0]
> http://archives.java.sun.com/cgi-bin/wa?A2=ind0903&L=JSR-314-OPEN&T=0&O=D&X=325AB10E911B3CEECF&Y=ed.burns%40sun.com&P=163
>
> EB>   [1] http://www.jcp.org/en/jsr/detail?id=314
>
> EB>   [2]
> http://wiki.java.net/bin/view/Projects/Jsf2RequirementsScratchpad
>
> EB>   [3] http://wiki.java.net/bin/view/Projects/Jsf2Requirements
>
> EB>   [4] http://archives.java.sun.com/jsr-314-eg.html
>
> EB> The archive for the open list is
> EB> http://archives.java.sun.com/jsr-314-open.html, though it appears to
> not
> EB> be working yet.
>
> And it appears not to be working again!  Dan's working on it.
>
> EB>   [5] https://javaserverfaces-spec-public.dev.java.net/
>
> EB>   [6] https://javaserverfaces-spec-eg.dev.java.net/
>
> --
> | ed.burns at sun.com  | office: 408 884 9519 OR x31640
> | homepage:         | http://ridingthecrest.com/
>



-- 
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jsr-314-open-mirror/attachments/20091210/a49e7f5b/attachment.html