===================================== # #meeting:fedoraproject.org: mindshare ===================================== Meeting started by @jflory7:fedora.im at 2025-10-30 11:01:19 Meeting summary --------------- * TOPIC: Agenda (@jflory7:fedora.im, 11:01:30) * INFO: 3. Ticket discussions (remaining time) (@jflory7:fedora.im, 11:02:02) * INFO: 4. Open floor (remaining 5-10 minutes) (@jflory7:fedora.im, 11:02:02) * INFO: 1. Intros, welcomes, hellos (~5m) (@jflory7:fedora.im, 11:02:02) * INFO: 2. Team announcements & news (~5-10m) (@jflory7:fedora.im, 11:02:02) * TOPIC: Intros, welcomes, hellos (@jflory7:fedora.im, 11:02:11) * TOPIC: Team announcements & news (@jflory7:fedora.im, 11:07:23) * INFO: Fedora Linux 43 released on Tuesday! Expect lots of noise and traffic across Fedora. Note that Infrastructure-related requests might be slower due to the heavy load during the release week. (@jflory7:fedora.im, 11:07:45) * LINK: https://fedoramagazine.org/announcing-fedora-linux-43/ (@jflory7:fedora.im, 11:07:51) * LINK: https://fedoraproject.org/wiki/Fedora_Linux_43_Release_Party_Schedule (@jflory7:fedora.im, 11:08:14) * INFO: Fedora Linux 43 Release Party: The schedule is shaping up. Reminders are going out to speakers for confirming their presentation slots. (@jflory7:fedora.im, 11:08:14) * INFO: AI-Assisted Contributions Policy: It's live and it is officially official. (@jflory7:fedora.im, 11:08:49) * LINK: https://fedoraproject.org/wiki/Category:AI_Assistance_Used (@jflory7:fedora.im, 11:08:49) * LINK: https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/ (@jflory7:fedora.im, 11:08:49) * INFO: Request for Review of Flock 2026 CFP themes by 2025-11-11: All Mindshare Committee members, please review the proposed 2026 CFP themes for Flock. Feedback is open until Tuesday, 11 November. We will not discuss this in today's meeting agenda due to a packed agenda, but please set some time aside to review and add feedback, if any. If you don't have any, a +1 is also great! (@jflory7:fedora.im, 11:09:56) * LINK: https://gitlab.com/fedora/mindshare/home/-/issues/86 (@jflory7:fedora.im, 11:09:56) * TOPIC: Ticket discussions (@jflory7:fedora.im, 11:12:42) * TOPIC: #85: Funding request: Fedora 43 Release Party at "Jesień Linuksowa 2025" in Rybnik, Poland (@jflory7:fedora.im, 11:16:11) * LINK: https://gitlab.com/fedora/mindshare/home/-/issues/85 (@jflory7:fedora.im, 11:16:18) * AGREED: zbyszek is approved as a Small Event type for up to $150 USD reimbursement. The Mindshare Committee awaits an event report to proceed with the Fedora Reimbursement Request. (@jflory7:fedora.im, 11:23:55) * LINK: https://gitlab.com/fedora/mindshare/home/-/issues/85#note_2855789827 (@jflory7:fedora.im, 11:23:57) * TOPIC: #87: Funding proposal: Fedora at Kirinyaga University - Kenya( Info session and Docs Workshop (November 8th, 2025) (@jflory7:fedora.im, 11:24:12) * LINK: https://gitlab.com/fedora/mindshare/home/-/issues/87 (@jflory7:fedora.im, 11:24:19) * LINK: https://fedoraproject.org/wiki/Fedora_at_kirinyaga_university#Budget_Proposal (@jflory7:fedora.im, 11:25:04) * INFO: The event looks awesome! The Mindshare Committee gives a big hoorah to Cornelius Emase for his efforts! W00t w00t! (@jflory7:fedora.im, 11:33:01) * IDEA: There is a poster design that a friend of Cornelius Emase's made. Cornelius is content to work with his friend and update the poster for the event. (@jflory7:fedora.im, 11:34:10) * ACTION: @lochipi Share the updated version of the poster with the Design Team before going to print for a quick review on brand and style guidelines for Fedora. (@jflory7:fedora.im, 11:34:33) * AGREED: The ticket is more or less approved, but will officially hit the required three-day voting period at 23:59 on Fri, 31 October 2025. Assuming no `-1` votes before this time, the event is approved for the requested budget. (@jflory7:fedora.im, 11:35:05) * LINK: https://gitlab.com/fedora/mindshare/home/-/issues/87#note_2855806276 (@jflory7:fedora.im, 11:35:26) * TOPIC: #88: Define the remit of Recognition Service in Mindshare (@jflory7:fedora.im, 11:36:46) * LINK: https://gitlab.com/fedora/mindshare/home/-/issues/88 (@jflory7:fedora.im, 11:36:52) * INFO: See some of the following questions asked by Akashdeep Dhar and Gwmngilfen to Mindshare Committee compatriots: (@jflory7:fedora.im, 11:39:10) * INFO: **About scope and definition**: What constitutes "recognition" in our context? (Should we focus on public recognition (blog posts, social media), tangible rewards (swag, conference tickets), or a mixture of both?) How do we define and/or evaluate contribution? (What activities should be scoped higher than the others? Technical, community, collaborative, sustained, leadership, chores etc.?) (@jflory7:fedora.im, 11:39:10) * INFO: **About process and implementation**: What cadence works best for recognition reviews (either automated or manual) to construct an impact assessment? Frequency of the metrics gathering to weigh action and result balance. How should we connect with other Fedora Project teams to widen our scope of recognition to teams and SIGs that are not necessarily connected directly with but are influenced by Mindshare? (@jflory7:fedora.im, 11:39:10) * INFO: **About measurement and metrics**: What metrics should we use to measure the contribution impact (action) and community health (result)? Qualitative (mentorship, accesses etc.) as well as quantitative (commits, issues etc.) How do we introspect the effectiveness of the recognition service itself? With us doing good or bad at what we do can result well or poorly on the other projects/SIGs of the Fedora Project. (@jflory7:fedora.im, 11:39:10) * INFO: **About resources and sustainability**: What budget and resources are realistic enough to be used here? Do we reserve a part of the assigned budget, or do we float atop it based on how many interested parties we might get? What would the day-to-day operation entail? Badges and Datanommer are good entry points but what do we do there to expect the maximum benefit in terms of recognition of contributors? (@jflory7:fedora.im, 11:39:10) * INFO: See the above questions and please take some time to review them and answer questions you are willing / have context for. Even answering one or two questions is fine if you don't feel like you have answers for all of them! (@jflory7:fedora.im, 11:42:59) * ACTION: @jflory7 @ekidney @lbazan @joseph @sumantrom Review ticket #88 asynchronously as comments on GitLab (@jflory7:fedora.im, 11:44:11) * AGREED: Feedback deadline is by the next Mindshare Committee is Thu, 13 Nov 2025 (@jflory7:fedora.im, 11:45:21) * TOPIC: #80: Committee Member Role Definition and Onboarding (@jflory7:fedora.im, 11:46:29) * LINK: https://gitlab.com/fedora/mindshare/home/-/issues/80 (@jflory7:fedora.im, 11:46:35) * IDEA: Rewrite the Mindshare Committee agenda to begin meetings with focus area updates from each focus area lead/co-lead, and then leave the latter half of the meeting for tickets? (@jflory7:fedora.im, 11:49:02) * INFO: Emma Kidney and Joseph Gayoso are on-board to co-lead the Digital Ambassadorship focus area. They plan to begin by reworking the docs to be more clear and address the questions raised in our previous meeting two weeks ago. (@jflory7:fedora.im, 11:50:37) * ACTION: @ekidney Open a new Mindshare Committee issue to track the launch of the Digital Ambassadorship focus area (@jflory7:fedora.im, 11:51:01) * ACTION: @lbazan Open a new Mindshare Committee ticket about the Regional Event Support focus area. Identify questions to ask to the wider Mindshare Committee group to help frame the focus. Also, maybe suggest edits to the Mindshare Committee charter if the focus area as written is not clear or not meeting the reality of today! (@jflory7:fedora.im, 11:58:08) * TOPIC: Open floor (@jflory7:fedora.im, 11:58:13) * LINK: https://gitlab.com/fedora/mindshare/home/-/issues/82 (@jflory7:fedora.im, 11:58:56) * INFO: #82: Define committee's coordination model with Mindshare Teams. Akashdeep Dhar asked some questions to the wider Committee in this issue. As your time allows, please review and weigh in if you have thoughts! (@jflory7:fedora.im, 11:58:56) Meeting ended at 2025-10-30 12:00:03 Action items ------------ * @lochipi Share the updated version of the poster with the Design Team before going to print for a quick review on brand and style guidelines for Fedora. * @jflory7 @ekidney @lbazan @joseph @sumantrom Review ticket #88 asynchronously as comments on GitLab * @ekidney Open a new Mindshare Committee issue to track the launch of the Digital Ambassadorship focus area * @lbazan Open a new Mindshare Committee ticket about the Regional Event Support focus area. Identify questions to ask to the wider Mindshare Committee group to help frame the focus. Also, maybe suggest edits to the Mindshare Committee charter if the focus area as written is not clear or not meeting the reality of today! People Present (lines said) --------------------------- * @jflory7:fedora.im (167) * @t0xic0der:fedora.im (30) * @gwmngilfen:fedora.im (14) * @ekidney:matrix.org (9) * @zodbot:fedora.im (7) * @lbazan:fedora.im (5) * @lochipi:matrix.org (4) * @meetbot:fedora.im (3) * @theprogram:fedora.im (2)