├── .github ├── DISCUSSION_TEMPLATE │ ├── comments-and-ideas-for-changing-cf.yml │ └── q-a-about-using-cf.yml └── ISSUE_TEMPLATE │ └── config.yml └── README.md /.github/DISCUSSION_TEMPLATE/comments-and-ideas-for-changing-cf.yml: -------------------------------------------------------------------------------- 1 | body: 2 | - type: textarea 3 | attributes: 4 | label: Topic for discussion 5 | description: | 6 | Comment on some aspect of CF that you think we should consider changing: how it could be improved, what's wrong with it, what its purposes should be, whether it could be managed better, etc. Please add one or more of the labels `conventions`, `vocabulary` (standard names etc.), `website`, `governance` or `GitHub`, to indicate which area of CF the discussion is relevant to, by clicking on the cogwheel :gear: next to **Labels** on the top right of this form. Apply more than one label if it's unclear which is applicable. You can also add and remove labels after starting the discussion. 7 | placeholder: Type in here. Markdown is supported, and you will be able to preview your text before posting it. 8 | validations: 9 | required: true 10 | -------------------------------------------------------------------------------- /.github/DISCUSSION_TEMPLATE/q-a-about-using-cf.yml: -------------------------------------------------------------------------------- 1 | body: 2 | - type: textarea 3 | attributes: 4 | label: Question 5 | description: | 6 | Ask a question about some aspect of CF e.g. how to do something, what something means, what standard name to choose, why something isn't working as expected, where to find some information, how to make a suggestion for change. Please add one or more of the labels `conventions`, `vocabulary` (standard names etc.), `website`, `governance` or `GitHub`, to indicate which area of CF the discussion is relevant to, by clicking on the cogwheel :gear: next to **Labels** on the top right of this form. Apply more than one label if it's unclear which is applicable. You can also add and remove labels after starting the discussion. 7 | placeholder: Type in here. Markdown is supported, and you will be able to preview your text before posting it. 8 | validations: 9 | required: true 10 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | contact_links: 3 | - name: Q&A about using CF 4 | url: https://github.com/orgs/cf-convention/discussions/new?category=q-a-about-using-cf 5 | about: Ask a question about how to use any aspect of CF or how it works (conventions, vocabulary, website, governance, GitHub etc.) 6 | - name: Comments and ideas for changing CF 7 | url: https://github.com/orgs/cf-convention/discussions/new?category=comments-and-ideas-for-changing-cf 8 | about: Start a discussions about an improvement to any aspect of CF (conventions, vocabulary, website, governance, GitHub etc.) 9 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # CF metadata discussions 2 | A forum for asking questions about the interpretation and use of the CF conventions, and suggestions for proposals to change or extend the CF conventions. 3 | To get started, create a [new issue](https://github.com/cf-convention/discuss/issues/new/choose). 4 | 5 | A complete proposal for an enhancement to the CF conventions (that may have well started as a conversation on this forum) should be raised as an issue on the cf-conventions repository: https://github.com/cf-convention/cf-conventions/issues 6 | --------------------------------------------------------------------------------