<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Jody,<br>
<br>
See comments below...<br>
<pre class="moz-signature" cols="72">Best Regards,
Brent Fraser</pre>
<br>
On 1/11/2012 3:35 PM, Jody Garnett wrote:
<blockquote cite="mid:41CC744A3635406A8DA434F840B0A71C@gmail.com"
type="cite">
<div>Hi Brent - yes you are on the right track :-)</div>
<div><br>
</div>
<div> It may be best to do it as a team effort - depending on the
size of your code base (how big is your code base?) </div>
</blockquote>
I expect I'll need some help; I'll call for volunteers soon (or at
least opinions). Our code base isn't very large (now that we have a
strong dependency on OpenLayers): mainly 40-ish JavaScript files and
20 PHP files, along with some icons, templates, and other small data
components. But we also deliver a very important set of demo GIS
data, so that will have to be vetted as well.<br>
<br>
<blockquote cite="mid:41CC744A3635406A8DA434F840B0A71C@gmail.com"
type="cite">
<div><br>
</div>
<div>The plan here is to check what you distribute (software,
docs, data, etc..) and ensure we are doing it correctly. It is
not the case that we have to fix everything; we only want to
list (even in your issue tracker) any work that needs to be
done.</div>
<div><br>
</div>
<div>One of the things an organisation will do prior to using
GeoMOOSE is a legal review.</div>
<div><br>
</div>
<div>The foundation does not have a bucket of cash to hire a team
to do a legal review for all the projects. So we are trying for
the next best thing; produce a list of known problems as a good
starting place for a legal review.</div>
<div><br>
</div>
<div>A couple of ideas:</div>
<div>- Go through all your source code files (by hand) and check
that their headers are correct (this is often why it is a team
effort). For GeoTools we had some files without header
information which I had to check version control history on to
see who created them.</div>
</blockquote>
One issue is that we are currently in the process of creating
GeoMoose v2.6 (90% done?); we'll need to decide when to review the
code (at 100% in 6 weeks?). Or we can start now and do a final
check at release time. Not really a big deal since the code base is
small.<br>
<blockquote cite="mid:41CC744A3635406A8DA434F840B0A71C@gmail.com"
type="cite">
<div>-- What you are checking for depends on the project? I don't
know if you ask developers to assign the code to an
organisation? Or is each file considered separately?</div>
</blockquote>
Interesting question, causing more questions:<br>
What should the license text be? Currently it is the same
copyright text as Mapserver.<br>
Who (or what) should be assigned the copyright? Currently Dan
Little holds the copyright.<br>
<br>
<blockquote cite="mid:41CC744A3635406A8DA434F840B0A71C@gmail.com"
type="cite">
<div>- Check how you distribute your documentation? Creative
Commons?</div>
</blockquote>
While the Sphinx docs text files are included with the distribution,
I'm not sure why. I'd expect everyone to access the doc on line at
geomoose.org. Currently those doc files are covered with the same
copyright license file included with the source code (we may need
to change that).<br>
<br>
<blockquote cite="mid:41CC744A3635406A8DA434F840B0A71C@gmail.com"
type="cite">
<div>- Check any same data included with your application or
documentation. If you don't know where it came from I recommend
the natural earth dataset :-)</div>
</blockquote>
While some of the layers available at Natural Earth may be useful to
us, the focus of GeoMoose is with datasets at the county level,
especially parcel data. I expect we'll need to put some effort
into making sure we have the rights to distribute the data
(especially privacy issues w.r.t. parcel owner's name, etc). I'm
sure this was discussed long before I joined the project, but it
will be useful to include a statement somewhere in the project.<br>
<br>
Wow, this is a good start to our Review Document...<br>
<br>
<blockquote cite="mid:41CC744A3635406A8DA434F840B0A71C@gmail.com"
type="cite">
<div><br>
</div>
<div>-- <br>
Jody Garnett<br>
<div><br>
</div>
</div>
<p style="color: #A0A0A8;">On Wednesday, 11 January 2012 at 9:17
AM, Brent Fraser wrote:</p>
<blockquote type="cite"
style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span>
<div>
<div>
<meta content="text/html; charset=UTF-8"
http-equiv="Content-Type">
Jody,<br>
<br>
I can't remember if someone has volunteered for the Code
Provenance Review. If not, then I will. From the OSGEO
page (<a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Code_Provenance_Review">http://wiki.osgeo.org/wiki/Code_Provenance_Review</a>),
it looks like the task will produce a Review Document
(perhaps as an RFC?) containing:<br>
<br>
1. A list of external components and their license
status.<br>
2. A statement of the open source licensing of our
source code, with a list of discrepancies.<br>
3. Any other licensing issues needing to be addressed.<br>
<br>
Am I on the right track?<br>
<br>
<pre cols="72">Best Regards,
Brent Fraser</pre>
<br>
On 1/8/2012 12:48 AM, Jody Garnett wrote:
<blockquote type="cite">
<div>
<div> Afternoon: </div>
<div><br>
</div>
<div>I need to report back to the incubation committee
for the next meeting ().</div>
<div><br>
</div>
<div>I know we have a the status page:</div>
<div>- <a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/GeoMoose_Incubation_Status">http://wiki.osgeo.org/wiki/GeoMoose_Incubation_Status</a></div>
<div><br>
</div>
<div>Thus I have not seen anyone set up a code review?
Is this a case of everyone being on holidays; or is
it something I can help get started? </div>
<div>
<div><br>
</div>
-- <br>
Jody Garnett<br>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre wrap="">_______________________________________________
Geomoose-users mailing list
<a moz-do-not-send="true" href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a>
<a moz-do-not-send="true" href="http://lists.osgeo.org/mailman/listinfo/geomoose-users">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a>
</pre>
</div>
</blockquote>
</div>
</div>
</span> </blockquote>
<div> <br>
</div>
</blockquote>
</body>
</html>