From October 29th - November 5th I'll host a Discord group of folks who want to dig into Postgres internals: write about it, try to break it, fix a bug in it, or improve the docs.
Basically, a support group for people who want to figure this stuff out together.
If all we do is get more folks looking at Postgres code, building it, and trying out tweaks to it -- without any contributions merged -- I'd see it as a success. If the week produces any new contributions merged into Postgres, fantastic.
Existing Postgres contributors are welcome to join.
In order to cut down on mod effort and the likelihood of this turning into the worst of Hacktoberfest, I'm going to limit invites to Discord to folks who have been programmers for a bit and can provide social proof such as a GitHub, LinkedIn, or technical website.
It is imperative to be respectful of open-source maintainers. And folks caught doing otherwise will get booted from the Discord.
After November 5th the Discord will be deleted. Any contributions made to Postgres (docs, bug fixes, etc.) will be noted on this page afterward, as will any non-trivial blog posts or GitHub projects showing something interesting about Postgres (created during the course of the event).
I'll also add to this page resources folks share for Postgres internals and contributing to Postgres.
Sign up here and I'll email you an invite to Discord.
Signups are now closed! Join us another time! :)
Postgres internals resources that were shared during the week.
Projects and posts that came out during, or as a result of, the week.