Deploying to gh-pages from @ fc83459 🚀

discussion.html

@@ -191,44 +191,50 @@
 
       <h1 id="discussion">Discussion</h1>
 
-<p>CF is carrying out a trial (beginning in March 2024) of using the CF <a href="https://github.com/orgs/cf-convention/discussions">GitHub organization Discussions</a> for announcements relevant to CF, community discussion of comments and ideas for changing CF, and for questions and answers about how to use CF.</p>
+<p>CF discussions and decisions are mostly made on <a href="https://github.com">GitHub</a>. No registration with CF is required to contribute; all that is needed is a freely available GitHub account.</p>
 
-<p>Announcements, discussions and Q&amp;A that were initiated <em>before</em> the trial of CF GitHub Discussions began are continuing as <a href="https://guides.github.com/features/issues">GitHub issues</a> in the <a href="https://github.com/cf-convention/discuss/issues"><code class="language-plaintext highlighter-rouge">discuss</code> repository</a>. (These might later be moved to GitHub Discussions if the trial is successful.)</p>
+<h3 id="questions-comments-and-announcements-about-cf">Questions, comments and announcements about CF</h3>
 
-<p>Proposals for changing CF are discussed as <a href="https://guides.github.com/features/issues">GitHub issues</a> in three repositories:</p>
+<p>In CF <a href="https://github.com/orgs/cf-convention/discussions">GitHub organization Discussions</a> you can <a href="https://github.com/orgs/cf-convention/discussions/new?category=q-a-about-using-cf">ask a question</a> about how to use CF, <a href="https://github.com/orgs/cf-convention/discussions/new?category=comments-and-ideas-for-changing-cf">comment</a> 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.</p>
+
+<p>To keep up-to-date with announcements and discussions, go to the <a href="https://github.com/cf-convention/discuss/issues"><code class="language-plaintext highlighter-rouge">discuss</code> repository</a> and enable notifications from the <svg aria-hidden="true" height="16" version="1.1" width="16" data-view-component="true" class="octicon octicon-eye"><path d="M8 2c1.981 0 3.671.992 4.933 2.078 1.27 1.091 2.187 2.345 2.637 3.023a1.62 1.62 0 0 1 0 1.798c-.45.678-1.367 1.932-2.637 3.023C11.67 13.008 9.981 14 8 14c-1.981 0-3.671-.992-4.933-2.078C1.797 10.83.88 9.576.43 8.898a1.62 1.62 0 0 1 0-1.798c.45-.677 1.367-1.931 2.637-3.022C4.33 2.992 6.019 2 8 2ZM1.679 7.932a.12.12 0 0 0 0 .136c.411.622 1.241 1.75 2.366 2.717C5.176 11.758 6.527 12.5 8 12.5c1.473 0 2.825-.742 3.955-1.715 1.124-.967 1.954-2.096 2.366-2.717a.12.12 0 0 0 0-.136c-.412-.621-1.242-1.75-2.366-2.717C10.824 4.242 9.473 3.5 8 3.5c-1.473 0-2.825.742-3.955 1.715-1.124.967-1.954 2.096-2.366 2.717ZM8 10a2 2 0 1 1-.001-3.999A2 2 0 0 1 8 10Z"></path>
+</svg> <b>Watch</b> drop-down menu.</p>
+
+<p>Discussions by category: ❓ <a href="https://github.com/orgs/cf-convention/discussions/categories/q-a-about-using-cf">Questions and answers about using CF</a>  💬 <a href="https://github.com/orgs/cf-convention/discussions/categories/comments-and-ideas-for-changing-cf">Comments and ideas for changing CF</a>  📣 <a href="https://github.com/orgs/cf-convention/discussions/categories/announcements-relevant-to-cf">Announcements relevant to CF</a></p>
+
+<h3 id="proposals-to-change-cf">Proposals to change CF</h3>
+
+<p>Proposals to change CF are made, debated and decided as <a href="https://guides.github.com/features/issues">GitHub issues</a> in three repositories:</p>
 
 <ul>
   <li>
-    <p><a href="https://github.com/cf-convention/vocabularies/issues">Vocabulary</a></p>
+    <p><a href="https://github.com/cf-convention/vocabularies/issues">Vocabulary issues</a>, in the <a href="https://github.com/cf-convention/vocabularies">vocabularies repository</a>, for proposing additions or amendments to standard names, their definitions, or other CF controlled vocabulary (area types and standardized regions). <a href="https://github.com/cf-convention/vocabularies/issues/new/choose">Open a new issue</a>. See also <a href="https://github.com/cf-convention/vocabularies/issues?q=is:issue+is:closed">closed vocabulary issues</a>.</p>
 
-    <p>For proposing additions or amendments to standard names, their definitions, or other CF controlled vocabulary (area types and standardized regions).</p>
-
-    <p>As well as in GitHub issues, the status of proposals about standard names is shown by the <a href="https://cfeditor.ceda.ac.uk/proposals/1">CEDA vocabulary editor</a>. To see a list of resolved proposals (accepted or rejected) for standard names from March 2011 onwards, click “Inactive” in the <a href="https://cfeditor.ceda.ac.uk/proposals/1">CEDA vocabulary editor</a></p>
+    <p>As well as in GitHub issues, the status of proposals about standard names is shown by the <a href="https://cfeditor.ceda.ac.uk/proposals/1">CEDA vocabulary editor</a>. To see a list of resolved proposals (accepted or rejected) for standard names from March 2011 onwards, click “Inactive” in the <a href="https://cfeditor.ceda.ac.uk/proposals/1">CEDA vocabulary editor</a>.</p>
   </li>
   <li>
-    <p><a href="https://github.com/cf-convention/cf-conventions/issues">Conventions</a></p>
-
-    <p>For proposing enhancements and reporting defects in the CF conventions.</p>
-
-    <p>Closed issues: <a href="https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:&quot;change agreed&quot;">change agreed</a>, <a href="https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:&quot;agreement not to change&quot;">agreement not to change</a>, <a href="https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:dormant">dormant</a> 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.</p>
+    <p><a href="https://github.com/cf-convention/cf-conventions/issues">Conventions issues</a>, in the <a href="https://github.com/cf-convention/cf-conventions">conventions repository</a>, for proposing enhancements and reporting defects in the CF conventions. <a href="https://github.com/cf-convention/cf-conventions/issues/new/choose">Open a new issue</a>. See also <a href="https://github.com/cf-convention/cf-conventions/issues?q=is:issue+is:closed">closed conventions issues</a>, classified by reason for closure: <a href="https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:&quot;change agreed&quot;">change agreed</a> • <a href="https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:&quot;agreement not to change&quot;">agreement not to change</a> • <a href="https://github.com/cf-convention/cf-conventions/issues?q=is:issue+label:dormant">dormant</a>. “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.</p>
   </li>
   <li>
-    <p><a href="https://github.com/cf-convention/cf-convention.github.io/issues">Website and governance</a></p>
-
-    <p>For discussing, proposing changes and reporting defects in the <a href="https://cfconventions.org">CF website</a> or CF governance.</p>
+    <p><a href="https://github.com/cf-convention/cf-convention.github.io/issues">Website and governance issues</a>, in the <a href="https://github.com/cf-convention/cf-convention.github.io">website repository</a>, for proposing changes and reporting defects in the <a href="https://cfconventions.org">CF website</a> or CF governance. <a href="https://github.com/cf-convention/cf-convention.github.io/issues/new/choose">Open a new issue</a>.</p>
   </li>
 </ul>
 
-<p>No registration with CF is required to contribute; all that is needed is a freely available <a href="https://github.com">GitHub account</a>.</p>
+<p>You can enable notifications of updates to issues for each kind of issue separately using the <b>Watch</b> menu in its repository.</p>
 
 <h3 id="archive-links">Archive links</h3>
 
-<p>Before the CF community migrated to GitHub, general and standard-name discussion took place on the <a href="https://cfconventions.org/mailing-list-archive/Data/">cf-metadata mailing list</a>, and enhancements to the conventions were proposed on the <a href="/Data/trac.html">CF Metadata Trac</a> site.</p>
+<p>Announcements, discussions and Q&amp;A that were initiated before CF GitHub Discussions began are continuing as GitHub issues in the <code class="language-plaintext highlighter-rouge">discuss</code> repository. They will soon be converted to GitHub Discussions.</p>
+
+<p>Before the CF community migrated to GitHub:</p>
 
 <ul>
-  <li>cf-metadata mailing list archive <a href="https://cfconventions.org/mailing-list-archive/Data/">copy on GitHub</a> or <a href="https://mailman.cgd.ucar.edu/pipermail/cf-metadata/">original at NCAR</a> (until December 2019)</li>
-  <li><a href="/Data/trac.html">CF Metadata Trac</a> (until July 2018)</li>
-  <li><a href="/about-trac.html">About CF Metadata Trac</a></li>
+  <li>
+    <p>until December 2019, general discussion took place and standard names were proposed on the <a href="https://cfconventions.org/mailing-list-archive/Data/">cf-metadata mailing list</a> (<a href="https://mailman.cgd.ucar.edu/pipermail/cf-metadata/">original at NCAR</a>).</p>
+  </li>
+  <li>
+    <p>until July 2018, changes to the conventions were proposed on the <a href="/about-trac.html">CF Metadata Trac</a> site.</p>
+  </li>
 </ul>
 
 

index.html

@@ -198,14 +198,13 @@ <h1 id="cf-metadata-conventions">CF Metadata Conventions</h1>
 
 <hr />
 
-<p><strong><em>Conventions</em>:</strong> <strong>Latest release</strong> (1.11) <a href="/Data/cf-conventions/cf-conventions-1.11/cf-conventions.html">HTML</a> <a href="/Data/cf-conventions/cf-conventions-1.11/cf-conventions.pdf">PDF</a>
-<code>&nbsp;&bull;&nbsp;</code>
+<p><a href="https://github.com/orgs/cf-convention/discussions/new?category=q-a-about-using-cf"><strong><em>Ask a question</em> about how to use CF</strong>  ❓</a></p>
+
+<p><strong><em>Read the conventions</em>:</strong> <strong>Latest release</strong> (1.11) <a href="/Data/cf-conventions/cf-conventions-1.11/cf-conventions.html">HTML</a> <a href="/Data/cf-conventions/cf-conventions-1.11/cf-conventions.pdf">PDF</a> • 
 <strong>Working draft</strong> <a href="/cf-conventions/cf-conventions.html">HTML</a> <a href="/cf-conventions/cf-conventions.pdf">PDF</a></p>
 
-<p><strong><em>Vocabularies</em>:</strong> <a href="/Data/cf-standard-names/current/build/cf-standard-name-table.html"><strong>Standard names</strong></a>
-<code>&nbsp;&bull;&nbsp;</code>
-<a href="/Data/area-type-table/current/build/area-type-table.html"><strong>Area types</strong></a>
-<code>&nbsp;&bull;&nbsp;</code>
+<p><strong><em>Check the latest vocabularies</em>:</strong> <a href="/Data/cf-standard-names/current/build/cf-standard-name-table.html"><strong>Standard names</strong></a> • 
+<a href="/Data/area-type-table/current/build/area-type-table.html"><strong>Area types</strong></a> • 
 <a href="/Data/standardized-region-list/standardized-region-list.current.html"><strong>Standardized regions</strong></a></p>
 
 <hr />