Difference between revisions of "Community Mapbuilder Incubation Progress"

From OSGeo
Jump to navigation Jump to search
m
(Changed template)
Line 1: Line 1:
== Project Evaluation Criteria ==
+
== Basics ==
  
Criteria for prioritizing projects for the incubation process.
+
; 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).
+
: Cameron Shorter is both on the OSGeo committee and is on the Mapbuilder PSC.
: Mapbuilder is licensed under the LGPL.
+
: ''Q for OSGeo: Is this sufficient, or are you looking for an independent OSGeo member?''
; 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.
 
  
=== Desirable ===
+
== Infrastructure Transition ==
; already reasonably mature (working quality code).
+
 
: Mapbuilder has been releasing stable web mapping clients for over 2 years.
+
''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.''
; already has a substantial user community.
+
 
: We have a vibrant developer community, with over 10 developers, and process an average 10 to 15 emails a dayOur user community is rapidly growing with our 1.0 release pending.
+
; Has the projectname.osgeo.org domain been populated with the projects web presence?
; already has a substantial developer community.
+
: ''If not why, and has the project page got a prominent link to the real home?''
: 4 core developers (the PSC) and around 10 to 15 other developers.
+
: http://communitymapbuilder.osgeo.org has been set up, but not populated.
; adheres to standards (ie. OGC, etc) where appropriate.
+
: Comments from Cameron Shorter: Currently I reluctant to move our services to colabnet.  Migrating to Colabnet would involve a medium amount of effort and would loose some information like bugs from the bug tracker.
: Mapbuilder implements OGC WMS, WMC, OWS, WFS, WFS-T, SLD, GeoRSS - probably more.
+
: Should we leave OSGeo in the future, or OSGeo decides to stop using Collabnet, we would be faced with a similar exit cost because there is not a free version of Colabnet for Open Source projects.
; has linkages with existing foundation projects.
+
: I would prefer to keep all project tools on one server rather than manyCurrently codehaus.org is providing our tools.  
: Mapbuilder is currently bundled with Geoserver.
+
: ''Q for Mapbuilder: Any comments to add here?  Provide feedback to the mapbuilder-devel list.''
: We hope to bundle with UDig and provide a Heavy/Light client solution for users.
+
 
: We have a long term goal of integrating with other AJAX Webmapping clients like Mapbender.
+
; Is the OSGeo bug tracker being used for the project? 
; fills a gap in the foundation software stack.
+
: ''If not, why?''
: Mapbuilder is a modular Webmapping toolkit which allows developers to easilly build customised web mapping clients.  It's modular design makes it easy to extend.
+
: No.  See justification above.
: Mapbuilder is currently the only Web based WFS-T client.
+
 
; prepared to develop in an open and collaborative fashion.
+
; Is the OSGeo mailing list manager being used for the project?
: Mapbuilder is controlled by a Project Steering Committee and welcomes new developers.
+
: ''If not, why?''
; has contributions and interest from more than just one company/organization.
+
: No.  Lists are stored on Sourceforge 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.
: All four Project Steering Committee members are from different countries and companiesDevelopers are similarly from all around the world and from different organisations.
+
 
; willing to migrate to foundation support infrastructure, and adopt website style consistent with the foundation.
+
; Is the OSGeo SVN or CVS system being used for the project?
: We are undecided as to whether the gain of moving to OSGeo is worth the effort.
+
: ''If not, why?''
: Also, I'm concerned about being tied to the proprietary Collabnet license.
+
: No.  See justification above.
 +
 
 +
; Are binary and source downloads available from the OSGeo download area?
 +
: ''If not, why?''
 +
Not yet, but we can do this if needed.
 +
 
 +
== Community Functioning ==
 +
 
 +
; Is there a functioning user support mechanisms (ie. mailing list)?
 +
: indicate the available user support mechanisms, and whether they seem to be functioning well (are getting used and get answers).
 +
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/no (and any caveats)''
 +
Yes.
 +
http://sourceforge.net/project/showfiles.php?group_id=35246
 +
 
 +
; Has a Project Steering Committee been formed, and given control of the project?
 +
: ''yes/no, indicate members and whether it has effective control.''
 +
: 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/no - provide pointers to various related documents.''
 +
: Documentation in this area is a bit weak.  This is what I could find:
 +
http://communitymapbuilder.org/display/MAP/Contributers+Guide
 +
: '''Action on Mapbuilder: We need to be more specific about project decision making.'''
 +
 
 +
; How many active developers are there?  Are they from multiple organizations?
 +
: ''Indicate number and some organizations involved.''
 +
: 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?
 +
: ''If not, indicate when this will occur.''
 +
: Not yet.
 +
: ''Question for OSGeo: What are you looking for here?''
 +
 
 +
; Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
 +
: If not, indicate what is planned.  (''note: currently an OSGeo web style has not been established'')
 +
: Not yet.  We will wait for an OSGeo web style to be established before using this style.
 +
 
 +
== Code Copyright Review ==
 +
 
 +
; Has a [[Code Provenance Review]] document been prepared for the project?
 +
: ''yes/no - point to review document.''
 +
: No.  '''Action on Mapbuilder'''.
 +
 
 +
 
 +
; Have issues raised in the provenance review been adequately addressed?
 +
: ''indicate outstanding issues.''
 +
:

Revision as of 21:21, 4 April 2006

Basics

Has the project been approved for incubation by the OSGeo board?
Yes.
Has an OSGeo committee member been assigned as Mentor?
Cameron Shorter is both on the OSGeo committee and is on the Mapbuilder PSC.
Q for OSGeo: Is this sufficient, or are you looking for an independent OSGeo member?

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, but not populated.
Comments from Cameron Shorter: Currently I reluctant to move our services to colabnet. Migrating to Colabnet would involve a medium amount of effort and would loose some information like bugs from the bug tracker.
Should we leave OSGeo in the future, or OSGeo decides to stop using Collabnet, we would be faced with a similar exit cost because there is not a free version of Colabnet for Open Source projects.
I would prefer to keep all project tools on one server rather than many. Currently codehaus.org is providing our tools.
Q for Mapbuilder: Any comments to add here? Provide feedback to the mapbuilder-devel list.
Is the OSGeo bug tracker being used for the project?
If not, why?
No. See justification above.
Is the OSGeo mailing list manager being used for the project?
If not, why?
No. Lists are stored on Sourceforge 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?
If not, why?
No. See justification above.
Are binary and source downloads available from the OSGeo download area?
If not, why?

Not yet, but we can do this if needed.

Community Functioning

Is there a functioning user support mechanisms (ie. mailing list)?
indicate the available user support mechanisms, and whether they seem to be functioning well (are getting used and get answers).

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/no (and any caveats)

Yes. http://sourceforge.net/project/showfiles.php?group_id=35246

Has a Project Steering Committee been formed, and given control of the project?
yes/no, indicate members and whether it has effective control.
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/no - provide pointers to various related documents.
Documentation in this area is a bit weak. This is what I could find:

http://communitymapbuilder.org/display/MAP/Contributers+Guide

Action on Mapbuilder: We need to be more specific about project decision making.
How many active developers are there? Are they from multiple organizations?
Indicate number and some organizations involved.
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?
If not, indicate when this will occur.
Not yet.
Question for OSGeo: What are you looking for here?
Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
If not, indicate what is planned. (note: currently an OSGeo web style has not been established)
Not yet. We will wait for an OSGeo web style to be established before using this style.

Code Copyright Review

Has a Code Provenance Review document been prepared for the project?
yes/no - point to review document.
No. Action on Mapbuilder.


Have issues raised in the provenance review been adequately addressed?
indicate outstanding issues.