Re: gSoC - ADD MERGE COMMAND - code patch submission - Mailing list pgsql-hackers

From Greg Smith
Subject Re: gSoC - ADD MERGE COMMAND - code patch submission
Date
Msg-id 4C3BA5CE.1000006@2ndquadrant.com
Whole thread Raw
In response to Re: gSoC - ADD MERGE COMMAND - code patch submission  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: gSoC - ADD MERGE COMMAND - code patch submission
List pgsql-hackers
Tom Lane wrote:
> Is there a specific period when that's supposed to happen for GSoC
> students?  Can we arrange for a commitfest to be running then

The GSoC "Community bonding period" is described at 
http://googlesummerofcode.blogspot.com/2007/04/so-what-is-this-community-bonding-all.html 
and what to cover is a near perfect match for things like introducing 
the patch review and submission process.  This year, the period from 
when proposals were accepted on April 26th through the official coding 
start on May 24th were labeled as being devoted to that.  Given the way 
the release schedule has worked out the last few years, I expect that 
every year there will be a whole stack of possibly moldy patches sitting 
in the queue for the first CF of the next version at that point.  I 
don't think we necessarily need to organize a full on CF around that 
schedule, but picking a small patch for each student to start chewing on 
during that period would usefully settle them into list interaction and 
community development process much more gradually than starting that 
with their code drops. 

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: gSoC - ADD MERGE COMMAND - code patch submission
Next
From: Tom Lane
Date:
Subject: explain.c: why trace PlanState and Plan trees separately?