Historically, the design of changes or features in Jaybird have been
documented inconsistently (or not at all). Which occasionally makes it
hard to reconstruct why things are the way they are.

To improve this, I'm starting something that I have called JDP (Jaybird
Design Proposal), which is similar to IETF's RFC, Java's JEP or Python's
PEP. Of course, as Jaybird is largely a one man show, the process will
not be as formal as those processes.

My primary intent is for this to help me structure design of new things
in Jaybird and hopefully solicit feedback. It will also provide
something to refer to when making changes or use to guide future design
decisions.

These documents are housed at
https://github.com/FirebirdSQL/jaybird/tree/master/devdoc/jdp

The first JDP, jdp-2019-01 defines this 'process':
https://github.com/FirebirdSQL/jaybird/blob/master/devdoc/jdp/jdp-2019-01-jaybird-design-proposal.md

If you have any feedback, let me know.

Mark

--
Mark Rotteveel