From: Dennis Davis ccsdhd@bath.ac.uk
Subject: [9fans] inferno licence terms
Date: Mon, 15 May 2000 14:59:59 +0000 [thread overview]
Message-ID: <20000515145959.K6e6gQfITe3tc2y9n5OJIuMKyTdioBJfHnMEu3_U_E8@z> (raw)
The following is the essence from a recent draft of the licence we are
preparing for Inferno. The intent should not change but the wording might be refined
to reflect the intent more accurately. I have added some clarifying
phrases in brackets.
* You get all the source code [to native and hosted systems, and tools].
* You can distribute without fee [ie, no run-time royalty to us] binary copies
of Inferno or binary copies of amended versions of Inferno
* You can distribute without fee [ie, nothing payable to us] Inferno source code to
other Inferno subscribers
* You can distribute without fee [ie, nothing payable to us] source code to the
tools, drivers and applications [code in /appl]
* You can keep modifications you make private - but we
encourage you to share. [ie, you own them, we don't]
* This is a personal licence owned by you and you alone.
One thing that is not obvious is that the licence allows commercial use
by any subscriber: the `without fee' is a restriction on us, not
on a subscriber.
Those are the basic terms for personal licences; the corporate licence
is almost identical but removes the restrictions of the last line.
Though not in the legal licence yet, I have asked that lecturers should be
allowed to share their personal licence benefits with students of a course
or project for the duration of the course or project. There might be other
similar tweaking of content and scope.
Charles Forsyth
Vita Nuova
next reply other threads:[~2000-05-15 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-15 14:59 Dennis [this message]
2000-05-15 21:37 G.David
2000-05-15 22:49 Ben
2000-05-16 13:00 forsyth
2000-05-18 8:58 Richard
2000-05-21 2:58 Richard
2000-05-21 2:59 Richard
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=20000515145959.K6e6gQfITe3tc2y9n5OJIuMKyTdioBJfHnMEu3_U_E8@z \
--to=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).