nextcloud / nextcloud/call_summary_bot
Agenda History
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 14
- Forks
- 3
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 6
Description
[!TIP]
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Feature request
The agenda bot is a very helpful feature to keep track of all the points that should be discussed during a call. I often find myself wishing I could check the agenda of e.g. 3 months ago to check on topics that were relevant at the time, to see what had been worked on and also to see things that we decided to postpone (but not lose track of).
Describe the solution you'd like
It would be a nice feature enhancement if the agenda bot could be configured manage a file with the history of all the agendas that have existed within a talk room, to more readily recall what topics were relevant at any given time.
Describe alternatives you've considered
My alternative is storing the agendas (with a date) in a local file and I consult that when I need it.
Additional context
At the end of a call, the summary could include a link to the agenda history file.
Contributor 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.
Research direction
The issue names no files or tests; start by locating the agenda-generation and call-summary entry points in the bot. Determine how configuration and agenda storage currently work, then verify that agendas can be retained in a configurable history file and that the call summary links to it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100