[mapserver-dev] github and Mapserver documentation
Havard Tveite
havard.tveite at umb.no
Mon Nov 5 08:38:04 PST 2012
I would prefer having them in docs.
Håvard
On 11/5/2012 5:13 PM, thomas bonfort wrote:
> huh, I misunderstood what option b) really was. I'm fine with opening new documentation issues, be they in docs/ or mapserver/, whatever doc maintainers prefer (putting them in docs has the advantage that doc committers have more rights on the tickets themselves, in order to label/open/reassign them)
> steve: no, tickets cannot be moved.
>
> --
> thomas
>
>
> On Mon, Nov 5, 2012 at 5:05 PM, Lime, Steve D (DNR) <Steve.Lime at state.mn.us <mailto:Steve.Lime at state.mn.us>> wrote:
>
> Can we move issues between trackers?
>
> -----Original Message-----
> From: mapserver-dev-bounces at lists.osgeo.org <mailto:mapserver-dev-bounces at lists.osgeo.org> [mailto:mapserver-dev-bounces at lists.osgeo.org <mailto:mapserver-dev-bounces at lists.osgeo.org>] On Behalf Of Daniel Morissette
> Sent: Monday, November 05, 2012 8:01 AM
> To: mapserver-dev at lists.osgeo.org <mailto:mapserver-dev at lists.osgeo.org>
> Subject: Re: [mapserver-dev] github and Mapserver documentation
>
> On 12-11-05 4:25 AM, thomas bonfort wrote:
> > +0 for option b)
> > I've activated the docs issue tracker at
> > https://github.com/mapserver/docs/issues
> >
>
> Oh, I didn't realize that the docs issues would live in a different tracker... still got to get used to the new github setup...
>
> --
> Daniel Morissette
> http://www.mapgears.com/
> Provider of Professional MapServer Support since 2000
More information about the mapserver-dev
mailing list