[fdo-internals] Re: OSGeo FDO SVN Write Access

Robert Fortin robert.fortin at autodesk.com
Thu Jul 26 12:49:08 EDT 2007

Make sense.  That's basically the case we are facing.  The new committer
would work closely under the supervision of an existing committer.


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Frank
Warmerdam (External)
Sent: Thursday, July 26, 2007 12:48 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] Re: OSGeo FDO SVN Write Access

Robert Fortin wrote:
> Can't we expedite the process a bit assuming that the proposed change
> will be reviewed by existing committer before getting dropped?  Assume
> that the new code drop is a patch.
> Ultimately, they want to contribute to the community as much as they
> can.  And it starts by making them fully part of the community. 


The normal process for contributors before they are committers is to
pass their patches to a committer who would review them and commit them.
Does that satisfy your requirement?

I do think we need to treat the committer role reasonably seriously,
but I would be receptive to a new-committer motion for someone without
much of a track record on the project if there was an existing committer
who spoke well of their capability and offered to monitor their
contributions for a while.

Is that reasonable?

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,

fdo-internals mailing list
fdo-internals at lists.osgeo.org

More information about the fdo-internals mailing list