[mapguide-internals] Motion to Change RFC Process

Zac Spitzer zac.spitzer at gmail.com
Wed Jul 28 21:35:26 EDT 2010


On 29 July 2010 03:09, Robert Bray <robert.bray at autodesk.com> wrote:

> Zac,
>
> I am curious about the motivation for the change. Is this simply to clean
> up the RFC list, so that RFCs that are discussed but not adopted never get a
> number?
>

Primarily yes, The RFC list also getting rather long and it's becoming
rather confusing, being a static wiki page you can sort or categorise it
either

z


>
> Bob
>
> -----Original Message-----
> From: mapguide-internals-bounces at lists.osgeo.org [mailto:
> mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Zac Spitzer
> Sent: July-28-10 6:25 AM
> To: MapGuide Internals Mail List
> Subject: [mapguide-internals] Motion to Change RFC Process
>
> I would like to change the RFC process to require firstly
> discussion and approval of concept over mapguide-internals
> before allocating RFC numbers..
>
> z
>
>
> --
> Zac Spitzer
> Solution Architect / Director
> Ennoble Consultancy Australia
> http://www.ennoble.com.au
> http://zacster.blogspot.com
> +61 405 847 168
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
> _______________________________________________
> mapguide-internals mailing list
> mapguide-internals at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-internals
>



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168


More information about the mapguide-internals mailing list