From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] license situation and OSI
Date: Wed, 26 May 2010 13:42:46 +0100 [thread overview]
Message-ID: <7ae079e8c3fd3f1bb06812607300224d@terzarima.net> (raw)
In-Reply-To: <FBDEF3CA-971E-4AFF-A80D-48A3D577DE9E@9srv.net>
>You don't get to change the license
``3. REQUIREMENTS
A. Distributor may choose to distribute the Program in any form under
this Agreement or under its own license agreement, provided that:
...
c. if distributed under Distributor's own license agreement, such
license agreement:
... [conditions placed on an alternative licence, including spelling out the differences]
''
next prev parent reply other threads:[~2010-05-26 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 8:37 staalmannen
2010-05-26 9:55 ` EBo
2010-05-26 12:03 ` Anthony Sorace
2010-05-26 12:42 ` Charles Forsyth [this message]
2010-05-26 15:57 ` Jack Johnson
2010-05-26 17:24 ` Nick LaForge
2010-05-26 19:57 ` Jack Johnson
2010-05-26 20:08 ` Corey
2010-05-26 20:28 ` Jack Johnson
2010-05-26 20:42 ` Corey
2010-05-27 3:10 ` Anthony Sorace
2010-05-26 18:50 ` Russ Cox
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=7ae079e8c3fd3f1bb06812607300224d@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).