I concur. I don't think we should be already forking ;-)
Eventually, I do agree that several aliases will make sense but I can't
say we are there yet.
Outside of the noise level, I think there is a value in understanding
what others are doing as well, we are sometimes acting too boxed within
each technology. With Thread aware email clients, it's easy to kill
entire conversations that are of no interest to me, so I think I can
manage noise for quite some time.
For instance we could request that people put some technology
information in the subject line of the email like :
persistence - team meeting notes
deployment - performance improved 30%, what's next ?
webservices - soap handlers processing order
that way, folks can create filters that will just achieve the same
effect than multiple email aliases yet providing the ability to share or
control for the time being.
Jerome
Jim Driscoll wrote:
> I'm still uneasy about creating a lot of mail aliases when the one we
> have doesn't get much traffic.
>
> But I seem to be outnumbered on this, so I'm backing away from the idea.
>
> I'd love to hear what others think.
>
> Jim
>
> Carla Mott wrote:
>> Last week I created a new email alias persistence_at_glasfish.dev.java.net
>> for the persistence team. They will have technical discussions about
>> CMP and entity-persistence on that alias. More to come later.
>>
>> Note that for at least the time being I have added this alias to get the
>> digest format of the persistence mails so people can see what is
>> going on.
>> I expect that the emails will be forwarded for a couple of weeks.
>>
>> I plan on continuing this practice when additional aliases are created.
>>
>> Comments?
>>
>> Carla
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>