I've asked for permissions to edit that doc, but in the meantime, here is a summary:
Both due to a maturing project and new tools it's a good time to discuss and perhaps update and/or clarify how proposals for changes to CF are managed. The CF conventions have been managed in gitHub for a while now, so that we now have a bit of experience with the system. It has worked fairly well in some cases, not so well in others. We will review the current rules for convention changes: http://cfconventions.org/rules.html, and discuss what's worked well, what has not, and mull over possible ideas from improvements. This discussion relates to the following issues in gitHub: https://github.com/cf-convention/cf-conventions/issues/151 https://github.com/cf-convention/cf-conventions/issues/130 https://github.com/cf-convention/cf-conventions/issues/172 (most of which are closed, but provide context) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/151#issuecomment-636204892 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].
