|
|
Yes, as I understand it, a slew of coders have contributed code over the
years; you don't have the legal authority to set up a new license without
their permission; some of these contributors have disappeared into the
woodwork. You might be able to get away with a new license, but wisely
choose to avoid the legal risk of someone re-emerging from the woodwork and
suing you.
I wonder however to what extent you could adopt some other license for one
of your re-writes (4.0?). There must be a license which would not only
protect your work against the commercial exploitation you rightly are
concerned about but also is a document that the software (linux!) world is
already familiar with (four examples I believe were listed earlier in the
thread). That is what I'd like to see.
Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> Nicolas George wrote:
> > The choice is yours
>
> Actually it's not, as we have explained many times. We have no choice about
> our current license.
>
> While I don't necessarily agree with everything said in the below-referenced
> article, it is a good enough introduction to the basic concepts:
>
> http://software.newsforge.com/software/06/01/17/201221.shtml
>
> -- Chris Cason
> POV-Team
Post a reply to this message
|
|