ANNOUCEMENT: new mailing list: commons-process@jakarta.apache.org

[Sam Ruby <ru...@us.ibm.com>]

All current subscribers to commons-dev are subscribed.  The moderator is
the same (Craig).

I'd like to suggest that all mail not specifically related to code issues
move over to this new list.  Any issues about how fine the line is between
code issues and non-code issues should move to the new list.  Any
discussion about how (in)appropriate my creating this new mailing list
should move to the new list.

- Sam Ruby

Re: ANNOUCEMENT: new mailing list: commons-process@jakarta.apache.org

[Ted Husted <hu...@apache.org>]

Let's either just open a USER list, or call this one DISCUSS, and say
it's where you can discuss proposals before opening a VOTE thread on the
DEV list. 

All VOTE threads must still happen on the DEV list. 

-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Java Web Development with Struts.
-- Tel +1 585 737-3463.
-- Web http://www.husted.com/struts/


Sam Ruby wrote:
> 
> All current subscribers to commons-dev are subscribed.  The moderator is
> the same (Craig).
> 
> I'd like to suggest that all mail not specifically related to code issues
> move over to this new list.  Any issues about how fine the line is between
> code issues and non-code issues should move to the new list.  Any
> discussion about how (in)appropriate my creating this new mailing list
> should move to the new list.
> 
> - Sam Ruby

Re: ANNOUCEMENT: new mailing list: commons-process@jakarta.apache.org

[Morgan Delagrange <md...@yahoo.com>]

+0, works for me.  I suspect that roughly 98.5% of dev users will subscribe
here too (including Ted ;), but it doesn't hurt to have a "tune-out" option.
(I also suspect that many "process" threads will still show up on dev, but
what can you do?)  You will, of course, post a link to this list on
http://jakarta.apache.org/site/mail2.html for new subscribers?

- Morgan


----- Original Message -----
From: "Sam Ruby" <ru...@us.ibm.com>
To: <co...@jakarta.apache.org>
Sent: Monday, February 04, 2002 6:24 AM
Subject: ANNOUCEMENT: new mailing list: commons-process@jakarta.apache.org


> All current subscribers to commons-dev are subscribed.  The moderator is
> the same (Craig).
>
> I'd like to suggest that all mail not specifically related to code issues
> move over to this new list.  Any issues about how fine the line is between
> code issues and non-code issues should move to the new list.  Any
> discussion about how (in)appropriate my creating this new mailing list
> should move to the new list.
>
> - Sam Ruby


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

RE: [PROPOSAL] Commons USER list?

[Paulo Gaspar <pa...@krankikom.de>]

This is OT.
It belongs to the "process" list.
=;o)

Paulo

> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org]
> Sent: Monday, February 04, 2002 1:39 PM
> To: commons-dev@jakarta.apache.org
> Subject: [PROPOSAL] Commons USER list?
>
>
> [ANNOUCEMENT: new mailing list: commons-process@jakarta.apache.org]
>
> In related news, I was wondering if might be time for a Commons-USER
> list.
>
> Is a DEV list enough right now?
>
> Or do we have sufficient product out there now, that we need a place
> where Users can subscribe and ask questions without sorting through the
> DEV discussions?
>
> Case in point, I just had someone post a Digester question to the Struts
> DEV list, since they thought their message might get lost in the Commons
> DEV traffic.
>
> Thoughts?
>
> -Ted.
>
> Sam Ruby wrote:
> >
> > All current subscribers to commons-dev are subscribed.  The moderator is
> > the same (Craig).
> >
> > I'd like to suggest that all mail not specifically related to
> code issues
> > move over to this new list.  Any issues about how fine the line
> is between
> > code issues and non-code issues should move to the new list.  Any
> > discussion about how (in)appropriate my creating this new mailing list
> > should move to the new list.
> >
> > - Sam Ruby
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

[PROPOSAL] Commons USER list?

[Ted Husted <hu...@apache.org>]

[ANNOUCEMENT: new mailing list: commons-process@jakarta.apache.org]

In related news, I was wondering if might be time for a Commons-USER
list. 

Is a DEV list enough right now? 

Or do we have sufficient product out there now, that we need a place
where Users can subscribe and ask questions without sorting through the
DEV discussions?

Case in point, I just had someone post a Digester question to the Struts
DEV list, since they thought their message might get lost in the Commons
DEV traffic.

Thoughts?

-Ted.

Sam Ruby wrote:
> 
> All current subscribers to commons-dev are subscribed.  The moderator is
> the same (Craig).
> 
> I'd like to suggest that all mail not specifically related to code issues
> move over to this new list.  Any issues about how fine the line is between
> code issues and non-code issues should move to the new list.  Any
> discussion about how (in)appropriate my creating this new mailing list
> should move to the new list.
> 
> - Sam Ruby

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: ANNOUCEMENT: new mailing list: commons-process@jakarta.apache.org

[Paulo Gaspar <pa...@krankikom.de>]

Cool!
Lets give noise its own place!
=;o)


have fun,
Paulo

> -----Original Message-----
> From: Sam Ruby [mailto:rubys@us.ibm.com]
> Sent: Monday, February 04, 2002 1:25 PM
> To: commons-process@jakarta.apache.org
> Subject: ANNOUCEMENT: new mailing list:
> commons-process@jakarta.apache.org
>
>
> All current subscribers to commons-dev are subscribed.  The moderator is
> the same (Craig).
>
> I'd like to suggest that all mail not specifically related to code issues
> move over to this new list.  Any issues about how fine the line is between
> code issues and non-code issues should move to the new list.  Any
> discussion about how (in)appropriate my creating this new mailing list
> should move to the new list.
>
> - Sam Ruby
>