Development protocol for NIPs standards

[weex]

Hello, I went looking for guidelines as to how to interact with this repository and couldn't find anything so I'm asking here, if there's are contribution guidelines or a development protocol that is being followed. The README offers the following guidance:

Criteria for acceptance of NIPs

1. They should be implemented in at least two clients and one relay -- when applicable.
2. They should make sense.
3. They should be optional and backwards-compatible: care must be taken such that clients and relays that choose to not implement them do not stop working when interacting with the ones that choose to.
4. There should be no more than one way of doing the same thing.
5. Other rules will be made up when necessary.

This does not touch on things like:

• what makes a good issue?
• what's expected in a pull request?
• do NIPs become final and what changes are allowed after that?
• what are the responsibilities of the maintainers before merging?

At this time there are 96 open pull requests only a few of which are draft of WIP and I'd love to help get that number down to increase development speed and agility.

On behalf of current and future contributors, I appreciate your thoughts and guidance.

Edit: Since I've been interested in this aspect of open source projects and protocols, I'd like to offer the potential solution of adopting https://rfc.zeromq.org/spec/42/ which addresses 3/4 of the bulleted concerns above.

[securitybrahh]

I think issues should be very specific to the problems with implementation possiblities (NIP's), otherwise it goes in discussions.

Pull request writer should be familiar with similar NIP's, issues, and PR's and nostr at large (how different clients and relays work, and the ecosystem works) hence there should be mention of those.

no NIP is final, but any amendments should be reasonabily backward campatable.

consensus with different maintainers, I think we should have a bot similar to what bitcoin ppl have, though not as extensive at first, just ACK, NOTACK for now? https://github.com/maflcko/DrahtBot

@fiatjaf @staab

Appendix A:

https://github.com/bitcoin/bips/blob/master/bip-0003.md

bolt vs blip vs rfc vs ietr vs NUT vs