<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.1">
</HEAD>
<BODY>
Dan, did you file an issue for this already, or should I?<BR>
<BR>
PS. I personally prefer uppercase [JSF2.NEXT] for aesthetic reasons, but that's harder to type on smart-phones.<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
---<BR>
Lincoln Baxter, III<BR>
<A HREF="http://ocpsoft.com">http://ocpsoft.com</A><BR>
<A HREF="http://scrumshark.com">http://scrumshark.com</A><BR>
"Keep it Simple" <BR>
<BR>
</TD>
</TR>
</TABLE>
On Thu, 2009-12-10 at 13:52 -0500, Dan Allen wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
DA> As a side note, I like the subject filter [JSF2.NEXT] for forward-looking<BR>
DA> issues. It keeps it open (JSF 2.1 only works until JSF 2.1 is out). Plus, it<BR>
DA> matches our twitter hash tag #jsf2next ;)<BR>
<BR>
Heck, we should just use #jsf2next as the header. Twitter didn't exist<BR>
when the email subject guidelines were written!
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
How about just [jsf2next]<BR>
<BR>
Easy to write an e-mail filter for that.<BR>
<BR>
Perhaps we can set up some other new conventions.<BR>
<BR>
[community] - stuff related to the community site, or just the community outreach in general<BR>
[admin] - I think this is already in place, but for admin related issues like mailinglist problems<BR>
...<BR>
<BR>
-Dan<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<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>
</BLOCKQUOTE>
</BODY>
</HTML>