@davidhassell agree with all your points. I also agree about the issue labels of changes being agreed or not, that would be easy to do and add value.
When we consider these process changes agreed, we should document them, e.g. in Rules.md or in the PR templates, in the form of a checklist. They're simple to do but would need easy presentation so that they don't get forgotten. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/345*issuecomment-1007261578__;Iw!!G2kpM7uM-TzIFchu!gtcpnk-hOgpXm09GDPhi-17oGQz664bIwNWGLLj_gZx1uTQLMeR9fdJ8aRnr1rzd71RuwuKWkVw$ You are receiving this because you are subscribed to this thread. Message ID: <cf-convention/cf-conventions/issues/345/[email protected]> This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
