:[EMAIL PROTECTED]
Sent: 05 April 2006 01:14
To: Andrew Smith
Cc: misc@openbsd.org
Subject: Re: GNU license files rules replacement guidelines with BSD one
On Wed, 5 Apr 2006 00:15:02 +0100 Andrew Smith
[EMAIL PROTECTED] wrote:
GPL cannot be revoked by the author and, what is more, a new version
On Wed, 5 Apr 2006 11:01:22 +0100 Andrew Smith
[EMAIL PROTECTED] wrote:
http://www.openbsd.org/policy.html
Scroll down to the section 'Permissions - the flip side' and consider
the consequences of the statements in paragraph 4.
This section is probably the biggest one that supports my
Andrew Smith wrote:
http://www.openbsd.org/policy.html
Scroll down to the section 'Permissions - the flip side' and consider the
consequences of the statements in paragraph 4.
This section is probably the biggest one that supports my view that GPL
cannot be recinded and after initiation and
On 4/5/06, Andrew Smith [EMAIL PROTECTED] wrote:
http://www.openbsd.org/policy.html
Scroll down to the section 'Permissions - the flip side' and consider the
consequences of the statements in paragraph 4.
This section is probably the biggest one that supports my view that GPL
cannot be
Please guys, like I put in my original questions.
Quote
I don't want this to turn into a flame war however.
If that's where it might be going, don't answer.
Quote /
Lets stick to the essence of the question. So far I got one good answer
from Ted. Not sure yet that I fully understand it, or
On Apr 5, 2006, at 12:11 PM, Daniel Ouellet wrote:
If I see a GNU software that I like and the structure of it makes
sense, or I think it makes sense, but I don't want to correct the
bugs in it because it will stay under GNU. At what point, or how
can it be replace by a BSD one where
On 4/5/06, Daniel Ouellet [EMAIL PROTECTED] wrote:
Back to the original topic,
If what you are talking about is rather if you can replace some GPL
file by an equivalent one but BSD licensed file, the answer is yes (as
long as you don't copy-paste).
But what does that really mean. It
** Reply to message from Daniel Ouellet [EMAIL PROTECTED] on Wed,
05 Apr 2006 15:25:52 -0400
Back to the original topic,
If what you are talking about is rather if you can replace some GPL
file by an equivalent one but BSD licensed file, the answer is yes (as
long as you don't copy-paste).
Arnaud Bergeron wrote:
For example, if you have a function that takes a string argument and
reverse the characters in it under GPL. You take what it does
(reverse character in a string) and re-implement it with your own
code. You can keep the same interface to the function (meaning name
and
On 05/04/06, Adam [EMAIL PROTECTED] wrote:
On Wed, 5 Apr 2006 00:15:02 +0100 Andrew Smith
[EMAIL PROTECTED] wrote:
- Linus faces this issue with future versions of Linux, he
doesn't like GPL 3 and won't accept it but he can't take GPL 2 off
Linux kernel since it is an evolving project and
On 05/04/06, Daniel Ouellet [EMAIL PROTECTED] wrote:
It means that a file with only #include statements is hardly
copyrightable and can be copied at will.
Can it really? I guess if in the end you make it KNF compliant and the
order of the various includes are changed, but are the exact same
If you want a good insight on the issue of legal implications of
creating derivative/non-derivative works with functionality that is
present in existing implementations, I suggest that you follow the SCO
vs. Linux lawsuit, the arguments around the issue are very relevant to
your question.
For
On 4/4/06, Daniel Ouellet [EMAIL PROTECTED] wrote:
I am not sure that this is a simple question, but what's the rules if
any, or guide line someone can go under to replace files and code with
BSD type in a project for example.
I need some help understanding what's right and what's wrong and
Nick Guenther wrote:
My understanding is that the owner of the copyright can change the
license at any time, but that that change only applies to new
versions.
So:
if you are forking someone else's GNU code then you can't arbitrarily
make it BSD (because of the restrictions in the GPL). I
license files rules replacement guidelines with BSD one
On 4/4/06, Daniel Ouellet [EMAIL PROTECTED] wrote:
I am not sure that this is a simple question, but what's the rules if
any, or guide line someone can go under to replace files and code with
BSD type in a project for example.
I need some help
On Wed, 5 Apr 2006 00:15:02 +0100 Andrew Smith
[EMAIL PROTECTED] wrote:
GPL cannot be revoked by the author and, what is more, a new version
being classed as a 'derived work' would still under the terms of GPL
be classed as GPL and the original author couldn't do anything about
it.
Revoking
On 2006/04/05 00:15, Andrew Smith wrote:
GPL cannot be revoked by the author
Cannot be revoked but can be re-licenced by the author under
another license. Where there's more than one author, all must agree
to the change.
This leads to dual-licensed code having things like
On 4/4/06, Daniel Ouellet [EMAIL PROTECTED] wrote:
Let say that you have a GNU project and that you need to keep full
compatibility with the system calls, in/out, same function names and in
some cases structure, but the way the process is done is different.
At what point is it correct and
18 matches
Mail list logo
