| layout | title | group |
|---|---|---|
default |
Discussion |
navigation |
CF discussions and decisions are mostly made on [GitHub][github]. No registration with CF is required to contribute; all that is needed is a freely available GitHub account.
In CF GitHub organization Discussions you can ask a question about how to use CF, comment on any aspect of CF or make a suggestion how CF could be changed or improved, contribute to any of the ongoing discussions, and read the previous ones. Announcements about CF are made there as well.
To keep up-to-date with announcements and discussions, go to the [discuss repository][github_discuss] and enable notifications from the
Watch drop-down menu.
Discussions by category: ❓ Questions and answers about using CF 💬 Comments and ideas for changing CF 📣 Announcements relevant to CF
Proposals to change CF are made, debated and decided as [GitHub issues][github_issues] in three repositories:
-
[Vocabulary issues][github_vocabularies], in the vocabularies repository, for proposing additions or amendments to standard names, their definitions, or other CF controlled vocabulary (area types and standardized regions). Open a new issue. See also [closed vocabulary issues][github_vocabularies_closed].
As well as in GitHub issues, the status of proposals about standard names is shown by the [CEDA vocabulary editor][vocab_editor]. To see a list of resolved proposals (accepted or rejected) for standard names from March 2011 onwards, click "Inactive" in the [CEDA vocabulary editor][vocab_editor].
-
Conventions issues, in the conventions repository, for proposing enhancements and reporting defects in the CF conventions. Open a new issue. See also closed conventions issues, classified by reason for closure: [change agreed][github_conventions_change] • [agreement not to change][github_conventions_nochange] • [dormant][github_conventions_dormant]. "Dormant" means the discussion on a proposed change did not reach a conclusion. Dormant issues may be reopened if there is a new impetus or ideas that might help bring about an agreement.
-
[Website and governance issues][github_website], in the website repository, for proposing changes and reporting defects in the [CF website][website] or CF governance. Open a new issue.
You can enable notifications of updates to issues for each kind of issue separately using the Watch menu in its repository.
Announcements, discussions and Q&A that were initiated before CF GitHub Discussions began are continuing as GitHub issues in the discuss repository. They will soon be converted to GitHub Discussions.
Before the CF community migrated to GitHub:
-
until December 2019, general discussion took place and standard names were proposed on the [cf-metadata mailing list][archives] ([original at NCAR][NCAR_archives]).
-
until July 2018, changes to the conventions were proposed on the [CF Metadata Trac][about] site.
[github_conventions_change]: https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:"change agreed" [github_conventions_nochange]: https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:"agreement not to change" [github_conventions_dormant]: https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:dormant [github_discuss]: https://github.com/cf-convention/discuss/issues [github_vocabularies]: https://github.com/cf-convention/vocabularies/issues [github_vocabularies_closed]: https://github.com/cf-convention/vocabularies/issues?q=is:issue+is:closed [github_website]: https://github.com/cf-convention/cf-convention.github.io/issues [github]: https://github.com [website]: https://cfconventions.org [trac]: Data/trac.html [about]: about-trac.md [mail]: http://mailman.cgd.ucar.edu/mailman/listinfo/cf-metadata [archives]: https://cfconventions.org/mailing-list-archive/Data/ [NCAR_archives]: https://mailman.cgd.ucar.edu/pipermail/cf-metadata/ [current]: https://cfeditor.ceda.ac.uk/proposals/1 [vocab_editor]: https://cfeditor.ceda.ac.uk/proposals/1 [github_issues]: https://guides.github.com/features/issues