[Live-demo] Planing Roadmap in OSGeo Trac for Live Project

Cameron Shorter cameron.shorter at gmail.com
Mon Apr 2 13:58:56 PDT 2012


I'm open to moving OSGeo-Live Subversion and TRAC into their own instance.

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?

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.

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: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Issue_Tracker

Issue Tracker

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:

Component field
     Set to `LiveDVD`
Keywords
     Version: Set to base release version: eg: 5.0, 5.5 (not 5.5rc1)
     Application: Set to application with issue (use lower case): eg: 
"geoserver"


On 02/04/12 21:17, Daniel Kastl wrote:
> I agree with what Frank and Angelos said.
> 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: https://trac.osgeo.org/
> I don't know how difficult it is though to do the changes.
>
> Daniel
>
>
> On Mon, Apr 2, 2012 at 7:25 PM, Angelos Tzotsos <gcpp.kalxas at gmail.com 
> <mailto:gcpp.kalxas at gmail.com>> wrote:
>
>     On 04/02/2012 12:42 PM, Frank Gasdorf wrote:
>
>         Hallo List,
>
>         Is it possible to define several milestones for the osgeo live
>         project
>         in Trac. IMHO its a good way to coordinate several activities and
>         committers. In addition we can use Milestones to write down
>         release
>         notes and included tickets for bugs enhancements and tasks. An
>         other
>         PRO is to the change to link bugs to the relevant released
>         version.
>
>         What do you think about defining a new Milestone 'OSGeo Live
>         6.0' and
>         a version 'OSGeo Live 5.5' right here :
>         http://trac.osgeo.org/osgeo/admin/ticket/versions (maybe for
>         the older
>         releases as well (5.0, 4.5))
>
>         If anybody got bug reports or have other issues with the
>         current or
>         prior release we could associate the bugs to the matching version.
>
>         What do you think about such a management improvement? I could
>         help
>         defining and managing such milestones. Properly we could plan
>         a next
>         release on IRC and put relevant issues/tasks into the basket.
>
>         What do you think about coordinate translations with such
>         Trac-tasks
>         instead of an wiki-Page
>         (http://wiki.osgeo.org/wiki/Talk:Live_GIS_Translate). IMHO its
>         quite
>         easy to assign tickets to myself and everybody have a clue
>         whats in
>         the pipeline and who is working on. And properly who needs help to
>         finish tasks for an upcoming release.
>
>         Feedback is warmly wellcome
>
>         Cheers
>         Frank
>         _______________________________________________
>         Live-demo mailing list
>         Live-demo at lists.osgeo.org <mailto:Live-demo at lists.osgeo.org>
>         http://lists.osgeo.org/mailman/listinfo/live-demo
>         http://live.osgeo.org
>         http://wiki.osgeo.org/wiki/Live_GIS_Disc
>
>     Hi Frank,
>
>     I agree that we should use Trac in more depth for our 6.0 development.
>     We also have to clear old bug reports and associate them with the
>     latest release, as you suggest.
>
>     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.
>
>     Cheers,
>     Angelos
>
>
>     -- 
>     Angelos Tzotsos
>     Remote Sensing Laboratory
>     National Technical University of Athens
>     http://users.ntua.gr/tzotsos
>
>     _______________________________________________
>     Live-demo mailing list
>     Live-demo at lists.osgeo.org <mailto:Live-demo at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/live-demo
>     http://live.osgeo.org
>     http://wiki.osgeo.org/wiki/Live_GIS_Disc
>
>
>
>
> -- 
> Georepublic UG & Georepublic Japan
> eMail: daniel.kastl at georepublic.de <mailto:daniel.kastl at georepublic.de>
> Web: http://georepublic.de <http://georepublic.de/>
>
>
> _______________________________________________
> Live-demo mailing list
> Live-demo at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/live-demo
> http://live.osgeo.org
> http://wiki.osgeo.org/wiki/Live_GIS_Disc


-- 
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
http://www.lisasoft.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/osgeolive/attachments/20120403/9bf58f9e/attachment.html>


More information about the Osgeolive mailing list