Changes between Version 13 and Version 14 of OSGeoAnnualReport2007


Ignore:
Timestamp:
Mar 1, 2008, 9:08:29 AM (16 years ago)
Author:
robertbray
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • OSGeoAnnualReport2007

    v13 v14  
    1313== Areas for Improvement ==
    1414 * While community contribution to the project is growing, most of those contributions are still on the periphery of the project. The core development on the !MapGuide project is still primarily fueled by developers at Autodesk. The project really needs developers from the communinity actively working on some of the core components.
     15 * Getting started with MapGuide is still more difficult than it needs to be. Improvements to the authoring tools (Web Studio / Map Studio) and a tutorial would go a long way to improving this experience.
    1516 * A public build system for !MapGuide would provide the community information on the state of trunk and access to daily builds of trunk.
    1617 * Linux based builds of !MapGuide and FDO remain more difficult than they should be. Some effort was put into an FGS installer but more work is required to the build systems of both FDO and !MapGuide to make FGS fully viable.
    … …  
    1920
    2021== Opportunities to Help ==
    21  * Contributions in website navigation and site structure.
     22All contributions and help is welcome, but in particular:
     23 * Contributions to the website navigation and site structure.
     24 * Contributions to the help and documentation, in particular a getting started tutorial.
     25 * Help with the Linux build system and completing the FGS package work.
     26 * Additional testing and quality bug reports.
    2227
    2328== Outlook for 2008 ==
    24 
     29The outlook for the !MapGuide Open Source project in 2008 and beyond is very bright. From a technology standpoint !MapGuide Open Source 2.0 will be released early in 2008. With the new AGG renderer and incorporation of Fusion we anticipate broad adoption of 2.0. Community contribution continues to grow at a steady pace, and we believe the 2.0 release will spark even more enthusiasm and collaboration. Finally with a little effort and support we believe the number of external developers contributing to the core code base will start to increase.