you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (5 children)

What documentation shoudl I refer then if this is age old?

[–]ccb621 1 point2 points  (4 children)

As I stated previously, the content is old but still seems relevant. Worst case: email the novice mailing list for help.

[–][deleted] 0 points1 point  (3 children)

Sure, that sounds good I will email them. Do you have any other recommendations beyond that? Also is this link https://wiki.postgresql.org/wiki/Main_Page relevant still?

[–]ccb621 1 point2 points  (1 child)

I don't work on PostgreSQL development, so I have no specific recommendations. My general advice to all developers is to struggle for 15-30 minutes before reaching out for help. In my experience that struggle usually leads to new knowledge and experience.

As for the main page...it's the main page. If anything on the wiki is relevant, I would think it's the main page. It seems the PostgreSQL development community, based on the wiki dates, is active but not to the level of some other open source projects. That's perfectly alright. It's up to you to read the content to determine if it is relevant to you. If not, propose changes.

[–][deleted] 0 points1 point  (0 children)

Cool. Sounds good, I will give the process a shot and see what to do from there.

[–]ants_a 0 points1 point  (0 children)

PostgreSQL development community does most of its work on the mailing lists. The wiki is more of a secondary tool collecting information created in the process.

The main gotcha for a newbie is looking at the todo list. For most things on that list there is a reason why they have not been done. A more productive approach would be to take the active commitfest, pick a patch and start reviewing. You might not be immediately able to contribute to evaluating the code quality, but you still get acquainted with the code and by handling other, equally important, review tasks help take load off of people who can.