<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>My original question had nothing to do with forking IIAB or using its code,
but rather sought it as a model for including licensing in the code I write so
as to make it usable by others. In addition to choosing different
licenses, the IIAB strategy is to include a license only at the top level of the
tree, whereas OLPC had a license at the top of each module.</DIV>
<DIV> </DIV>
<DIV>Having said all that, I think IIAB has modules that could be of interest to
developers outside of IIAB as a whole.</DIV>
<DIV> </DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">Tim</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=braddock@gmail.com
href="mailto:braddock@gmail.com">Braddock Gaskill</A> </DIV>
<DIV><B>Sent:</B> Saturday, November 01, 2014 7:20 PM</DIV>
<DIV><B>To:</B> <A title=xsce-devel@googlegroups.com
href="mailto:xsce-devel@googlegroups.com">xsce-devel@googlegroups.com</A> </DIV>
<DIV><B>Cc:</B> <A title=server-devel@lists.laptop.org
href="mailto:server-devel@lists.laptop.org">server-devel</A> </DIV>
<DIV><B>Subject:</B> Re: [XSCE] copyright and licensing</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV dir=ltr>You don't need our (IIAB) permission to relicense our software
under GPL or AGPL because the BSD 2 clause license we are using is compatible
with GPL forks. BSD is gives more rights than GPL.
<DIV> </DIV>
<DIV>That said, I'd strongly prefer no one forks our code base in that way and
instead contribute back to the core IIAB project software (under a BSD
license).</DIV>
<DIV> </DIV>
<DIV>There is no reason BSD components and GPL components cannot co-exist, as
they do everywhere else, assuming basic linking hygiene is used. If you
don't understand this post please don't make licensing decisions.</DIV>
<DIV> </DIV>
<DIV>-braddock</DIV></DIV>
<DIV class=gmail_extra>
<DIV> </DIV>
<DIV class=gmail_quote>On Fri, Oct 31, 2014 at 8:26 AM, Anish Mangal <SPAN
dir=ltr><<A href="mailto:anishmangal2002@gmail.com"
target=_blank>anishmangal2002@gmail.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<P dir=ltr>GPL or AGPL? Can/Should we ask the IIAB maintainers and
contributors for permission to license under GPL if it's not too
complicated?</P>
<DIV class=HOEnZb>
<DIV class=h5>
<DIV class=gmail_quote>On Oct 31, 2014 8:52 PM, "Tim Moody" <<A
href="mailto:tim@timmoody.com" target=_blank>tim@timmoody.com</A>>
wrote:<BR type="attribution">
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>I am starting to write larger chunks of code and wondering what
copyright and licensing I should include. Any suggestions
welcome. (In Canada copyright rests with the author unless it is
relinquished.)</DIV>
<DIV> </DIV>
<DIV>Most XS code has something like:</DIV>
<DIV> </DIV>
<DIV># Copyright 2007, One Laptop per Child</DIV>
<DIV># Author: John Watlington</DIV>
<DIV>#</DIV>
<DIV># This program is free software; you can redistribute it and/or</DIV>
<DIV># modify it under the terms of the GNU Library General Public
License</DIV>
<DIV># as published by the Free Software Foundation; either version 2</DIV>
<DIV># of the License, or (at your option) any later version.</DIV>
<DIV>#</DIV>
<DIV># This program is distributed in the hope that it will be useful,</DIV>
<DIV># but WITHOUT ANY WARRANTY; without even the implied warranty of</DIV>
<DIV># MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See
the</DIV>
<DIV># GNU General Public License for more details.</DIV>
<DIV>#</DIV>
<DIV># You should have received a copy of the GNU Library General
Public</DIV>
<DIV># License along with this program; if not, write to the Free
Software</DIV>
<DIV># Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA</DIV>
<DIV># 02111-1307, USA.</DIV>
<DIV> </DIV>
<DIV>IIAB has:</DIV>
<DIV> </DIV>
<DIV>This software is licensed with the BSD 2-clause license</DIV>
<DIV>(See <A href="http://opensource.org/licenses/BSD-2-Clause)"
target=_blank>http://opensource.org/licenses/BSD-2-Clause)</A></DIV>
<DIV> </DIV>
<DIV>Copyright (c) 2013, Humane Informatics LLC</DIV>
<DIV>All rights reserved.</DIV>
<DIV> </DIV>
<DIV>Redistribution and use in source and binary forms, with or
without</DIV>
<DIV>modification, are permitted provided that the following conditions are
met:</DIV>
<DIV> </DIV>
<DIV> Redistributions of source code must retain the above
copyright notice, this</DIV>
<DIV>list of conditions and the following disclaimer.</DIV>
<DIV> Redistributions in binary form must reproduce the
above copyright notice,</DIV>
<DIV>this list of conditions and the following disclaimer in the
documentation</DIV>
<DIV>and/or other materials provided with the distribution.</DIV>
<DIV> </DIV>
<DIV>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND</DIV>
<DIV>ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED</DIV>
<DIV>WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE</DIV>
<DIV>DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
LIABLE</DIV>
<DIV>FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL</DIV>
<DIV>DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR</DIV>
<DIV>SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER</DIV>
<DIV>CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY,</DIV>
<DIV>OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE</DIV>
<DIV>OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
DAMAGE.</DIV>
<DIV> </DIV>
<DIV
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">Tim</DIV></DIV></DIV></DIV></BLOCKQUOTE></DIV></DIV></DIV></BLOCKQUOTE></DIV>
<DIV> </DIV></DIV></DIV></DIV></DIV></BODY></HTML>