Licensing issues

I was trying to figure out a license for the samples, and
stumbled
across a couple other issues that affect how we should be
building
wxWidgets for inclusion into our gem.

If possible, we should NOT build in TIFF nor JPEG support,
as both have
special attribution requirements. Other wx modules do as
well, but we
don't use them anyway (ODBC, wxXML, and wx 2.4 regex). 

For those of you who will be building our gems on Mac and MS
Windows,
please check to see if you can build without built-in TIFF
and JPEG
support. If you need to build those in, we need to mention
that in our
README file. Let me know.

Now, for the sample license: Public domain really isn't
appropriate,
partly because it is not valid in many countries. Here is my
proposal:


--------------------------
wxRuby2 Sample Code
Copyright (c) 2004-2006 Kevin B. Smith

Permission is hereby granted, free of charge, to any person
obtaining 
a copy of this software, to deal in the Software without
restriction,
including without limitation the rights to use, copy,
modify, merge,
publish, distribute, sublicense, and/or sell copies of any
portion of 
this Software, and to permit persons to whom the Software is
furnished
to do so. This copyright notice need not be retained in any
derived
work.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT
WARRANTY OF ANY KIND, EXPRESS
OR  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE
FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
--------------------------

Kevin


_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users

Kevin Smith wrote:
> I was trying to figure out a license for the samples,
and stumbled
> across a couple other issues that affect how we should
be building
> wxWidgets for inclusion into our gem.
>   
Thanks for investigating this.
> If possible, we should NOT build in TIFF nor JPEG
support, as both have
> special attribution requirements.
I would be very sad to lose JPEG support - I am using this
feature 
already, and I can see it being something others would want
(eg to make 
a photo browser). Looking at the relevant docs we only have
to add an 
attribution line somewhere in our docs; there is no need to
modify our 
licence terms. We don't redistribute any of their source (I
don't think 
our include/wxBitmap.h nor just defining BITMAP_TYPE_JPEG
are derivative 
works) so the short attribution could be used, as required
for redist in 
binary form.

TIFF is a less widespread format but again I would rather
not lose it - 
so far as I can tell a slightly longer attribution is all
that's required.
> Other wx modules do as well, but we
> don't use them anyway (ODBC, wxXML, and wx 2.4 regex).

>   
wxXML is a dependency for using XRC Resoures, I think - if
you try 
configuring WxWidgets --without-expat it warns that XRC will
be 
disabled. I don't use XRC but seems like a feature we
don't want to lose 
(eg for use with GUI designers).

My reading of the MIT licence (http://en.wi
kipedia.org/wiki/MIT_License) 
covering expat is that only an attribution is required.
> For those of you who will be building our gems on Mac
and MS Windows,
> please check to see if you can build without built-in
TIFF and JPEG
> support. If you need to build those in, we need to
mention that in our
> README file. Let me know.
>   
Can do, but see above.
> Now, for the sample license: Public domain really
isn't appropriate,
> partly because it is not valid in many countries. Here
is my proposal:
>   
Looks good, thanks again for your work on this.

Alex
_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users

On Sun, 2006-08-27 at 13:19 +0100, Alex Fenton wrote:
> > If possible, we should NOT build in TIFF nor JPEG
support, as both have
> > special attribution requirements.
> I would be very sad to lose JPEG support - I am using
this feature 
> already, and I can see it being something others would
want (eg to make 
> a photo browser). 

I agree. Under Linux, I have the option to build JPEG
support into the
wx library, or to leave it out so it dynamically loads it
from the
system. I suppose that's not an option under MS Windows.

> Looking at the relevant docs we only have to add an 
> attribution line somewhere in our docs; there is no
need to modify our 
> licence terms. We don't redistribute any of their
source (I don't think 
> our include/wxBitmap.h nor just defining
BITMAP_TYPE_JPEG are derivative 
> works) so the short attribution could be used, as
required for redist in 
> binary form.

True. Sounds simple enough. Do you think we would add a
CREDITS file, or
just have a CREDITS section in our README? Or something
else?

> TIFF is a less widespread format but again I would
rather not lose it - 

Agreed.

> wxXML is a dependency for using XRC Resoures, I think -
if you try 
> configuring WxWidgets --without-expat it warns that XRC
will be 
> disabled. I don't use XRC but seems like a feature we
don't want to lose 
> (eg for use with GUI designers).

Oh, then I guess we need that as well. Again, with Linux we
can leave
that stuff out and assume it is provided by the OS. But if
you are going
to include it one platform, we might as well be consistent.

> > Now, for the sample license: Public domain really
isn't appropriate,
> > partly because it is not valid in many countries.
Here is my proposal:
> >   
> Looks good, thanks again for your work on this.

Cool. Thanks.

Kevin


_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users

Kevin Smith wrote:
> Under Linux, I have the option to build JPEG support
into the
> wx library, or to leave it out so it dynamically loads
it from the
> system. I suppose that's not an option under MS
Windows.
>   
On OS X it defaults to using built-in; other apps I have
installled 
(HTMLDoc, GRASS) bundle it rather than install it to
/usr/local/lib.
> True. Sounds simple enough. Do you think we would add a
CREDITS file, or
> just have a CREDITS section in our README? Or something
else?
>   
Just a credits section in the README, or possibly appended
to the 
LICEN[CS]E file would be enough I think.

If you could post a standard header that should go in all
the samples, I 
am happy to go through them, update and commit.

Thanks
alex
_______________________________________________
wxruby-users mailing list
wxruby-usersrubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users