[geomoose-psc] First draft of RFC4 - GeoMoose commit Management
Brian Fischer
bfischer at houstoneng.com
Fri Nov 30 13:41:23 PST 2012
My only comment is to strike this part of a statement. "and may be personally legally liable for improperly contributing code to the source repository"
Otherwise I think it looks good and have not further comments.
Brian Fischer, CFM
Principal | GIS Project Manager
Houston Engineering, Inc.
O 763.493.4522 | D 763.493.6664 | M 763.229.2734
From: geomoose-psc-bounces at lists.osgeo.org [mailto:geomoose-psc-bounces at lists.osgeo.org] On Behalf Of Basques, Bob (CI-StPaul)
Sent: Friday, November 30, 2012 10:52 AM
To: geomoose-psc at lists.osgeo.org
Subject: [geomoose-psc] First draft of RFC4 - GeoMoose commit Management
All,
I started a draft of RFC4 - GeoMoose Commit Management. This borrowed heavily from Mapserver RFC 7.1.
The main reason for moving this along was the legal piece at the bottom of the RFC related to Code contributions and related Licensing management. This chunk is a Incubation required Item.
Please review, edit and/or sign off on as you see fit.
There are a couple of outstanding pieces that I either didn't know right off, or didn't know how to grab or point at. You can do a search on "??" in the txt to find these locations about where clarification is needed.
NOTES:
* One item that may be a extra work item, is the need to include the COMMITTERS.txt file in the GeoMoose source tree.
* Probably already in place, but there will need to be a designated Commit Administrator.
I can start TRAC tickets if someone want to send me back titles for them.
Thanks
See attached.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20121130/e784f01b/attachment.html>
More information about the geomoose-psc
mailing list