Hello *,

On Fri, 20 Oct 2006 17:07:43 -0700
[EMAIL PROTECTED] wrote:

> essage: 8
> Date: Fri, 20 Oct 2006 20:11:02 +0200
> From: Armin Burger <[EMAIL PROTECTED]>
> Subject: Re: [pmapper-users] bug in pmapper 2.1.1
> To: Alessandro Pasotti <[EMAIL PROTECTED]>
> Cc: pmapper-users@lists.sourceforge.net
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> I uploaded version 2.1.2 with this bug fix and one for Postgis layers.

I will not stress it too much again, but I have some questions
regarding the pmapper-development strategies for upcoming releases.

Currently there are at least 2 mailinglist (sourceforge, faunalia),
probably some more at wald?!
Which one is the 'master' mailinglist? We should 

I would like to see a concentration of our power to one list, one SVN,
one tracker, one wiki, one whateverweneed.

This will definetly bring p.mapper to a wider range of people. As Paolo
also mentioned this will help bugfixes/extensions/scripts apply to
upstream version managed by Armin.

I know it was discussed thousand times, but why dont we use a
centratlized source-code storage, e.g. at sourceforge or wald? This
would make lots of things easier and p.mapper would definetly benefit
from this approach.

just my 0.02¢

Cheers
        Stephan

-- 
Stephan Holl   : www.intevation.de/~stephan | GISpatcher:
www.gispatcher.de Intevation GmbH: www.intevation.de          | GAV
e.V.: www.grass-verein.de Georgstr.4     : 49074 Osnabrück            | 

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Reply via email to