[Geomoose-users] RFC-4: GeoMoose Commit Management

[Brian Fischer]

Jim just one small commit to this sentence.  I would add a sentence at the end to handle the situation if no one is found to manage the code.  Otherwise looks good to me.

"The new committer should also be prepared to support any new feature or changes that he/she commits to the GeoMOOSE source tree in future releases, or to find someone to which to delegate responsibility for them if he/she stops being available to support the portions of code that he/she is responsible for."  ADD SOMETHING LIKE THIS.  In the event no delegate is found to support the code, it will be subject to removal pending discussion by the PSC.  Each feature that falls into this situation will be handled on a case by case basis.

Brian Fischer
Principal | GIS Project Manager 
Houston Engineering, Inc.
O 763.493.4522 | D 763.493.6664 | F 763.493.5572


-----Original Message-----
From: geomoose-users-bounces at lists.osgeo.org [mailto:geomoose-users-bounces at lists.osgeo.org] On Behalf Of Jim Klassen
Sent: Thursday, June 20, 2013 7:16 AM
To: geomoose-users at lists.osgeo.org List
Subject: [Geomoose-users] RFC-4: GeoMoose Commit Management

Are there any final comments on RFC-4: GeoMoose Commit Management?  It has been sitting out there for almost a month now.

If not, I will call a vote on RFC-4 next week.
_______________________________________________
Geomoose-users mailing list
Geomoose-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/geomoose-users