<!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.26.0">
</HEAD>
<BODY>
I like this solution.<BR>
<BR>
I'd also like to see these lists, and how to subscribe to them posted publicly and in a way that is intuitive to find / execute.<BR>
<BR>
--Lincoln<BR>
<BR>
On Mon, 2009-09-21 at 14:16 -0400, Dan Allen wrote:
<BLOCKQUOTE TYPE=CITE>
On Fri, Sep 18, 2009 at 7:00 AM, Pete Muir <<A HREF="mailto:pmuir@redhat.com">pmuir@redhat.com</A>> wrote:
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
<BR>
On 18 Sep 2009, at 00:09, Dan Allen wrote:<BR>
<BR>
<BLOCKQUOTE>
Our first choice for request #1 is to allow all subscribed members of the jsr-314-open list to post, with moderation of a person's inaugural post (webbeans-dev uses this approach, for instance). The second choice would be to have a separate list open to the community. In either case, both lists should satisfy request #2.<BR>
</BLOCKQUOTE>
<BR>
<BR>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BLOCKQUOTE>
My preference would be for there to be two email lists, both with public, non-password-protected, archives. The first is the EG list. The second is the a discussion list. A regular member of the EG can post unmoderated to either list. Any subscriber can post to the discussion list. If a member of the community is an expert on a particular sub-topic, we should pull them into the EG list, using moderation to allow their posts through.
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
After considering the three alternatives presented here, I'm in favor of Pete's suggestion. It gives the community a place to speak more freely, without having to knock at the EG's door directly, so to speak.<BR>
<BR>
When we identify a community expert, we should say that we will "invite" them to the EG list, as hopefully they will see it as a priviledge and honor.<BR>
<BR>
The important point, though, is that a person does not necessarily have to be on the EG to be allowed to post to the EG list. Otherwise, we will just have too many people trying to be on the EG for no other reason than to post.<BR>
<BR>
-Dan<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<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>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
--<BR>
<B>Lincoln Baxter, III</B><BR>
Co-Founder of <A HREF="http://ocpsoft.com">OcpSoft</A><BR>
<BR>
Creator of:<BR>
<A HREF="http://ocpsoft.com/prettyfaces">PrettyFaces</A>: URL rewriting for JSF<BR>
<A HREF="http://ocpsoft.com/prettytime">PrettyTime</A>: Java elapsed timestamp formatting<BR>
<BR>
<BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>