I've put this on the wiki for handy reference: <a href="http://wiki.jcp.org/wiki/index.php?page=JSR-314+Mailinglist+Guidelines">http://wiki.jcp.org/wiki/index.php?page=JSR-314+Mailinglist+Guidelines</a> (you can find it by navigating the wiki)<br>
<br>I've taken some liberty in updating the conventions. Please feel free to revise until we get something that we'll all stick to.<br><br>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.<br>
<br>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.<br>
<br>I'm sure in time we'll settle into a nice groove.<br><br>-Dan<br><br><div class="gmail_quote">On Mon, Dec 7, 2009 at 1:19 PM, Ed Burns <span dir="ltr"><<a href="mailto:Ed.Burns@sun.com">Ed.Burns@sun.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Rather than copy and paste the whole email, which may be found at [0],<br>
I'm only including the bit about our email process.<br>
<br>
EB> Please send all mail in ASCII, not HTML. If you must, non ASCII<br>
EB> attachments are ok, but generally it's better to put that sort of<br>
EB> thing as an attachment to an issue in the issue-tracker.<br>
<br>
EB> As mentioned above, everyone needs a <a href="http://java.net" target="_blank">java.net</a> user id. We'll be using<br>
EB> the javaserverfaces-spec-public [5] and javaserverfaces-spec-eg [6]<br>
EB> projects. In the spirit of JCP 2.6, we intend to use the former more<br>
EB> than the latter, since the latter is private to EG members only.<br>
EB> We'll use the javaserverfaces-spec-public issue tracker for all<br>
EB> issues. Generally only the spec leads will be submitting issues here,<br>
EB> but you may be asked to submit one yourself for expedience. We'll use<br>
EB> the javaserverfaces-spec-eg issue tracker to host the development of<br>
EB> the spec document itself.<br>
<br>
EB> We may have occasional conference calls if the need arises.<br>
<br>
EB> Reference Implementation and TCK<br>
<br>
EB> The official reference implementation for JSR-314 is being developed<br>
EB> out in the open on the <a href="http://java.net" target="_blank">java.net</a> project called javaserverfaces.<br>
EB> Please let us know if you have a problem with this practice. The TCK<br>
EB> will be developed by Sun internally.<br>
<br>
EB> Email practices<br>
<br>
EB> During JSR-127, we used the following conventions, and they seemed<br>
EB> to work reasonably well, especially for the purposes of looking back<br>
EB> over the archive.<br>
<br>
EB> The subject line of All core discussion threads will be prefixed<br>
EB> by [TargetVersion-IssueNumber-ShortName]. TargetVersion is<br>
EB> optional and is assumed to be JSFv2.0 if omitted. Having this<br>
EB> convention covers us if we end up talking about something targeted<br>
EB> at JSFv2.1 or 3.0. IssueNumber is the issue number in the<br>
EB> javaserverfaces-spec-public issue tracker. If we need to refer to<br>
EB> an issue in the EG private tracker, prefix the number with "EG".<br>
EB> ShortName is a WikiWord that enables us to look at the email<br>
EB> subject line and quickly recall the topic of the thread. For<br>
EB> example, Subject: "[43-XMLSchema] Status"<br>
<br>
<br>
EB> If you want to originate a thread, send it to the EG prefixed by<br>
EB> [NEW] in the subject line. If the spec lead sees the need for an<br>
EB> issue tracker issue, we'll put it in the issue tracker, re-subject<br>
EB> the email to be prefixed with [IssueNumber-ShortName], and<br>
EB> discussion will continue on that thread, NOT the thread with [NEW]<br>
EB> in the title.<br>
<br>
EB> Put [ADMIN] at the start of the subject line for all schedule and<br>
EB> administrative related emails (such as this one).<br>
<br>
<br>
[0] <a href="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" target="_blank">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</a><br>
<br>
EB> [1] <a href="http://www.jcp.org/en/jsr/detail?id=314" target="_blank">http://www.jcp.org/en/jsr/detail?id=314</a><br>
<br>
EB> [2] <a href="http://wiki.java.net/bin/view/Projects/Jsf2RequirementsScratchpad" target="_blank">http://wiki.java.net/bin/view/Projects/Jsf2RequirementsScratchpad</a><br>
<br>
EB> [3] <a href="http://wiki.java.net/bin/view/Projects/Jsf2Requirements" target="_blank">http://wiki.java.net/bin/view/Projects/Jsf2Requirements</a><br>
<br>
EB> [4] <a href="http://archives.java.sun.com/jsr-314-eg.html" target="_blank">http://archives.java.sun.com/jsr-314-eg.html</a><br>
<br>
EB> The archive for the open list is<br>
EB> <a href="http://archives.java.sun.com/jsr-314-open.html" target="_blank">http://archives.java.sun.com/jsr-314-open.html</a>, though it appears to not<br>
EB> be working yet.<br>
<br>
And it appears not to be working again! Dan's working on it.<br>
<br>
EB> [5] <a href="https://javaserverfaces-spec-public.dev.java.net/" target="_blank">https://javaserverfaces-spec-public.dev.java.net/</a><br>
<br>
EB> [6] <a href="https://javaserverfaces-spec-eg.dev.java.net/" target="_blank">https://javaserverfaces-spec-eg.dev.java.net/</a><br>
<font color="#888888"><br>
--<br>
| <a href="mailto:ed.burns@sun.com">ed.burns@sun.com</a> | office: 408 884 9519 OR x31640<br>
| homepage: | <a href="http://ridingthecrest.com/" target="_blank">http://ridingthecrest.com/</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>