public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: last rites: games-fps/postal2mp-demo
Date: Wed, 16 Jul 2014 12:06:44 -0400	[thread overview]
Message-ID: <CAGfcS_=+UkhQjHCZUJSn5TT7Txo8h4XZENvzyOddjPdHA=DZBg@mail.gmail.com> (raw)
In-Reply-To: <21446.37158.790000.421879@a1i15.kph.uni-mainz.de>

On Wed, Jul 16, 2014 at 10:50 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
> IANAL, but there is no such concept as "abandonware" in copyright law.
> Copyright can expire, at which point the work enters into the public
> domain. However, the time for that is generally too long to play any
> practical role for software (typically 70 years post mortem auctoris).
>
> Therefore we cannot distribute a package unless it is explicitly
> allowed by its license.
>

Well, copyright law varies by jurisdiction.  However, I don't think it
really makes sense for Gentoo to pursue this for a few reasons.

Please note that I'm completely sympathetic to the cause here - I just
don't think this is a wise way to go about it.

This is legally a very risky thing to do.  If you're going to do it
you want to take advantage of countries with friendly laws, etc.
Sticking a file on every Gentoo mirror is basically the exact opposite
of that - every one of our sponsors in countries all over the world
are open to lawsuit, and those targetting us could have their pick of
jurisdiction.

Also, why combine a low-risk activity like running a distro with a
high-risk one like hosting abandonware.  There is no technical
requirement to co-mingle these activities.  Gentoo depends on lots of
servers/sponsors/etc for its core mission.  Why put all of that at
risk for something that really isn't essential to our mission?

If somebody is interested in maintaining abandonware I'd take an
entirely different approach.  It should be managed as its own upstream
project, completely independent of Gentoo or any other distro.  They
should understand the legal risks, and structure their project in a
way that minimizes them, such as by operating in countries where this
activity is legal.

Rich


  reply	other threads:[~2014-07-16 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53BB07C1.8090801@gentoo.org>
     [not found] ` <53BC12E2.6030002@gentoo.org>
2014-07-16 14:08   ` [gentoo-dev] Re: [gentoo-dev-announce] last rites: games-fps/postal2mp-demo Denis Dupeyron
2014-07-16 14:50     ` [gentoo-dev] " Ulrich Mueller
2014-07-16 16:06       ` Rich Freeman [this message]
2014-07-16 16:20         ` Wulf C. Krueger
2014-07-16 18:22           ` Alexander Berntsen
2014-07-16 19:19             ` Denis Dupeyron
2014-07-16 19:24               ` Alexander Berntsen
2014-07-16 19:28               ` Ian Stakenvicius
2014-07-16 19:44                 ` Denis Dupeyron
2014-07-16 19:54                   ` Rich Freeman
2014-07-16 20:24                     ` Ian Stakenvicius
2014-07-17  4:13           ` Alec Warner

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='CAGfcS_=+UkhQjHCZUJSn5TT7Txo8h4XZENvzyOddjPdHA=DZBg@mail.gmail.com' \
    --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