Difference between revisions of "MapServer incubation status"

From OSGeo
Jump to navigation Jump to search
(→‎Community Functioning: link to full PSC membership list)
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
'''MapServer is a graduated OSGeo project. This page is the archive of the incubation process.'''
 +
 
== Basics ==
 
== Basics ==
  
Line 10: Line 12:
  
 
; Has the projectname.osgeo.org domain been populated with the projects web presence?  
 
; Has the projectname.osgeo.org domain been populated with the projects web presence?  
: Yes, to a point. There is a basic page that points to our primary, plone-based, website.
+
: Yes, to a point. There is a [http://mapserver.osgeo.org basic page] that points to our primary, plone-based, website.
  
 
; Is the OSGeo bug tracker being used for the project?   
 
; Is the OSGeo bug tracker being used for the project?   
: Yes, we migrated to the OSGeo TRAC instance in late April 2007.
+
: Yes, we migrated to the [http://trac.osgeo.org/mapserver/ OSGeo TRAC] instance in late April 2007.
  
 
; Bug tracking repository moved?
 
; Bug tracking repository moved?
Line 19: Line 21:
  
 
; Is the OSGeo mailing list manager being used for the project?
 
; Is the OSGeo mailing list manager being used for the project?
: No. mailing lists are hosted at http://lists.umn.edu/ and we would like to move to OSGeo hosted lists at some point soon.
+
: Yes, mailing lists including history have been migrated
 +
* http://lists.osgeo.org/mailman/listinfo/mapserver-users
 +
* http://lists.osgeo.org/mailman/listinfo/mapserver-dev
 +
* http://lists.osgeo.org/mailman/listinfo/mapserver-announce
  
 
; Is the OSGeo SVN or CVS system being used for the project?
 
; Is the OSGeo SVN or CVS system being used for the project?
Line 25: Line 30:
  
 
; Are binary and source downloads available from the OSGeo download area?
 
; Are binary and source downloads available from the OSGeo download area?
: Yes, source downloads (nightly and official releases)were moved to OSGeo in early May 2007.
+
: Yes, source downloads (nightly and official releases) were moved to OSGeo in early May 2007.
  
 
== Community Functioning ==
 
== Community Functioning ==
Line 42: Line 47:
  
 
; How many active developers are there?  Are they from multiple organizations?
 
; How many active developers are there?  Are they from multiple organizations?
: Yes, approximately 15 committers are established from 10 or more organizations. See [http://mapserver.gis.umn.edu/community/osgeo/incubation/contributors-list/ detailed list].
+
: Yes, approximately 15 committers are established from 10 or more organizations. See [http://mapserver.gis.umn.edu/community/osgeo/incubation/contributors-list/ detailed list] (updated 7/8/2008).
  
 
== Foundation Membership ==
 
== Foundation Membership ==
  
 
; Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
 
; 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.
+
: Yes, the MapServer [http://mapserver.gis.umn.edu/ homepage] indicates that the project is an OSGeo project. There are links to the OSGeo homepage and MapServer incubation documentation under [http://mapserver.gis.umn.edu/community/ community] portion of the website.  
  
 
; Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?  
 
; 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 bee established'')
+
: No, not yet. It feels like that should wait until graduation. At that point a OSGeo logo will be featured prominently on the MapServer home page.
  
 
== Code Copyright Review ==
 
== Code Copyright Review ==
  
 
; Has a [[Code Provenance Review]] document been prepared for the project?
 
; Has a [[Code Provenance Review]] document been prepared for the project?
: The code provenance review has begun and a roster of siginificant developers has been built and is available via the MapServer website. We are using an online spreadsheet as to tool to track the review, presence of a license, etc... for each source file in the MapServer distribution.
+
: Yes, a [http://mapserver.gis.umn.edu/community/osgeo/incubation/contributors-list/ contributors list] has been developed. A shared [http://spreadsheets.google.com/pub?key=p3ovxbvq1mBuBRaJiIT14eA spreadsheet] is being used to track provenance for MapServer proper and MapScript. A provenance '''task list''' is part of that work and is being used to track any issues uncovered.
  
 
; Have issues raised in the provenance review been adequately addressed?
 
; Have issues raised in the provenance review been adequately addressed?
Line 61: Line 66:
  
 
[[Category:Incubation]]
 
[[Category:Incubation]]
 +
[[Category:MapServer]]

Latest revision as of 10:51, 2 September 2022

MapServer is a graduated OSGeo project. This page is the archive of the incubation process.

Basics

Has the project been approved for incubation by the OSGeo board?
Yes, selected for "founding project" incubation by the OSGeo board.
Has an Incubation committee member been assigned as Mentor?
Yes, Chris Holmes has been assigned as MapServer incubation mentor.

Infrastructure Transition

Has the projectname.osgeo.org domain been populated with the projects web presence?
Yes, to a point. There is a basic page that points to our primary, plone-based, website.
Is the OSGeo bug tracker being used for the project?
Yes, we migrated to the OSGeo TRAC instance in late April 2007.
Bug tracking repository moved?
Yes.
Is the OSGeo mailing list manager being used for the project?
Yes, mailing lists including history have been migrated
Is the OSGeo SVN or CVS system being used for the project?
Yes, we migrated from CVS to the OSGeo SVN instance in early May 2007.
Are binary and source downloads available from the OSGeo download area?
Yes, source downloads (nightly and official releases) were moved to OSGeo in early May 2007.

Community Functioning

Is there a functioning user support mechanisms (ie. mailing list)?
The mapserver-users mailing list is quite active and well posed questions often result in more than one helpful response.
Are source and binary downloads for the package available?
Yes, visit http://mapserver.gis.umn.edu/
Has a Project Steering Committee been formed, and given control of the project?
Yes, the RFC transitioning our technical steering committee (TSC) to the PSC passed in April 2007. PSC membership is now complete.
Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
Yes, see RFC's (for PSC, and committer rules at least). May need to review committer rules in light of tighter OSGeo policy.
How many active developers are there? Are they from multiple organizations?
Yes, approximately 15 committers are established from 10 or more organizations. See detailed list (updated 7/8/2008).

Foundation Membership

Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
Yes, the MapServer homepage indicates that the project is an OSGeo project. There are links to the OSGeo homepage and MapServer incubation documentation under community portion of the website.
Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
No, not yet. It feels like that should wait until graduation. At that point a OSGeo logo will be featured prominently on the MapServer home page.

Code Copyright Review

Has a Code Provenance Review document been prepared for the project?
Yes, a contributors list has been developed. A shared spreadsheet is being used to track provenance for MapServer proper and MapScript. A provenance task list is part of that work and is being used to track any issues uncovered.
Have issues raised in the provenance review been adequately addressed?
indicate outstanding issues.