<div class="gmail_quote">On Fri, Nov 5, 2010 at 7:18 AM, Andy Schwartz <span dir="ltr"><<a href="mailto:andy.schwartz@oracle.com">andy.schwartz@oracle.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><br></div></div>
Dan's mission, before the expert group was disbanded, was to get all of these archives, including the threads from the missing periods:<br></blockquote><div><br></div><div>Somewhere in my long list of missions, it's still in there :)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
1. Online. And...<br>
2. Accessible without login.<br>
<br>
I still think that this is a very critical goal for JSF.<br></blockquote><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
While I am grateful for the effort that JBoss has made in making the latest archives available on <a href="http://lists.jboss.org" target="_blank">lists.jboss.org</a> - and I have been taking full advantage of the ability to share these publicly accessible links - this looks like a stop-gap measure to me. It's been over a year since we first reported the problems with our archives to the JCP. We need the JCP to finally come through and provide a more formal solution.<br>
<font class="Apple-style-span" color="#888888"><br></font></blockquote><div>Absolutely. That's why I'm still so confused when I read statements like this on made by Eduardo:</div><div><br></div><div>"Some things you are asking already exist. For example, open mailing lists are totally OK with the current JCP process – although I know the infrastructure support for some of this is not where it should be." [1]</div>
<div><br></div><div>Not where it should be? I think it's pretty clear that the infrastructure for an open mailing list is pretty much non-existent. We *are* the expert group (or were) and we can't even make this happen.</div>
<div><br></div><div>The JCP has their own promises to worry about. I'm just trying to deliver on our promise. Every message sent to <a href="mailto:jsr-314-open@jcp.org">jsr-314-open@jcp.org</a> should be available to the public and in one place.</div>
<div><br></div><div>-Dan</div><div><br></div><div>[1] <a href="http://ocpsoft.com/opensource/open-letter-to-the-jcp-executive-committee-calling-for-jcp-reform/#comment-2018">http://ocpsoft.com/opensource/open-letter-to-the-jcp-executive-committee-calling-for-jcp-reform/#comment-2018</a></div>
<div><br></div></div>-- <br>Dan Allen<br>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen" target="_blank">http://www.google.com/profiles/dan.j.allen</a><br>