pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Greg Smith <greg@2ndQuadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Last gasp
Date: Wed, 11 Apr 2012 06:04:42 -0400
Message-ID: <4F85573A.3070807@2ndQuadrant.com> (raw)
In-Reply-To: <CA+TgmoaN2wi85HVS-xuZkw9O6O_RmF4ovxX+=n6o2x6a1S2b-A@mail.gmail.com>
References: <CA+Tgmoa75QujxzCZC+dj=0+JayGPhJD2kQMDBmbGmmq_HPgHxw@mail.gmail.com>
	<CAAZKuFbHQA6Q3hO5amMLh6Zvh=-8tdKeQFUacdDVREnvp889Jg@mail.gmail.com>
	<4F7E99BA.1080805@2ndQuadrant.com>
	<CA+TgmoaRRSyLQ4qaW82aLQ1bM40oJ-eZc0mWXsBF2__xjH4xzA@mail.gmail.com>
	<20120409053852.GG11987@tornado.leadboat.com>
	<CA+TgmoZphWOJdF7AjBGs1Awf6QM3Gb0e+kvZe4+8-uyBTgSsJg@mail.gmail.com>
	<20120409222359.GE30702@tornado.leadboat.com>
	<CA+TgmobrGWaatFbuMGJKL4J2AcJCaw3hF-37r8xmxHg7v98smw@mail.gmail.com>
	<CAFNqd5V274gzVEAX7q=nwGn3eTsPa+B_E_WkQ8oPu1ZEYxa1eg@mail.gmail.com>
	<4F83FCB10200002500046D70@gw.wicourts.gov>
	<CAEYLb_W3hOXQYGEA=aJCk-Y-7OFak4V7e3vT1y-XcMukGY3-tQ@mail.gmail.com>
	<CA+TgmoY+p8BiRPgCQQdON_a4DQvy3Hx03ug-j2eL8=Za_88WFQ@mail.gmail.com>
	<CAEYLb_VUiz57BeDy8d2gWQt_HRn9xpw83gt7MS0+wYmUopasrA@mail.gmail.com>
	<CA+TgmoZLWG=napMA-Fx4u8PTGDkY2CMz84LXAACsvhKRL+D2vg@mail.gmail.com>
	<4F84D3A0.8010808@2ndQuadrant.com>
	<CA+TgmoaN2wi85HVS-xuZkw9O6O_RmF4ovxX+=n6o2x6a1S2b-A@mail.gmail.com>

On 04/10/2012 09:14 PM, Robert Haas wrote:
> I wouldn't object to creating some doc-only committers.  OTOH, I would
> object to anyone making non-trivial documentation enhancements without
> posting their patches first and having a second person look it over,
> so how much difference is there, really?

This workflow is the easy one:

-Committer suggests doc change
-No one has an opinion against it strong enough to comment, or minor 
review comments are made
-Commit change with feedback when received

That's a predictable, short process unless the change is controversial, 
in which case good feedback normally comes out of that discussion.  And 
if I feel review is needed but don't catch any volunteers, there is a 
much broader pool of people who can be hired to help with review work, 
relative to the size of the committer one.

Compare with:

-Submitter suggests doc change
-No one has a strong opinion on it, may not be picked up at all
-Submitter adds to the next CF
-Wait for review
-[Possible repost update with reviewer changes]
-Ready for committer
-Committer takes time away from code review to look at it
-Possibly another feedback/review resubmission
-Commit final versions

It's usually not this bad, but in every case it's pulling resources off 
of more valuable jobs.

I'd like to dump around 50 pages of new material into the docs as a 
start, but I don't want to take so much time away from the code oriented 
committers to chew on that much.

-- 
Greg Smith   2ndQuadrant US    greg@2ndQuadrant.com   Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com



view thread (161+ messages)  latest in thread

Message-ID: <4F85573A.3070807@2ndQuadrant.com>
Permalink:  ../4F85573A.3070807@2ndQuadrant.com/
Also on:    postgresql.org/message-id/4F85573A.3070807@2ndQuadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: greg@2ndQuadrant.com, robertmhaas@gmail.com
  Subject: Re: Last gasp
  In-Reply-To: <4F85573A.3070807@2ndQuadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox