<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Yes it is absolutely the intent for the author to maintain the
copyright.<br>
<br>
Bob<br>
<br>
Jason Birch wrote:
<blockquote
cite="mid8E468917B01800408B91984428BE03DD05853115@starfish.nanaimo.ca"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta content="MSHTML 6.00.5730.11" name="GENERATOR">
<div dir="ltr" align="left"><span class="459581316-23012007"><font
color="#0000ff" face="Arial" size="2">I believe that we have a real
opportunity to take code that is free and clear, having been legally
transferred to OSGeo by the sole rights-owner, and keep in that way. </font></span></div>
<div dir="ltr" align="left"><span class="459581316-23012007"></span> </div>
<div dir="ltr" align="left"><span class="459581316-23012007"><font
color="#0000ff" face="Arial" size="2">I am 100% in support of
requiring contribution agreements, especially in light of differing
work-for-hire law in different countries.</font></span></div>
<div dir="ltr" align="left"><span class="459581316-23012007"></span> </div>
<div dir="ltr" align="left"><span class="459581316-23012007"><font
color="#0000ff" face="Arial" size="2">One thing of note is that the
contributor agreement does not appear to transfer copyright. I don't
think that this is necessarily a bad thing (for instance, authors
of large components like web studio, fusion, king.oracle and postgis
fdo providers have a right to maintain their copyright so that they can
repurpose at a later date), just wanted to clarify if it's what we want.</font></span></div>
<div dir="ltr" align="left"><span class="459581316-23012007"></span><span
class="459581316-23012007"></span> </div>
<div dir="ltr" align="left"><span class="459581316-23012007"><font
color="#0000ff" face="Arial" size="2">Jason</font></span></div>
<br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:mapguide-internals-bounces@lists.osgeo.org">mapguide-internals-bounces@lists.osgeo.org</a>
[<a class="moz-txt-link-freetext" href="mailto:mapguide-internals-bounces@lists.osgeo.org">mailto:mapguide-internals-bounces@lists.osgeo.org</a>] <b>On Behalf Of </b>Robert
Bray<br>
<b>Sent:</b> Monday, January 22, 2007 21:56<br>
<b>To:</b> MapGuide Internals Mail List<br>
<b>Subject:</b> [mapguide-internals] PSC: Contributor Agreements<br>
</font><br>
</div>
One of the final things we need to do for graduation is deal with code
contribution. The legal team here strongly recommends the use of a
Contribution Agreement to protect both the foundation and the
developers. All developers with commit access would need to sign the
Contributor Agreement form and send/fax it to OSGeo before commit
access could be granted/continued. A fairly good FAQ on contribution
agreements can be found here: <a
href="http://wiki.osgeo.org/index.php/Contributor_Agreement">http://wiki.osgeo.org/index.php/Contributor_Agreement</a>.
<br>
<br>
The proposed contributor agreement can be found here: <a
href="http://mapguide.osgeo.org/files/Individual%20Contributor%20Agreement.pdf">http://mapguide.osgeo.org/files/Individual%20Contributor%20Agreement.pdf.</a>
This agreement was originally put together by Rich Steele and was
recently vetted again by our legal team.<br>
<br>
Please read both over and let me know what you think. This is another
item I would like to bring to motion this week.<br>
<br>
Bob<br>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
mapguide-internals mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mapguide-internals@lists.osgeo.org">mapguide-internals@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/mapguide-internals">http://lists.osgeo.org/mailman/listinfo/mapguide-internals</a>
</pre>
</blockquote>
<br>
</body>
</html>