public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jakub Moc <jakub@gentoo.org>
To: Brian Harring <gentoo-dev@lists.gentoo.org>
Subject: Re[2]: [gentoo-dev] mac/xmms-mac licence issue
Date: Sun, 25 Dec 2005 04:10:57 +0100	[thread overview]
Message-ID: <1643775053.20051225041057@gentoo.org> (raw)
In-Reply-To: <20051225025114.GJ5796@nightcrawler.e-centre.net>

[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]


25.12.2005, 3:51:15, Brian Harring wrote:


> Jakub responded in this thread about shipping a crap license... imo, 
> that's not the issue.

> The issue is that we would be knowingly violating a license (however 
> horrid the license is).  

> Two routes out of this- clean room reimplementation of the codec, or
> someone manages to track down the original author and gets the code 
> converted to a different license.  Latter still is tricky, since any 
> contributions to the project, you would need all authors to sign off 
> on the new license- this is assuming the project doesn't do 
> centralized copyright, and assuming people have actually contributed 
> to it beyond original author.


Not exactly what I meant. There's actually no (clear) license, the original
one would apply to the original code, not to the patches submitted after
it's been "re-licensed" under LGPL. Since upstream is dead, we can't ship
the original code (leaving the question why we should do it at all aside),
also we can't exactly find all the people who contributed the patches under
LGPL, and there's no way to contribute the code back to upstream as the
original license requires. Such code is a real "bargain" to commit :P

Rewrite from scratch, that's what left here. So much you get if you start
with a bullshit license originally and then go MIA. :/

-- 
Best regards,

 Jakub Moc
 mailto:jakub@gentoo.org
 GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E
 Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95  B30F 8717 D5FD CEBA 3D9E

 ... still no signature ;)

[-- Attachment #2: Type: application/pgp-signature, Size: 183 bytes --]

  reply	other threads:[~2005-12-25  3:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-25  2:11 [gentoo-dev] mac/xmms-mac licence issue Bret Towe
2005-12-25  2:37 ` Jakub Moc
2005-12-25  2:51 ` Brian Harring
2005-12-25  3:10   ` Jakub Moc [this message]
2005-12-25  3:22   ` Bret Towe
2005-12-25  3:34     ` Brian Harring
2005-12-25  3:43       ` Bret Towe
2005-12-25  3:02 ` Carsten Lohrke
2005-12-25  3:17   ` Bret Towe
2005-12-25  3:25     ` Ciaran McCreesh
2005-12-25  3:35       ` Bret Towe
2005-12-25  3:42         ` Daniel Ostrow
2005-12-25  3:47           ` Bret Towe
2005-12-25 14:17         ` Luis F. Araujo
2005-12-25 16:04       ` Curtis Napier
2005-12-25  3:28     ` Brian Harring
2005-12-25  3:32     ` Daniel Ostrow
2005-12-25  3:38       ` Bret Towe
2005-12-25  3:49       ` Ciaran McCreesh
2005-12-25  3:32     ` Re[2]: " Jakub Moc
2005-12-25  3:41     ` Dale

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=1643775053.20051225041057@gentoo.org \
    --to=jakub@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