Hi all,
FWIW: I am happy with either of these approaches, but also prefer #2.
I like the analogy to a users/dev list.
regards,
Martin
On 4/21/09, Dan Allen <dan.j.allen(a)gmail.com> wrote:
>
>
> 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.
>>
>
> Made me think that you must have had some reason in mind for preferring
> the
> forward approach (#1). Glad to hear that is not the case.
That's because at the time, my understanding was that having a separate list
was completely out of the question and #1 was better than burdening the spec
lead with constantly forwarding messages. I'm relieved that #2 is back on
the table because I believe it's really the best arrangement in terms of
effort, order, and allowing the community to be heard and affect change.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces