Thanks everyone for the suggestions. It sounds like the most useful thing I can do at the moment is perform code reviews. I assumed I'd need more experience with the PG code base, but I keep on reading that newcomers' reviews are welcome. Unless someone has a better idea, I'll start with that.
The projects that Pavel and David mentioned sound very interesting. Hopefully I can tackle one of them after I've done a few code reviews. Thanks again, Christian On Tue, Sep 6, 2016 at 4:20 AM, Aleksander Alekseev <a.aleks...@postgrespro.ru> wrote: > Hello, Christian > >> Can anyone suggest a project for my first PG contribution? > > In my experience good starting points are: > > * Doing code review. It's really important for PostgreSQL project. > Everyone likes to write code, no one likes to read or test it :) > * Finding typos, there are a lot of them. > * Finding bugs: static code analysis, sanitizers, etc. Also subscribe to > pgsql-bugs@ mailing list. > * Fixing bottlenecks. Tricky part here is to find one. Could be > difficult unless you are working for a company with many clients or > maintain a project that uses PostgreSQL. > > Also please note that such activity as answering questions on IRC or in > pgsql-general@, highlighting project news in your blog, writing articles > (or maybe even a book) about PostgreSQL internals, organizing local user > group, etc - all of this are very significant contributions. > > Good luck! > > -- > Best regards, > Aleksander Alekseev -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
