commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Rall <...@finemaltcoding.com>
Subject Re: [PROPOSAL] Commons-USER, Commons-DISCUSS
Date Thu, 21 Feb 2002 02:21:37 GMT
"Sam Ruby" <rubys@us.ibm.com> writes:

> Ringo Desmet wrote:
> >
>> commons-commit
>> - CVS commit messages
>> - reply goes to commons-dev
>> - I don't need commit messages.
>
> Having the commit messages go to the developer's list gets more developers
> to participate in the reviews.  And has the side benefit of pushing people
> to use the -user's list.
>
>> commons-user
>> - usage of commons packages.
>>
>> I don't see a reason for commons-process. If the commit messages are on a
>> separate list, I can cope with the source and non-source discussions held on
>> commons-dev.I don't see a reason for commons-process. If the commit messages are
on a
>> separate list, I can cope with the source and non-source discussions held on
>> commons-dev.
>
> My two cents: you want to offload the wrong stuff off the -dev list.  A
> -user list could be very helpful.  Perhaps a -discuss or -process list is
> not required, but there certainly has been a lot of non-user and non-code
> related discussion lately.

+1, I agree.

Mime
View raw message