From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Sandboxes
Date: Thu, 23 Mar 2006 20:15:01 -0500 [thread overview]
Message-ID: <44234815.2040509@gentoo.org> (raw)
In-Reply-To: <e79639220603231621k230c4323v9b8d354e380f97d5@mail.gmail.com>
Stefan Schweizer wrote:
> On 3/24/06, Alec Warner <antarus@gentoo.org> wrote:
>
>>Thoughts on ideas on this somewhat more focussed idea? ( or at least I
>>think it's more focused :P )
>
>
> IMO motivation b) is not taken into account enough.
>
> You are missing out a general-user-overlay, where the developer adding
> a user to the access list would be responsible for him.
Hmmm that is not an intended goal at this time. "User-Contrib" sounds
overly too large. The aim is to make the overlay rather small, to allow
normal users to contribute to development of packages.
> We really need a general user overlay for stuff that is abandoned in
> the treee (maintainer-needed@gentoo.org) or stuff that has not even
> been added to the tree (maintainer-wanted@gentoo.org). Those are
> ebuilds that no developer is interested in, so a general way for users
> needs to be present to be able to take care of those in a
> policy-based-overlay instead of bugzilla. Also the overlay will be
> easier to access and more bug-free as every person who is trusted by
> gentoo-devs can just fix bugs that come up without spamming every CC:
> on the list as it would be in bugzilla.
This generally breaks the rule of "overlays.gentoo.org is not for end
users." The support in portage isn't there, the debugging is a
nightmare. The point of overlays is to expedite *development* where
user A wants to help maintain package B because it's pragmatic for him
to do so, but he doesn't want to be a full Gentoo developer. It is not
meant to be a "User-Contrib" overlay. I think that should be a seperate
( if related ) project with different semantics.
>
> Regards,
> Stefan
>
-Alec Warner
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-24 1:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 23:45 [gentoo-dev] Sandboxes Alec Warner
2006-03-24 0:21 ` Stefan Schweizer
2006-03-24 1:15 ` Alec Warner [this message]
2006-03-24 0:23 ` Mike Frysinger
2006-03-24 8:51 ` Paul de Vrieze
2006-03-24 15:23 ` Stuart Herbert
2006-03-24 16:32 ` Andrej Kacian
2006-03-24 18:23 ` Mike Frysinger
2006-03-25 2:30 ` [gentoo-dev] Sandboxes Duncan
2006-03-27 20:17 ` Mike Frysinger
2006-03-28 20:31 ` Lars Strojny
2006-03-29 0:32 ` Mike Frysinger
2006-03-24 0:54 ` [gentoo-dev] Sandboxes Thomas Cort
2006-03-24 8:52 ` Paul de Vrieze
2006-03-24 9:42 ` Henrik Brix Andersen
2006-03-24 9:47 ` Kalin KOZHUHAROV
2006-03-24 15:34 ` Mike Frysinger
2006-03-24 13:37 ` Chris Gianelloni
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=44234815.2040509@gentoo.org \
--to=antarus@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