From 506fb46ad8e06b3c46de612373a2d600a1c270c9 Mon Sep 17 00:00:00 2001 From: JonathanGregory Date: Thu, 19 Sep 2024 11:22:38 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20Jonathan?= =?UTF-8?q?Gregory/cf-convention.github.io@a0c76ca56a9cc68423fb8a5b60d7da9?= =?UTF-8?q?1a8ef17f6=20=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- discussion.html | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/discussion.html b/discussion.html index 948408d47..89c8227ef 100644 --- a/discussion.html +++ b/discussion.html @@ -200,11 +200,7 @@

Questions, comments and a

To keep up-to-date with announcements and other discussions, go to the discuss repository and enable email notifications from the  Watch drop-down menu.

-

❓ Questions and answers about using CF

- -

💬 Comments and ideas for changing CF

- -

📣; [Announcements relevant to CF][github_announce]

+

❓ Questions and answers about using CF; ; 💬 Comments and ideas for changing CF; ; 📣 Announcements relevant to CF

Proposals to change CF

@@ -223,7 +219,9 @@

Proposals to change CF

For proposing enhancements and reporting defects in the CF conventions.

-

Closed issues: change agreed, agreement not to change, dormant i.e. 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.

+

Concluded issues: change agreed • agreement not to change • 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

    @@ -234,7 +232,7 @@

    Proposals to change CF

    -

    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.

    +

    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, general and standard-name discussion took place on the cf-metadata mailing list, and enhancements to the conventions were proposed on the CF Metadata Trac site.