You might say this question was once simple, but is no longer. A one
word answer will not do...this is particularly so with regard to
software (software, by definition, involves the practical application of
algorithms).
I suspect the person who posed the question may not have posed it as
preci
On Monday 21 January 2002 08:03 am, Michael Bauer wrote:
> On the other hand, I always thought forking code was a bad thing. Unless
> you wanted to develop a nice commercial alternative to open source.
A quick list of Good Forks(tm):
Gnu Emacs / XEmacs
Some bad blood still exists betwe
Patrik Wallstrom wrote:
> On Mon, 21 Jan 2002, Randy Kramer wrote:
>
> > > So, is the algorithm patented as well as copyrighted? If so, I think
> > > another can of worms is about to have the top popped off.
> > >
> > > > You can license something that is patented, thus, if an algorithm is
> > >
On Mon, 21 Jan 2002, Randy Kramer wrote:
> > So, is the algorithm patented as well as copyrighted? If so, I think
> > another can of worms is about to have the top popped off.
> >
> > > You can license something that is patented, thus, if an algorithm is
> > > patented, it could be licensed.
>
>
Quoting Thorsten Glaser ([EMAIL PROTECTED]):
> begin Rick Moen dicebat
> As anyone knows, emacs is short for
> << Escape Meta Alt Ctrl Shift
Eighty Megs And Constantly Swapping.
(We could go on.)
--
Cheers,
Rick Moen Emacs is a decent operating system,
[EMAIL PROTECTED]
begin Rick Moen dicebat
>Quoting Michael Bauer ([EMAIL PROTECTED]):
>
>> On the other hand, I always thought forking code was a bad thing.
>
>Not really.
>http://linuxmafia.com/~rick/essays/forking.html
As anyone knows, emacs is short for
<< Escape Meta Alt Ctrl Shift
ma"I use JOE"neo
--
end
Michael Bauer wrote:
> Randy Kramer wrote:
> So, is the algorithm patented as well as copyrighted? If so, I think
> another can of worms is about to have the top popped off.
>
> > You can license something that is patented, thus, if an algorithm is
> > patented, it could be licensed.
What algor
Rick Moen scripsit:
> Quoting Michael Bauer ([EMAIL PROTECTED]):
>
> > On the other hand, I always thought forking code was a bad thing.
>
> Not really.
> http://linuxmafia.com/~rick/essays/forking.html
[T]he right to fork is like the right to strike, the
right to sue, or the r
Ah, a most excellent and enlightening article, Rick. Thank you.
On Mon, 21 Jan 2002, Rick Moen wrote:
> Quoting Michael Bauer ([EMAIL PROTECTED]):
>
> > On the other hand, I always thought forking code was a bad thing.
>
> Not really.
> http://linuxmafia.com/~rick/essays/forking.html
> --
>
So, is the algorithm patented as well as copyrighted? If so, I think
another can of worms is about to have the top popped off.
On Mon, 21 Jan 2002, Randy Kramer wrote:
> Michael Bauer wrote:
> > I don't think copyright protects an algorithm. I think you'd need a
> > patent for that. So, I d
Michael Bauer wrote:
> I don't think copyright protects an algorithm. I think you'd need a
> patent for that. So, I don't think you can license an algorithm. Of
> course, IANAL (just anal).
Michael,
LOL!
You can license something that is patented, thus, if an algorithm is
patented, it could
Quoting Michael Bauer ([EMAIL PROTECTED]):
> On the other hand, I always thought forking code was a bad thing.
Not really.
http://linuxmafia.com/~rick/essays/forking.html
--
license-discuss archive is at http://crynwr.com/cgi-bin/ezmlm-cgi?3
I don't think copyright protects an algorithm. I think you'd need a
patent for that. So, I don't think you can license an algorithm. Of
course, IANAL (just anal).
On the other hand, I always thought forking code was a bad thing. Unless
you wanted to develop a nice commercial alternative t
On Monday 21 January 2002 12:07 pm, Patrik Wallstrom wrote:
> I know this has been up for discussion before, but I didn't really
> follow the thread, and I want to know some extra things.
>
> Is there any current open source licenses that can enforce the software
> to follow an exact algorithm (as
Patrik Wallstrom scripsit:
> Is there any current open source licenses that can enforce the software to
> follow an exact algorithm (as provided by the copyright owner) and
> protocol?
No. That would limit the freedom to create derivative works.
> Does any of the licenses also prohibit a name
I know this has been up for discussion before, but I didn't really follow
the thread, and I want to know some extra things.
Is there any current open source licenses that can enforce the software to
follow an exact algorithm (as provided by the copyright owner) and
protocol? Does any of the lice
16 matches
Mail list logo