From: Andy Elvey <andy.elvey@paradise.net.nz>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"?
Date: Wed, 25 Jul 2012 18:01:17 +1200 [thread overview]
Message-ID: <500F8BAD.3020102@paradise.net.nz> (raw)
In-Reply-To: <CAL4LZyitNsCPrTwNXMwDUiz__dJk5Rw1=QUT5z015+O2YQEGEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]
On 25/07/12 16:06, John Floren wrote:
(snip)
> Just write the code, nobody cares. The manual pages define an
> interface, and you're going to implement it. The manual pages are
> copyrighted, sure, because they're written works and are automatically
> protected by copyright. Besides the recent Google vs. Oracle fiasco, I
> can't think of a time an open-source project had legal problems by
> writing new code to implement an API. And, based on a brief reading of
> http://www.groklaw.net/pdf3/OraGoogle-1202.pdf, it looks as though a
> US judge has ruled that an API is not subject to copyright; if you
> implement the 9P API, you should be fine. Also, since you're doing a
> free reimplementation of code which is currently available free to
> everyone by the creators (Lucent), I have a hard time figuring out
> exactly what basis they'd have for a lawsuit. john
Hi John - thanks for that.
Thanks also to everyone who has commented in this thread - you've been
very helpful! This is one of the most helpful lists that I've been on.
This feedback is very useful as a guide to how to proceed.
Although I'm not running Plan 9 at present (I'm on Linux), I'm very
impressed with its elegance. Everything from kbdfs to the plumber to the
Venti filesystem - it's all beautifully thought-out. The way that Venti
uses SHA1 hashes to store data reminds me a lot of Git (which I also
really like - there's another elegantly designed bit of software).
Thanks again, all - bye for now :)
- Andy
[-- Attachment #2: Type: text/html, Size: 2175 bytes --]
next prev parent reply other threads:[~2012-07-25 6:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 0:24 Andy Elvey
2012-07-25 2:18 ` hiro
2012-07-25 2:47 ` andrey mirtchovski
2012-07-25 2:52 ` andrey mirtchovski
2012-07-25 3:31 ` Andy Elvey
2012-07-25 3:58 ` erik quanstrom
2012-07-25 4:06 ` John Floren
2012-07-25 6:01 ` Andy Elvey [this message]
2012-07-25 14:14 ` David Leimbach
2012-07-25 4:08 ` andrey mirtchovski
[not found] ` <CAK4xykXO3AGWN_=LjeCOdNXsP1pq-6iy+M6Srm6ch4BrAz01sA@mail.gmail.c>
2012-07-25 4:10 ` erik quanstrom
2012-07-25 4:33 ` Skip Tavakkolian
2012-07-25 5:09 ` Jens Staal
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=500F8BAD.3020102@paradise.net.nz \
--to=andy.elvey@paradise.net.nz \
--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).