#3255 Consider reworking summaries for meetings
Opened 4 months ago by sgallagh. Modified 3 months ago

As has been discussed on the mailing list and in previous meetings, the general sense is that the meeting minutes we've been sending out have not be sufficiently informative.

We've had several suggestions on how to improve this:

  1. Increase our usage of !info during meetings to provide more context in the generated minutes. Pros: uses existing tools and processes. Cons: requires discipline to summarize live discussions (without fanning flames of disagreement)

  2. Feed the discussion into a large language model after the meeting to produce a readable summary, edited by the chairperson for the meeting. Pros: Provides a short, easily accessible summary of the discussion in common English. Cons: Not everyone is comfortable with the use of LLMs in general and third-party hosted LLMs in specific; requires careful examination to avoid hallucinations.

  3. The chairperson writes up a comprehensive summary after each meeting. Pros: the person writing the summary will have a clear idea of the content of the discussion, as well as things left unsaid or TBD. Cons: This is tedious additional work; not all FESCo members are native English speakers which can lead to unintentional miscommunication.

I'm sure there are other ideas that we can come up with (perhaps some combination of the above), but I think the first step is to agree that the current situation is indeed unacceptable.


Personally, I would prefer some combination of options 1) and 3).

I prefer a combination of 1) and 3) too. But if we can agree on some guidelines for using GenAI I'm not necessarily opposed to 2) -- but most likely opposed to the use of those with known questionable training data sourcing

I think more usage of !info will be good, but I would not expect to capture all the nuance of the discussion while participating. Even a small increase should help though.

I like #1. #3 is also fine, but I don't see it necessary. I am not comfortable with #2.

Metadata Update from @sgallagh:
- Issue tagged with: stalled

3 months ago

Log in to comment on this ticket.

Metadata