pg.ddx.io  pgsql-students@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Page <dpage@postgresql.org>
To: Magnus Hagander <magnus@hagander.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Seeking Google SoC Mentors
Date: Tue, 27 Feb 2007 09:53:41 +0000
Message-ID: <45E3FFA5.2070708@postgresql.org> (raw)
In-Reply-To: <20070227093737.GH12721@svr2.hagander.net>
References: <200702261311.39684.josh@agliodbs.com>
	<45E34F9F.7090002@dunslane.net>
	<200702261550.14414.wt@penguintechs.org>
	<45E36722.1080703@dunslane.net>
	<9533.1172542238@sss.pgh.pa.us>
	<45E3F826.3080003@postgresql.org>
	<20070227093737.GH12721@svr2.hagander.net>

Magnus Hagander wrote:
> On Tue, Feb 27, 2007 at 09:21:42AM +0000, Dave Page wrote:
>> Tom Lane wrote:
>>> Andrew Dunstan <andrew@dunslane.net> writes:
>>>> Well, here's a question. Given the recent discussion re full 
>>>> disjunction, I'd like to know what sort of commitment we are going to 
>>>> give people who work on proposed projects.
>>> Um, if you mean are we going to promise to accept a patch in advance of
>>> seeing it, the answer is certainly not.  Still, a SoC author can improve
>>> his chances in all the usual ways, primarily by getting discussion and
>>> rough consensus on a spec and then on an implementation sketch before
>>> he starts to do much code.  Lots of showstopper problems can be caught
>>> at that stage.
>> We cannot necessarily expect the students to work this way without
>> guidance if they are not familiar with our processes before they start.
>> The mentors should be there to guide not just with the technical aspects
>> of the project, but the procedural as well imho.
> 
> IIRC, last time we had a pgsql-students (or similar) mailinglist for the
> SoC people. That was closed. Perhaps that's a bit counterproductive - it's
> better to get introduced to the "normal way of doing things" right away? 
> With the help of the mentor, of course.

Yes. The other issue though is that initial project proposal scoring and
discussion is done on a private Google site by the mentors. I don't know
if we're allowed to make the proposals public before they get accepted
by Google in case the students copy or improve each others proposals.
From their (and Google's) point of view their proposals are essentially
job applications.

Once they've been ranked, and Google have approved the top-N projects I
guess it's open season!

Regards, Dave



view thread (26+ messages)  latest in thread

Message-ID: <45E3FFA5.2070708@postgresql.org>
Permalink:  ../45E3FFA5.2070708@postgresql.org/
Also on:    postgresql.org/message-id/45E3FFA5.2070708@postgresql.org

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-students@postgresql.org
  Cc: dpage@postgresql.org, magnus@hagander.net, tgl@sss.pgh.pa.us, andrew@dunslane.net, pgsql-hackers@postgresql.org
  Subject: Re: Seeking Google SoC Mentors
  In-Reply-To: <45E3FFA5.2070708@postgresql.org>
  References: <200702261311.39684.josh@agliodbs.com> <45E34F9F.7090002@dunslane.net> <200702261550.14414.wt@penguintechs.org> <45E36722.1080703@dunslane.net> <9533.1172542238@sss.pgh.pa.us> <45E3F826.3080003@postgresql.org> <20070227093737.GH12721@svr2.hagander.net> <45E3FFA5.2070708@postgresql.org>

* 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