Changes between Version 14 and Version 15 of GoogleSoC2010

Timestamp:

May 24, 2010, 2:53:27 AM (14 years ago)

Author:

rohitr

Comment:

--

GoogleSoC2010

@@ -14 +14 @@
 === Outline ===
 
-The MapGuide user base is having difficulty using MapGuide Open Source on Linux.  Many current Linux distributions, including popular ones such as Ubuntu 9.10 are difficult to use due to the fact MapGuide does not compile under GCC 4.4.  In addition, RPM binary packaging for CentOS/RedHat (our primary targets in the GIS space) has not been implemented yet. Third party dependencies are also outdated. I propose to update the code base to current standards and create easy installation experience for Linux users on many different distros. My first goal is to create a 'cleaner' installation experience for the end user and to eventually aim for inclusion of MapGuide in standard repositories.
+The MapGuide user base is having difficulty using !MapGuide Open Source on Linux.  Many current Linux distributions, including popular ones such as Ubuntu 9.10 are difficult to use due to the fact !MapGuide does not compile under GCC 4.4.  In addition, RPM binary packaging for CentOS/RedHat (our primary targets in the GIS space) has not been implemented yet. Third party dependencies are also outdated. I propose to update the code base to current standards and create easy installation experience for Linux users on many different distros. My first goal is to create a 'cleaner' installation experience for the end user and to eventually aim for inclusion of !MapGuide in standard repositories.
 
-For my second goal, MapGuide Open Source has a well defined role and permission based security model.  However, this model has not been extended to facilitate map authoring and application creation. I intend to extend this to enable control layer inclusion on a map based on user and group information.  If the user has permission to read both the LayerDefinition and FeatureSource for a specific layer, that layer will be included on the map. 
+For my second goal, !MapGuide Open Source has a well defined role and permission based security model.  However, this model has not been extended to facilitate map authoring and application creation. I intend to extend this to enable control layer inclusion on a map based on user and group information.  If the user has permission to read both the LayerDefinition and FeatureSource for a specific layer, that layer will be included on the map. 
 
 If time permits, then I intend to extend the security model to selectively display GUI elements. The controls available would change depending on the security 'clearance' of the user. This is pretty complex part in its own right , but I am definitely going to attempt, at least some part of it.