[Mapbender-dev] [Mapbender_dev] Motion to use the issue tracker from github for Mapbender3

[Christian Wygoda]

Hi,

a publicly facing tracker is definately needed and with the public code 
repo already hosted at Github, the motion would be the natural move. 
Therefore I +1 it.
We probably would need the labels "Bug", "Feature", "Feature-Request". 
Right now the code is split up in three repositories:

* mapbender-starter for the basic application skeleton
* mapbender for the actual Mapbender code
* fom for the "auxiliary" code like user management and backend 
infrastructure.

I would favor trackers for each, even if that would probably mean that 
we need to shift tickets around from time to time if they are posted to 
the wrong repository.

Cheers & Alaaf,
   Crischan

On 02/07/2013 10:02 AM, Astrid Emde wrote:
> Hello,
>
> for Mapbender 2.x we used the issue tracker at trac
> http://trac.osgeo.org/mapbender/report
>
>
> I would like to make the motion to use the github issue tracker for
> Mapbender3 from the mapbender-repository
>
> https://github.com/mapbender/mapbender/issues
>
> Ticktes for documentation could be made at:
>
> https://github.com/mapbender/mapbender-documentation/issues
>
> What do you think about this idea? Please give feedback.
>


-- 
********************************************
FOSS Academy Winterschule, 25.02.-01.03.2013
GDI in 5 Tagen!
http://www.foss-academy.eu/Winterschule_2013
********************************************
--------------------------------------------
WhereGroup GmbH & Co. KG
Eifelstraße 7
53119 Bonn
Germany

Christian Wygoda
Anwendungsentwickler

Fon: +49 (0)228 / 90 90 38 - 15
Fax: +49 (0)228 / 90 90 38 - 11

info at wheregroup.com
www.wheregroup.com
Amtsgericht Bonn, HRA 6788
--------------------------------------------
Komplementärin:
WhereGroup Verwaltungs GmbH
vertreten durch:
Olaf Knopp, Peter Stamm
--------------------------------------------