<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Jody,<br>
<br>
El 06/08/15 a las 08:17, Jody Garnett escribió:<br>
</div>
<blockquote
cite="mid:CAOhbgA=Obn+BWVfmJc+BeWi0wv2GwOVv6p_TdxvJb21AHEcHNg@mail.gmail.com"
type="cite">
<pre wrap="">So yeah, once again if you can update the checklist - and hopefully other
members of the commit can jump in here (those that are not on summer
vacation).</pre>
</blockquote>
We've updated the wiki already, adding the link to “provenance
review”.<br>
<blockquote
cite="mid:CAOhbgA=Obn+BWVfmJc+BeWi0wv2GwOVv6p_TdxvJb21AHEcHNg@mail.gmail.com"
type="cite">
<pre wrap="">
My initial impression is that gvSig has gone above and beyond the call of
duty in isolating external code into a seperate play area. Open source
licenses do allow for copy-and-paste (as long as the headers are clear). It
should however make things clear, and perhaps be easier to maintain going
forward
</pre>
</blockquote>
In reference to your comment about the "extremism" in separating
source code...
<br>
:-)
<br>
<br>
It's not that we have been extreme in separating the external source
code, not always it has been at this way, only when we have
considered it relevant when using big blocks of external code.
Instead of being embedded, we consider it's better to have it
separately, link to it and use it. Concretelly, following the
“Provenance Review” link they would be: Jedit, JUMP, Raven and jdk.
This source code is used until gvSIG 2.1. From then we only use
JDK.
<br>
<br>
But in the other cases, when there are a few functions with external
code, we haven't extracted them to an external project, and as you
say we have used them keeping the headers. Following the “Provenance
Review” link, they would be the listed ones from the “Apart from
this, there is still external source code in the following modules
inside the project:...” paragraph (I don't copy the list here for
not to make the mail longer).
<br>
<br>
In summary, when they are little things we keep them in our source
code, and when they are big things we have extracted them.
<br>
<br>
Thank you very much for your comments, and I hope the questions are
clear now.
<br>
:-)<br>
<br>
Best,<br>
Alvaro<br>
<blockquote
cite="mid:CAOhbgA=Obn+BWVfmJc+BeWi0wv2GwOVv6p_TdxvJb21AHEcHNg@mail.gmail.com"
type="cite">
<pre wrap="">
--
Jody Garnett
On 5 August 2015 at 22:40, Manuel Madrid <a class="moz-txt-link-rfc2396E" href="mailto:mmadrid@gvsig.com"><mmadrid@gvsig.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Jody,
Yes, that's the correct link.
Regards,
Manuel.
On 05/08/15 23:29, Jody Garnett wrote:
Quick question, looking for a link to the code providence review.
3. The project code, documentation and data has been adequately vetted to
</pre>
<blockquote type="cite">
<pre wrap="">assure it is all properly licensed, and a copyright notice included, as per
a Provenance Review. *Yes. All the information is vetted before
publishing (manuals, source code, cartography...).*
4. The project maintains a list of all copyright holders identified in
the Provenance Review Document.* No, as all the source code is owned by
the gvSIG Association. All the developers have signed the CLA
(<a class="moz-txt-link-freetext" href="http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status">http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status</a>
<a class="moz-txt-link-rfc2396E" href="http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status"><http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status></a>).*
</pre>
</blockquote>
<pre wrap="">
Checking the osgeo wiki links me ...
- <a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/GvSIG_Provenance_Review">http://wiki.osgeo.org/wiki/GvSIG_Provenance_Review</a>
Which links me to ...
-
<a class="moz-txt-link-freetext" href="http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/provenance-review">http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/provenance-review</a>
Is this the correct link I should be reviewing? Looks like it was modified
on "13/06/2015"...
Jody
--
Jody Garnett
On 28 July 2015 at 04:27, Dimitris Kotzinos <a class="moz-txt-link-rfc2396E" href="mailto:kotzino@gmail.com"><kotzino@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear all,
I am happy today to report to the list that the gvSIG project has
fulfilled in my view all the criteria put forward by the OSGeo
Incubation Committee and as the project mentor I support the project's
request for graduation.
gvSIG is one of the healthiest and very active projects around, with a
solid developer and user base. It has been around for a long time and
has done excellent things, the latest being an award at the NASA World
Wind contest received in FOSS4G-Europe in Como, Italy this month.
I had the chance to meet with the gvSIG people at FOSS4G-E in Como and
we finalized the checklist for the project graduation. You can find the
checklist here:
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/GvSIG_Incubation_Checklist">http://wiki.osgeo.org/wiki/GvSIG_Incubation_Checklist</a>
The people around gvSIG have responded greatly to all the requests I
made as a mentor, they have gone even beyond that in many occasions,
e.g. by providing live statistics on their developers' activity.
They have gone through a code provenance review, they have user and
developer lists in many languages and they have in place governance
practices that abide with what I would consider proper governance of
open source projects.
I would like to ask the list to take the time and have a look to the
checklist mentioned above and if anything is found out of the order
please let me and Manuel Madrid <a class="moz-txt-link-rfc2396E" href="mailto:mmadrid@gvsig.com"><mmadrid@gvsig.com></a> know.
I would also like to ask Jody to initiate the proper time period for
comments and declare the time for voting when the time comes.
Finally I would like to thank Manuel and Alvaro from the gvSIG
Association for their excellent collaboration and to publicly apologize
to them that sometimes the work load prohibited me to be as available
and responsive as I would like.
Thank you for your attention,
Best regards,
Dimitris
P.S.1: Although the project has made a great effort to provide English
documentation for ... everything, some things might be found in Spanish
(their language of origin), as well as some of the most active lists are
the Spanish ones. I respected that and I let the project take its time
and decide by itself on what to translate and what not.
But I would like to say kudos on their efforts to provide everything in
at least both Spanish and English.
P.S.2: Since during the process we had to switch from the checklist
v.1.0 to v.2.0 of graduation requirements I was wondering what is the
proper way to introduce comments and requests for changes for this.
--
Dimitris Kotzinos
Professor
Head MIDI team
Lab. ETIS (ENSEA/UCP/CNRS UMR 8051)
& Dept. Sciences Informatiques, Université de Cergy-Pontoise
2 av. Adolphe Chauvin
Site Saint Martin, bureau A561
95000 Pontoise
France
phone: +33 13425 2855
e-mail: <a class="moz-txt-link-abbreviated" href="mailto:Dimitrios.Kotzinos@u-cergy.fr">Dimitrios.Kotzinos@u-cergy.fr</a>
_______________________________________________
Incubator mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Incubator@lists.osgeo.org">Incubator@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/incubator">http://lists.osgeo.org/mailman/listinfo/incubator</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Incubator mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Incubator@lists.osgeo.org">Incubator@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/incubator">http://lists.osgeo.org/mailman/listinfo/incubator</a></pre>
</blockquote>
<br>
</body>
</html>