[Incubator] GRASS (and) PSC

[Frank Warmerdam]

Daniel Brookshier wrote:
> Here is a recommended way of running the process that is patterned after 
> several successful projects: 
> http://wiki.osgeo.org/index.php/Managing_Changes_to_Code

Daniel,

I am curious if any of the existing OSGeo projects follow a process like the
one above.  With mapserver there has been some question whether we should be
creating bugzilla entries for every code change but resisters like me have
kept this from being mandated.  I *feel* like it would make it hard to make
small improvements.

Also, do folks really browse through patches to see if they seem sensible?
I find patches very hard going as a rule for manual review.

Also, generally for mapserver we only do RFC's and PSC votes for "significant
changes" where significant is loosely defined in RFC-1.

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 OSGF, http://osgeo.org