Skip to content

Commit

Permalink
Deploying to gh-pages from @ bc6adb8 🚀
Browse files Browse the repository at this point in the history
  • Loading branch information
@cofinoa
cofinoa committed Jun 13, 2024
1 parent 3aa8d77 commit 494cdb0
Show file tree
Hide file tree
Showing 1,580 changed files with 6,992,764 additions and 0 deletions.
24 changes: 24 additions & 0 deletions CONTRIBUTING.md
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Contributing to the netCDF-CF Conventions website

Dear CF community member,

Thank you for taking the time to consider making a contribution to the [website of the cf-conventions][cf-website].

This set of guidelines provides an overview of the process for making changes to the website.
Separate guidelines apply for [changing the CF Conventions or proposing standard names][contribute-conventions].
If you have a general question about CF matters, please raise them as issues in the [discuss repository][discuss].

When raising an issue, please use the appropriate issue template.
The template explains the approval process for issues of that type and automatically adds the correct label to the issue you create.
Consider associating that issue to a pull request that implements the proposed change.
Each issue template notes that the approval of one or more members of the following bodies is necessary for the proposed change to be merged:
- The [CF Information Management and Support Team][info-mgmt],
- The [Conventions Committee and Standard Names Committee][committee], or
- The [Governance Panel][gov-panel]

[cf-website]: http://cfconventions.org/
[contribute-conventions]: https://github.com/cf-convention/cf-conventions/blob/master/CONTRIBUTING.md
[discuss]: https://github.com/cf-convention/discuss/issues
[info-mgmt]: http://cfconventions.org/governance.html#information-management-and-support
[committee]: http://cfconventions.org/governance.html#conventions-committee-and-standard-names-committee
[gov-panel]: http://cfconventions.org/governance.html#governance-panel
337 changes: 337 additions & 0 deletions Committees/Conventions_and_Standard_Names/2023-09-29-meeting.html
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,337 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="Climate and Forecast Metadata also known as the CF Convention or CF Metadata" />
<meta name="author" content="Matthew Harris (mattben)">
<link rel="icon" type="image/png" href="/Data/media/images/logo.png">
<link rel="apple-touch-icon" type="image/png" href="/Data/media/images/logo.png">
<title>2023-09-29 CF Conventions Committee and Standard Names Committee Panel meeting</title>

<!-- Bootstrap Core CSS -->
<link rel="stylesheet" href="https://stackpath.bootstrapcdn.com/bootstrap/3.4.1/css/bootstrap.min.css" integrity="sha384-HSMxcRTRxnN+Bdg0JdbxYKrThecOKuH5zCYotlSAcp1+c8xmyTe9GYg1l9a69psu" crossorigin="anonymous">

<!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->
<!-- WARNING: Respond.js doesn't work if you view the page via file:// -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.3/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
<!-- Custom styles for this template -->
<style>
body {
padding-bottom: 20px;
}
p a.anchor {
display: block;
position: relative;
top: -50px;
visibility: hidden;
}
</style>
</head>

<body>
<div class="navbar navbar-inverse" style="margin-bottom: 0px;" role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="/">
<img class="pull-left" src="/Data/media/images/logo.png" style="position: relative; top: -10px; left: -10px"/>
CF MetaData
</a>
</div>
<div class="navbar-collapse collapse">
<ul class="nav navbar-nav">



























<li><a href="/conventions.html">Conventions</a></li>







<li><a href="/discussion.html">Discussion</a></li>









<li><a href="/governance.html">Governance</a></li>





<li><a href="/Training/">Training</a></li>





<li><a href="/Meetings/">Meetings</a></li>





















<li><a href="/vocabularies.html">Vocabularies</a></li>






































</ul>
</div><!--/.nav-collapse -->
</div>
</div>

<!-- Main jumbotron for a primary marketing message or call to action -->

<div class="container">

<h1 id="2023-09-29-cf-conventions-committee-and-standard-names-committee-panel-meeting">2023-09-29 CF Conventions Committee and Standard Names Committee Panel meeting</h1>

<h2 id="attendees">Attendees</h2>

<p>Lars Bärring, Philip Cameron-Smith, Jonathan Gregory, David Hassell, Daniel Lee, Roy Lowry, Alison Pamment, Karl Taylor</p>

<h2 id="agenda">Agenda</h2>

<ul>
<li>
<p>Proposed changes to labels and use of repositories.</p>
</li>
<li>
<p>Are moderators needed for issues for enhancements? Can the proposer of a change moderate by default? Are members of the committee willing to be asked to moderate? How should we prevent issues from going dormant? When should an issue be closed as dormant?</p>
</li>
<li>
<p>Are members of the committee willing to be asked to draft PRs for defects, if the proposer doesn’t do it?</p>
</li>
<li>
<p>After how long should we close answered questions? What should we do about questions that are not answered? Whose responsibility are these actions?</p>
</li>
<li>
<p>Is the FAQ useful? Would anyone like to work on it? What should be added?</p>
</li>
<li>
<p>Possible future rearrangement of the repositories.</p>
</li>
<li>
<p>Any of the issues marked “discuss with cttee”.</p>
</li>
<li>
<p>Should we have regular committee meetings of this kind? It has been suggested they could be open to the “public” to join.</p>
</li>
</ul>

<h2 id="discussion">Discussion</h2>

<p>Proposed changes to labels and use of repositories.</p>

<ul>
<li>
<p>DECISION: <code class="language-plaintext highlighter-rouge">duplicate</code> label: Could be used as a reason for closing an issue as it informs the opener of the duplicate issue</p>
</li>
<li>DECISION: <code class="language-plaintext highlighter-rouge">dormant</code> label: Having a dormant label is good, but it shouldn’t trigger the automatic closing of the issue.
<ul>
<li>Before a dormant issue is closed, actions should be taken to revitalise it, such as posting to the issue (multiple times) asking for more input and contacting the active participants directly, on the issue or by e-mail.</li>
</ul>
</li>
<li>
<p>Truly dormant issues should be closed after a defined period of inactivity. 9 months was suggested.</p>
</li>
<li>Temporary labels for short-lived projects: These are useful for managing, e.g., large numbers of related standard name requests.
<ul>
<li>No label should be temporary, for future searching. Project-based labels could have a namespace (something like <code class="language-plaintext highlighter-rouge">project_name:standard_name</code>).
<ul>
<li>An alternative could be to edit the title, but if this is done then the old title should always be recorded in the title for future searching.</li>
</ul>
</li>
</ul>
</li>
</ul>

<p>Are moderators needed for issues for enhancements? Can the proposer of a change moderate by default? Are members of the committee willing to be asked to moderate? How should we prevent issues from going dormant? When should an issue be closed as dormant? (This item overlaps with the agenda item 1.)</p>

<ul>
<li>
<p>DECISION: The proposer should not, in general, be the moderator.</p>
</li>
<li>
<p>DECISION: The chair of the committee (Jonathan) can ask another committee member to act when an issue is need of some sort of input (such as contacting the proposer/moderator to request input).</p>
</li>
</ul>

<p>Are members of the committee willing to be asked to draft PRs for defects, if the proposer doesn’t do it?</p>

<ul>
<li>DECISION: Yes. A committee member may well say “no”, though.
<ul>
<li>Training materials (such as a manual and YouTube video), and a comprehensive checklist in the PR template (updating the one that we already have).</li>
</ul>
</li>
</ul>

<p>After how long should we close answered questions? What should we do about questions that are not answered? Whose responsibility are these actions?</p>

<ul>
<li>Not discussed.</li>
</ul>

<p>Is the FAQ useful? Would anyone like to work on it? What should be added?</p>

<ul>
<li>Not discussed.</li>
</ul>

<p>Possible future rearrangement of the repositories.</p>

<ul>
<li>This discussion was taken much further at the 2023 CF meeting, however we discussed:
<ul>
<li>The current situation is confusing, especially when a PR is opened in one repository following a discussion on the other.</li>
<li>Making it clearer where you should ask questions. Could disallow them on the conventions repository. A separate vocabulary issue tracker is attractive. Could convert “discuss” to a “vocabulary” repository, and allow questions on both, depending on their nature.</li>
<li>Could use the GitHub discussions feature</li>
<li>Having multiple issue trackers is confusing: issues will inevitably get opened in the wrong place.</li>
</ul>
</li>
</ul>

<p>Any of the issues marked “discuss with cttee”.</p>

<ul>
<li>Not discussed.</li>
</ul>

<p>Should we have regular committee meetings of this kind? It has been suggested they could be open to the “public” to join.</p>

<ul>
<li>DECISION: Committee meeting should be quarterly.</li>
<li>DECISION: Committee meetings should not be open (in that the meeting URL will not be published), but will be advertised so anyone can ask to attend on a one-off basis.</li>
</ul>

<p>Any comments welcome on any of the above.</p>

<h2 id="review-previous-action-items">Review previous action items</h2>

<p>Not applicable.</p>

<h2 id="new-action-items">New Action items</h2>

<ul class="task-list">
<li class="task-list-item"><input type="checkbox" class="task-list-item-checkbox" disabled="disabled" />(David) Find date for the next meeting in ~3 months time.</li>
</ul>


<hr>
<footer>
<p>
<a href="/discussion">Contact the CF community</a> with questions, comments and suggestions about CF metadata or this website
</p>
<p>This site is open source in line with the <a href="https://creativecommons.org/publicdomain/zero/1.0/">Creative Commons Zero CC0 Deed</a>.&emsp;&emsp;&emsp;&emsp;&emsp;
<a href="https://github.com/cf-convention/cf-convention.github.io/edit/main/Committees/Conventions_and_Standard_Names/2023-09-29-meeting.md">Improve this page!</a></p>
</footer>
</div> <!-- /container -->


<!-- Bootstrap core JavaScript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->
<script src="https://code.jquery.com/jquery-1.12.4.min.js" integrity="sha384-nvAa0+6Qg9clwYCGGPpDQLVpLNn0fRaROjHqs13t4Ggj3Ez50XnGQqc/r8MhnRDZ" crossorigin="anonymous"></script>
<!-- Include all compiled plugins (below), or include individual files as needed -->
<script src="https://stackpath.bootstrapcdn.com/bootstrap/3.4.1/js/bootstrap.min.js" integrity="sha384-aJ21OjlMXNL5UyIl/XNwTMqvzeRMZH2w8c5cRVpzpU8Y5bApTppSuUkhZXN0VxHd" crossorigin="anonymous"></script>
<script src="/Data/media/js/links.js"></script>

</body>
</html>


Loading

0 comments on commit 494cdb0

Please sign in to comment.