Meeting notes: summary, action items, and questions about a meeting
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- ai
Research direction
This depends on #118 (local AI layer) and #170 (transcript), and the payload names no source files. Before starting, check whether those two issues have landed, and look at how history and transcripts are stored today, since the issue asks for the same local storage. The thread has no decided design for what a good summary or action-item view looks like, so a maintainer needs to settle that first.
Written by the indexing model from the issue text.
Description
The part people actually want: after a meeting, a short summary, the decisions, and who agreed to do what. Then being able to ask "what did we say about pricing?" and get an answer with the moment it was said.
All of it is prompts on top of the local AI layer (#118) and a transcript (#170), so the work is mostly product: what a good summary looks like, how to show action items, and how asking questions feels.
Worth doing:
- A summary with decisions and action items, generated when a meeting ends.
- A question box over one meeting, then over all of them.
- Everything stored on the computer, like history and transcripts are today.
- Honest behaviour when no local model is set up: keep the transcript, skip the summary, say why.
This is where the paid apps' free tiers stop: they cap how many meetings a week you get. Ours shouldn't.
- Dominant language
- Swift
- Stars
- 540
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from karansinghgit/speaktype
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
karansinghgit/speaktype#211 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
karansinghgit/speaktype#183 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
karansinghgit/speaktype#209 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
karansinghgit/speaktype#208 · 2 comments ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
karansinghgit/speaktype#207 ·
All issues in karansinghgit/speaktype
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
swiftlang/swift-markdown#299 ·
-
area: agents follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
manaflow-ai/cmux#37234 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug product / functions
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day