From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Non-free software in Gentoo
Date: Thu, 07 Jan 2010 09:37:42 -0500 [thread overview]
Message-ID: <4B45F1B6.4000604@gentoo.org> (raw)
In-Reply-To: <4B457CEC.8030801@doublecreations.com>
On 01/07/2010 01:19 AM, Vincent Launchbury wrote:
> All I'm asking for is that users who care about this will be shown an
> accurate license,
I think that this really sums this whole thing up. Can you run a
computer with ONLY FOSS on it (firmware to ROMs to hard drive
controlers) - probably not, but maybe. I think that is really a
separate matter.
I think this really just boils down to this: If we have a piece of
metadata on a package it should be accurate. The license should reflect
the license of whatever ends up on a user's hard drive. Maybe knowing
the license isn't that important - in that case maybe we shouldn't track
licenses at all. However, if we're going to track the license, then it
should be completely accurate (or at least we should aim for that even
if Gentoo metadata can never be perfect). That's why I also support
having GPL2 vs GPL2+ / etc in the license field. Sure, it won't be
exactly right for a while, but it is worth shooting for.
Ditto for other metadata - homepages should be official, maintainers
should be active, and all that. QA will always have work to do as this
will never be 100% right for everything in the tree, but there is value
in being accurate anytime we can be.
By all means the default install should have an ACCEPT_LICENSE that is
both legal and fully functional - if people want to trim it down that is
up to them. Maybe somebody wants to use Gentoo to build an appliance
and they want to go pure non-copyleft - that's a major chore but we
could still give them a great head-start on identifying where the issues
with that are and at least getting them 80% of a functional system.
I think this whole thread really boils down to - make the license
accurate. What users do with it is up to them, and we don't need to
support non-standard configurations just because we make them possible.
next prev parent reply other threads:[~2010-01-07 16:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 5:36 [gentoo-dev] Non-free software in Gentoo Vincent Launchbury
2009-12-28 8:10 ` Rémi Cardona
2009-12-28 13:11 ` Nirbheek Chauhan
2009-12-29 8:59 ` Peter Volkov
2009-12-29 5:24 ` Vincent Launchbury
2009-12-29 9:02 ` Peter Volkov
2009-12-29 18:32 ` Robin H. Johnson
2009-12-29 23:17 ` Brian Harring
2009-12-28 11:21 ` Jeroen Roovers
2009-12-28 14:37 ` Jeremy Olexa
2009-12-28 18:56 ` Robin H. Johnson
2009-12-28 22:15 ` Richard Freeman
2009-12-28 22:53 ` Robin H. Johnson
2009-12-29 1:16 ` Richard Freeman
2009-12-30 0:52 ` Greg KH
2009-12-30 11:43 ` Richard Freeman
2009-12-31 4:51 ` Greg KH
2009-12-31 6:02 ` Harald van Dijk
2009-12-30 0:50 ` Greg KH
2009-12-30 2:42 ` Vincent Launchbury
2009-12-31 4:48 ` Greg KH
2009-12-31 12:30 ` Richard Freeman
2010-01-06 4:55 ` Vincent Launchbury
2010-01-06 18:57 ` Greg KH
2010-01-06 21:55 ` Harald van Dijk
2010-01-07 6:19 ` Vincent Launchbury
2010-01-07 14:37 ` Richard Freeman [this message]
2010-01-08 5:26 ` Greg KH
2010-01-08 15:48 ` Richard Freeman
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=4B45F1B6.4000604@gentoo.org \
--to=rich0@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