public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fred Van Andel <fred@vanandel.net>
To: Mike Frysinger <vapier@gentoo.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] A proposal for discussion
Date: Sun, 29 Sep 2002 22:37:21 -0700	[thread overview]
Message-ID: <5.1.0.14.0.20020929221420.020719e0@192.168.0.1> (raw)
In-Reply-To: <200209300008.51711.vapier@gentoo.org>

At 12:08 AM 9/30/02 -0400, Mike Frysinger wrote:
>i would have to disagree on this ...
>running a todo list is kind of out of scope of opening public access to the
>-core list.  plus, turning -core into the center of todo operations is outside
>the scode of the -core list.
>discussions that happen on -core are meant for the 'core' of Gentoo.
>also, as we've seen in the past, some topics that are discussed on -core
>can lead to an explosion of misguided discussions.
>-mike


I must agree. The openness of the -core list is unrelated to a todo list 
and should be considered as a separate issue.

The person who maintains to todo list must have to support/guidance of the 
core developers and should have access to the -core list to ensure that the 
todo list does not conflict with the direction that -core is going.  The 
obvious way to accomplish this would be to have one of the core members 
maintain the todo list.  This is exactly the type of non-technical routine 
work that the todo list is designed to off load from the core group. Only 
the core developers can decide what direction that they want to go on that one.

Fred Van Andel



      reply	other threads:[~2002-09-30  5:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 22:13 [gentoo-dev] A proposal for discussion Fred Van Andel
2002-09-28 13:19 ` Alan
2002-09-28 14:14 ` Mark Bainter
2002-09-30  4:12 ` k
2002-09-30  4:08   ` Mike Frysinger
2002-09-30  5:37     ` Fred Van Andel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.1.0.14.0.20020929221420.020719e0@192.168.0.1 \
    --to=fred@vanandel.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=vapier@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox