Idea: broaden /minutes file

[exploreriii]

Proposal: Rename /minutes to /meetings (or /calls) and introduce sub‑directories

Background
We currently store all meeting summaries under the single folder path /minutes. https://github.com/hiero-ledger/sdk-collaboration-hub/tree/main/minutes
These notes are invaluable for quickly recalling prior discussions, but the name “minutes” feels narrow and limits how we can organize related artifacts.

Suggested Change
Rename the top‑level folder from /minutes to a broader name such as:
/meetings
or
/calls

Create useful subdirectories:
/calls
/agenda → Pre‑meeting notes, goals, and talking points
/minutes → The meeting summary, including maybe links to the recordings.
/actions → Assigned follow‑up tasks and owners.

Benefits
Broader scope: /meetings or /calls retains current functionality but allows for more activity.

Clearer navigation: members can jump directly to the agenda or action items without reviewing minutes.

Better engagement: Separating out action items highlights next steps, increasing accountability and making it easier to track progress.

Scalability: As our process evolves, we can simply add new subfolders under /calls.

[rwalworth]

The README.md already specifies a meeting-notes/ directory, maybe that can be used to contain all of the discussion summaries? I am open to discuss renaming this as well if so desired.

I like the different subdirectories you called out, but I propose a different approach. Instead of having separate directories for agenda/, minutes/, and actions/, I think it may be a bit easier to navigate if we instead have a folder for each meeting (e.g. 2025-04-21-hiero-sdk-community-call), and within each meeting folder we have an agenda.md, minutes.md, and actions.md. I think that keeping track of this information by meeting would make it a bit easier for users to navigate.

[exploreriii]

Great point, I believe you are correct that will be much easier to navigate.

I like: a single file for each call e.g. 2025-04-21-hiero-sdk-community-call with subfiles.md.
The downside is we can lose some across-time context. But that's not very important right now.

I really like the idea of an agenda.md because this could be something the community could plan and contribute to?
I also like how actions.md may help to establish and keep track of key tasks.

meeting-notes/ sounds about right. Maybe a bit too formal for my preferences but clear/fits well.

[rwalworth]

I am open to renaming the meeting-notes/ directory if you don't like it. Maybe keeping it broader with meetings/ would be better?

[exploreriii]

Thanks, right now I see minutes existing not meeting-notes.

Readme.md says: proposals, guides, templates, meeting-notes.

However, in the code I see: proposals, guides, templates, minutes.

[rwalworth]

Yep you are correct, these don't match. I can put up a PR to change the README and/or the folder name to whatever we decide. Or perhaps you could update it in #11 ?

[rwalworth]

I'm going to go ahead and put up a PR to change the folder name to meetings/

[jwagantall]

Thank you for opening this discussion,, I like the example mentioned here

(e.g. 2025-04-21-hiero-sdk-community-call), and within each meeting folder we have an agenda.md, minutes.md, and actions.md.

It allows for faster access as someone is trying to search for a particular meeting that happened in a specific day..

[rwalworth]

New structure has been implemented first here #35 so going to close this discussion.