---
# System prepended metadata

title: Summit Apr-22 Retro
tags: [summit_2022_04]

---

###### tags: `summit_2022_04`

# Summit Apr-22 Retro



- Greg
    - Breakoutrooms per talk might be nice next time
    - Do we need a speakers-only backroom?
        - kinda forces speakers to have a matrix id :P
    - extend qabot (or use zodbot) to make a note of interesting links etc
    - many groups have regular meetings, how can we promote better?
- Andrei
    - last summit was ~half a year ago and my personal feeling is that this is a good frequency
    - the discussions happened in two channels in parallel, is it possible to conduct it only in #ansible-social next time not to jump between channels? (But maybe it's OK actually, i don't know) The main summit's goal, imo, is socialization, so #ansible-social seems suitable
        - Carol: I think the main conference chat should still be in the conference room/channel, as people may be asking questions, following the presentations etc. The social room is like the hallway track, I don't think we need to restrict to just one or the other.
- gundalow
    - Create internal placeholder invite earlier
    - Get links in advance for presenters
    - Internal doc with deadlines for tasks in
        - This will be more important for AnsibleFest







# some handy things to cut/paste to chat

## Main room

Stream is at https://youtu.be/mili3ax3V4o

Tag `ansibot` to ask questions

## Speakers

Speakers shouldn't try to watch for Q&A, we'll manage that

Jitsi is at https://ansible.cloud-fr1.unispace.io/ContributorSummit202204

