Keeping pear-core mailing list?

[Christian Weiske]

Hi all,


As many of you probably know do we have two cvs mailing lists: pear-cvs
and pear-core. Commits to pear-core, pearweb, and pear2 go to both
lists.
That's a bit annoying to me and I would like to change that. Should we
drop pear-core and rely on pear-cvs only? As far as I know, pear-core
has been used for discussion about pear installer internals, but today
pear-dev is and should be used since it's low traffic.

What do you guys think? Drop pear-core? Limit it to pear-core only and
do not send pear2 and pearweb to it?

--
Regards/Mit freundlichen Grüßen
Christian Weiske

-= Geeking around in the name of science since 1982 =-

[Ken Guest]

On Sat, Aug 15, 2009 at 11:31 AM, Christian Weiske <cweiske@...>wrote:

> Hi all,
>
>
> As many of you probably know do we have two cvs mailing lists: pear-cvs
> and pear-core. Commits to pear-core, pearweb, and pear2 go to both
> lists.
> That's a bit annoying to me and I would like to change that. Should we
> drop pear-core and rely on pear-cvs only? As far as I know, pear-core
> has been used for discussion about pear installer internals, but today
> pear-dev is and should be used since it's low traffic.
>
> What do you guys think? Drop pear-core? Limit it to pear-core only and
> do not send pear2 and pearweb to it?

I don't see much point in having two seperate mailing lists.

just my 2c worth


Ken



--
http://blogs.linux.ie/kenguest/

[Brett Bieber]

On Sat, Aug 15, 2009 at 9:34 AM, Ken Guest<ken@...> wrote:

> On Sat, Aug 15, 2009 at 11:31 AM, Christian Weiske <cweiske@...>wrote:
>
>> Hi all,
>>
>>
>> As many of you probably know do we have two cvs mailing lists: pear-cvs
>> and pear-core. Commits to pear-core, pearweb, and pear2 go to both
>> lists.
>> That's a bit annoying to me and I would like to change that. Should we
>> drop pear-core and rely on pear-cvs only? As far as I know, pear-core
>> has been used for discussion about pear installer internals, but today
>> pear-dev is and should be used since it's low traffic.
>>
>> What do you guys think? Drop pear-core? Limit it to pear-core only and
>> do not send pear2 and pearweb to it?

I definitely don't think they need to go to both lists, but I like
that they have a separate purpose. Pyrus, pear-core, and pearweb have
a separate audience, if we could target those commits to the correct
list, I think that would be good.

I'd prefer to get immediate commit emails for the core elements, and
digests for general pear package commits, so two lists would be more
flexible for me.

--
Brett Bieber

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[Igor Feghali-4]

my opinion: drop pear-core (move it to pear-dev) and rename pear-cvs
to something more general such as pear-commits / pear-tracking /
pear-activity / etc.

--
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php