pg.ddx.io  pgsql-students@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim C. Nasby <jim@nasby.net>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Seeking Google SoC Mentors
Date: Tue, 27 Feb 2007 00:47:14 -0500
Message-ID: <12559.1172555234@sss.pgh.pa.us> (raw)
In-Reply-To: <20070227044345.GI29041@nasby.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>
	<20070227044345.GI29041@nasby.net>

"Jim C. Nasby" <jim@nasby.net> writes:
> Yes, but the list being discussed is SoC projects that the community
> would like to see done, which means most people would assume that #1
> isn't an issue.

> We need to make sure that every project on the list of SoC ideas is
> supported by the community.

Agreed, except that in most cases a one-liner description of an idea
isn't enough to get a meaningful reading on whether people think it's
sane or not.  To take our current example: do you think a one-liner
description of full disjunctions would have gotten any feedback, except
for requests for more detail?

I'm not sure how we fix that --- laying out every acceptable project
in great detail in advance won't happen for lack of manpower, and wouldn't
be a good idea even if we could do it, because that sounds like a great
way to stifle creativity.  At the same time we can hardly promise to
accept every wild-west idea that someone manages to turn into some kind
of code.  What can we tell the students other than "get as much feedback
as you can, as early as you can"?

			regards, tom lane



view thread (26+ messages)  latest in thread

Message-ID: <12559.1172555234@sss.pgh.pa.us>
Permalink:  ../12559.1172555234@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/12559.1172555234@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, jim@nasby.net, andrew@dunslane.net, pgsql-hackers@postgresql.org
  Subject: Re: Seeking Google SoC Mentors
  In-Reply-To: <12559.1172555234@sss.pgh.pa.us>
  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> <20070227044345.GI29041@nasby.net> <12559.1172555234@sss.pgh.pa.us>

* 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