Diagnose degrading Mindshare Committee activity frequency #153

New issue

Open

opened 2026-09-17 18:24:12 +00:00 by t0xic0der · 2 comments

t0xic0der commented 2026-09-17 18:24:12 +00:00

Owner

Copy link

I do not take pleasure noting this but we as a committee have been on a downward trajectory for a while now.

Take, for instance, this is what the attendance looked like for the last five meetings.

	Aug 06 [1]	Aug 20 [2]	Sep 03 [3]	Sep 10 [4]	Sep 17 [5]
TYPE			AV	AV
Akashdeep Dhar [@t0xic0der]	[x]	[x]	[x]	[x]	[x]
Justin Wheeler [@jflory7] (Optional)
Luis Bazan [@lbazan]		[x]	[x]	[x]
Mat Holmes [@theprogram]	[x]
Samyak Jain [@jnsamyak]			[x]
Shaun McCance [@shaunm]		[x]	[x]	[x]	[x]

---

Had it been just the meeting attendance, things would not have been as bad but it unfortunately extends from there.

I have found myself repeatedly using the !group members mindshare chat command to invoke activity from members.

From Aug 06, 2026

From Aug 20, 2026

From Aug 23, 2026

From Aug 31, 2026

From Sep 07, 2026

From Sep 10, 2026

From Sep 17, 2026 (i.e. Today)

The Fedora Mindshare matrix chat has also been more or less dead silent.

It generally came down to @shaunm and myself to address queries and make copious use of lazy approvals.

Folks, please note that "lazy approval" is supposed to be a means with which we keep the ticket voting progress rolling.

Please do not be mistaken here - It is not supposed to be the justification of the reduction in curation activity etc.

---

Our documentation prescribes that we are to get back to the event proposal tickets with our votes within a certain period.

That timeline ranges from three days for small events[6], eleven days for medium events[7] and large events[8].

Have we really been sticking with that timeline?

Here are some examples from the Q3 2026 category.

For French community swags (#126) [4x approvals ✔️, 1x undecided ❌]

• It took us about five days to make our first contact with the requester (i.e. 25th Jun[9]) after the ticket creation
• It is alright since it is not time sensitive ⌛

For All Things Open 2026 event (#128) [Suspended ⌛]

• We were pretty much able to make our first contact on that day itself (i.e. 25th Jun[10]) or a day later (i.e. 26th Jun[11])
• This is a good example to follow honestly ✔️

For Poland community swags (#138) [3x approvals ✔️, 2x undecided ❌]

• We got to the original ticket after about three days (i.e. 20th Jul[12]) after the original ticket had been opened
• This also is a good example to follow ✔️

For Data Con LA 2026 event (#143) [4x approvals ✔️, 1x undecided ❌]

• We were able to reach back to the original request on the same day (i.e. 04 Aug[13]) or two days later (i.e. 06 Aug[14])
• This is perfectly fine as well ✔️

For Software Freedom Day Bukidnon 2026 event (#146) [3x approvals ✔️, 2x undecided ❌]

• It took us eleven whole days to make our first contact with the requester (i.e. 03rd Sep[15])
• And no, this was not a medium or large event ❌

For IndiaFOSS 2026 event (#147) [3x approvals ✔️, 2x sustained ✔️]

• We got the first contact to the requester after eight days (i.e. 03rd Sep[16]) after the original ticket had been opened
• Here again, we have been just as slow ❌

For Texas Linux Fest 2026 event (#148) [4x approvals ✔️, 1x undecided ❌]

• We were able to make our first contact to the requester after five days (i.e. 03rd Sep[17]) after the ticket creation
• We should actively communicate even if the event is later ❌

Please understand that we have to assume lazy approval for every undecided vote which is not ideal.

This makes us wait until the last vote, which puts us far beyond the accepted ticket curation timelines[6][7][8].

This sucks good and proper here - because we have NOT been receiving the last vote for a while now.

Like how exactly do we expect to empower the community folks with the resources when we are this casual?

---

If availability has been a problem, then please consider conveying the same in the matrix channels duly.

If the meeting times do not work well, then the only way we could do something about it is by knowing it first.

If there are process inconveniences that make it difficult for you to participate, we can only fix it if we know it.

If folks are no longer interested to participate, that is also fine - we totally understand that but please say so.

---

I want this issue ticket to be a wake up call for our committee members -- and that includes myself and @shaunm too.

In the Fedora Council[18] matrix chat, I asked @ngompa to interact with us but there is no point, if we do not do ourselves.

Please note the very first step towards solving a problem is, of course, acknowledging that it exists in the first place.

Let us talk our problems out and pledge active participation in the community governance that we were elected into[19].

---

2350IST here. A part of me wanted to keep this for tomorrow. But to do hell with that. I decided to finish this tonight itself.

I know that the committee members care about the community. This just happens to be my care[20] for the members.

---

References

1. https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-08-06/mindshare.2026-08-06-12.11.log.html
2. https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-08-20/mindshare.2026-08-20-12.04.log.html
3. Unrecorded video conferencing meeting
4. Unrecorded video conferencing meeting
5. https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-09-17/mindshare.2026-09-17-12.00.log.html
6. https://docs.fedoraproject.org/en-US/mindshare-committee/events/requests/small/#committee-vote
7. https://docs.fedoraproject.org/en-US/mindshare-committee/events/requests/medium/#committee-vote
8. https://docs.fedoraproject.org/en-US/mindshare-committee/events/requests/large/#committee-vote
9. #126 (comment)
10. #128 (comment)
11. #128 (comment)
12. #138 (comment)
13. #143 (comment)
14. #143 (comment)
15. #146 (comment)
16. #147 (comment)
17. #148 (comment)
18. https://chat.fedoraproject.org/#/room/#council:fedoraproject.org
19. https://communityblog.fedoraproject.org/f44-election-results/
20. #131

I do not take pleasure noting this but we as a committee have been on a downward trajectory for a while now. Take, for instance, this is what the attendance looked like for the last five meetings. | | Aug 06 [1] | Aug 20 [2] | Sep 03 [3] | Sep 10 [4] | Sep 17 [5] | |--------------------------------------|------------|------------|------------|------------|------------| | TYPE | | | AV | AV | | | Akashdeep Dhar [@t0xic0der] | [x] | [x] | [x] | [x] | [x] | | Justin Wheeler [@jflory7] (Optional) | | | | | | | Luis Bazan [@lbazan] | | [x] | [x] | [x] | | | Mat Holmes [@theprogram] | [x] | | | | | | Samyak Jain [@jnsamyak] | | | [x] | | | | Shaun McCance [@shaunm] | | [x] | [x] | [x] | [x] | --- Had it been just the meeting attendance, things would not have been as bad but it unfortunately extends from there. I have found myself repeatedly using the `!group members mindshare` chat command to invoke activity from members. From Aug 06, 2026  From Aug 20, 2026  From Aug 23, 2026  From Aug 31, 2026  From Sep 07, 2026  From Sep 10, 2026  From Sep 17, 2026 (i.e. Today)  The [Fedora Mindshare matrix chat](https://chat.fedoraproject.org/#/room/#mindshare:fedoraproject.org) has also been more or less dead silent. It generally came down to @shaunm and myself to address queries and make copious use of lazy approvals. Folks, please note that "lazy approval" is supposed to be a means with which we keep the ticket voting progress rolling. Please do not be mistaken here - It is not supposed to be the justification of the reduction in curation activity etc. --- Our documentation prescribes that we are to get back to the event proposal tickets with our votes within a certain period. That timeline ranges from three days for small events[6], eleven days for medium events[7] and large events[8]. Have we really been sticking with that timeline? Here are some examples from the Q3 2026 category. _For French community swags_ (#126) [**4x** approvals ✔️, **1x** undecided ❌] - It took us about five days to make our first contact with the requester (i.e. 25th Jun[9]) after the ticket creation - It is alright since it is not time sensitive ⌛ _For All Things Open 2026 event_ (#128) [Suspended ⌛] - We were pretty much able to make our first contact on that day itself (i.e. 25th Jun[10]) or a day later (i.e. 26th Jun[11]) - This is a good example to follow honestly ✔️ _For Poland community swags_ (#138) [**3x** approvals ✔️, **2x** undecided ❌] - We got to the original ticket after about three days (i.e. 20th Jul[12]) after the original ticket had been opened - This also is a good example to follow ✔️ _For Data Con LA 2026 event_ (#143) [**4x** approvals ✔️, **1x** undecided ❌] - We were able to reach back to the original request on the same day (i.e. 04 Aug[13]) or two days later (i.e. 06 Aug[14]) - This is perfectly fine as well ✔️ _For Software Freedom Day Bukidnon 2026 event_ (#146) [**3x** approvals ✔️, **2x** undecided ❌] - It took us eleven whole days to make our first contact with the requester (i.e. 03rd Sep[15]) - And no, this was not a medium or large event ❌ _For IndiaFOSS 2026 event_ (#147) [**3x** approvals ✔️, **2x** sustained ✔️] - We got the first contact to the requester after eight days (i.e. 03rd Sep[16]) after the original ticket had been opened - Here again, we have been just as slow ❌ _For Texas Linux Fest 2026 event_ (#148) [**4x** approvals ✔️, **1x** undecided ❌] - We were able to make our first contact to the requester after five days (i.e. 03rd Sep[17]) after the ticket creation - We should actively communicate even if the event is later ❌ Please understand that we have to assume lazy approval for every undecided vote which is not ideal. This makes us wait until the last vote, which puts us far beyond the accepted ticket curation timelines[6][7][8]. This sucks good and proper here - because we have NOT been receiving the last vote for a while now. Like how exactly do we expect to empower the community folks with the resources when we are this casual? --- If availability has been a problem, then please _consider conveying the same_ in the matrix channels duly. If the meeting times do not work well, then the only way we could do something about it is _by knowing it first_. If there are process inconveniences that make it difficult for you to participate, we can only fix it _if we know it_. If folks are no longer interested to participate, that is also fine - we totally understand that _but please say so_. --- I want this issue ticket to be a wake up call for our committee members -- and that includes myself and @shaunm too. In the Fedora Council[18] matrix chat, I asked @ngompa to interact with us but there is no point, if we do not do ourselves.  Please note the very first step towards solving a problem is, of course, acknowledging that it exists in the first place. Let us talk our problems out and pledge active participation in the community governance that we were elected into[19]. --- 2350IST here. A part of me wanted to keep this for tomorrow. But to do hell with that. I decided to finish this tonight itself. I know that the committee members care about the community. This just happens to be my care[20] for the members. --- References 1. https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-08-06/mindshare.2026-08-06-12.11.log.html 2. https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-08-20/mindshare.2026-08-20-12.04.log.html 3. Unrecorded video conferencing meeting 4. Unrecorded video conferencing meeting 5. https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-09-17/mindshare.2026-09-17-12.00.log.html 6. https://docs.fedoraproject.org/en-US/mindshare-committee/events/requests/small/#committee-vote 7. https://docs.fedoraproject.org/en-US/mindshare-committee/events/requests/medium/#committee-vote 8. https://docs.fedoraproject.org/en-US/mindshare-committee/events/requests/large/#committee-vote 9. https://forge.fedoraproject.org/mindshare/tickets/issues/126#issuecomment-866935 10. https://forge.fedoraproject.org/mindshare/tickets/issues/128#issuecomment-866941 11. https://forge.fedoraproject.org/mindshare/tickets/issues/128#issuecomment-867723 12. https://forge.fedoraproject.org/mindshare/tickets/issues/138#issuecomment-1066839 13. https://forge.fedoraproject.org/mindshare/tickets/issues/143#issuecomment-1079965 14. https://forge.fedoraproject.org/mindshare/tickets/issues/143#issuecomment-1261786 15. https://forge.fedoraproject.org/mindshare/tickets/issues/146#issuecomment-1353018 16. https://forge.fedoraproject.org/mindshare/tickets/issues/147#issuecomment-1353017 17. https://forge.fedoraproject.org/mindshare/tickets/issues/148#issuecomment-1353031 18. https://chat.fedoraproject.org/#/room/#council:fedoraproject.org 19. https://communityblog.fedoraproject.org/f44-election-results/ 20. https://forge.fedoraproject.org/mindshare/tickets/issues/131

image.png

73 KiB

image.png

149 KiB

image.png

84 KiB

image.png

64 KiB

image.png

203 KiB

image.png

73 KiB

image.png

80 KiB

image.png

75 KiB

t0xic0der self-assigned this 2026-09-17 18:24:37 +00:00

theprogram was assigned by t0xic0der 2026-09-17 18:24:37 +00:00

shaunm was assigned by t0xic0der 2026-09-17 18:24:38 +00:00

jnsamyak was assigned by t0xic0der 2026-09-17 18:24:38 +00:00

lbazan was assigned by t0xic0der 2026-09-17 18:24:38 +00:00

ngompa commented 2026-09-17 18:55:39 +00:00

Copy link

FWIW, this problem is why I stopped bothering with Fedora KDE requests to Mindshare. By the time anyone bothered to do anything, events and opportunities had come and gone and I had basically been stalled out so many times it wasn't worth it anymore.

FWIW, this problem is why I stopped bothering with Fedora KDE requests to Mindshare. By the time anyone bothered to do anything, events and opportunities had come and gone and I had basically been stalled out so many times it wasn't worth it anymore.

t0xic0der added a new dependency 2026-10-01 11:41:03 +00:00

#139 Document the Fedora Council Representative's role

t0xic0der commented 2026-10-08 05:23:04 +00:00

Author

Owner

Copy link

@theprogram, @jnsamyak and @lbazan, could you folks please pledge your timely availabilities from here on out?

Once that has been duly recorded, we can close this ticket as completed.

@theprogram, @jnsamyak and @lbazan, could you folks please pledge your timely availabilities from here on out? Once that has been duly recorded, we can close this ticket as completed.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

No results found.

Labels

Clear labels   

category

budget

Related to the Mindshare Committee spending allocation and budget management

  

category

docs

Improving documentation about the Fedora Mindshare Committee or community processes

  

category

limesurvey

Requests for using Fedora's LimeSurvey instance for community surveys and polls

  

category

meta

Improvements and changes to the Fedora Mindshare Committee itself

  

category

physical events

Requests, planning, & other organizing for a physical event presence

  

category

swag

Management, distribution, and purchasing of Fedora-branded swag and merchandise

  

category

virtual events

Planning and organizing our virtual event presences

  

Q1

Tickets related for allocating budgets - Q1

  

Q2

Tickets related for allocating budgets - Q2

  

Q3

Tickets related for allocating budgets - Q3

  

Q4

Tickets related for allocating budgets - Q4

  

charter

ambassadorship

Promote Fedora, its projects, and its values by actively interacting with and fostering engagement within online communities

  

charter

events

Support and coordinate budget requests for events in each region, acting as a liaison between the regions, the FCA, and the wider committee

  

charter

recognition

Recognize the efforts of contributors across the project by working with project teams to reward contributions

  

good first issue

Good tickets to begin with (if you want to get involved, try working on one of these!)

  

help wanted

Tickets where we need help or need feedback from the wider Fedora community

  

needs

event report

An event request that needs a published event report before closing as complete

  

needs

reporter feedback

Additional feedback or information from the reporter is needed to advance

  

needs

vote

A vote is required from Mindshare Committee members in order to advance

  

scope

bug

Something isn't working

  

scope

improvement

Requests for something we are either repeating or improving

  

scope

new

Requests for something brand new that has not been done before

  

state

approved

Tickets that received approval by the Fedora Mindshare Committee

  

state

blocked

Cannot move forward: blocked by feedback, other tickets, etc.

  

state

duplicate

This issue or pull request already exists

  

state

invalid

This doesn't seem right

  

state

wontfix

This will not be worked on

  

team

advocates

Requests, tickets, & discussions about Fedora Advocates

  

team

ambassadors

Requests, tickets, & discussions about Fedora Ambassadors

  

team

commops

Requests, tickets, & discussions about Fedora Community Operations (CommOps)

  

team

council

Requests, tickets, & discussions about the Fedora Council

  

team

design

Requests, tickets, & discussions about the Fedora Design Team

  

team

docs

Requests, tickets, & discussions about the Fedora Documentation Team

  

team

g11n

Requests, tickets, & discussions about the Fedora Globalization Team (including Localization and Internationalization)

  

team

marketing

Requests, tickets, & discussions about the Fedora Marketing Team

  

team

mindshare

Requests, tickets, & discussions about the Fedora Mindshare Committee itself

  

team

websites-apps

Requests, tickets, & discussions about the Fedora Websites & Apps Team

No labels

category

budget

category

docs

category

limesurvey

category

meta

category

physical events

category

swag

category

virtual events

Q1

Q2

Q3

Q4

charter

ambassadorship

charter

events

charter

recognition

good first issue

help wanted

needs

event report

needs

reporter feedback

needs

vote

scope

bug

scope

improvement

scope

new

state

approved

state

blocked

state

duplicate

state

invalid

state

wontfix

team

advocates

team

ambassadors

team

commops

team

council

team

design

team

docs

team

g11n

team

marketing

team

mindshare

team

websites-apps

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

t0xic0der

theprogram

shaunm

jnsamyak

lbazan

2 participants

Notifications

Subscribe

Due date

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

No due date set.

Blocks

#139 Document the Fedora Council Representative's role

mindshare/tickets

Reference

mindshare/tickets#153

No description provided.