public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: Paul de Vrieze <pauldv@gentoo.org>
Cc: gentoo-core@gentoo.org, gentoo-dev@gentoo.org
Subject: [gentoo-dev] Portage features implementation
Date: Thu, 26 Jun 2003 12:41:38 -0600	[thread overview]
Message-ID: <20030626184138.GA7264@inventor.gentoo.org> (raw)
In-Reply-To: <200306262028.36599.pauldv@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]

On Thu, Jun 26, 2003 at 08:28:23PM +0200, Paul de Vrieze wrote:
> Personally I have only one issue that could be addressed. It concerns portage. 
> There are many features that portage will implement someday and that have 
> allready been identified. Many of those TODO's have been there a long time. 
> While I know that it is necessary to keep portage stable, and I know that 
> adding features is much work, I would like to know the status of those 
> features.

Me too :) In our existing management structure, you'll see that carpaski is
the operational manager for portage, and as such will be responsible for
providing weekly updates on the status of his project, just like all
managers will. These status updates will be publicly available and linked to
on our Web site. You'll also see that I specifically listed a "package
research" sub-project that will be involved in architecting new
functionality for Portage.

Also, if other projects or sub-projects need functionality in Portage, they
can inform their respective top-level managers about these needed features.
Then it's the the responsibility of that top-level manager to communicate these
needs to carpaski at the top-level manager meeting, and coordinating with
carpaski to find an agreeable and reasonable schedule for implementation.

This is how it is intended to work for all projects that have specific needs
from other projects. Your respective top-level manager should be your
ombudsman and work to get needed features on the roadmap of other projects.

I believe that this arrangement address all your concerns. Please let me
know if that's not the case, and anyone is welcome to chime in if they see
an opportunity to improve this process.

Best Regards,

-- 
Daniel Robbins
Chief Architect, Gentoo Linux
http://www.gentoo.org

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-26 18:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26  1:08 [gentoo-dev] FORK: The Time Is Now Zach Welch
2003-06-26  1:15 ` Matt Thrailkill
2003-06-26  1:25   ` Mike Frysinger
2003-06-26 13:10   ` Brad Laue
2003-06-26  4:02 ` [gentoo-dev] Re: [gentoo-core] " Daniel Robbins
2003-06-26  4:50   ` Joseph Hardin
2003-06-26 11:56   ` Peter Johanson
2003-06-26 12:28     ` Seemant Kulleen
2003-06-26 12:43       ` FRLinux
2003-06-26 13:07         ` Michael Cummings
2003-06-26 13:43         ` Philippe Lafoucrière
2003-06-26 14:08           ` Brad Laue
2003-06-26 14:11           ` foser
2003-06-26 15:10             ` [gentoo-dev] " Daniel Armyr
2003-06-26 16:46               ` [gentoo-dev] Growing Gentoo Daniel Robbins
2003-06-26 16:26             ` [gentoo-dev] FORK: The Time Is Now FRLinux
2003-06-26 19:23               ` Paul de Vrieze
2003-06-26 19:27                 ` FRLinux
2003-06-26 18:28       ` [gentoo-dev] Re: [gentoo-core] Re: [gentoo-dev] Re: [gentoo-core] " Paul de Vrieze
2003-06-26 18:41         ` Daniel Robbins [this message]
2003-06-26 21:22         ` Terje Kvernes
2003-06-26 12:41     ` Brad Laue

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=20030626184138.GA7264@inventor.gentoo.org \
    --to=drobbins@gentoo.org \
    --cc=gentoo-core@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=pauldv@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