From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans Reiser Subject: Re: implementing reiserfs in C++ for a new OS Date: Tue, 10 Aug 2004 15:05:04 -0700 Message-ID: <41194690.5050908@namesys.com> References: <71d3364904080706112e72fb6b@mail.gmail.com> <20040809172437.GP1284@nysv.org> <71d3364904080922267e8c14af@mail.gmail.com> <200408101312.48888.reiserfs-list@quinnh.org> <4119273E.1040104@namesys.com> <20040810211951.GU1284@nysv.org> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <20040810211951.GU1284@nysv.org> List-Id: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: =?ISO-8859-1?Q?Markus_T=F6rnqvist?= Cc: Quinn Harris , reiserfs-list@namesys.com Markus T=F6rnqvist wrote: >On Tue, Aug 10, 2004 at 12:51:26PM -0700, Hans Reiser wrote: > =20 > >>Yes, but it protects the expression not just in every literal word, but=20 >>in the sense of it. Look at the lawsuits over ripping off movie script=20 >>writers. >> =20 >> > >That happens mostly in the so-called land of the free, where movie writers >engage in pissing contests over who has the biggest asteroid or volcano. > >Of course it's possible these ideas came simultaneously, and you can't >lock an idea down because people have the same ideas, it's just that >those guys are greedy as well and thus start shouting about intellectual >property infringment just to cover their industrial espionage. > =20 > No, if you walk into someone's office with a cute movie concept, you=20 should not get ripped off, and you should not have to keep it secret=20 until you have your own resources to produce the movie for fear that you=20 will be. > =20 > >>Taking the essence of our expression, and transforming it into C++ and=20 >>Indian, will not avoid infringement of our copyright. Our documentation = >>is as protected as the source code, probably more so, because we=20 >>haven't GPL'd everything on the website. >> =20 >> > >I have nothing but respect for you, your team and your work, but this >is a bit wrong. > >Sure the documentation is copyrighted, but it's the actual documentation, >not the idea behind it, that is copyrighted. > =20 > There is an idea, and then there is an expression of an idea. =20 expression is not just the letters, or the words, it is somewhere=20 between the exact characters and the idea. > =20 > >>I don't really understand why he doesn't license it from us or adhere to = >>the GPL if it is going to be free as he describes.=20 >> =20 >> I think he is going to clarify it, he sent me a private email in which=20 things make more sense, I'll let him say the rest.