<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 24/09/13 05:35, Paolo Cavallini
wrote:<br>
</div>
<blockquote cite="mid:52409818.60903@faunalia.it" type="cite">
<pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 23/09/2013 20:46, Cameron Shorter ha scritto:
</pre>
<blockquote type="cite">
<pre wrap="">From what I can gather from the outside, it seems osgeo4w's primary requirement is a
1+ dedicated developer(s) who will drive the core functions of the project. Namely,
setting a release schedule, chasing developers for contributions, triaging bug lists,
etc. This can be done with or without a PSC or official OSGeo endorsement.
</pre>
</blockquote>
<pre wrap="">
I slightly disagree with this: what we mainly need IMHO is a clear direction, and
therefore a mechanism to take decisions (e.g. the approach from Tamas is quite
interesting, and different from the current one; Mateusz has suggested an alternative
route; etc.).
When there is a reliable roadmap, I think resources (time~money) can be found from
our Windows user base.</pre>
</blockquote>
Paulo,<br>
Your comments are valid. I should extend my suggestion to state that<br>
"OSGeo4W's primary value would be gained from a developer, or team
of developers, to clearly define the project's goals, direction and
scope, including defining the packaging technologies and processes
to use. This would need to be followed through with the hard work of
implementation and verification of this stack of software."<br>
<br>
I agree, that a PSC would be a valuable way to manage an OSGeo4W
project.<br>
<br>
For OSGeo-Live, we defined our primary scope and technology
principles here:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://wiki.osgeo.org/wiki/Live_GIS_Add_Project">http://wiki.osgeo.org/wiki/Live_GIS_Add_Project</a><br>
<br>
This OSGeo-Live presentation might also be of interest:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://cameronshorter.blogspot.com/2011/06/memoirs-of-cat-herder-coordinating.html">http://cameronshorter.blogspot.com/2011/06/memoirs-of-cat-herder-coordinating.html</a><br>
</body>
</html>