AW: [Mapbender-dev] branches, tags and svn ...

[Samson, Marko]

I think, a testarea would be.
For all the millions of not generic special extensions, perhaps there could be an extra folder at the testarea-to-be.
Perhaps a little infostandard for every extension would be a nice idea. So that everyone can see, if an extension will be executable, configurable, usable an interesting on one's own system.
Perhaps something like a little standard readme with a standard head like,

Function:
Used db:
Used php Version:
Used Version:
Known Bugs:
Short configure text:
.......

would be nice? Or should all this be done at the mb-wiki?!

Gruß,
Marko 


Marko Samson
Landesbetrieb Wald und Holz
GIS-Anwendungsentwicklung
Referat I-5
Albrecht-Thaer-Straße 34
48147 Münster

Tel.: 0251/2376-930
Mail: marko.samson at wald-und-holz.nrw.de
 

> -----Ursprüngliche Nachricht-----
> Von: Astrid Emde [mailto:astrid.emde at ccgis.de] 
> Gesendet: Freitag, 3. November 2006 11:01
> An: dev at mapbender.osgeo.org
> Betreff: Re: [Mapbender-dev] branches, tags and svn ...
> 
> Hi Michael,
> 
> > For users and want-to-contributors like me, what is the way 
> to go to 
> > submit new code or code changes or invoke a discussion on these 
> > changes? Are there development branches in the repository 
> that are not 
> > directly linked to latest stable branch, i.e is everybody at the 
> > moment committing into trunk? Is there a way to test new or changed 
> > code?
> > 
> > Thanks for any responses.
> > 
> > Greetings, Michael
> 
> You asked about the svn. At the moment we commit the new or 
> changed code 
>    only to the mapbender trunk and don't offer a testbed.
> 
> I think it's a good idea to setup a testarea where new code 
> can be presented to the community. But I don't know, how this 
> can be organized in the svn.
> 
> I would appreciate it if more people become part of the 
> developer team and get contributors. I could make a proposal 
> to add you to the developer team.
> 
> Another question we discussed about at the FOSSGIS 2006 was: 
> Where can we leave code which is not generic or assume a 
> special database or architecture or is not following the 
> standars, but maybe is nice to have (some examples poi-search 
> [needs configuration and geodata in a postgresql database], 
> str/hsnr-search implemented on postgresql ...). It would be 
> nice to have a branch where this code could be left.
> 
> Let's discuss about it
> 
> 
> -- 
> 
> Greetings Astrid
> 
> 
> ----------------------------------
> 
>   Astrid Emde
>   CCGIS GbR
>   Siemensstraße 8
>   53121 Bonn
>   Germany
> 
> ----------------------------------
>       astrid.emde at ccgis.de
>           www.ccgis.de
> ----------------------------------
>   Tel.:      ++49 (0) 228 90826 19
>   Fax.:      ++49 (0) 228 90826 11
>   Zentrale:  ++49 (0) 228 90826 0
> ----------------------------------
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe at mapbender.osgeo.org
> For additional commands, e-mail: dev-help at mapbender.osgeo.org
> 
>