<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
DA> We certainly don't need both <a href="mailto:jsr-314-eg@jcp.org">jsr-314-eg@jcp.org</a> and<br>
DA> <a href="mailto:jsr-314-observers@jcp.org">jsr-314-observers@jcp.org</a>.<br>
<br>
I don't know about that, but I do know we need <a href="mailto:jsr-314-eg@jcp.org">jsr-314-eg@jcp.org</a> to be<br>
an EG private email list. Contractual discussions regarding licenses<br>
and other topics that vendors feel sensitive about discussing openly<br>
need a place to happen. <a href="mailto:jsr-314-eg@jcp.org">jsr-314-eg@jcp.org</a> has been and will continue<br>
to be that place.<br></blockquote><div><br>Ah. I see. That makes sense. So to revise my statement, we don't need it for API discussions ;)<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Thanks for scratching your itch on this Dan. Your advocacy for<br>
open-ness fits in with the continuing push of JCP to be more open.<br></blockquote><div><br>:)<br> </div></div>-Dan<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://wwwgoogle.com/profiles/dan.j.allen</a><br>