mindshare/tickets

Fork 0

Revisit the Mindshare Committee meeting cadence #135

New issue

Open

opened 2026-07-13 03:57:10 +00:00 by t0xic0der · 4 comments

t0xic0der commented

2026-07-13 03:57:10 +00:00

Owner

Revisit the Mindshare Committee meeting cadence

Extending from this comment, where I have mentioned -

I want to loop this in as a part of a bigger conversation of whether or not we should consider having weekly meetings instead of fortnightly ones in Fedora Mindshare. In my personal observation, a cancellation of one meeting led to the earliest catchup happening almost after a month. Depending on the issue tickets we have on queue, this can be destructive for those proposing events. Maybe we can have pre-emptible slots that we can call off (entirely or early) if we do not have something to talk about?

Revisit the Mindshare Committee meeting cadence Extending from [this comment](https://forge.fedoraproject.org/mindshare/tickets/issues/129#issuecomment-867724), where I have mentioned - > I want to loop this in as a part of a bigger conversation of whether or not we should consider having weekly meetings instead of fortnightly ones in Fedora Mindshare. In my personal observation, a cancellation of one meeting led to the earliest catchup happening almost after a month. Depending on the issue tickets we have on queue, this can be destructive for those proposing events. Maybe we can have pre-emptible slots that we can call off (entirely or early) if we do not have something to talk about?

t0xic0der added the

labels

2026-07-13 03:58:23 +00:00

t0xic0der added this to the 2026 Q3 Team Goals milestone

2026-07-13 03:58:45 +00:00

theprogram commented

2026-07-13 05:22:58 +00:00

Owner

I am fine with that, as long as the time of day suits me.
It may add an unfair burden on Justin if we keep the Chair / Agenda / Reporting requirements as they are.

We do need to be more on top of tickets than in last term, so the other option other than meeting regularly is people making at least one day each week to respond to tickets asynchronously.

I am fine with that, as long as the time of day suits me. It may add an unfair burden on Justin if we keep the Chair / Agenda / Reporting requirements as they are. We do need to be more on top of tickets than in last term, so the other option other than meeting regularly is people making at least one day each week to respond to tickets asynchronously.

👍 1

t0xic0der commented

2026-07-13 06:58:38 +00:00

Author

Owner

It may add an unfair burden on Justin if we keep the Chair / Agenda / Reporting requirements as they are.

Just as much as it would for the likes of you, @jnsamyak, @lbazan and myself ;P

We do need to be more on top of tickets than in last term, so the other option other than meeting regularly is people making at least one day each week to respond to tickets asynchronously.

I am not sure if I agree with this, but I do get the spirit of what you are saying. Zero shade on the last term - especially when I was a part of it too haha, but there have been times when certain proposals could not come to fruition just because there was not a complete consensus. Going forward, we either have to make do with timegating voting (as I mentioned in this comment) while adopting lazy approvals, have more meetings to pry up synchronous participation or a combination of these two.

> It may add an unfair burden on Justin if we keep the Chair / Agenda / Reporting requirements as they are. Just as much as it would for the likes of you, @jnsamyak, @lbazan and myself ;P > We do need to be more on top of tickets than in last term, so the other option other than meeting regularly is people making at least one day each week to respond to tickets asynchronously. I am not sure if I agree with this, but I do get the spirit of what you are saying. Zero shade on the last term - especially when I was a part of it too haha, but there have been times when certain proposals could not come to fruition just because there was not a complete consensus. Going forward, we either have to make do with timegating voting (as I mentioned in [this comment](https://forge.fedoraproject.org/mindshare/tickets/issues/129#issuecomment-867724)) while adopting lazy approvals, have more meetings to pry up synchronous participation or a combination of these two.

lbazan commented

2026-07-13 13:50:42 +00:00

Owner

Weekly meetings is better! maybe! +1

jflory7 self-assigned this

2026-07-13 17:46:11 +00:00

jflory7 commented

2026-07-13 17:53:20 +00:00

Owner

I had some meeting cadence options that I wanted to float, and see what others thought.

Monthly AV, three weeks async: Once a month, the Mindshare Committee meets on video to discuss the bigger picture areas of our charters, make sure we are all staying in sync, and have opportunity to discuss. This meeting is open to the public, but we would ask for common etiquette for anyone joining, e.g., use raise hand button when you wish to speak, mute when not speaking, be aware of the planned meeting structure and help keep things moving forward, etc.
Weekly Matrix cadence with fortnightly variation: Every week, the Mindshare Committee convenes at the same time. Every other week, the Committee alternates between two meeting style types. Either the usual Matrix text meeting (as per the current standard), but the other week is a more independent, scheduled time for async ticket review. We can use Matrix to coordinate and chat while we review tickets, but it is optional. The main focus is that everyone is tending to updates and keeping the Committee members informed, updated, and timely on responding to event feedback requests.
Current style but weekly: Start meeting weekly for one hour on a Matrix text meeting at the new meeting start time this term.

I had some meeting cadence options that I wanted to float, and see what others thought. 1. **Monthly AV, three weeks async**: Once a month, the Mindshare Committee meets on video to discuss the bigger picture areas of our charters, make sure we are all staying in sync, and have opportunity to discuss. This meeting is open to the public, but we would ask for common etiquette for anyone joining, e.g., use raise hand button when you wish to speak, mute when not speaking, be aware of the planned meeting structure and help keep things moving forward, etc. 2. **Weekly Matrix cadence with fortnightly variation**: Every week, the Mindshare Committee convenes at the same time. Every other week, the Committee alternates between two meeting style types. Either the usual Matrix text meeting (as per the current standard), but the other week is a more independent, scheduled time for async ticket review. We can use Matrix to coordinate and chat while we review tickets, but it is optional. The main focus is that everyone is tending to updates and keeping the Committee members informed, updated, and timely on responding to event feedback requests. 3. **Current style but weekly**: Start meeting weekly for one hour on a Matrix text meeting at the new meeting start time this term.

jflory7 added the due date 2026-07-23

2026-07-13 17:53:43 +00:00

No milestone

No project

No assignees

4 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-07-23

Dependencies

No dependencies set.

Reference

mindshare/tickets#135

No description provided.

Rows
Columns