Skip to content

Conversation

@fkr
Copy link
Member

@fkr fkr commented Dec 17, 2025

No description provided.

Signed-off-by: Felix Kronlage-Dammers <fkr@hazardous.org>
@fkr fkr requested review from berendt, garloff and jschoone December 17, 2025 22:19
@fkr fkr requested a review from matofeder as a code owner December 17, 2025 22:19
@jklare
Copy link
Contributor

jklare commented Dec 18, 2025

I think we should not rename the file that was approved by the last project board, at least I do not see any reason to. For the new one, we might want to rename it to be more clear about the term, but then we should be very explicit about it imho.

@fkr
Copy link
Member Author

fkr commented Dec 18, 2025

I came across this while documenting the naming of the file in SCS-0005 and since the file starts with the date when the term starts (since with Kurt’s recent change it is documented in SCS-0005 that the term is the calendar year), mentioning the year twice seems redundant.
As for the renaming: the history is visible in git so I see no reason that speaks against renaming such a file.

Copy link
Member

@matofeder matofeder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, Just please ensure that references to the new name work here and there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants