| From: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> | 
|---|---|
| To: | Christian Convey <christian(dot)convey(at)gmail(dot)com> | 
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: Suggestions for first contribution? | 
| Date: | 2016-09-06 08:20:27 | 
| Message-ID: | 20160906082026.GA91749@e733 | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Ullrich | 2016-09-06 08:36:45 | Re: pgsql: Add putenv support for msvcrt from Visual Studio 2013 | 
| Previous Message | Simon Riggs | 2016-09-06 08:12:18 | Re: Proposal for changes to recovery.conf API |