[MetaCRS] RFC 1: MetaCRS PSC

[Norm Olsen]

Hello Frank . . .

I think some clarification on how sub-projects are to be governed may be beneficial.

With regard to the sub-projects, are the following statements correct?

1> Governance of sub-projects is provided by a committee consisting of the PSC appointed sub-project lead (Chair) and all committers approved for that specific sub-project.

2> Issues which are within the domain of the sub-project committee shall be resolved by consensus.  In the absence of unanimous consensus, the issue shall/may be referred to the MetaCRS PSC.

3> Committers are approved for specific sub-project.  An individual can be a committer for more than one sub-project, but a separate MetaCRS PSC approval is required for each.

If these are indeed true, then I believe that each sub-project should have its own source code and documentation repository and its own bug tracking system.

Finally, it might make some sense to consider definition dictionaries as a separate sub-project.  That is, a project which maintains a single database and code to generate dictionaries in a form specific to the code specific sub-projects.  That sub-project would have its own repository and bug tracking system.

Just thoughts.  I've been a one man band for 20+ years, so my experience concerning the organization of a cooperative effort is absolutely zero!!!

Norm

-----Original Message-----
From: metacrs-bounces at lists.osgeo.org [mailto:metacrs-bounces at lists.osgeo.org] On Behalf Of Frank Warmerdam (External)
Sent: Friday, April 25, 2008 12:28 PM
To: metacrs at lists.osgeo.org
Subject: [MetaCRS] RFC 1: MetaCRS PSC

Folks,

I think I promised to write a MetaCRS governance document.  I have prepared
an initial draft.  The voting mechanism is essentially the same as many other
projects (GDAL, MapServer, MapGuide), but a distinguishing factor of this
document is that it recognise the existance of sub-projects with sub-project
leads that are free to make technical decisions internally by consensus
without having to call for a MetaCRS PSC vote.

The MetaCRS PSC is primarily for resolving situations that cannot be settled
by consensus, for addressing matters that cross between sub-projects
including matters about interpretation of CRS definitions and interchange
best practice.  Also the MetaCRS PSC is the venue for things that need
an "official" decision, including approval of commiters.

I'm hoping that this keeps the overhead managable, while providing a
clear chain of governance when required.

   http://wiki.osgeo.org/wiki/MetaCRS_PSC

Feedback welcome.  I'll likely call for a bootstrapping approval vote
early next week depending on the feedback.

PS. I have presumed to name myself as chair for now, not because I'm the
leading light on coordinate system matters, but rather because I have a
fair amount of experience facilitating open source project governance.

Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo, http://osgeo.org

_______________________________________________
MetaCRS mailing list
MetaCRS at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/metacrs