-
Notifications
You must be signed in to change notification settings - Fork 44
Add notes for 4 Dec 2025 CF InfoMgmt Team meeting. #623
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ethanrd
wants to merge
1
commit into
cf-convention:main
Choose a base branch
from
ethanrd:add-2025-12-04-CF-InfoMgmt-mtgNotes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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,27 @@ | ||
| --- | ||
| layout: default | ||
| title: 2025-12-04 CF Information Management and Support Team meeting | ||
| --- | ||
| # 2025-12-04 CF Information Management and Support Team meeting | ||
|
|
||
| ## Attending | ||
| Attending: Andrew Barna, Jonathan Gregory, Ethan Davis, Fran Eggleton, Sadie Bartholomew, Alison Pamment | ||
|
|
||
| ## Agenda/Notes | ||
| * Schedule next meeting | ||
| * 5 March 2026 at 16:00 UTC | ||
| * Should CF Website enforce HTTPS (Issue \#[615](https://github.com/cf-convention/cf-convention.github.io/issues/615))? | ||
| * AGREE we should enable\! | ||
| * DONE \- we enforced on web site repo, tested, and closed issue \#615. | ||
| * Also done on cf-conventions, vocabularies, and mailing-list-archive repos | ||
| * What to do (in the next year or so) about the definite removal of XSLT from browsers (an issue raised by Barna) | ||
| * Two options were discussed: | ||
| * adding an xslt rendering script to the top of each xml | ||
| * Making a javascript “single page app” that renders the standard name table from the xml like how the KWIK indexer works. | ||
| * The option of the single page app was decided as good to explore due to the potential for a more data source agnostic view of the standard name table, e.g. we could switch to using NVS as the data source at some point in the future and still have the same views. | ||
| * As per the [Google Chrome announcement](https://developer.chrome.com/docs/web-platform/deprecating-xslt), xslt will be removed from stable chrome on November 17, 2026, but as early as March 10, 2026 for development release users. | ||
| * Update on vocab restructure (PR #[286](https://github.com/cf-convention/vocabularies/pull/286)) | ||
| * Going ahead with this and will have existing and new webpage running for an overlap period, then once happy website repo will no longer need to maintain vocab files. | ||
| * Review branch rules on GitHub repositories (do we want to add min review on PRs?) \+ to highlight no protection on vocab repo (only just realised this, I think because it’s newly added, happy to add protection if agreed \- FE) | ||
| * Fran to add branch protection on Vocabs repo \- just reviewed and realise this is a non issue that GitHub is flagging up, as only admin can delete anyway. | ||
| * Agreed no need for minimum review on PRs as roles cover merge ability | ||
This file contains hidden or 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
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reads a little awkward from how I remember the conversation. I think we basically agreed that we did not need to implement any of the additional technical controls that github offers because the existing role permissions and internal processes already handle things. It's not that no minimum review is needed, just that one won't be enforced by github itself.