Housekeeping: archive old meeting notes into git

tabbysable commented 1 month ago

to help keep the google docs snappy, let's copy some of the old notes into documents here in this git repo.

Proposed plan:

Keep the current year and the previous calendar year in the Google doc
For each year older than that, copy all the meeting notes into a markdown doc for that year
Get them committed and merged
Once they are committed and merged, delete them from the tail of the Google doc

tabbysable commented 1 month ago

/label sig/security /label good-first-issue

k8s-ci-robot commented 1 month ago

@tabbysable: The label(s) /label sig/security , /label good-first-issue cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to [this](https://github.com/kubernetes/sig-security/issues/120#issuecomment-2223442280): >/label sig/security >/label good-first-issue Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

tabbysable commented 1 month ago

/sig security /good-first-issue

k8s-ci-robot commented 1 month ago

@tabbysable: This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

Why are we solving this issue?
To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
Does this issue have zero to low barrier of entry?
How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-good-first-issue command.

In response to [this](https://github.com/kubernetes/sig-security/issues/120): >/sig security >/good-first-issue > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

tabbysable commented 1 month ago

offhand thought: perhaps in a meeting-notes-archive directory, with subdirectories per subproject, and then names like 2022.md?

PushkarJ commented 1 month ago

Maybe this was discussed already:

Would this mean our archived notes are open for whole internet v/s accessible as before to only k-dev mailing list members? If yes, are we all okay with that?

tturquette commented 1 month ago

Hello @tabbysable. I am open to help with this activity. Please let me know if this is something I can work on.

lavishpal commented 1 month ago

Hi @tabbysable , would like to work on this issue. Can you assign this to me ?

tabbysable commented 1 month ago

Maybe this was discussed already:

Would this mean our archived notes are open for whole internet v/s accessible as before to only k-dev mailing list members? If yes, are we all okay with that?

Yeah, the notes docs are open for anonymous writes, so it will be good for the archived notes to be open too.

tabbysable commented 1 month ago

The three meeting notes docs that would benefit from archiving into git markdown are here: SIG Security meeting Tooling subproject Docs subproject

@tturquette @lavishpal Thank you both for your offers to help! You could certainly work together if you liked.

Last time I tried something like this, there were a few ways to copy out of google docs into Markdown with retained formatting, but none of them were perfect. I recommend doing some searching to see if anyone has published a good script or tool for that, and then just giving a try to generate some Markdown from the old notes.

tabbysable commented 1 month ago

Please do not delete any of the old notes from the Google docs. I will do that once we have some good markdown files commited to git.

kubernetes / sig-security

Housekeeping: archive old meeting notes into git #120

Guidelines