The next Summer of Code is just around the corner.

Last year, we had 46 submissions and seven we accepted. Out of the SoC we got
two ongoing contributors, several good patches, two code refactors and even
an employee for a PostgreSQL company. I'd like to see us do the same this
year!

Therefore, we need volunteer mentors. Here's how it works:

-- You help review and rate submissions in March.
-- From May-August, you mentor one or two SoC students in working on
PostgreSQL patches. This means that you must be readily available to your
student(s) during this summer and have time (2-5 hours per week, more at the
beginning) to coach them.
-- You need to evaluate the student's progress both midsummer and on
completion.
-- You prepare the student code for submission as an 8.4 feature, if
applicable.
-- Around October, Google gives SPI $500 for your mentoring. You can choose
to take this money (less transaction fees) or leave it as a donation. You
also get a nifty t-shirt.

We're looking for mentors who are:
-- patient
-- available
-- knowledgeable in depth in some particular area/add-in to PostgreSQL
-- interested in reviewing student code
-- interested in helping create the next generation of contributors

Particularly we'd like people who can mentor on:
-- PostgreSQL internals
-- GIS
-- applications & client tools
-- advanced indexing
-- XML
... based on last year's submissions, but there will be more this year.

Also, I am looking for contacts at universities where I can direct notices
when SoC opens.

E-mail me ASAP.

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Josh Berkus wrote:
> The next Summer of Code is just around the corner.
>
> Last year, we had 46 submissions and seven we accepted. Out of the SoC we got
> two ongoing contributors, several good patches, two code refactors and even
> an employee for a PostgreSQL company. I'd like to see us do the same this
> year!
>
> Therefore, we need volunteer mentors. Here's how it works:
>
> -- You help review and rate submissions in March.
> -- From May-August, you mentor one or two SoC students in working on
> PostgreSQL patches. This means that you must be readily available to your
> student(s) during this summer and have time (2-5 hours per week, more at the
> beginning) to coach them.
> -- You need to evaluate the student's progress both midsummer and on
> completion.
> -- You prepare the student code for submission as an 8.4 feature, if
> applicable.
> -- Around October, Google gives SPI $500 for your mentoring. You can choose
> to take this money (less transaction fees) or leave it as a donation. You
> also get a nifty t-shirt.
>
> We're looking for mentors who are:
> -- patient
> -- available
> -- knowledgeable in depth in some particular area/add-in to PostgreSQL
> -- interested in reviewing student code
> -- interested in helping create the next generation of contributors
>
> Particularly we'd like people who can mentor on:
> -- PostgreSQL internals
> -- GIS
> -- applications & client tools
> -- advanced indexing
> -- XML
> ... based on last year's submissions, but there will be more this year.
>
> Also, I am looking for contacts at universities where I can direct notices
> when SoC opens.
>
> E-mail me ASAP.
>
>

Is there a list of projects? Or can we suggest some?

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

On 2/26/07, Andrew Dunstan <andrew@dunslane.net> wrote:
> Josh Berkus wrote:
> > The next Summer of Code is just around the corner.
> >
> > Last year, we had 46 submissions and seven we accepted. Out of the SoC we got
> > two ongoing contributors, several good patches, two code refactors and even
> > an employee for a PostgreSQL company. I'd like to see us do the same this
> > year!
> >
> > Therefore, we need volunteer mentors. Here's how it works:
> >
> > -- You help review and rate submissions in March.
> > -- From May-August, you mentor one or two SoC students in working on
> > PostgreSQL patches. This means that you must be readily available to your
> > student(s) during this summer and have time (2-5 hours per week, more at the
> > beginning) to coach them.
> > -- You need to evaluate the student's progress both midsummer and on
> > completion.
> > -- You prepare the student code for submission as an 8.4 feature, if
> > applicable.
> > -- Around October, Google gives SPI $500 for your mentoring. You can choose
> > to take this money (less transaction fees) or leave it as a donation. You
> > also get a nifty t-shirt.
> >
> > We're looking for mentors who are:
> > -- patient
> > -- available
> > -- knowledgeable in depth in some particular area/add-in to PostgreSQL
> > -- interested in reviewing student code
> > -- interested in helping create the next generation of contributors
> >
> > Particularly we'd like people who can mentor on:
> > -- PostgreSQL internals
> > -- GIS
> > -- applications & client tools
> > -- advanced indexing
> > -- XML
> > ... based on last year's submissions, but there will be more this year.
> >
> > Also, I am looking for contacts at universities where I can direct notices
> > when SoC opens.
> >
> > E-mail me ASAP.
> >
> >
>
> Is there a list of projects? Or can we suggest some?

I'd like to suggest working on a patch testing tool that was discussed
previously.

Regards,
Mark

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Andrew,

> Is there a list of projects? Or can we suggest some?

Suggest away, please!

I'm going to update the website soon, would appreciate new content.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Josh Berkus wrote:
> Andrew,
>
>
>> Is there a list of projects? Or can we suggest some?
>>
>
> Suggest away, please!
>
> I'm going to update the website soon, would appreciate new content.
>
>

here are a few ideas to be going on with (none of these are new):

buildfarm:

1. Buildfarm web app: is in urgent need of renovation. (perl + postgres
+ template toolkit. might be nice to rework it as a Catalyst app).
2. Buildfarm client: support downloading patches from an approved
server, doing apply, build, install, and test. (perl + maybe SOAP)
3. Buildfarm client + web app: support running performance tests and
reporting on them (start with pgbench) (s/w as above)



postgres core:

4. allow use of LIKE syntax in all type expressions e.g. select * from
mysrf() as (label text, like foo); create type xx as (label text, like bar);


cheers

andrew





---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

On 2/26/07, Josh Berkus <josh@agliodbs.com> wrote:
> Andrew,
>
> > Is there a list of projects? Or can we suggest some?
>
> Suggest away, please!
>
> I'm going to update the website soon, would appreciate new content.

I can also volunteer to mentor continuing work on a TPC-E kit, for C
stored procedures and improved results reporting.

Mark

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

On Monday 26 February 2007 14:22, Andrew Dunstan wrote:
> Is there a list of projects? Or can we suggest some?

Temporal database support
* base data types
- verify current for ISO compliance (timestamp, interval)
- implement period datatype
* operators for those datatypes
* add support for valid time tables
* add support for transaction time tables
* add support for bi-temporal tables

Check out [1] for more info.

[1]http://www.cs.arizona.edu/~rts/

wt
--
Warren Turkal (w00t)

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Warren Turkal wrote:
> On Monday 26 February 2007 14:22, Andrew Dunstan wrote:
>
>> Is there a list of projects? Or can we suggest some?
>>
>
> Temporal database support
> * base data types
> - verify current for ISO compliance (timestamp, interval)
> - implement period datatype
> * operators for those datatypes
> * add support for valid time tables
> * add support for transaction time tables
> * add support for bi-temporal tables
>
>


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. I understand Warren's
keenness for this, but it's not clear to me that it has lots of support
elsewhere, and IIRC the idea was rejected by the SQL Standards body. I
don't object to making new data types available, but new table
properties is quite another matter.

So, what exactly are we promising?

cheers

andrew

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Could you also please share your thoughts on what would be a good
student profile- for instance, how much theoretical background and
practical experience, for working on a SoC project?

Demian

> The next Summer of Code is just around the corner.
>
> Last year, we had 46 submissions and seven we accepted. Out of the SoC we got
> two ongoing contributors, several good patches, two code refactors and even
> an employee for a PostgreSQL company. I'd like to see us do the same this
> year!
>
> Therefore, we need volunteer mentors. Here's how it works:
>
> -- You help review and rate submissions in March.
> -- From May-August, you mentor one or two SoC students in working on
> PostgreSQL patches. This means that you must be readily available to your
> student(s) during this summer and have time (2-5 hours per week, more at the
> beginning) to coach them.
> -- You need to evaluate the student's progress both midsummer and on
> completion.
> -- You prepare the student code for submission as an 8.4 feature, if
> applicable.
> -- Around October, Google gives SPI $500 for your mentoring. You can choose
> to take this money (less transaction fees) or leave it as a donation. You
> also get a nifty t-shirt.
>
> We're looking for mentors who are:
> -- patient
> -- available
> -- knowledgeable in depth in some particular area/add-in to PostgreSQL
> -- interested in reviewing student code
> -- interested in helping create the next generation of contributors
>
> Particularly we'd like people who can mentor on:
> -- PostgreSQL internals
> -- GIS
> -- applications & client tools
> -- advanced indexing
> -- XML
> ... based on last year's submissions, but there will be more this year.
>
> Also, I am looking for contacts at universities where I can direct notices
> when SoC opens.
>
> E-mail me ASAP.
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFF4204Ws7G5iIp9akRAh6yAKCMp3Fy66BsPmsAGQ7i6C wavE2hFQCgoIZG
66zWJUCOweH0LCgQA9NpotA=
=Ea5J
-----END PGP SIGNATURE-----

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Demian,

> Could you also please share your thoughts on what would be a good
> student profile- for instance, how much theoretical background and
> practical experience, for working on a SoC project?

Well, it shouldn't be the student's first year writing code. Basically,
they're committing to developing a feature *to completion* in 3 months.
We're going to be evaluating proposals based on whether we think students
can do that.

References of some kind will be important, given that we'll only be
accepting about 12% of proposals. So, some demonstration of the student's
ability to code from either the open source world or previous coursework.

I don't know, honestly, that we care very much about theoretical
background, except where it relates directly to and cutting-edge concepts
in you proposal. PostgreSQL-space is littered with half-completed
academic projects; we're not seeking more of those.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend