9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <john@jfloren.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 technical docs and man pages - licensed or "public domain"?
Date: Tue, 24 Jul 2012 21:06:07 -0700	[thread overview]
Message-ID: <CAL4LZyitNsCPrTwNXMwDUiz__dJk5Rw1=QUT5z015+O2YQEGEg@mail.gmail.com> (raw)
In-Reply-To: <500F6896.4010605@paradise.net.nz>

On Tue, Jul 24, 2012 at 8:31 PM, Andy Elvey <andy.elvey@paradise.net.nz> wrote:
> Hi Andrey - thanks for your reply!
>
> On 25/07/12 14:47, andrey mirtchovski wrote:
>
> I'm not a lawyer but I play one in comedy clubs. The first
> implementation of 9p came about long before Plan 9 had a free (as in
> rms) license. Nobody got sued, nobody died, although a few bystanders
> were maimed.
>
> Interesting. It's good to find out a bit of the history behind 9p.
>
> My advice as your lawyer [in comedy] would be to go nuts and do
> whatever you want. The documentation[1] is a good place to start if
> you don't want to look at any source (no license required to see
> that!), and if you want to cover all corner cases, a running Plan 9
> kernel is a good client/server to test against.
>
> ----
> 1: http://plan9.bell-labs.com/sys/man/5/INDEX.html
>
> Thanks for that!  I'll check that page out too.
> Btw - I clicked on the "copyright" link at the bottom, but the link is dead
> - nothing but a 404 page error.
>
> In looking at Tim Newsham's P9.py, he has a comment in the code - "9P
> protocol implementation as documented in plan9 intro(5) and <fcall.h>."
> ( I would likely be even more cautious and avoid looking at any header files
> if possible. )
> Thanks again, Andrey - you've been very helpful!
> - Andy

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



  parent reply	other threads:[~2012-07-25  4:06 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 [this message]
2012-07-25  6:01         ` Andy Elvey
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='CAL4LZyitNsCPrTwNXMwDUiz__dJk5Rw1=QUT5z015+O2YQEGEg@mail.gmail.com' \
    --to=john@jfloren.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).