TAG December 15, 2021

Zoom link: TBD

Attending

Agenda

• Seth Shaw
• Rosie Le Faive (chair)
• Willow Gillingham
• Don Richards
• Jared Whikloj
• Bethany Seeger (notes)

Old Business

• Talk about how TAG might operate going forward and document it (https://docs.google.com/document/d/13lq1kn7yV3h3DhrcBuryqwm7FJML44ccwhDY7EhsY5U/edit)
• Understand role of chair and talk about future meeting to get chair
• Create a rotation of people to run the Tech call
• Drupal 8 update (https://docs.google.com/document/d/1vNhGkjMKTUSlSmSc59McG2SgrIuqoVkP4vXWvA8FaZs/edit)

New Business

Minutes

• Look at TAG group document. Good that TAG can grow and evolve as things change. Note that TAG is not a decision making body.
  • Is TAG a small core group joined by any one else who is interested?
  • Whether or not TAG has a core group, being able to put TAG on CV is nice.
  • How is this core membership decided?
    • previously one was asked by Danny. TAG is a group of knowledgeable folks who were interested in helping make decisions & find balance in the community.
  • We should confirm our understanding what we think TAG should be. Submit our proposal to Leadership and see what they think. Confirm what their expectations are of us, as well as our own.
    • function as a core group and whomever else wants to join us when we look at topics.
    • communicate to the tech group
  • Next step: update document and let leadership look at it.
• Chair conversation: if we work with this core group, nominate someone from it to chair meetings
  • the list of chair responsibilities is large. Can we split it up? We'd have a chair who organizes the meetings, but really the core group is responsible for all the tasks, so the core group would share the responsibilities.
  • the group on the call likes this idea.
• Rotation for tech call
  • we can think of no current model for chair rotation (other than what is being done)
  • different chairs might run the meeting differently - it's kinda nice
  • Fedora always has the technical lead run the meeting, and committers fill in when the lead is not around.
  • one idea: put all committers on a chair list - they need to opt out.
  • another idea: Create a document that committers can fill out - ask them to grab 4-5 slots; given that there are about 20 committers, it's not a huge ask overall.
  • Question: who makes Technical Meeting Agenda? Make a discussions document that we link to the meeting agenda.
• Drupal 8 notice
  • Rosie will send out document about proposal for Drupal 8 support