Difference between revisions of "Community Mapbuilder Incubation Progress"

From OSGeo
Jump to navigation Jump to search
m
 
(28 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
== Project Evaluation Criteria ==
+
''This page is based upon the [http://wiki.osgeo.org/index.php/Project_Status_Template OSGeo Project Status Template]''
  
−
Criteria for prioritizing projects for the incubation process.
+
== Basics ==
 +
; Has the project been approved for incubation by the OSGeo board?
 +
: Yes.
  
−
=== Requirements ===
+
; Has an OSGeo committee member been assigned as Mentor?
−
; the code is under an OSI approved license (data & doc projects need to specify their choice for a type of license).
+
: Steve Lime has been designated incubation mentor for Community MapBuilder.
−
: Mapbender is licensed under the LGPL.
 
−
; project willing to keep code clear of encumbrances (committer agreements, etc).
 
−
: Project Management Committee have agreed to sign [http://www.fossgis.de/osgeo/index.php/Individual_Contributor_License_Agreement_%28CLA%29 Individual Contributor License Agreement (CLA)] (once it is approved).  Our project is young and we can contact all previous committers.  I'm not expecting any objections to signing the CLA.
 
−
I'm still waiting on guidance from the OSGeo committee as to whether we should support the CLA or not.
 
−
; the project is "geospatial", or directly in support of geospatial applications.
 
−
Mapbuilder is a Web Mapping client which implements many OGC standards.
 
  
−
<html>
+
== Infrastructure Transition ==
−
<iframe src='http://wms1.ccgis.de/mapbender2/frames/login.php?name=mapbender&password=mapbender&mb_user_myGui=ccgis_de'
 
−
width='250' height='200' frameborder='0'>
 
−
</iframe>
 
−
</html>
 
  
−
''This application is a Mapbender MiniMe.''
+
''Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.''
  
−
=== Desirable ===
+
; Has the projectname.osgeo.org domain been populated with the projects web presence?
−
; already reasonably mature (working quality code).
+
: ''If not why, and has the project page got a prominent link to the real home?''
−
: Mapbender has been in productive use for more than a year in at least 30 larger installations. The roots go back to the year 1999 when the software was first implemented as a proprietary package. At the end of 2002 it was published for the first time as Free Software, in August 2003 it was moved to SourceForge, at the end of 2004 code moved into the CVS.
+
: http://communitymapbuilder.osgeo.org has been set up and points to http://communitymapbuilder.org.
−
; already has a substantial user community.
+
: Comments from [[User:camerons|Cameron Shorter]]: Currently I'm reluctant to move our services to Collabnet. Here are the reasons:
−
: The user mailing list countes 197 subscribers (Feb 2006), at the the first national Mapbender user meeting in May 2005 in Bonn, Germany 80 people showed up.
+
# While Collabnet is currently very supportive of OSGeo which is excellent to see, the reallity of the commercial world is that in five years there might be a change of management at Collabnet and the OSGeo support might be cut off. So before we enter in with Collabnet, we need to think about an exit strategy if we loose Collabnet support. As I understand it, the current exit strategy would involve migrating from proprietary tools to "free for open source" tools which would be expensive in effort.
−
; already has a substantial developer community.
+
# Migrating to Colabnet would involve a medium amount of effort and we would loose some information like bugs from the bug tracker.
−
: 8 active contributors
+
: I would prefer to keep all project tools on one server rather than many. Currently codehaus.org is providing most of our tools. They provide tools for free, and the tools used are available for free to open source projects so we have a low cost exit stratagy if Codehaus folds.
−
: 10 to 50 CVS commits per week
+
 
−
; adheres to standards (ie. OGC, etc) where appropriate.  
+
; Is the OSGeo bug tracker being used for the project? 
−
: Mapbender implements OGC WMS, WFS, WFS-T, WCD, CS-W 2.0 beta, WKT, SFS, and many more
+
:: No, we use JIRA at http://jira.codehaus.org/browse/MAP  See justification above. Moving to OSGeo will require medium effort and we will loose an amount of data.
−
; has linkages with existing foundation projects.
+
 
−
* [https://mapserver.osgeo.org/ MapServer] (adopted OSGeo project)
+
; Is the OSGeo mailing list manager being used for the project?
−
* [http://www.mapbender.org/index.php/GeoServer GeoServer] (adopted OSGeo project)
+
: No.  Lists are stored on Sourceforge at http://sourceforge.net/mail/?group_id=35246 which has a slightly better interface - (Web subscribe interface, threads in the archieve).  We could move our lists in future if archieves can be moved as well.  But as yet, I don't see a need to move to an inferior tool.
−
* [http://www.mapbender.org/index.php/MapBuilder MapBuilder] (adopted OSGeo project)
+
 
−
* [http://www.mapbender.org/index.php/PostGIS PostGIS] (external OSGeo friend project)
+
; Is the OSGeo SVN or CVS system being used for the project?
−
; fills a gap in the foundation software stack.
+
: No.  We use SVN on http://codehaus.org It would be relatively easy to use SVN at OSGeo but we like to keep our tools all on the one server. Codehaus also provides Fisheye, a nice tool for viewing the subversion repository.
−
: Mapbender is probably the only comprehensive server side OGC OWS management interfaces that includes user and group management with multi-client capacity, CMS-style interface development, security module, log, monitor, etc. We do not know whether we fill any gaps, but we have friendly contacts to the MapBuilder team and plan to cooperate closely.
+
 
−
; prepared to develop in an open and collaborative fashion.
+
; Are binary and source downloads available from the OSGeo download area?
−
: Contributors are welcome. Cross project interaction is being discussed and joining with the MapBuilder project is planned as long time goal.
+
: We currently use Sourceforge to download releases, however we are in the process of setting up a nightly build and download on an OSGeo server. This would be relatively easy to move to OSGeo.
−
; has contributions and interest from more than just one company/organization.
+
 
−
: Core developers come from the companies [http://www.mapbender.org/index.php/CCGIS CCGIS], [http://www.mapbender.org/index.php/CeGIT CeGIT] and [http://www.mapbender.org/index.php/Terrestris terrestris], code contributions come from [http://www.mapbender.org/index.php/KARTA.GO KARTA.GO], [http://www.mapbender.org/index.php/Geo-Consortium Geo-Consortium], [http://www.mapbender.org/index.php/In_medias_res in medias res], some individuals and larger customers.
+
== Community Functioning ==
−
; willing to migrate to foundation support infrastructure, and adopt website style consistent with the foundation.
+
 
−
: CVS, Mailing lists (user, CVS) are ready to migrate, mailto:dev@mapbender.osgeo.org has already migrated to OSGeo. The web page, documentation, develoment coordination, demo site, developer beta and testing pages are all integrated into the [http://www.mapbender.org Mapbender Wiki] and available at http://www.mapbender.org which is good as it is, we do not see the need to migrate this URL.
+
; Is there a functioning user support mechanisms (ie. mailing list)?
 +
: Yes, we have a busy list with lots of answers to user queries.
 +
: http://sourceforge.net/mailarchive/forum.php?forum=mapbuilder-devel
 +
: http://sourceforge.net/mailarchive/forum.php?forum=mapbuilder-users
 +
 
 +
; Are source and binary downloads for the package available?
 +
: Yes. http://sourceforge.net/project/showfiles.php?group_id=35246
 +
 
 +
; Has a Project Steering Committee been formed, and given control of the project?
 +
: Yes. Project Steering Committee has been in effect since the start of the project. It currently consists of:
 +
* Cameron Shorter
 +
* Mike Adair
 +
* Patrice Cappelaere
 +
* Steven Ottens
 +
 
 +
; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.  
 +
: Yes.
 +
: http://communitymapbuilder.org/display/MAP/Contributers Guide describes project roles and responsibilities.
 +
: http://communitymapbuilder.org/display/MAP/Decision Making describes decision making.
 +
 
 +
; How many active developers are there?  Are they from multiple organizations?
 +
: 4 Core developers (the PSC) and around 10 to 15 other developers.
 +
: All the PSC work for different organisations and live in different countries.  Similarly, the developers and users all come from different organisations and geographic locations.
 +
 
 +
== Foundation Membership ==
 +
 
 +
; Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
 +
: Yes
 +
 
 +
; Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
 +
: Not yet. We will wait for an OSGeo web style to be established before using this style. The following issue has been raised to track this: [http://jira.codehaus.org/browse/MAP-146].
 +
 
 +
== Code Copyright Review ==
 +
 
 +
; Has a [[Code Provenance Review]] document been prepared for the project?
 +
: Yes.  Results are in the Mapbuilder repository at mapbuilder/docs/licenseAudit/* and copied to [[Community Mapbuilder Provenance Review]].
 +
 
 +
; Have issues raised in the provenance review been adequately addressed?
 +
: Yes, most issues related to the code providence review. We were unsure of the origin of some of our code. There were also a few tweaks required for the documentation.
 +
 
 +
[[Category:Incubation]]

Latest revision as of 00:20, 14 April 2007

This page is based upon the OSGeo Project Status Template

Basics

Has the project been approved for incubation by the OSGeo board?
Yes.
Has an OSGeo committee member been assigned as Mentor?
Steve Lime has been designated incubation mentor for Community MapBuilder.

Infrastructure Transition

Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.

Has the projectname.osgeo.org domain been populated with the projects web presence?
If not why, and has the project page got a prominent link to the real home?
http://communitymapbuilder.osgeo.org has been set up and points to http://communitymapbuilder.org.
Comments from Cameron Shorter: Currently I'm reluctant to move our services to Collabnet. Here are the reasons:
  1. While Collabnet is currently very supportive of OSGeo which is excellent to see, the reallity of the commercial world is that in five years there might be a change of management at Collabnet and the OSGeo support might be cut off. So before we enter in with Collabnet, we need to think about an exit strategy if we loose Collabnet support. As I understand it, the current exit strategy would involve migrating from proprietary tools to "free for open source" tools which would be expensive in effort.
  2. Migrating to Colabnet would involve a medium amount of effort and we would loose some information like bugs from the bug tracker.
I would prefer to keep all project tools on one server rather than many. Currently codehaus.org is providing most of our tools. They provide tools for free, and the tools used are available for free to open source projects so we have a low cost exit stratagy if Codehaus folds.
Is the OSGeo bug tracker being used for the project?
No, we use JIRA at http://jira.codehaus.org/browse/MAP See justification above. Moving to OSGeo will require medium effort and we will loose an amount of data.
Is the OSGeo mailing list manager being used for the project?
No. Lists are stored on Sourceforge at http://sourceforge.net/mail/?group_id=35246 which has a slightly better interface - (Web subscribe interface, threads in the archieve). We could move our lists in future if archieves can be moved as well. But as yet, I don't see a need to move to an inferior tool.
Is the OSGeo SVN or CVS system being used for the project?
No. We use SVN on http://codehaus.org It would be relatively easy to use SVN at OSGeo but we like to keep our tools all on the one server. Codehaus also provides Fisheye, a nice tool for viewing the subversion repository.
Are binary and source downloads available from the OSGeo download area?
We currently use Sourceforge to download releases, however we are in the process of setting up a nightly build and download on an OSGeo server. This would be relatively easy to move to OSGeo.

Community Functioning

Is there a functioning user support mechanisms (ie. mailing list)?
Yes, we have a busy list with lots of answers to user queries.
http://sourceforge.net/mailarchive/forum.php?forum=mapbuilder-devel
http://sourceforge.net/mailarchive/forum.php?forum=mapbuilder-users
Are source and binary downloads for the package available?
Yes. http://sourceforge.net/project/showfiles.php?group_id=35246
Has a Project Steering Committee been formed, and given control of the project?
Yes. Project Steering Committee has been in effect since the start of the project. It currently consists of:
  • Cameron Shorter
  • Mike Adair
  • Patrice Cappelaere
  • Steven Ottens
Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
Yes.
http://communitymapbuilder.org/display/MAP/Contributers Guide describes project roles and responsibilities.
http://communitymapbuilder.org/display/MAP/Decision Making describes decision making.
How many active developers are there? Are they from multiple organizations?
4 Core developers (the PSC) and around 10 to 15 other developers.
All the PSC work for different organisations and live in different countries. Similarly, the developers and users all come from different organisations and geographic locations.

Foundation Membership

Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
Yes
Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
Not yet. We will wait for an OSGeo web style to be established before using this style. The following issue has been raised to track this: [1].

Code Copyright Review

Has a Code Provenance Review document been prepared for the project?
Yes. Results are in the Mapbuilder repository at mapbuilder/docs/licenseAudit/* and copied to Community Mapbuilder Provenance Review.
Have issues raised in the provenance review been adequately addressed?
Yes, most issues related to the code providence review. We were unsure of the origin of some of our code. There were also a few tweaks required for the documentation.
Retrieved from "http://wiki.osgeo.org/w/index.php?title=Community_Mapbuilder_Incubation_Progress&oldid=13828"