I think there could be some benefits for this, but yes, we'd need to update the contribution guidelines to be really clear. Perhaps the easiest thing to do would be to clone the cf-conventions repo and rename that so that topical pull requests / discussions go there, and then once things have been integrated on that side pull them across to e.g. this repo, which would be used for releases, including syntactical / editorial changes in order to keep the adocs up to date. As @dblodgett-usgs notes this would be easier for users wanting to only be involved in the content-related discussions.
For me this seems overly complex, but if the community really wants to be able to restrict spamming it could be a good way to go. Personally, I think the better alternative would be to post to different lists based on issue tags - I've heard of Hubot integrations which allow this, for example. In that vein, I'd also be in favour of moving the Conformance into this repo, because that would make the workflow easier for ensuring that both the Conventions are updated simultaneously (I'm thinking of PR checks, as an example). -- 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/130#issuecomment-400762846
