[Mapbender-dev] Inconsitent PSC job description
arnulf.christl at wheregroup.com
Fri May 11 12:58:52 EDT 2007
there are some inconsitencies in the PSC job description:
The PSC defines the Development and Voting Processes. The chair of the PSC is officer of the OSGeo Foundation and member of the OSGeo Incubation Committee. Beyond that the PSC and chair do not have a lot of things to do.
The development group grants committ access to the code repository. All Mapbender Contributors have been granted Wiki edit access to collaborate on all development processes. The OSGeo operates SVN software for the Mapbender Code Repository where code, deployment and versioning are managed. The repository is readble for the world, registered Mapbender developers also have commit access.
On the voting process page it says this:
Mapbender Project Steering Committtee
The Mapbender PSC is the day to day activity decision body. Mapbender Code Repository commit and Wiki Editor privileges can only be granted and revoked by the Mapbender PSC. This allows for quick action and is required to manage (operate, run, foster) the project. The inner circle comprises Mapbender developers and contributors (initially this was the CCGIS core development team). The Mapbender PSC is voted by Contributing Members.
I propose to change this to read what it says here:
Please discuss. If someone feels like working over the whole process feel free to do so. Have a look at MapServer's RFC23 and related pages, I think they did a good job there.
More information about the Mapbender_dev