Re: about google summer of code 2016 - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: about google summer of code 2016
Date
Msg-id 56C6850C.8080307@anastigmatix.net
Whole thread Raw
In response to Re: about google summer of code 2016  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: about google summer of code 2016
List pgsql-hackers
On 02/18/16 19:35, Amit Langote wrote:

> Apparently, the deadline is: February 20, 2016 at 04:00 (+0900 UTC)
> 
> https://summerofcode.withgoogle.com/

For anybody finding that web site as anti-navigable as I did, here
are more direct links to the actual rules, and terms of agreement
for the various participants:

https://summerofcode.withgoogle.com/rules/
https://summerofcode.withgoogle.com/terms/org
https://summerofcode.withgoogle.com/terms/mentor
https://summerofcode.withgoogle.com/terms/student

Here is a question: does it ever happen that PostgreSQL acts as
the org for a project that is PostgreSQL-related but isn't
directly PGDG-led?

... there are definitely interesting and promising areas for further
development in PL/Java beyond what I would ever have time to tackle
solo, and I could easily enjoy mentoring someone through one or
another of them over a summer, which could also help reinvigorate
the project and get another developer familiar with it at a
non-superficial level.  While I could easily see myself mentoring,
I think it would feel like overkill to apply individually as a
one-trick 'organization'.

I see that there was a "based on PL/Java" GSoC'12 project, so maybe
there is some room for non-core ideas under the PostgreSQL ægis?

In any case, I am quite confident that I could *not* complete a
separate org application by tomorrow 2 pm EST. In reading the rules,
it looks possible that the Ideas List does not have to accompany
the org application, but would be needed shortly after acceptance?

If acceptance announcements are 29 February, I could have some
ideas drafted by then.

Is this a thinkable thought?

-Chap



pgsql-hackers by date:

Previous
From: Takashi Horikawa
Date:
Subject: Typo in bufmgr.c that result in waste of memory
Next
From: Michael Paquier
Date:
Subject: Re: exposing pg_controldata and pg_config as functions