[postgis-devel] [MOTION] Give commit rights to Martin Davis (was: Becoming a committer for PostGIS docs?)

Regina Obe lr at pcorp.us
Thu Mar 28 08:13:09 PDT 2019


Don't forget even though Martin is practically part of the family, you still need to read him the riot act.

> -----Original Message-----
> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On
> Behalf Of Paul Ramsey
> Sent: Thursday, March 28, 2019 11:04 AM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> Subject: Re: [postgis-devel] [MOTION] Give commit rights to Martin Davis
> (was: Becoming a committer for PostGIS docs?)
> 
> +1 Paul
> 
> On Thu, Mar 28, 2019 at 7:27 AM Regina Obe <lr at pcorp.us> wrote:
> >
> > +1
> >
> > > -----Original Message-----
> > > From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org]
> > > On Behalf Of Sandro Santilli
> > > Sent: Thursday, March 28, 2019 5:18 AM
> > > To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> > > Subject: [postgis-devel] [MOTION] Give commit rights to Martin Davis
> (was:
> > > Becoming a committer for PostGIS docs?)
> > >
> > > Started new thread to be an official call.
> > >
> > > In short: shall we give Martin Davis commit access to PostGIS repository ?
> > >
> > > +1 from me.
> > >
> > > More info follows, with inline comments.
> > >
> > > On Wed, Mar 27, 2019 at 02:28:52PM -0700, Martin Davis wrote:
> > >
> > > > I've been working on creating doc patches.  Thanks to some good
> > > > reviews and Sandro being the commiter, have been making their way
> > > > into
> > > trunk.
> > >
> > > For proper credit: it was not me committing those changes but
> > > Darafei Praliaskouski (Komzpa). You was probably fooled by my avatar
> > > pushing the commits from SVN to GIT for the mirrors.
> > >
> > > > To streamline this process for the benefit of all, I'd like to
> > > > request to become a PostGIS committer.  Would it be possible for
> > > > the PSC to follow due process and make this happen?
> > >
> > > I can anticipate my +1, but beware of technology traps (we're using
> > > SVN, not GIT! ready for git-svn foo ?)
> > >
> > > > To put some context around this, I only expect to be submitting
> > > > doc patches.  And I'm happy to surface them as GitHub PRs to allow
> > > > review before commiting (within a reasonable timebox, ideally).
> > >
> > > Note you can use any of the GIT based mirrors to send PRs for review:
> > > https://trac.osgeo.org/postgis/wiki/CodeMirrors
> > >
> > > GitLab also allows inline comments to patches, and has CI testing
> > > changes (same as the OSGeo Gitea instance).
> > >
> > > > The other reason for asking for commit access is that Crunchy Data
> > > > is joining the Google Season of Docs program, and I'm going to
> > > > propose that PostGIS participate in this with me as a mentor.
> > > > This will likely go more efficiently if Im a committer.  I'll send
> > > > out a more specific
> > > email soon.
> > >
> > > Thanks !
> > >
> > > --strk;
> > > _______________________________________________
> > > postgis-devel mailing list
> > > postgis-devel at lists.osgeo.org
> > > https://lists.osgeo.org/mailman/listinfo/postgis-devel
> >
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/postgis-devel
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-devel



More information about the postgis-devel mailing list