[mapserver-dev] Suggestion: Add more documentation groups to trac

[Lime, Steve D (DNR)]

The documentation components look like this now:

Documentation - MapCache 
Documentation - MapScript
Documentation - MapServer
Documentation - mapserver.org
Documentation - TinyOWS

The MapServer and mapserver.org ones where created by renaming existing components. I didn't add the language specific ones yet since there was no obvious owner that I knew of.

Steve

-----Original Message-----
From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Daniel Morissette
Sent: Tuesday, January 24, 2012 12:34 PM
To: mapserver-dev at lists.osgeo.org
Subject: Re: [mapserver-dev] Suggestion: Add more documentation groups to trac

Works for me.


On 12-01-24 1:20 PM, Lime, Steve D (DNR) wrote:
> An objection if I set these up?
>
> Steve
>
> -----Original Message-----
> From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Alan Boudreault
> Sent: Tuesday, January 17, 2012 6:45 PM
> To: mapserver-dev at lists.osgeo.org
> Subject: Re: [mapserver-dev] Suggestion: Add more documentation groups to trac
>
> Great idea!
>
> Alan
>
> On 12-01-17 03:55 PM, Lime, Steve D (DNR) wrote:
>> I'm fine with this proposal. The input and output drivers follow a similar naming convention.
>>
>> Steve
>>
>> -----Original Message-----
>> From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Havard Tveite
>> Sent: Monday, January 16, 2012 4:17 AM
>> To: 'MapServer Dev Mailing List'
>> Subject: [mapserver-dev] Suggestion: Add more documentation groups to trac
>>
>> Dear MapServer developers (Jeff in particular),
>>
>> I think it would be useful to have more Mapserver Documentation
>> components in trac.  That way it would be easier to organise
>> tickets.  I raise the issue now that the MapServer project has
>> been extended with TinyOWS and MapCache, adding to the
>> complexity.
>>
>> I have been trying to help improve the MapServer documentation,
>> and I have found that it would be convenient for me to be able
>> to classify the documentation tickets a bit.
>> I have, for instance often only partly fixed MapServer tickets
>> by updating the documentation for "core" MapServer, leaving the
>> MapScript part to others.  In such cases, it would be nice to
>> be able to "clean the desk" by moving the ticket somewhere
>> else.
>> Trac components seem to be the most convenient way to handle
>> this.
>>
>> I would suggest that TinyOWS and MapCache get their own
>> documentation components.  I would also like to have a
>> new component for MapScript, and for the translations.
>> These are my suggestions for the new group of Mapserver
>> documentation components (I think it is a good idea to let
>> them all start with "Documentation", as that will make
>> them easy to find when filing tickets):
>>
>> Documentation - MapServer
>> Documentation - MapCache
>> Documentation - MapScript
>> Documentation - TinyOWS
>> Documentation - de
>> Documentation - fr
>> Documentation - cn
>>
>>
>> What do you say, Jeff?
>>
>> Håvard
>>
>
>


-- 
Daniel Morissette
http://www.mapgears.com/
Provider of Professional MapServer Support since 2000

_______________________________________________
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-dev