This will need significant discussion, but can largely be based on the existing work done for BIPs, ZAPs, EIPs, etc.
Of note, these initial drafts will skip 0003 as I believe it may be necessary to define an ERC-style (ORC?) documentation standard for non-protocol specific standards and having a consecutive number with the definition of OIPs seems logical.
The primary points of discussion that I can identify prior to drafting would be:
Defining 'maintainers'/'editors' - I believe this is a fundamental flaw with BIPs, but may be necessary short term until we can design/implement a more engineering-focused meritocratic system
Defining permissiveness for assignment of numbers - I am open to this being very permissive, but think that defining two buckets that we can sort these into would be good. All proposals that are not fundamentally flawed should receive a number, but be sorted based on if they 'align' with the existing technical standards/implementations. Example, Slanidro gets a number, but should be in the 'non-standard' bucket unless it has widespread support (social consensus).
Defining technical writing standards - Minimum licensing (see #5), community discussion/support, and even required analysis/documentation that is needed to support the inclusion of an OIP. This should err on the side of permissiveness, but still require a reasonable level of technical veracity expressed in a way that can be understood by the target audience (developers and technical users).
Additionally, I would like to include a nod to Casey for his amazing work that led us to this point and a direct link to support the Ordinals Project directly (as Raph is now the lead maintainer and is community funded).
This will need significant discussion, but can largely be based on the existing work done for BIPs, ZAPs, EIPs, etc.
Of note, these initial drafts will skip 0003 as I believe it may be necessary to define an ERC-style (ORC?) documentation standard for non-protocol specific standards and having a consecutive number with the definition of OIPs seems logical.
The primary points of discussion that I can identify prior to drafting would be:
Additionally, I would like to include a nod to Casey for his amazing work that led us to this point and a direct link to support the Ordinals Project directly (as Raph is now the lead maintainer and is community funded).