From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New project: Gentoo Seeds
Date: Wed, 20 Sep 2006 17:39:15 -0400 [thread overview]
Message-ID: <1158788356.23583.30.camel@sys947.dtic.mil> (raw)
In-Reply-To: <20060920212715.5e82c91d@snowdrop.home>
On Wed, 2006-09-20 at 21:27 +0100, Ciaran McCreesh wrote:
> On Wed, 20 Sep 2006 20:27:50 +0100 "Stuart Herbert"
> <stuart.herbert@gmail.com> wrote:
> | I was hoping to avoid having to say this - actually I was hoping to
> | avoid this whole drama - but we _don't_ need releng's approval to do
> | this. To delay progress, Chris will need to make a formal complaint
> | to the Council.
>
> I was under the impression that you were supposed to GLEP anything of
> this scope and get council approval... The "anyone can make a project"
> rule doesn't replace the requirement to GLEP large changes.
>
So far in this discussion, as an observer I haven't seen anyone mention
any "large changes." So far most of this discussion has been about the
concept. If the end result is a toolset for creating stage4's for
people, does that need a glep? Did we glep making livecd's the default
for x86 and a few other platforms (the ones that launch X, not just
bootable cd's with install tools)? I find a few of the concepts
intriguing enough to like the project, but since at this stage it isn't
in a position to be glepable (that's a word, i swear). if it moves
beyond the discussion phase and has usable stage4 scenarios (maybe it
does already, i'm just basing this on the thread here) then i think at
that point discussions should start with releng on whether this
something that should be made part of the release media cycle - but even
then, a glep?
nb. I was dealing with a box today that couldn't be updated for over a
year and a half. Being able to seed it up to a semi-current state and
toss a finger towards the ubuntu-fanatics in the office with their "we
just installed a new cd over the old install and it worked fine" would
be nice. so maybe i'm already biased in all of this.
nb2. maybe i'm also missing the point of parts of this discussion.
nb3. there is no nb3.
--
-----o()o----------------------------------------------
Michael Cummings | #gentoo-dev, #gentoo-perl
Gentoo Perl Dev | on irc.freenode.net
Gentoo/SPARC
Gentoo/AMD64
GPG: 0543 6FA3 5F82 3A76 3BF7 8323 AB5C ED4E 9E7F 4E2E
-----o()o----------------------------------------------
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-20 21:42 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <429613795-1158764726-cardhu_blackberry.rim.net-1614084655-@bxe050-cell01.bisx.prod.on.blackberry>
[not found] ` <200609192122.29838.mattm@gentoo.org>
2006-09-20 19:27 ` [gentoo-dev] New project: Gentoo Seeds Stuart Herbert
2006-09-20 19:44 ` Steve Dibb
2006-09-20 20:20 ` Donnie Berkholz
2006-09-20 20:27 ` Ciaran McCreesh
2006-09-20 20:37 ` Mike Frysinger
2006-09-20 20:41 ` Jakub Moc
2006-09-20 21:13 ` Ciaran McCreesh
2006-09-20 21:42 ` Jakub Moc
2006-09-20 21:56 ` Ciaran McCreesh
2006-09-20 22:06 ` Jakub Moc
2006-09-20 22:08 ` Josh Saddler
2006-09-20 21:33 ` Chris White
2006-09-20 22:24 ` Danny van Dyk
2006-09-20 22:42 ` Alec Warner
2006-09-20 22:53 ` Ciaran McCreesh
2006-09-20 23:06 ` Mike Frysinger
2006-09-20 23:29 ` Jakub Moc
2006-09-20 23:50 ` Stephen Bennett
2006-09-21 0:06 ` Mike Frysinger
2006-09-21 19:38 ` Nick Rout
2006-09-21 19:52 ` Alec Warner
2006-09-21 22:35 ` Nick Rout
[not found] ` <20060921195500.GB9269@lemming.rechner>
2006-09-21 23:53 ` Dice R. Random
2006-09-22 8:20 ` Alin Nastac
2006-09-22 8:34 ` Simon Stelling
2006-09-20 23:17 ` Daniel Ostrow
2006-09-20 23:36 ` Seemant Kulleen
2006-09-21 2:41 ` Donnie Berkholz
2006-09-20 21:39 ` Michael Cummings [this message]
2006-09-19 19:00 Stuart Herbert
2006-09-19 22:56 ` Carsten Lohrke
2006-09-19 23:13 ` Daniel Ostrow
2006-09-20 10:50 ` Stuart Herbert
2006-09-19 23:32 ` Thomas Cort
2006-09-20 1:11 ` Mike Frysinger
2006-09-20 10:40 ` Thomas Cort
2006-09-20 14:49 ` Chris Gianelloni
2006-09-20 13:59 ` Chris Gianelloni
2006-09-20 14:04 ` Donnie Berkholz
2006-09-20 14:49 ` Chris Gianelloni
2006-09-20 15:13 ` Stuart Herbert
2006-09-20 18:16 ` Jon Portnoy
[not found] ` <45118DC1.1000706@gentoo.org>
2006-09-20 19:12 ` Donnie Berkholz
2006-09-20 19:52 ` Joshua Jackson
2006-09-20 14:07 ` Stuart Herbert
2006-09-20 14:54 ` Chris Gianelloni
2006-09-20 0:56 ` Donnie Berkholz
2006-09-20 16:21 ` Ramon van Alteren
[not found] ` <b38c6f4c0609201117w3d55bcf5k8cbe12e819f7ee24@mail.gmail.com>
[not found] ` <200609202102.03590.kugelfang@gentoo.org>
2006-09-20 18:56 ` Donnie Berkholz
2006-09-20 19:39 ` Danny van Dyk
2006-09-20 20:35 ` Stuart Herbert
2006-09-20 20:47 ` Josh Saddler
2006-09-20 20:27 ` Stuart Herbert
2006-09-20 16:38 ` Alec Warner
2006-09-20 17:06 ` Mike Frysinger
[not found] ` <451184FB.6010209@gentoo.org>
2006-09-20 18:54 ` Donnie Berkholz
2006-09-20 19:26 ` Andrew Gaffney
2006-09-20 19:48 ` Mike Frysinger
2006-09-20 19:55 ` Josh Saddler
2006-09-21 0:01 ` Josh Saddler
2006-09-20 19:33 ` Ciaran McCreesh
2006-09-20 20:45 ` Seemant Kulleen
2006-09-20 21:06 ` Ciaran McCreesh
2006-09-24 12:27 ` Paul de Vrieze
2006-09-20 20:49 ` Josh Saddler
2006-09-20 21:04 ` Mike Frysinger
2006-09-20 23:24 ` Luca Barbato
2006-09-21 0:31 ` Stuart Herbert
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=1158788356.23583.30.camel@sys947.dtic.mil \
--to=mcummings@gentoo.org \
--cc=gentoo-dev@lists.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