Re: Summer of Code Preparation

From: Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Josh Berkus <josh(at)agliodbs(dot)com>
Subject: Re: Summer of Code Preparation
Date: 2006-04-06 16:39:37
Message-ID: 20060406163937.GG27103@quartz.itdept.newn.cam.ac.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 06, 2006 at 06:31:01AM -0500, Jim C. Nasby wrote:
> On Wed, Apr 05, 2006 at 11:55:15PM -0300, Marc G. Fournier wrote:
> > On Wed, 5 Apr 2006, Jim Nasby wrote:
> >
> > >One idea that comes to mind is to come up with a list of popular OSS
> > >projects that we'd like to see add PostgreSQL support and have students
> > >work on those...
> >
> > As nice an idea as this is, we'd also need to quickly co-ordinate with
> > those projects to make sure that there is a semblance of a chance of
> > having those patches included in their distribution ... I realize that the
> > Code of Summer program doesn't need a guarantee that the code will be
> > committed, but if we're going to do something like the above, would rather
> > see it done for projects that wanted the end results ...
>
> Absolutely, though we can't do that without a list of possibilities
> first. People want to start throwing out names? (I can't really think of
> any off the top of my head, other than OpenQRM, but I have ulterior
> motives for that one so perhaps my vote shouldn't count. :) )

Was that throw out names for projects? How about Postgres-R for PostgreSQL-8?
Even if nothing comes out of it, both databases and group communications
are excellent CS topics for a student.

Cheers,

Patrick

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Hallgren 2006-04-06 16:56:24 Re: Support Parallel Query Execution in Executor
Previous Message William ZHANG 2006-04-06 15:30:22 Re: Strange results from to_timestamp