|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ok, I'm trying to wrap up all the lose details of this GUI Extension, and
make sure I comply with the license. Part of the license is that the source
code has to be made available. I have no problem doing this, but I have
some questions. I used the GUI Extension demonstration code from the
POV-Ray source distribution, and there's a big Copyright POV-Team 1996-2002,
Author Christopher J. Cason at the top. I'm assuming that when I release
the source, I need to put back in the #error directives, take out the copy
text part, and remove the AUTHOR, EMAIL tag, etc.
My question is about the Copyright, and Author: Chris Cason. I have no
problem leaving it in, but it's not entirely true. Also there's a big deal
made about not having anyone contact the POV-Team for support, and if I
leave it in, it's possible that someone might just do that. Do I put a note
in that it only applies to the original GUI Demonstration code, and then put
my own Copyright and Author: in with it. In general I just don't like to
remove a copyright.
What do I do?
Andrew Wilcox
--
#macro Q(A,E,W)box{-A/2,A/2pigment{rgb 9*W}translate E*A+W/1000}#end#macro
M(D,E)#local A=1/pow(3,D);#if(D<3)#local C=D+1;union{M(C,1)M(C,x+y)M(C,x+z)
M(C,y+z)M(C,x+y-z)M(C,x+z-y)M(C,y+z-x)M(C,x-y)M(C,z-x)M(C,y-z)M(C,y-x)M(C,
x-z)M(C,z-y)M(C,x-y-z)M(C,y-x-z)M(C,z-x-y)translate A*E}#else Q(A,E,x)Q(A,E
,y)Q(A,E,z)#end#end union{M(0,0)rotate<45,145,0>translate z*2}//Andrew
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3dac7b7c$1@news.povray.org> , "Andrew Wilcox"
<awi### [at] unpuzzledcom> wrote:
> I used the GUI Extension demonstration code from the
> POV-Ray source distribution, and there's a big Copyright POV-Team 1996-2002,
> Author Christopher J. Cason at the top. I'm assuming that when I release
> the source, I need to put back in the #error directives, take out the copy
> text part, and remove the AUTHOR, EMAIL tag, etc.
>
> My question is about the Copyright, and Author: Chris Cason. I have no
> problem leaving it in, but it's not entirely true.
Oh, come on, don't be so complicated. It clearly says:
" EXCLUSION FROM STANDARD LICENCE PROVISIONS
Software authors may use this source code in derived programs PROVIDED
thay they comply with the terms of POVEXT.TXT."
And in POVEXT.TXT it says:
"Extensions may be based on the 'extension toolkit' source code we provide.
That is, we explicitly permit you to re-use our demonstration source code
(and in fact encourage it, since it helps ensure that you comply with our
standards.) This permission DOES NOT extend to other POV-Ray source files."
So if you comply with it, you may use this source code. Very easy, isn't
it? The source code is copyrighted and provided to you under the given
license. Obviously you have to refer to the given license when making it
available. But the changed source code remains your copyrighted program, of
course.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
So then I can remove the current copyright?
Should I release the source like the demo is released, with the #error
directives in?
> Oh, come on, don't be so complicated. It clearly says:
>
> " EXCLUSION FROM STANDARD LICENCE PROVISIONS
>
> Software authors may use this source code in derived programs PROVIDED
> thay they comply with the terms of POVEXT.TXT."
>
> And in POVEXT.TXT it says:
>
> "Extensions may be based on the 'extension toolkit' source code we
provide.
> That is, we explicitly permit you to re-use our demonstration source code
> (and in fact encourage it, since it helps ensure that you comply with our
> standards.) This permission DOES NOT extend to other POV-Ray source
files."
>
> So if you comply with it, you may use this source code. Very easy, isn't
> it? The source code is copyrighted and provided to you under the given
> license. Obviously you have to refer to the given license when making it
> available. But the changed source code remains your copyrighted program,
of
> course.
>
> Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, since know one knows, I'm going to leave it in, and put a big note in
the top of the file, about why there are two Copyrights. Then I'll put the
#error directives back in, and that'll be that.
Andrew Wilcox
> So then I can remove the current copyright?
>
> Should I release the source like the demo is released, with the #error
> directives in?
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Andrew Wilcox" <awi### [at] unpuzzledcom> wrote in message
news:3daf0e71$1@news.povray.org...
> Well, since know one knows, I'm going to leave it in, and put a big note in
> the top of the file, about why there are two Copyrights. Then I'll put the
> #error directives back in, and that'll be that.
Add a new copyright, and include a comment that it is based on the sample GUIEXT
source
code provide with POV-Ray for Windows v3.5, and that the original copyright applies as
well as whatever you add (i.e. you have created a derivative work).
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
thanks!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|