Future project maintenance

I'm not currently using this project nor have I been closely following the advancements in the replication protocol. While I still have been reviewing and merging PRs my ability to adequately judge PRs has diminished. The best I can do is review for obvious errors. This is leading to holdups on PRs that probably should be merged like #68 as I don't have the sufficient context to know if the design is good.

I'd like to either add more maintainers to this project or coordinate a friendly fork or handoff.

If anyone has any suggestions or wants to volunteer, please reply here.

Start by reviewing this issue and the context of issue #68, then read the project's PostgreSQL logical replication responsibilities before proposing a maintainer addition, fork, or handoff. Done means the project has an agreed ownership or maintenance path; the issue names no specific files or tests to run.

Written by the indexing model from the issue text.