Andy,
Personally, I much prefer (2) as well. I think the distinction you
describe is a good thing, and I also think it makes mail organization
easier.
On 19 Apr 2009, at 15:06, Andy Schwartz wrote:
Hi Ed -
As discussed in the "Open Community Feedback List?" thread, I am
very much in favor of opening up the way in which the community
provides feedback. It seems like we've got two options for how to
do this:
1. Forward emails from jsr-314-comments to jsr-314-open.
2. Open up jsr-314-comments (ie. make jsr-314-comments read/write/
archived for the world).
#2 maintains some separation between EG communications and EG
+community communications. #1 blurs the lines a bit more than #2 -
ie. #1 is somewhat closer to making jsr-314-open truly open/writable
to the world. Anyone can send email to jsr-314-open - just that
some folks use a different alias. Perhaps eliminating the
separation is a good thing.
I don't have a strong sense for which of these two options would
work better in practice. Dan - I know you have spent more time
thinking this through than I have. Can you comment on how you view
#1 vs #2? Do you have a strong preference for #1?
I definitely prefer either of these options over our current
situation. Just would like to hear more thoughts on the trade-offs
between these options. Oh, and, I am only speculating that #2 is
actually a valid option. If it is not, then, yes, I definitely
support #1.
Andy
Ed Burns wrote On 4/19/2009 2:01 AM ET:
> Since at least 2004, the JCP jsr-XXX-comments(a)jcp.org email lists
> set up
> by the JCP go to the spec leads. Spec leads may then send such
> comments
> on to the EG at their discretion.
> Dan Allen suggests we change this arrangement and have
> jsr-314-comments(a)jcp.org go straight to the jsr-314-open(a)jcp.org
> list.
> Personally, I favor the existing arrangement but will go with the
> prevalent opinion. Thoughts?
>
> Ed
>
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete