130424meetingminutes

13/04/2024 - Team:Content Meeting

=

1. 1. Introductions

- Hugh - Nicolas - Kirils - Jos - Chantal - Sahra - Dany - Eelco

1. 1. Agenda

1. [Go through lessons learned](https://wiki.mch2022.org/Team:Content/LessonsLearned) 2. PL: how many stages this year? 'Soon!'

   - Proposal for an additional stage track: Foundation 
       - 'Super simple stuff' - very educationally focussed 
       - Much more accessible and interesting to people who aren't tech focussed
       - Always learn something new :) 
   - 2 relatively large main stages
   - 2 slightly smaller main stages
   - No very large stage
   - Want to avoid too much going on at the same time
       - VoC & Heralds struggle to support 
   - [ ] Tell PL we want 4 stages (3 main + 1 foundation) - MiFareLady

3. Workshops

   - In the agenda
   - Heralds helping with the workshops
       - 3500 attendees 
       - Would we be able to get enough people? 

4. Structure between Content/SpeakerDesk/Reviwers/Heralds

   - Advantages and disadvantages to more external review
   - Pretalx can not allow reviewers to see who the speakers are
   - Review blind, and then handle diversity post review (at acceptance)
       - Blind review doesn't allow us to filter out 'bad' proposals 
       - Quality of speakers has to be managed
       - Team:Content can help balance the blind review 
       - [ ] Set up list of external review & process (Unattributed)
   - Diversity of content
   - On the structure between the different functions
       - Better integration between subteams of Team:Content
       - Bunch of subteams underneath the Content umbrella
       [ ] Define the roles of the subteams on the Wiki (Hugh/Kirils)
       - Making sure people aren't overloaded and doing too many jobs
           - One main subteam, involved in others
           - Different subteams become active at different phases (pre-event, during-event)
           - [ ] High level Gantt chart of subteam work intensity (Kirils)
       - Heralds should be working closely with Content

5. Federated agenda

   - Should we do this? 
   - How can we solve this (with or without Pretalx) :) 

7. Recurring meeting time

   - Biweekly meetings 
   - [ ] Circulate a way to express availability (Hugh)
   - Circulate agenda before the meeting so people have an option to comment
       - Allow people to contribute to decisions before the meeting 
       - But decisions will be made in people's absence, and we cannot keep going over them 
       - [ ] Start agenda for the next meeting (Nicolas)

9. Set some deadlines/timeline around the CfP

   - Push to next agenda 

10. Team leads for Content

   - Kirils/MiFareLady, if no one else volunteers
   - Good idea to share the responsibility