Difference between revisions of "IncCom Report22"

From OSGeo
Jump to navigation Jump to search
Line 64: Line 64:
  
 
==rasdaman==
 
==rasdaman==
 +
 +
The Rasdaman community seems to be past the technical hurdles of the code review and license checks, and is now working on open governance procedures.
  
 
* mentor: Bruce Bannerman
 
* mentor: Bruce Bannerman
* Project is seeing a lot of activity and success
+
** [[Rasdaman Code Provenance Review http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/wiki/OSGeoCodeProvenance]] (done?)
** CRS name resolver has been deployed as OGC's official CRS name resolver.
+
** [[Rasdaman Incubation Checklist http://www.rasdaman.org/wiki/OSGeoIncubationChecklist]]. (80%)
** Working on CITE compliance
+
 
* Working on progress towards incubation goals
+
(Bruce) My general observations on the project for the last period are:
** community comment on planning / public roadmap
 
** [[Rasdaman Code Provenance Review http://rasdaman.eecs.jacobs-university.de/trac/rasdaman/wiki/OSGeoCodeProvenance]]
 
** [[Rasdaman Incubation Checklist http://www.rasdaman.org/wiki/OSGeoIncubationChecklist]].
 
  
The Rasdaman community seems through the technical hurdles of the code review and license checks, and is now working on open governance procedures.
+
* Overall, the project appears to be in good shape, with 26 new user registrations this month alone.
 +
* Project activity has increased with a marked increase in email traffic on the developer and user lists.
 +
* Considerable activity is occuring related to documenting and fine tuning of software release processes, including tying these to processes relating to the use of git.
 +
* Work is underway to support git branching with a view towards maintained releases.
 +
* Work is under way to support regression testing for OGC compliance e.g. WCPS and WCS.
 +
* Work is underway to improve the testing framework.
 +
* Rasdaman's CRS name resolver has been deployed as OGC's official CRS name resolver.
 +
* I'm starting to see future planning activities being presented to the Rasdaman Community for comment. This is good to see.
 +
* We still don't have documented processes describing a range of factors, however I anticipate that these will come in time. Some examples are:
 +
** Project Governance and processes
 +
** Who is on the Project Steering Committee? How are PSC members (s)elected, replaced etc? What are the responsibilities of the PSC?
 +
** What Code review is expected for new contributions? Who does this review?
 +
* How are Commiters selected? What are their responsibilities? How is commit status reviewed?
 +
** The project has a reasonably well defined roadmap [2]. What I'm not clear on yet is e.g.:
 +
** How was this roadmap has been defined?
 +
** What community review process is used to arrive at the roadmap?
 +
** How were relative priorities determined?
 +
** How are new priorities balanced against existing priorities?
  
 
==TEAM Engine==
 
==TEAM Engine==

Revision as of 23:09, 6 July 2013

Incubation Status report for Q2 2013.

TLDR: Waiting on the board for GeoMoose announcement, and listing project officers for GeoMoose and GeoServer. Rasdaman is getting close to completing incubation requirements. Remaining incubation projects show no progress, with dropping TEAM Engine being discussed. Landon has some ideas for promoting OSGeo Labs projects.

Incubation Committee

Actions from IncCom Meeting21

  • Arnulf to Mentor Marble, we will need to make a motion on the email list
  • Jody to contact OSM project and see if it is still ticking
  • OGC Team Engine motioned with Justin Deoliveira as mentor
  • Jody: ask GeoMoose for clarification on contribution, and results of code/doc/data review
  • jmckenna: fix ZOO-Project link on osgeo.org (done)
  • Jody: take "Incubation Phases" proposal back to email for discussion
  • Jody: kalxas: filling in pycsw questionnaire

Recent Graduates

GeoMoose

GeoServer

Incubation

gvSIG

  • mentor:
  • no progress to report

Marble

  • mentor:
  • no progress to report

MetaCRS

  • mentor:
  • no progress to report

Opticks

  • mentor:
  • no progress to report

pycsw

  • mentor:
  • no progress to report

rasdaman

The Rasdaman community seems to be past the technical hurdles of the code review and license checks, and is now working on open governance procedures.

(Bruce) My general observations on the project for the last period are:

  • Overall, the project appears to be in good shape, with 26 new user registrations this month alone.
  • Project activity has increased with a marked increase in email traffic on the developer and user lists.
  • Considerable activity is occuring related to documenting and fine tuning of software release processes, including tying these to processes relating to the use of git.
  • Work is underway to support git branching with a view towards maintained releases.
  • Work is under way to support regression testing for OGC compliance e.g. WCPS and WCS.
  • Work is underway to improve the testing framework.
  • Rasdaman's CRS name resolver has been deployed as OGC's official CRS name resolver.
  • I'm starting to see future planning activities being presented to the Rasdaman Community for comment. This is good to see.
  • We still don't have documented processes describing a range of factors, however I anticipate that these will come in time. Some examples are:
    • Project Governance and processes
    • Who is on the Project Steering Committee? How are PSC members (s)elected, replaced etc? What are the responsibilities of the PSC?
    • What Code review is expected for new contributions? Who does this review?
  • How are Commiters selected? What are their responsibilities? How is commit status reviewed?
    • The project has a reasonably well defined roadmap [2]. What I'm not clear on yet is e.g.:
    • How was this roadmap has been defined?
    • What community review process is used to arrive at the roadmap?
    • How were relative priorities determined?
    • How are new priorities balanced against existing priorities?

TEAM Engine

  • mentor: Justin Deolivera
  • no progress to report

Incubation committee has discussed dropping this project due to lack of progress / lack of plan to progress.

ZOO-Project

  • mentor:
  • no progress to report

Labs

Thanks to Landon Blake for his excellent leadership in reaching out to OSGeo Incubation Lab projects.

  • We have extended an invitation to OSGeo Labs projects to participate in the incubation list, as for many routine questions we can help without a dedicated mentor.
  • Landon has the idea of setting up resources for community building / project marketing / project governance

Geoinformatica

OSGeo Participation:


pgRouting

  • Website: http://pgrouting.org
  • User Mailing List: yes
  • User Documentation: unknown
  • Number of users: no estimate

OSGeo Participation:

PAGC

  • Website: http://www.pagcgeo.org
  • User Mailing List: no
  • User Documentation: unknown
  • Number of Users: no estimate

OSGeo Participation:

  • OSGeo Wiki: [[OSGeo_Labs:_PAGC] (page empty)]
  • OSGeo Live:

MapProxy

OSGeo Participation:

    • pycsw**

OSGeo Participation:

  • OSgeo Wiki:
  • OSGeo Live:

The SurveyOS KML Toolkit

  • Website:
  • User Mailing List: no
  • User Documentation: unknown
  • Number of Users: no estimate

OSGeo Participation:

SlitherGrid

  • Website:
  • User Mailing List: no
  • User Documentation: unknown
  • Number of Users: no estimate

OSGeo Participation:

Virtual Terrain Project

  • Website: http://vterrain.org/
  • User Mailing List: no
  • User Documentation: unknown
  • Number of Users: no estimate

OSGeo Participation:

PyWPS

OSGeo Participation: