From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Sandboxes
Date: Thu, 23 Mar 2006 18:45:38 -0500 [thread overview]
Message-ID: <44233322.2040801@gentoo.org> (raw)
To hijack the overlay thread, I see a few things here:
MOTIVATION:
a) Developers don't like putting experimental stuff in the tree: This is
usually because Joe Ricer picks up the ebuild, 'tests' it, it breaks and
he files a bug. Joe Ricer has no clue what went wrong or what he is
doing and said Developer gets annoyed as hell by Joe Ricer's lack of
knowledge/co-operation with regards to bug report. For more popular
packages, multiply Joe Ricer by some random two digit number.
b) Developers want users to contribute too: Users don't have commit
access to the main tree (for good reason, as stated in the other
thread). However developers would like users to be able to contribute
in some meaningful way to a project/package without the red tape that is
bugzilla.
PROPOSAL:
a) overlays.gentoo.org -> A sub-domain for hosting overlays or
'development sandboxes'. Developers want an area for sandboxed
development of packages outside of the main tree. As stated in the
previous thread this allows faster developer with less overread (QA,
changelogs, etc..). These sandboxed areas also allow non-developers to
contribute to projects in a useful manner.
b) overlays.gentoo.org -> Is not meant for public consumption by users.
overlays.gentoo.org is merely a development aid and not meant for
public consumption. Users tend to not know how overlays are
implemented. Multiple activated overlays also can cause hard to debug
issues as overlays over-ride ebuilds and eclass in each other and the
tree itself.
c) Overlays may be secured on an per-overlay basis to prevent normal
users from both reading and writing to the overlay. For example a
project may wish to have an overlay and invite two or three
non-developers to contribute. This makes creating small development
units easy, while keeping QA the main tree relatively high.
This is what I see, and this is kinda what I would want. As an overlay
"creator" I should be able to add/remove accounts from my own overlay (
to reduce the load on the overlay project/infra ). In essence, creating
a bunch of small communities for development.
Thoughts on ideas on this somewhat more focussed idea? ( or at least I
think it's more focused :P )
-Alec Warner
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2006-03-24 0:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 23:45 Alec Warner [this message]
2006-03-24 0:21 ` [gentoo-dev] Sandboxes Stefan Schweizer
2006-03-24 1:15 ` Alec Warner
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=44233322.2040801@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