> Only accept patches on the mailing list

imho: PostgreSQL's practice of using mailing lists for patch submissions leads to thorough code reviews and deep community involvement. While less convenient than modern platforms, it ensures transparency and keeps the project independent of third-party services.

https://wiki.postgresql.org/wiki/Submitting_a_Patch

https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_develo...

recommended:

Tom MacWright "Polite Technology"

"This is a book about the social interactions and situations that are the underpinnings of the open source world. It's about how humans collaboratively create software."

https://macwright.com/sites/polite.technology/preview

"Maintaining open source software

Let's talk about everything except for software development. Sometimes the image of a software developer is a person typing, alone, all day long. In most cases, programming consumes less than half your actual work time, even if that's your job description. Some of that is hated busy-work, some of it is social interaction that keeps you sane, some of it is akin to emotional labor.

Technology changes and every project is unique but there are common components to this work, like interacting with people, supporting and critiquing the work of others, and explaining your craft.

Let's find the parts in common and pick ways of expressing them that are both productive and kind."