I got to thinking some about the license how-to thing. I *do* believe
that a guide to selecting licenses *would* be useful.
I was planning on writing that document. The following is the table of
contents I thought it should have, as I wrote it two days ago:
1 Introduction
Just s
Are there any archives for this list?
I'm particularly interested in discussion of not-quite-free licenses
such as the BitKeeper license.
--
J C Lawrence Life: http://www.kanga.nu/ Home: [EMAIL PROTECTED]
-(*)Work (Linux/IA64): [EMAIL PROTECTED]
... Beware of cr
Ian Lance Taylor wrote:
>
>Date: Fri, 30 Jul 1999 09:43:04 -0400
>From: John Cowan <[EMAIL PROTECTED]>
>
>Ian Lance Taylor wrote:
>
>> One easy and relatively inexpensive way to publish an algorithm with a
>> legally verifiable date in the U.S. is to register it with the
>
Date: Fri, 30 Jul 1999 09:43:04 -0400
From: John Cowan <[EMAIL PROTECTED]>
Ian Lance Taylor wrote:
> One easy and relatively inexpensive way to publish an algorithm with a
> legally verifiable date in the U.S. is to register it with the
> U.S. copyright office. You can send th
Ian Lance Taylor wrote:
> One easy and relatively inexpensive way to publish an algorithm with a
> legally verifiable date in the U.S. is to register it with the
> U.S. copyright office. You can send them a program listing, and they
> will basically file it with a timestamp.
Sorry, not enough.
On Wed, Jul 28, 1999 at 20:07:40 -0600, Jacques Chester wrote:
> I got to thinking some about the license how-to thing. I *do* believe
> that a guide to selecting licenses *would* be useful.
Have you taken a look at
Mark Koek, "Free Software Licensing"?
(See http://linuxtoday.com/stories/
Hello again;
On reflection I may have been a bit of a troll. Oh well ...
I got to thinking some about the license how-to thing. I *do* believe
that a guide to selecting licenses *would* be useful.
Some topics might include:
* The legal theory behind opensource/freedomware licenses
* Issues of
7 matches
Mail list logo