[mapguide-internals] RFC60 ??? - at least a sandbox please
Trevor Wekel
trevor_wekel at otxsystems.com
Fri Sep 18 12:57:08 EDT 2009
Based on UV's discussion, I think the RFC 60 work does require a sandbox. There are still outstanding items related to new stylize compatibility which need to be addressed. However, there has already been significant headway made by UV and it would be disappointing to lose a significant server side code contribution from a developer outside of Autodesk.
I can set up a sandbox for RFC 60 but I do not know where commit rights lie. From what I recall, there was an outstanding request with SAC to enable commit rights only on sandboxes. Has this been resolved? If so, how do we grant sandbox commit rights to UV?
Based on previous mapguide-internals "discussions", I do not believe full commit rights for UV would be accepted yet.
Thanks,
Trevor
-----Original Message-----
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of UV
Sent: September 18, 2009 9:28 AM
To: MapGuide Internals Mail List
Subject: [mapguide-internals] RFC60 ??? - at least a sandbox please
It seems like RFC60 will not be included in any release on the basis
that it does not support the new stylization.
In this context I would like to request a sandbox to be able to upload
at least a working configuration.
Adapting the pach to the ever changing code base is an ever increasing task.
i have been asking a few times for sample test maps to implement this
additional functionality I only been shown some unit test code and
never a real map.
For the complexity of this feature this is not sufficient and I am still
lacking resources to do an efficient job.
Furthermore nobody seems to use that stylization so it seems that RFC60,
a simple addition in functionality, would do no harm and not disturb any
maps using new stylization.
I am very disappointed about working months for this project an nobody
would even allow me to
contribute anything to the code base after fixing the issues in the patch.
something seems missing in the open source here ...
our customer now has a big problem to continue with updating MGOS as the
missing patch is very visible
on his site. thank you very much.
to keep at least the code base i am requesting
_______________________________________________
mapguide-internals mailing list
mapguide-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-internals
More information about the mapguide-internals
mailing list