<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">As far as licenses, you might consider:<DIV><BR class="khtml-block-placeholder"></DIV><DIV>Open Source Initiative (OSI <A href="http://www.opensource.org">http://www.opensource.org</A>/ ) licenses are approved for applications and Creative Commons(CC <A href="http://creativecommons.org">http://creativecommons.org</A>/ ) for other data, documentation, images, media, and others not covered by a project's chosen OSI license. Any other non OSI or CC license use by a project requires a consensus approval by the board on a project owner's request. The board may add licenses to the approved licenses available to all projects with a consensus vote.<DIV><DIV> </DIV><DIV>This would allow you to set expectations in general and allow for a simple approval by the board for other cases. This also allows the board to add a license to the set if there is a specific license you find is prevalent for a type of data or existing software. </DIV><DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>Daniel Brookshier</DIV><DIV>Community Manager </DIV><DIV><A href="https://www.projects.dev2dev.bea.com">https://www.projects.dev2dev.bea.com</A>/</DIV><DIV><A href="mailto:turbogeek@cluck.com">turbogeek@cluck.com</A></DIV><DIV><A href="mailto:dbrookshier@collab.net">dbrookshier@collab.net</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>This e-mail and any files transmitted with it are for the sole use of the intended recipient(s)</DIV><DIV>and may contain confidential and privileged information.</DIV><BR class="Apple-interchange-newline"></SPAN></SPAN></SPAN></SPAN> </DIV><BR><DIV><DIV>On Feb 26, 2006, at 9:27 AM, Markus Neteler wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite">On 2/23/06, <B class="gmail_sendername">Frank Warmerdam</B> <<A href="mailto:warmerdam@pobox.com">warmerdam@pobox.com</A>> wrote:<DIV><SPAN class="gmail_quote"></SPAN><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Arnulf Christl (CCGIS) wrote:<BR>> Spatial data is somewhat special in this respect. I talked to Jimmy Wales<BR>> Richard Stallman they think GNU FDL is good. Ward Cunningham is into CC,<BR>> and says its cool for spatial data too obviously. <BR>><BR>> I am not sure though. Daniel Faivre (camptocamp) is very actively<BR>> promoting a license specially designed to fit spatial data backed by an<BR>> active Canadian group, they call it PGL. I believe Jo has something up the <BR>> sleeve too and OSM is also thinking in this line. All of them are highly<BR>> interested in the OSGeo (well, dunno about OSM, they are sort of sleepy)<BR>> and it might happen that the Foundation itself will be the body creating <BR>> this special license. In the end this is one of the things that we came<BR>> together to do here. What I want to say is that we do not have to choose<BR>> from different licenses but maybe set out to create one. <BR><BR>Arnulf / Markus,<BR><BR>At one point I proposed that the requirement our software projects use<BR>OSI approved licenses be written into the bylaws with the intent that it<BR>would not be easy for a board to contemplate changing any "copyright assigned" <BR>software to a non-OSI license. That is, as a sort of limitation on the board<BR>and the foundation.</BLOCKQUOTE><DIV><BR> <BR> Frank,<BR> <BR> I was refering to data etc, not to software. I am fine with our statement according<BR> to software (OSI approved licenses). <BR> </DIV><BR><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Since we haven't worked out details of what license(s) are necessary best<BR>for various kinds of "content" or spatial data, I would suggest we not try to <BR>address this in the bylaws at this time. As has been done, it is useful to<BR>make clear in the bylaws that the OSI approval requirement is for software.</BLOCKQUOTE><DIV><BR> (sure; but I was talking data :-)<BR> </DIV><BR><BLOCKQUOTE class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Certainly, I would like to see discussion about appropriate licenses for<BR>web/educational/promotional materials and spatial data. But there is not <BR>yet much clarity on the topic.</BLOCKQUOTE><DIV><BR> Agreed. There no widely accepted spatial data license yet. I just wanted to<BR> avoid that things are mixed with software licenses which won't work.<BR> For written texts and promotional material the CC licenses seem to work<BR> well, so there is less of a problem.<BR> </DIV></DIV><BR> My issue was only to not limit the bylaws to only talk about software which<BR> seems to be the case. No need to hard-code and license there, just be open<BR> to not *exclude* any future license which may be applicable.<BR> <BR> Markus<BR></BLOCKQUOTE></DIV><BR></DIV></DIV></DIV></BODY></HTML>