public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: "Yaakov (Cygwin Ports)" <yselkowitz@users.sourceforge.net>
To: cygwin-apps@cygwin.com
Subject: Re: GPLv3
Date: Mon, 02 Jul 2007 23:52:00 -0000	[thread overview]
Message-ID: <46898FC2.6020703@users.sourceforge.net> (raw)
In-Reply-To: <01c001c7bd00$8d50f050$2e08a8c0@CAM.ARTIMI.COM>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dave Korn wrote:
>>  If IMHO, the GPLv3 does comply with the
>> definition as published at the provided URL, who says I need to wait for
>> the OSI to actually certify it as such?
> 
>   You don't, as long as you are confident that the licensors will concur with
> your MHO.  Well, technically, you don't have to wait for anything ever: this
> is a civil matter, there are no restraining injunctions, it would be up to RH
> legal to decide whether they felt GPLv3 complies, in which case they wouldn't
> sue your, or whether they felt it doesn't, in which case they would have the
> option of suing you, in the event of which it would then still be up to a
> court to decide whether the standards by which they have adjudged whether it
> 'complies' or not are reasonable under the standards by which civil contracts
> are judged, and hence enforcable, or not, and hence not.  Herein lies both
> your security - they don't /have/ to sue you if they don't want to, even if
> something you do doesn't technically live up to the word of the license,
> because they are at liberty to decide for themselves if it 'complies' or note
> - and also your risk, because none of it is defined with mathematical rigour,
> there is an element of judgement to all the phraseology used, and it's a
> matter of contract law.  Note very importantly the difference between whether
> X 'complies with' Y, which is a subjective judgement, and whether X is
> *certified as* Y, which is a matter of fact or not according to the decision
> of the relevant certifying body.

While wrt GPLv3 software I agree that this is purely hypothetical and
certainly soon to be moot (when OSI certifies GPLv3), one could conceive
another case which would be relevant and possibly damaging to RH:

1) 3PP distributes clearly non-FOSS software depending on Cygwin (either
w/o Cygwin itself or with Cygwin and sources).

2) RH sues 3PP for violation of Cygwin license.

3) Defendant successfully argues that "complies with" != "certified",
and continues with elaborate explanation how his license supposedly
complies with OSI definition.

4) Court (or, worse yet, uneducated, uninformed, layman jury) falls for
defendant's hot air.

While I'm certain RH has excellent lawyers and this argument would be
well fought, this "subjective judgement", as you put it, could make this
problematic, or just unnecessary difficult (and expensive) at best.


Yaakov

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGiY/CpiWmPGlmQSMRCNg9AKDswbG7h12wQPyL8aKT/J5FSe9GygCgj/RS
jdtTmvYVfX2vJFlkqjGvEWg=
=pLiA
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-07-02 23:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01  3:46 GPLv3 Eric Blake
2007-07-01  4:12 ` GPLv3 Brian Dessent
2007-07-01 14:17   ` GPLv3 Eric Blake
2007-07-01 14:24     ` GPLv3 Eric Blake
2007-07-02  7:40     ` GPLv3 Corinna Vinschen
2007-07-02 14:40       ` GPLv3 Andrew Schulman
2007-07-02 15:18         ` GPLv3 Corinna Vinschen
2007-07-02 15:29           ` GPLv3 Andrew Schulman
2007-07-02 18:04             ` GPLv3 Corinna Vinschen
2007-07-02 20:09               ` GPLv3 Yaakov (Cygwin Ports)
2007-07-02 23:29                 ` GPLv3 Dave Korn
2007-07-02 23:52                   ` Yaakov (Cygwin Ports) [this message]
2007-07-03  7:09                 ` GPLv3 Corinna Vinschen
2007-07-03 17:45                   ` GPLv3 Dave Korn
2007-07-03 18:07                     ` GPLv3 Corinna Vinschen
2007-07-02 20:15               ` GPLv3 Yaakov (Cygwin Ports)
2007-07-05  2:33               ` GPLv3 Eric Blake

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=46898FC2.6020703@users.sourceforge.net \
    --to=yselkowitz@users.sourceforge.net \
    --cc=cygwin-apps@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).