We segregate responsibilities so no one has complete control of the PostgREST project. For example, begriffs[1] is in charge of handling the funds (Patreon), wo

We segregate responsibilities so no one has complete control of the PostgREST project. For example, begriffs[1] is in charge of handling the funds (Patreon), wolfgangwalther[2] owns the .org and .com domains and both are owners of the PostgREST's GitHub org. For development, this ensures I don't go crazy and add some feature that is Supabase-specific, since I'm not the only one who has a say in the project's direction. This has been working well until now and if you follow PostgREST's development, you'll notice that all enhancements are vendor-neutral and keep the original design. We're a much smaller team but we took some inspiration from PostgreSQL distributed model (no single company owns development) for this. [1]: PostgREST author https://github.com/begriffs https://github.com/begriffs [2]: Also part of the PostgREST team and major contributor https://github.com/PostgREST/postgrest/graphs/contributors https://github.com/PostgREST/postgrest/graphs/contributors