Re: Formatting Curmudgeons WAS: MMAP Buffers

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>, "Kevin Barnard" <kevinbarnard(at)mac(dot)com>
Cc: "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Formatting Curmudgeons WAS: MMAP Buffers
Date: 2011-05-13 21:47:16
Message-ID: 4DCD6094020000250003D7B0@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Barnard <kevinbarnard(at)mac(dot)com> wrote:

> A ticketing system with work flow could help with transparency.
> If it's setup correctly the work flow could help document where
> the item is in the review process. As another idea maybe have a
> status to indicate that the patch has been reviewed for
> formatting. It might make things easier to deal with because a
> ticket identified as WIP is obviously not ready for a CF etc etc.
> Hell you may even be able to find somebody to take care of
> reviewing formatting and dealing with those issues before it get's
> sent to a committer.

What you describe and more-is the intent of the CommifFest process
and its related web application. If you review these links and have
suggestions on how to improve the process, or how to make it more
obvious to newcomers, we'd be happy to hear about them.

http://wiki.postgresql.org/wiki/CommitFest

http://wiki.postgresql.org/wiki/Submitting_a_Patch

http://wiki.postgresql.org/wiki/Reviewing_a_Patch

http://wiki.postgresql.org/wiki/RRReviewers

https://commitfest.postgresql.org/action/commitfest_view/open

This process has, in my opinion, been a very big improvement on the
vagueness that came before.

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-05-13 22:02:16 Re: Double ocurring Subplan
Previous Message Brar Piening 2011-05-13 21:34:05 Re: Visual Studio 2010/Windows SDK 7.1 support