-
Notifications
You must be signed in to change notification settings - Fork 45
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #407 from ethanrd/add-cf-gov-panel-notes
Add minutes from 2023 Q1 and Q2 CF Governance Panel meetings.
- Loading branch information
Showing
4 changed files
with
92 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# 2023-03-09 CF Governance Panel meeting | ||
|
||
## Attendees | ||
Jonathan, Ethan, Bryan, Karl | ||
|
||
## Agenda | ||
* Schedule next meeting | ||
* Updates to CF Information Management and Support Team list/description | ||
* Discuss standard names process | ||
* Discuss outreach, engagement, marketing | ||
* AOB | ||
|
||
## Discussion | ||
Schedule next CF Governance Panel meeting/call | ||
* DECISION: Thursday, 29 June 2023 at 15:00 UTC | ||
|
||
Update of description of and rules for the CF info team, update membership | ||
* DECISION: Approve mention of Gov Panel (see issue #[341](https://github.com/cf-convention/cf-convention.github.io/issues/341) and PR #[342](https://github.com/cf-convention/cf-convention.github.io/pull/342)) | ||
|
||
Discuss standard names process | ||
* Recent automation of process/reminder | ||
* Appreciation of work by Alison and Fran | ||
|
||
Outreach, engagement, marketing | ||
* Consider working on improved messaging | ||
* Look for more outreach opportunities, more speakers, more user stories | ||
* Very active Python community: look for opportunities to discuss cf-python and cfdm | ||
* Encourage further develop CF Common Concepts | ||
* Encapsulates data variable description (CF Standard Names, coordinates, etc.) into single concept. | ||
* Two proposals were close to accepted: | ||
* Trac ticket #[24](http://cfconventions.org/Data/Trac-tickets/24.html) "Common Concept:vocabulary with mapping to CF attributes" | ||
* Trac ticket #[94](http://cfconventions.org/Data/Trac-tickets/94.html) "Proposal for a CF String Syntax (CFSS)" | ||
* Consider porting Python CF Data Model package (cfdm) into a C library. Maybe CF Aggregation as well. | ||
|
||
AOB | ||
* 2023 CF Workshop | ||
* Possible AGU session on CF and netCDF |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
# 2023-06-29 CF Governance Panel meeting | ||
|
||
## Attendees | ||
* Bryan, Ethan, Karl, Jonathan, Fanny | ||
|
||
## Agenda | ||
* Schedule next meeting | ||
* Should we use Figshare or Zenodo for CF Workshop presentations/posters? | ||
* Consider suggestion on rotating CF Workshops every nine months | ||
* Consider clarifying rule “When three weeks have passed with no contributions …” | ||
* Discuss ways to encourage engagement on issues that elicit little response due to difficulty/complexity. | ||
* Discuss opening standard names process to non-CEDA folks | ||
* AGU session on CF and netCDF | ||
* CF Workshop | ||
* AOB | ||
|
||
## Discussion | ||
Schedule next CF Governance Panel meeting/call | ||
* DECISION: Tentative 11 Sept 2023 15:00 UTC (alternate 27 Sept) | ||
* Final: 27 Sept 2023 at 15:00 UTC | ||
|
||
Discuss use of Figshare or Zenodo for CF Workshop presentations/posters | ||
* DECISION: Recommend use of Figshare, Zenodo, or institutional repository | ||
* Repository used should provide persistence and a DOI. | ||
|
||
Discuss suggestion on rotating CF Workshops every nine months | ||
* If alternating in-person and virtual, this would keep in-person under 24-months apart | ||
* Higher frequency might be difficult to plan. Could depend on funding for meetings. | ||
* DECISION: Discuss at workshop | ||
|
||
Discuss the “When three weeks have passed with no contributions …” rule and clarifying that messages of agreement don't extend the 3-week period. | ||
* DECISION: Should be something like "no further concerns raised" (all agreed) | ||
* ACTION: Create issue and PR | ||
|
||
Discuss ways to encourage engagement on issues that elicit little response due to difficulty/complexity. | ||
* Hard to build momentum | ||
* Hard without funding | ||
* Maybe regular (quarterly?) meetings to review, encourage action, make decisions | ||
* Issue triage | ||
* Hackathon meetings (Could this contribute to higher frequency of workshops?) | ||
* DECISION: Discuss having regular meetings at CF Workshop. | ||
* ACTION: Fanny and Bryan will ask CMIP IPO about helping organize regular meetings | ||
* ACTION: Ethan will bring up as agenda topic for CF Workshop | ||
|
||
Discuss opening standard names process to non-CEDA folks | ||
* Could CEDA Editor permissions be connected to GH? | ||
* Process (CEDA Editor) is now accessible to approved people outside CEDA. | ||
* ACTION: Bryan and Jonathan ask CEDA about CF standard names process | ||
|
||
AOB | ||
* AGU session on CF and netCDF proposed | ||
* CF Workshop organizing committee meeting regularly |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10,4 +10,4 @@ | |
|
||
## New Action items | ||
|
||
* [ ] (_assigned to_) action item description | ||
* [ ] (_assigned to_) action item description |