[gentoo-dev] Re: mailing lists

[gentoo-dev] Re: mailing lists

[Daniel Robbins]

On Fri, Aug 03, 2001 at 08:30:57PM -0600, Pete Gavin wrote:
> Hi,
> 
> I think this has been brought up before, but I think the gentoo-dev
> mailing list would be more helpful if we could split it up into
> something like gentoo-dev (for developer questions and discussion, no
> ebuild/package related stuff or non-developers allowed to post),
> gentoo-ebuild (for ebuild submittal and announcement, anyone can
> post), and gentoo-user (for everything else). Would this be alright?
> 
> Pete
> <alkaline@gentoo.org>

I will do it if I can get some kind of assurance from our developers that the
gentoo-ebuild and especially the gentoo-user mailing lists will be moderated by
at least some of the developers.  Dan Armak can handle a good amount of
gentoo-ebuild, but I really need someone who's willing to moderate gentoo-user.
A moderator for gentoo-dev would be nice too :)

Maybe you could ask on CVS over the weekend and see if anyone is interested
in moderating the mail lists.

Also, I'll be creating team mailing lists and the # Author: comment in all new
ebuilds will specify the team, i.e.: system@gentoo.org,
infrastructure@gentoo.org, etc.  It's too hard to track the specifc author
anyway; we'll just track the team.  It'll be up to the team to keep their own
internal organization for all the ebuilds that belong to them.  We'll probably
change the # Author: comment to # Maintainer: system@gentoo.org, for example.
This'll work for me.

I'm going to cc: this to gentoo-dev.

Best Regards,

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Re: mailing lists

[Daniel Robbins]

On Sat, Aug 04, 2001 at 02:49:44AM -0600, Daniel Robbins wrote:

> Maybe you could ask on CVS over the weekend and see if anyone is interested
> in moderating the mail lists.

Err.. that's ask on *IRC*.  Time to sleep... X)

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Re: mailing lists

[Dan Armak]

On Saturday 04 August 2001 11:49, you wrote:
> On Fri, Aug 03, 2001 at 08:30:57PM -0600, Pete Gavin wrote:
> > Hi,
> >
> > I think this has been brought up before, but I think the gentoo-dev
> > mailing list would be more helpful if we could split it up into
> > something like gentoo-dev (for developer questions and discussion, no
> > ebuild/package related stuff or non-developers allowed to post),
> > gentoo-ebuild (for ebuild submittal and announcement, anyone can
> > post), and gentoo-user (for everything else). Would this be alright?
> >
> > Pete
> > <alkaline@gentoo.org>
>
> I will do it if I can get some kind of assurance from our developers that
> the gentoo-ebuild and especially the gentoo-user mailing lists will be
> moderated by at least some of the developers.  Dan Armak can handle a good
> amount of gentoo-ebuild
Yes, I'm willing to become the official gentoo-ebuild moderator/handler.

> , but I really need someone who's willing to
> moderate gentoo-user. A moderator for gentoo-dev would be nice too :)
>
> Maybe you could ask on CVS over the weekend and see if anyone is interested
> in moderating the mail lists.
>
> Also, I'll be creating team mailing lists and the # Author: comment in all
> new ebuilds will specify the team, i.e.: system@gentoo.org,
> infrastructure@gentoo.org, etc.  It's too hard to track the specifc author
> anyway; we'll just track the team.  It'll be up to the team to keep their
> own internal organization for all the ebuilds that belong to them.  We'll
> probably change the # Author: comment to # Maintainer: system@gentoo.org,
> for example. This'll work for me.
>
> I'm going to cc: this to gentoo-dev.
>

So, from one public mailing list (gentoo-dev) we'll have:
-dev, -user, -ebuild: 3
-system, -desktop, -server, -tools, -infrastructure, -security: 6
plus the one-directional -announce and -cvs lists.

So they'll probably be pretty spare to begin with, but that's probably to the 
best. Certainly it will make discussions much more focused.

BTW, drobbins, what do you think about the propositions made in the 
"maintainership and commit policy" (was: xchat anomalies)?


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Re: mailing lists

[Dan Armak]

On Saturday 04 August 2001 11:49, you wrote:
> On Fri, Aug 03, 2001 at 08:30:57PM -0600, Pete Gavin wrote:
> > Hi,
> >
> > I think this has been brought up before, but I think the gentoo-dev
> > mailing list would be more helpful if we could split it up into
> > something like gentoo-dev (for developer questions and discussion, no
> > ebuild/package related stuff or non-developers allowed to post),
> > gentoo-ebuild (for ebuild submittal and announcement, anyone can
> > post), and gentoo-user (for everything else). Would this be alright?
> >
> > Pete
> > <alkaline@gentoo.org>
>
> I will do it if I can get some kind of assurance from our developers that
> the gentoo-ebuild and especially the gentoo-user mailing lists will be
> moderated by at least some of the developers.  Dan Armak can handle a good
> amount of gentoo-ebuild, but I really need someone who's willing to
> moderate gentoo-user. A moderator for gentoo-dev would be nice too :)
>
> Maybe you could ask on CVS over the weekend and see if anyone is interested
> in moderating the mail lists.
>
> Also, I'll be creating team mailing lists and the # Author: comment in all
> new ebuilds will specify the team, i.e.: system@gentoo.org,
> infrastructure@gentoo.org, etc.  It's too hard to track the specifc author
> anyway; we'll just track the team.  It'll be up to the team to keep their
> own internal organization for all the ebuilds that belong to them.  We'll
> probably change the # Author: comment to # Maintainer: system@gentoo.org,
> for example. This'll work for me.

How does this combine with the ebuild categories? After all it makes sense 
that e.g. the desktop team is resposible for kde-* and gnome-*. If a 
developer from another team adds an ebuild to these categories, should his 
team be named as maintainer? Should he transfer maintanence to a desktop 
developer? What about developers who are part of more than one team?


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Re: mailing lists

[Mikael Hallendal]

Hi!

> > I will do it if I can get some kind of assurance from our developers
> >that the gentoo-ebuild and especially the gentoo-user mailing lists
> >will be moderated by at least some of the developers.  Dan Armak can
> >handle a good amount of gentoo-ebuild, but I really need someone
> >who's willing to moderate gentoo-user. A moderator for gentoo-dev
> >would be nice too :)

What do you mean by moderate the list?
I think that all developers should listen to all three lists, perhaps
not everyone has to listen to -ebuild (would probably be enough with
one developer for each team).

> > Also, I'll be creating team mailing lists and the # Author: comment
> >in all new ebuilds will specify the team, i.e.: system@gentoo.org,
> >infrastructure@gentoo.org, etc.  It's too hard to track the specifc
> >author anyway; we'll just track the team.  It'll be up to the team to
> >keep their own internal organization for all the ebuilds that belong
> >to them.  We'll probably change the # Author: comment to #
> >Maintainer: system@gentoo.org, for example. This'll work for me.

This split is going to be needed in the future, but I don't see why it
needs to happend right now, this split can happend when it's needed.
I think that for now the -dev, -user and -ebuild will be enough.
 
> How does this combine with the ebuild categories? After all it makes
> sense that e.g. the desktop team is resposible for kde-* and
> gnome-*. If a developer from another team adds an ebuild to these
> categories, should his team be named as maintainer? Should he transfer
> maintanence to a desktop developer? What about developers who are part
> of more than one team?

We have to write down somewhere which teams will handle what
packages. 

But the maintaining team shouldn't have anything todo with who's
creating the ebuild. It should be the team into which the package
falls. This also solves the question about a developer part of more
then one team.

After all it's the team that is responsible to make the ebuild working
before a release. I also think that (as stated by pm in another
thread) when a developer is creating an ebuild that goes into another
team he should put it into incoming for the correct team to include
into the CVS tree.

Regards,
Mikael Hallendal

-- 
Mikael Hallendal                micke@codefactory.se
CodeFactory AB                  http://www.codefactory.se/
Office: +46 (0)8 587 583 05     Cell: +46 (0)709 718 918