<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Daniel,<br>
<br>
El 10/09/15 a las 04:12, Daniel Morissette escribió:<br>
</div>
<blockquote cite="mid:55F0E6FD.4030602@mapgears.com" type="cite">Dear
All,
<br>
<br>
I started looking into the gvSIG incubation checklist at
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/GvSIG_Incubation_Checklist">http://wiki.osgeo.org/wiki/GvSIG_Incubation_Checklist</a> and am
having a hard time tracking down info about the Technical Steering
Committee.
<br>
<br>
The checklist points to
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/GvSIG_Technical_Steering_Committee">http://wiki.osgeo.org/wiki/GvSIG_Technical_Steering_Committee</a>
which in turn points to two broken links for the
[<a class="moz-txt-link-freetext" href="https://gvsig.org/web/working-groups/organizacion">https://gvsig.org/web/working-groups/organizacion</a> gvSIG TSC front
page] and
[<a class="moz-txt-link-freetext" href="https://lists.forge.osor.eu/listinfo/gvsig-desktop-tsc-pub">https://lists.forge.osor.eu/listinfo/gvsig-desktop-tsc-pub</a> public
mailing list]
<br>
<br>
Can you please review the Incubation Checklist page (and the pages
that it links to) and make sure all links are working? I'd like to
see archives of the TSC mailing list showing that decisions are
indeed made in an open manner and in collaboration with the
community on a public list and I cannot find that at the moment. I
managed to find an old TSC archive at
<a class="moz-txt-link-freetext" href="http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub">http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub</a>
but the most recent posts date from 2013.
<br>
</blockquote>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">Thank
you for the feedback!. <br>
You are completely right. In its day, that part
was reviewed and accepted already, so we complete the reviewing
tasks
that were pending. And right, there has been enough time to evolve
the management of that part. </p>
<p style="margin-bottom: 0cm; line-height: 100%"><span lang="en-US">Such
was
the case that we didn't pay attention to these links, and with
the new gvSIG website </span><span lang="en-US">(</span><a
href="http://www.gvsig.org/"><a class="moz-txt-link-abbreviated" href="http://www.gvsig.org">www.gvsig.org</a></a><span lang="en-US">),
</span><span lang="en-US">to consult the contents of the old
website,
the text “docs” has to be added to the URL. For example, the
link (</span><a
href="https://docs.gvsig.org/web/working-groups/organizacion"><a class="moz-txt-link-freetext" href="https://gvsig.org/web/working-groups/organizacion">https://gvsig.org/web/working-groups/organizacion</a></a><span
lang="en-US">)</span><span lang="en-US">
</span><span lang="en-US">would be</span><span lang="en-US">:</span></p>
<p style="margin-bottom: 0cm; line-height: 100%"><a
href="http://docs.gvsig.org/web/working-groups/organizacion"><span
lang="en-US"><a class="moz-txt-link-freetext" href="http://docs.gvsig.org/web/working-groups/organizacion">http://docs.gvsig.org/web/working-groups/organizacion</a></span></a></p>
<p style="margin-bottom: 0cm; line-height: 100%"><span lang="en-US">With
the
advance of the project we have been correcting issues that we
think they make us to be more efficient. Efficient in the
meaning of
eliminating the bureaucratic parts and speed up the decision
making.
It has also been possible, in a big part, thank to the
professional
structure of the project who works daily for the project. It can
be
different to other projects. It makes that the day-to-day
decisions
can be made by people of the professional structure (there's an
architecture and development manager, and a product manager).
The
efficacy has been notable, and having a meeting every week to
make
small decisions didn't make as much as sense. It is thank to the
professional structure that can dedicate </span><span
lang="en-US">all
the time to gvSIG. </span>
</p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">And
the
TSC, that is composed of the main developers that are working on
gvSIG, has a meeting after every final version in order to make
decisions for the next version. Currently it is planned to release
2
versions per year (one version in May and another one in
December),
although this year it has been an exception because we will
release
three versions (gvSIG 2.3 will be released in December). At that
meeting it is decided what to work on for the next version. For
example, for gvSIG 2.3, the next version, it's panned to make the
effort to have a first distribution for MAC OS X and Windows 64
bits.
It involves to change libraries for raster accessing and
projections
mainly... and we are working on it now. </p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">And
instead of having proceedings, we preferred to advance one more
step
and publish the decisions publicly, because the proceedings are
not
read by a lot of people. Concretely in our blog. At this way,
following the example of gvSIG 2.3, we announced that decision
(this
is the link in English but it was published in Spanish too): </p>
<p style="margin-bottom: 0cm; line-height: 100%"><a
href="http://blog.gvsig.org/2015/06/25/on-the-road-to-gvsig-2-3/"><span
lang="en-US"><a class="moz-txt-link-freetext" href="http://blog.gvsig.org/2015/06/25/on-the-road-to-gvsig-2-3/">http://blog.gvsig.org/2015/06/25/on-the-road-to-gvsig-2-3/</a></span></a></p>
<p style="margin-bottom: 0cm; line-height: 100%"><span lang="en-US">Of
course
it doesn't mean that gvSIG includes only these changes. We
have to include all the possible functionalities developed by
the
community that are integrated with that version (but it's out of
the
initial planning and the </span><span lang="en-US">gvSIG scope
of
decision). </span>
</p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">And
there's also some decisions about some objectives at these
meetings
that are not carried out at the next version. It is listed at the
gvSIG redmine, at the “whislist” option -the access to this list
is also public-:</p>
<p style="margin-bottom: 0cm; line-height: 100%"><a
href="https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues?utf8=%3F&set_filter=1&f[]=status_id&op[status_id]=o&f[]=tracker_id&op[tracker_id]=%3D&v[tracker_id][]=11&f[]=&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=assigned_to&c[]=updated_on&group_by"><a class="moz-txt-link-freetext" href="https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues?utf8=%E2%9C%93&set_filter=1&f">https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues?utf8=%E2%9C%93&set_filter=1&f</a>[]=status_id&op[status_id]=o&f[]=tracker_id&op[tracker_id]=%3D&v[tracker_id][]=11&f[]=&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=assigned_to&c[]=updated_on&group_by</a><span
lang="en-US">=</span></p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US"><b>In
summary:</b></p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">We can
correct these links, adding “docs”, but it wouldn't make much
sense because now we work in another way, although it was reviewed
then. It's another way that I think it is more open and agile. </p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">We
would be able to summarize the information of this e-mail and add
it
to the checklist.</p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US"><br>
</p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">And
thank you again for reviewing our job!</p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">Alvaro
Anguix</p>
<p style="margin-bottom: 0cm; line-height: 100%" lang="en-US">gvSIG
Association<br>
<br>
</p>
<title></title>
<meta name="generator" content="LibreOffice 4.2.8.2 (Linux)">
<style type="text/css">
<!--
@page { margin: 2cm }
p { margin-bottom: 0.25cm; line-height: 120% }
a:link { so-language: zxx }
-->
</style>
<blockquote cite="mid:55F0E6FD.4030602@mapgears.com" type="cite">
<br>
Thanks
<br>
<br>
Daniel
<br>
<br>
<br>
<br>
On 2015-08-11 1:07 PM, Jody Garnett wrote:
<br>
<blockquote type="cite">General call out to the committee to help
review on this one :)
<br>
<br>
--
<br>
Jody Garnett
<br>
<br>
On 28 July 2015 at 04:27, Dimitris Kotzinos
<<a class="moz-txt-link-abbreviated" href="mailto:kotzino@gmail.com">kotzino@gmail.com</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:kotzino@gmail.com"><mailto:kotzino@gmail.com></a>> wrote:
<br>
<br>
Dear all,
<br>
<br>
I am happy today to report to the list that the gvSIG
project has
<br>
fulfilled in my view all the criteria put forward by the
OSGeo
<br>
Incubation Committee and as the project mentor I support the
project's
<br>
request for graduation.
<br>
gvSIG is one of the healthiest and very active projects
around, with a
<br>
solid developer and user base. It has been around for a long
time and
<br>
has done excellent things, the latest being an award at the
NASA World
<br>
Wind contest received in FOSS4G-Europe in Como, Italy this
month.
<br>
<br>
I had the chance to meet with the gvSIG people at FOSS4G-E
in Como and
<br>
we finalized the checklist for the project graduation. You
can find the
<br>
checklist here:
<br>
<br>
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/GvSIG_Incubation_Checklist">http://wiki.osgeo.org/wiki/GvSIG_Incubation_Checklist</a>
<br>
<br>
The people around gvSIG have responded greatly to all the
requests I
<br>
made as a mentor, they have gone even beyond that in many
occasions,
<br>
e.g. by providing live statistics on their developers'
activity.
<br>
They have gone through a code provenance review, they have
user and
<br>
developer lists in many languages and they have in place
governance
<br>
practices that abide with what I would consider proper
governance of
<br>
open source projects.
<br>
<br>
I would like to ask the list to take the time and have a
look to the
<br>
checklist mentioned above and if anything is found out of
the order
<br>
please let me and Manuel Madrid <<a class="moz-txt-link-abbreviated" href="mailto:mmadrid@gvsig.com">mmadrid@gvsig.com</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:mmadrid@gvsig.com"><mailto:mmadrid@gvsig.com></a>> know.
<br>
I would also like to ask Jody to initiate the proper time
period for
<br>
comments and declare the time for voting when the time
comes.
<br>
<br>
Finally I would like to thank Manuel and Alvaro from the
gvSIG
<br>
Association for their excellent collaboration and to
publicly apologize
<br>
to them that sometimes the work load prohibited me to be as
available
<br>
and responsive as I would like.
<br>
<br>
Thank you for your attention,
<br>
Best regards,
<br>
<br>
Dimitris
<br>
<br>
P.S.1: Although the project has made a great effort to
provide English
<br>
documentation for ... everything, some things might be found
in Spanish
<br>
(their language of origin), as well as some of the most
active lists are
<br>
the Spanish ones. I respected that and I let the project
take its time
<br>
and decide by itself on what to translate and what not.
<br>
But I would like to say kudos on their efforts to provide
everything in
<br>
at least both Spanish and English.
<br>
<br>
P.S.2: Since during the process we had to switch from the
checklist
<br>
v.1.0 to v.2.0 of graduation requirements I was wondering
what is the
<br>
proper way to introduce comments and requests for changes
for this.
<br>
<br>
<br>
--
<br>
Dimitris Kotzinos
<br>
Professor
<br>
Head MIDI team
<br>
Lab. ETIS (ENSEA/UCP/CNRS UMR 8051)
<br>
& Dept. Sciences Informatiques, Université de
Cergy-Pontoise
<br>
2 av. Adolphe Chauvin
<br>
Site Saint Martin, bureau A561
<br>
95000 Pontoise
<br>
France
<br>
phone: +33 13425 2855
<br>
e-mail: <a class="moz-txt-link-abbreviated" href="mailto:Dimitrios.Kotzinos@u-cergy.fr">Dimitrios.Kotzinos@u-cergy.fr</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:Dimitrios.Kotzinos@u-cergy.fr"><mailto:Dimitrios.Kotzinos@u-cergy.fr></a>
<br>
_______________________________________________
<br>
Incubator mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Incubator@lists.osgeo.org">Incubator@lists.osgeo.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Incubator@lists.osgeo.org"><mailto:Incubator@lists.osgeo.org></a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/incubator">http://lists.osgeo.org/mailman/listinfo/incubator</a>
<br>
<br>
<br>
<br>
<br>
_______________________________________________
<br>
Incubator mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Incubator@lists.osgeo.org">Incubator@lists.osgeo.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/incubator">http://lists.osgeo.org/mailman/listinfo/incubator</a>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>