From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Sandboxes
Date: Fri, 24 Mar 2006 19:30:35 -0700 [thread overview]
Message-ID: <pan.2006.03.25.02.30.34.904971@cox.net> (raw)
In-Reply-To: 200603241323.11429.vapier@gentoo.org
Mike Frysinger posted <200603241323.11429.vapier@gentoo.org>, excerpted
below, on Fri, 24 Mar 2006 13:23:11 -0500:
> On Friday 24 March 2006 11:32, Andrej Kacian wrote:
>>
>> "Stuart Herbert" <stuart.herbert@gmail.com> napísal:
>> > On 3/24/06, Mike Frysinger <vapier@gentoo.org> wrote:
>> > > so we're clear, users would be able to create their own overlays
>> > > and publish their ebuilds right ?
>> >
>> > Not on overlays.g.o, no.
>>
>> FWIW, this is already possible on ebuildexchange.org.
>
> how about trying to help out visibility of these user-oriented sites then ...
> perhaps the front page of overlays.g.o would have a section on user driven
> sites ...
I like the idea of a pointer to user sites, tho I too would be
uncomfortable having j. random user's ebuilds on *.gentoo.org
(specifically hand-selected users that are working with specific devs is
different, particularly where a dev then retains some accountability for
said selection).
One thing to remember, however. In the US at least, linking to specific
illegal material is considered illegal in itself. There is a "common
carrier" exemption, however, with the caveat of DMCA takedown notices.
Thus, the section on user overlays couldn't mention any non-Gentoo
controlled j random user overlays specifically.
What /could/ happen is that the overlays front-page story introduces the
concept in general terms, with a link to a forum for discussion. The
forum infrastructure would then provide the ability for users to link
to various overlays, and take care of any abuse or DMCA takedown notices
as it already does. That would keep Gentoo's involvement legal and
above-board.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-25 2:33 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
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 ` Duncan [this message]
2006-03-27 20:17 ` [gentoo-dev] Sandboxes 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=pan.2006.03.25.02.30.34.904971@cox.net \
--to=1i5t5.duncan@cox.net \
--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