|From:||Stephen Frost <sfrost(at)snowman(dot)net>|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Google Summer of Code is back for 2019! They have a similar set of
requirements, expectations, and timeline as last year.
Now is the time to be working to get together a set of projects we'd
like to have GSoC students work on over the summer. Similar to last
year, we need to have a good set of projects for students to choose from
in advance of the deadline for mentoring organizations.
The deadline for Mentoring organizations to apply is: February 6.
The list of accepted organization will be published around February 26.
Unsurprisingly, we'll need to have an Ideas page again, so I've gone
ahead and created one (copying last year's):
Google discusses what makes a good "Ideas" list here:
All the entries are marked with '2018' to indicate they were pulled from
last year. If the project from last year is still relevant, please
update it to be '2019' and make sure to update all of the information
(in particular, make sure to list yourself as a mentor and remove the
other mentors, as appropriate).
New entries are certainly welcome and encouraged, just be sure to note
them as '2019' when you add it.
Projects from last year which were worked on but have significant
follow-on work to be completed are absolutely welcome as well- simply
update the description appropriately and mark it as being for '2019'.
When we get closer to actually submitting our application, I'll clean
out the '2018' entries that didn't get any updates.
As a reminder, each idea on the page should be in the format that the
other entries are in and should include:
- Project title/one-line description
- Brief, 2-5 sentence, description of the project (remember, these are
- Description of programming skills needed and estimation of the
- List of potential mentors
- Expected Outcomes
As with last year, please consider PostgreSQL to be an "Umbrella"
project and that anything which would be considered "PostgreSQL Family"
per the News/Announce policy  is likely to be acceptable as a
PostgreSQL GSoC project.
In other words, if you're a contributor or developer on barman,
pgBackRest, the PostgreSQL website (pgweb), the PgEU/PgUS website code
(pgeu-website), pgAdmin4, PostgresXL, pgbouncer, Citus, pldebugger, the
PG RPMs (pgrpms), the JDBC driver, the ODBC driver, or any of the many
other PG Family projects, please feel free to add a project for
consideration! If we get quite a few, we can organize the page further
based on which project or maybe what skills are needed or similar.
Let's have another great year of GSoC with PostgreSQL!
|Next Message||Andres Freund||2019-01-07 22:12:04||Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)|
|Previous Message||didier||2019-01-07 21:44:24||Re: [proposal] Add an option for returning SQLSTATE in psql error message|