<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm open to moving OSGeo-Live Subversion and TRAC into their own
instance.<br>
<br>
We last visited this question a few years back, and have set up our
current setup based upon Frank Warmerdam's recommendation. FrankW,
do you wish to weigh in on this thread?<br>
<br>
Re: coordinating translations. I'd still like to use our Google Docs
spreadsheet. We have some magic formulas in these spreadsheets we
are using to compare subversion version numbers to determine if a
doc is translated or not, which would be hard to emulate in trac.<br>
<br>
Re: using the issue tracker. We do use track, and I'm open to
improving our use of it. Our current process includes tagging
releases, as described here:
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker">http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker</a><br>
<br>
Issue Tracker<br>
<br>
Our issue tracker is hosted at OSGeo's Trac system, and you will
need to create an OSGeo UserId before you can login and edit issues.
To distinguish the LiveDVD project from other OSGeo projects, use
the following conventions:<br>
<br>
Component field<br>
Set to `LiveDVD` <br>
Keywords<br>
Version: Set to base release version: eg: 5.0, 5.5 (not 5.5rc1)
<br>
Application: Set to application with issue (use lower case): eg:
"geoserver" <br>
<br>
<br>
On 02/04/12 21:17, Daniel Kastl wrote:
<blockquote
cite="mid:CABXBSH9jcKHb+g+c0ZrHibYp0oKn=UvWB_7KKXVGCAu4urNANQ@mail.gmail.com"
type="cite">I agree with what Frank and Angelos said.
<div>It could be also a good idea to move the OSGeo Live project
to its own SVN repository and TRAC instance. Currently it uses
the "osgeo" repository and TRAC, but I think it would better fit
into this list as a separate project: <a moz-do-not-send="true"
href="https://trac.osgeo.org/">https://trac.osgeo.org/</a></div>
<div>I don't know how difficult it is though to do the changes.</div>
<div><br>
</div>
<div>Daniel</div>
<div><br>
<br>
<div class="gmail_quote">On Mon, Apr 2, 2012 at 7:25 PM, Angelos
Tzotsos <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:gcpp.kalxas@gmail.com">gcpp.kalxas@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
04/02/2012 12:42 PM, Frank Gasdorf wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hallo List,<br>
<br>
Is it possible to define several milestones for the osgeo
live project<br>
in Trac. IMHO its a good way to coordinate several
activities and<br>
committers. In addition we can use Milestones to write
down release<br>
notes and included tickets for bugs enhancements and
tasks. An other<br>
PRO is to the change to link bugs to the relevant released
version.<br>
<br>
What do you think about defining a new Milestone 'OSGeo
Live 6.0' and<br>
a version 'OSGeo Live 5.5' right here :<br>
<a moz-do-not-send="true"
href="http://trac.osgeo.org/osgeo/admin/ticket/versions"
target="_blank">http://trac.osgeo.org/osgeo/admin/ticket/versions</a>
(maybe for the older<br>
releases as well (5.0, 4.5))<br>
<br>
If anybody got bug reports or have other issues with the
current or<br>
prior release we could associate the bugs to the matching
version.<br>
<br>
What do you think about such a management improvement? I
could help<br>
defining and managing such milestones. Properly we could
plan a next<br>
release on IRC and put relevant issues/tasks into the
basket.<br>
<br>
What do you think about coordinate translations with such
Trac-tasks<br>
instead of an wiki-Page<br>
(<a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Talk:Live_GIS_Translate"
target="_blank">http://wiki.osgeo.org/wiki/Talk:Live_GIS_Translate</a>).
IMHO its quite<br>
easy to assign tickets to myself and everybody have a clue
whats in<br>
the pipeline and who is working on. And properly who needs
help to<br>
finish tasks for an upcoming release.<br>
<br>
Feedback is warmly wellcome<br>
<br>
Cheers<br>
Frank<br>
_______________________________________________<br>
Live-demo mailing list<br>
<a moz-do-not-send="true"
href="mailto:Live-demo@lists.osgeo.org" target="_blank">Live-demo@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/live-demo"
target="_blank">http://lists.osgeo.org/mailman/listinfo/live-demo</a><br>
<a moz-do-not-send="true" href="http://live.osgeo.org"
target="_blank">http://live.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Live_GIS_Disc"
target="_blank">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a><br>
<br>
</blockquote>
Hi Frank,<br>
<br>
I agree that we should use Trac in more depth for our 6.0
development.<br>
We also have to clear old bug reports and associate them
with the latest release, as you suggest.<br>
<br>
For the coordination of translations though I think the
current tools serve us well, since each language is
maintained by separate teams, so we do not need to put much
details in Trac (this would require enough effort). If you
just mean to track milestones for translations (eg Overviews
completeness, Quickstart completeness, sync of each language
with trunk english documents etc) then +1 from me.<br>
<br>
Cheers,<br>
Angelos<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
-- <br>
Angelos Tzotsos<br>
Remote Sensing Laboratory<br>
National Technical University of Athens<br>
<a moz-do-not-send="true"
href="http://users.ntua.gr/tzotsos" target="_blank">http://users.ntua.gr/tzotsos</a><br>
<br>
_______________________________________________<br>
Live-demo mailing list<br>
<a moz-do-not-send="true"
href="mailto:Live-demo@lists.osgeo.org"
target="_blank">Live-demo@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/live-demo"
target="_blank">http://lists.osgeo.org/mailman/listinfo/live-demo</a><br>
<a moz-do-not-send="true" href="http://live.osgeo.org"
target="_blank">http://live.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://wiki.osgeo.org/wiki/Live_GIS_Disc"
target="_blank">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a><br>
</font></span></blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<span
style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse">Georepublic
UG & Georepublic Japan<br>
eMail: <a moz-do-not-send="true"
href="mailto:daniel.kastl@georepublic.de"
style="color:rgb(66,99,171)" target="_blank">daniel.kastl@georepublic.de</a><br>
Web: <a moz-do-not-send="true" href="http://georepublic.de/"
style="color:rgb(66,99,171)" target="_blank">http://georepublic.de</a></span><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Live-demo mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Live-demo@lists.osgeo.org">Live-demo@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/live-demo">http://lists.osgeo.org/mailman/listinfo/live-demo</a>
<a class="moz-txt-link-freetext" href="http://live.osgeo.org">http://live.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/Live_GIS_Disc">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Geospatial Solutions Manager
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254
Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
<a class="moz-txt-link-freetext" href="http://www.lisasoft.com">http://www.lisasoft.com</a>
</pre>
</body>
</html>