[gentoo-council] Nuking this mailing lists

[gentoo-council] Nuking this mailing lists

[Petteri Räty]

What we currently have now:
1. gentoo-dev: technical issues
2. gentoo-project: non technical cross project issues
3. gentoo-council: supposedly council related things

Problems I see with this:
1. People are unsure where to post to and cross post to mailing lists in
order to reach more devs. The right way here is a single mailing list
and gentoo-dev-announce.
2. We have two relative low traffic mailing lists gentoo-project and
gentoo-council.
3. If we truly use gentoo-council for all council related matters it
splits cross project technical talk between gentoo-dev and gentoo-council.
4. The original point in creating gentoo-project / gentoo-dev-announce
was that people wouldn't have to receive discussion about technical
items if they wanted to. So technical items should stay on gentoo-dev
instead of floating elsewhere.
5. -council is probably not reaching as many developers as -dev so
technical issues might not get input. Granted this point can be helped
by using gentoo-dev-announce but then devs who only want to see the
decisions would see the initial discussion too.
6. A user not familiar with our mailing list setup might not find
-council to follow up important threads if they want to.

What I propose:
1. Use gentoo-dev for technical council related matters
2. Use gentoo-project for non technical council related matters
3. Use gentoo-dev-announce to start threads if deemed necessary but
moderators should be alert in order to not have too much of these
through -dev-announce.

Regards,
Petteri

Re: [gentoo-council] Nuking this mailing lists

[Luca Barbato]

Petteri Räty wrote:
> What I propose:
> 1. Use gentoo-dev for technical council related matters
> 2. Use gentoo-project for non technical council related matters
> 3. Use gentoo-dev-announce to start threads if deemed necessary but
> moderators should be alert in order to not have too much of these
> through -dev-announce.

I'd keep the council ml, I agree that there is some overlap, but
-project and -dev have a broader scope and much higher noise/signal ratio.

lu

-- 

Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero

Re: [gentoo-council] Nuking this mailing lists

[Ned Ludd]

On Tue, 2009-07-21 at 12:24 +0200, Luca Barbato wrote:
> Petteri Räty wrote:
> > What I propose:
> > 1. Use gentoo-dev for technical council related matters
> > 2. Use gentoo-project for non technical council related matters
> > 3. Use gentoo-dev-announce to start threads if deemed necessary but
> > moderators should be alert in order to not have too much of these
> > through -dev-announce.
> 
> I'd keep the council ml, I agree that there is some overlap, but
> -project and -dev have a broader scope and much higher noise/signal ratio.

I tend to agree with this also. 

The -council mailing list is one I'd like to see used for it's official
matters. If not simply for logs and historical tracking.

Re: [gentoo-council] Nuking this mailing lists

[Denis Dupeyron]

On Tue, Jul 21, 2009 at 8:01 PM, Ned Ludd<solar@gentoo.org> wrote:
> On Tue, 2009-07-21 at 12:24 +0200, Luca Barbato wrote:
>> Petteri Räty wrote:
>> > What I propose:
>> > 1. Use gentoo-dev for technical council related matters
>> > 2. Use gentoo-project for non technical council related matters
>> > 3. Use gentoo-dev-announce to start threads if deemed necessary but
>> > moderators should be alert in order to not have too much of these
>> > through -dev-announce.
>>
>> I'd keep the council ml, I agree that there is some overlap, but
>> -project and -dev have a broader scope and much higher noise/signal ratio.
>
> I tend to agree with this also.
>
> The -council mailing list is one I'd like to see used for it's official
> matters. If not simply for logs and historical tracking.

Although I think the gentoo-council mailing list makes sense, I don't
really mind where we post our ideas and discuss them. As long as we
agree and do discuss them.

What I care a lot about is that we only have one list. Not everything
will be purely technical or non-technical. Where do we draw the line?
In case of ambiguous topic most will just post at random, others will
tend to always post on the same list, and in the end we'll have to
read 2 lists to make sure we catch all what would have interested us
on only one of them. Not counting those who really don't care about
the council and will complain about our gibberish. So why bother?

So, whichever list it is I don't mind, but please make a decision
because I have stuff to push there.

Denis.