<@jflory7:fedora.im>
11:01:00
!startmeeting Fedora Mindshare Committee - 2026-02-19
<@meetbot:fedora.im>
11:01:01
Meeting started at 2026-02-19 11:01:00 UTC
<@meetbot:fedora.im>
11:01:01
The Meeting name is 'Fedora Mindshare Committee - 2026-02-19'
<@jflory7:fedora.im>
11:01:05
!meetingname mindshare
<@meetbot:fedora.im>
11:01:06
The Meeting Name is now mindshare
<@gwmngilfen:fedora.im>
11:01:12
!hi
<@zodbot:fedora.im>
11:01:13
Greg Sutcliffe (gwmngilfen) - he / him / his
<@jflory7:fedora.im>
11:01:14
!topic Roll Call & Welcome
<@jflory7:fedora.im>
11:01:15
!hi
<@zodbot:fedora.im>
11:01:17
Justin Wheeler (jflory7) - he / him / his
<@t0xic0der:fedora.im>
11:01:17
!hi
<@zodbot:fedora.im>
11:01:18
Akashdeep Dhar (t0xic0der) - he / him / his
<@jflory7:fedora.im>
11:01:19
Hey folks π
<@jflory7:fedora.im>
11:01:22
!group members mindshare
<@zodbot:fedora.im>
11:01:24
Members of mindshare: emma kidney, Greg Sutcliffe, jflory7 (@jflory7:fedora.im, @fca:fedoraproject.org), Joseph Gayoso, lbazan, Sumantro Mukherjee, Akashdeep Dhar
<@ekidney:matrix.org>
11:01:32
!hi
<@jflory7:fedora.im>
11:01:33
We will give it a few minutes for folks to show up. And for me to finish making my coffee π
<@zodbot:fedora.im>
11:01:34
emma kidney (ekidney) - she / her / hers
<@jflory7:fedora.im>
11:01:48
At a quick glance, we have quite a few event tickets this week: https://gitlab.com/fedora/mindshare/home/-/issues?first_page_size=100&sort=created_date&state=opened
<@jflory7:fedora.im>
11:02:06
And also, we should probably chat about getting over to Forgejo too.
<@jflory7:fedora.im>
11:02:44
Should probably discuss tickets #101 and #102. Any else top of mind for folks?
<@t0xic0der:fedora.im>
11:02:48
I plan to open issue tickets pertaining to each action items that we derived from the Fedora Council Strategy Summit's Mindshare representation.
<@t0xic0der:fedora.im>
11:03:52
Admittedly, it took me a while to get things onto the board - But once we do, things should be very "decentralizable" in terms of who is responsible for what part of the work etc.
<@jflory7:fedora.im>
11:03:52
Oh! Actually, a summary of the Strategy Summit would be helpful for this meeting too, since it is logged
<@jflory7:fedora.im>
11:04:12
[@t0xic0der:fedora.im](https://matrix.to/#/@t0xic0der:fedora.im) Are you up for sharing a quick summary of that in the next `topic`?
<@t0xic0der:fedora.im>
11:04:35
Sure
<@jflory7:fedora.im>
11:05:01
So, here is the on-the-fly agenda for today. Let me know what you think. ππ» or π€ :
<@jflory7:fedora.im>
11:05:42
4. Any charter-related work that folks have ready to discuss or provide updates on
<@jflory7:fedora.im>
11:05:42
3. New event funding tickets
<@jflory7:fedora.im>
11:05:42
2. Forgejo migration
<@jflory7:fedora.im>
11:05:42
1. News & Announcements, including a brief readout of Strategy Summit in a Mindshare context
<@jflory7:fedora.im>
11:05:46
WDYT?
<@jflory7:fedora.im>
11:06:23
It's raining thumbs. Let's go!
<@jflory7:fedora.im>
11:06:35
!topic News, announcements, and community updates
<@jflory7:fedora.im>
11:06:48
[@t0xic0der:fedora.im](https://matrix.to/#/@t0xic0der:fedora.im) You can write us some `!info` here!
<@t0xic0der:fedora.im>
11:06:52
!link https://discussion.fedoraproject.org/t/fedora-council-2026-strategy-summit-daily-briefings-summaries-tirana-albania/180535/5
<@jflory7:fedora.im>
11:06:55
Anyone else is welcome to throw some updates in the chat too.
<@t0xic0der:fedora.im>
11:06:58
!link https://github.com/gridhead/gridhead/blob/master/FedoraCouncilStrategySummit2026_1030IST_04Feb2026_FedoraMindshareProgressUpdate.pdf
<@jflory7:fedora.im>
11:07:01
I have a couple as well
<@t0xic0der:fedora.im>
11:07:39
!info @t0xic0der delivered Fedora Mindshare Progress Update during Fedora Council Strategy Summit on the Day Two of the event
<@t0xic0der:fedora.im>
11:08:43
!info Discussions around expansion to the APAC region, refilling of the swags / stickers inventory before Flock, revisiting of the information brochure as swags, leading by example for moving over to Forgejo and providing the updates back to Council were made
<@t0xic0der:fedora.im>
11:09:16
!info Further action items on Fedora Mindshare's part would be tracked on the issue tracker - Once the move over to Forgejo takes place
<@t0xic0der:fedora.im>
11:09:36
Yep, that's about it - I will pass it back to you Justin Wheeler.
<@jflory7:fedora.im>
11:11:19
Great ποΈ Thanks for the update and for representing the committee at the Strategy Summit.
<@jflory7:fedora.im>
11:11:40
!info === "Save the Date: Fedora Council Video Meeting on 2026 Strategy Summit" ===
<@jflory7:fedora.im>
11:11:48
!link https://fedoramagazine.org/fedora-council-meeting-2026-strategy-summit/
<@jflory7:fedora.im>
11:12:16
!info Join the Fedora Council public video meeting on Wednesday, February 25, 2026, at 14:00 UTC. Fedora Project Leader Jef Spaleta will share outcomes from the recent 2026 Strategy Summit and outline the strategic direction for the upcoming year. Attendees can ask questions live on Google Meet or submit them early via the Fedora Discussion topic. This is your opportunity to engage directly with leadership regarding Fedora's future.
<@jflory7:fedora.im>
11:12:27
!info === "Mrhbaan Syria! Fedora now available in Syria" ===
<@jflory7:fedora.im>
11:12:35
!link https://fedoramagazine.org/fedora-syria/
<@jflory7:fedora.im>
11:12:43
!info As of 10 February 2026, Fedora is now available in Syria. The Fedora Infrastructure Team has lifted IP blocks on Syrian addresses following recent United States policy changes. This restores full access to Fedora Linux ISOs, repositories, and services. We are thrilled to welcome our Syrian contributors and users back to the community!
<@jflory7:fedora.im>
11:13:17
I hope to see folks here at the Council readout next Wednesday! I have a Google Calendar with the meeting details, in case you want the invite and aren't on it already. Let me know if that is you.
<@t0xic0der:fedora.im>
11:13:31
I have one more - Just a sec please
<@jflory7:fedora.im>
11:13:53
!info === Notice: Event report collection phase begins for FOSDEM, DevConf India ===
<@t0xic0der:fedora.im>
11:14:33
!info Fedora Project Community Corner had an amazing representation during DevConf.IN 2026. Kudos to jnsamyak (at DevConf.IN 12-16 Feb), @sdglitched and Yaash. (Oh and mattdm)! We had a footfall of 1200 people at the booth, making it the maximum throughout the event.
<@jflory7:fedora.im>
11:14:42
!info We are now entering the post-event phase for FOSDEM and DevConf India. All sponsored, funded attendees by the Fedora Project must complete event reports within 30 days of the conclusion of the event. This is both the success criteria for completing reimbursements as well as closing the Mindshare Committee tickets for each event.
<@jflory7:fedora.im>
11:14:56
!link https://docs.fedoraproject.org/en-US/mindshare-committee/policy/events/reports/
<@jflory7:fedora.im>
11:15:00
<eof>
<@jflory7:fedora.im>
11:15:40
Akashdeep Dhar++ jnsamyak (at DevConf.IN 12-16 Feb)++ Yaash++ mattdm++
<@zodbot:fedora.im>
11:15:41
jflory7 has already given cookies to t0xic0der during the F43 timeframe
<@jflory7:fedora.im>
11:15:47
jnsamyak (at DevConf.IN 12-16 Feb)++
<@zodbot:fedora.im>
11:15:48
jflory7 gave a cookie to jnsamyak. They now have 44 cookies, 3 of which were obtained in the Fedora 43 release cycle
<@jflory7:fedora.im>
11:15:50
Yaash++
<@zodbot:fedora.im>
11:15:51
jflory7 gave a cookie to thisisyaash. They now have 14 cookies, 1 of which were obtained in the Fedora 43 release cycle
<@jflory7:fedora.im>
11:15:58
mattdm++
<@zodbot:fedora.im>
11:16:00
jflory7 gave a cookie to mattdm. They now have 173 cookies, 1 of which were obtained in the Fedora 43 release cycle
<@jflory7:fedora.im>
11:17:02
Any other news and announcements?
<@jflory7:fedora.im>
11:18:01
## News and announcements, going onceβ¦
<@jflory7:fedora.im>
11:18:20
## News and announcements, going twiceβ¦
<@jflory7:fedora.im>
11:18:40
## News and announcements, going thriceβ¦
<@jflory7:fedora.im>
11:19:00
!topic Forgejo migration for Mindshare Committee
<@jflory7:fedora.im>
11:19:10
OK. So, this is a big one.
<@jflory7:fedora.im>
11:19:20
I don't think we actually have a work tracking ticket open for it either.
<@t0xic0der:fedora.im>
11:19:28
Nope, we do not.
<@t0xic0der:fedora.im>
11:20:15
In retrospect, it is good that I have not opened the action item issue tickets on GitLab. It just makes sense to have them opened on the destination namespace, as long as the migration itself does not take forever.
<@jflory7:fedora.im>
11:20:34
Now we do π
<@jflory7:fedora.im>
11:20:36
!link https://gitlab.com/fedora/mindshare/home/-/issues/104
<@t0xic0der:fedora.im>
11:20:55
Look at you go, cool guy π
<@jflory7:fedora.im>
11:21:13
I gave up on the notion of writing perfect issues in real time, and allowing myself the grace to come back to them later π
<@jflory7:fedora.im>
11:21:29
Anyways, it might be worth mapping out what we need to move, the timeline for moving, and identifying folks who can help us with that
<@jflory7:fedora.im>
11:21:39
I also don't know if we requested an organization on Forgejo yet π€
<@t0xic0der:fedora.im>
11:21:39
The mapping of the FAS groups and the namespace has been done in the past couple of weeks. We do have to note about things like the documentation building pipelines while moving away from GitLab and the feature parity that we have on Forgejo.
<@jflory7:fedora.im>
11:21:45
The coffee is not strong enough this morning π
<@jflory7:fedora.im>
11:22:08
Oh, it is not bad at all
<@jflory7:fedora.im>
11:22:13
Just two repos, tickets and docs
<@jflory7:fedora.im>
11:22:15
Easy peasy
<@t0xic0der:fedora.im>
11:22:20
!link https://forge.fedoraproject.org/mindshare
<@t0xic0der:fedora.im>
11:22:25
You're welcome ;P
<@jflory7:fedora.im>
11:22:26
Sweet.
<@jflory7:fedora.im>
11:22:45
So, we exist. That is like, a quarter of the battle π
<@t0xic0der:fedora.im>
11:23:25
Since we have the namespace already - it has to be self service from here on out. We would love to have takers (if there are any) who are willing to help us out with this move.
<@jflory7:fedora.im>
11:23:29
!info A Forgejo organization already exists for the Fedora Mindshare Committee. We have a landing place for our migrated repos now.
<@jflory7:fedora.im>
11:24:15
!info There are only two repositories to move from GitLab to Forgejo: tickets and docs. Per past experience with the GitLab migrator, it may take some debugging as things like releases and wikis caused problems for the DEI and CommOps teams when they migrated.
<@jflory7:fedora.im>
11:24:55
!halp We need a volunteer to help do the initial migration via the web UI on forge.fp.o. It should be point-and-click, but there may be some minor headaches depending on GitLab functionality and Forgejo-GitLab migrator bugs.
<@jflory7:fedora.im>
11:25:29
I'm on the hook for managing the Council migration, CommOps migration, DEI Team migration, and need to help with the Marketing Team and Docs Team migrations too
<@jflory7:fedora.im>
11:25:32
I have a lot on my plate π
<@jflory7:fedora.im>
11:25:44
So, it would not be wise for me to take this one on right now, if we are getting it done any time soon
<@gwmngilfen:fedora.im>
11:26:01
i can maybe do these two. i should be helping with sme of the infra migration anyway π
<@t0xic0der:fedora.im>
11:26:07
That's fair. I could help whoever raises their hand for being a star here, since I am involved in the initiative.
<@jflory7:fedora.im>
11:26:15
Gwmngilfen++ That would be awesome.
<@zodbot:fedora.im>
11:26:17
jflory7 gave a cookie to gwmngilfen. They now have 25 cookies, 11 of which were obtained in the Fedora 43 release cycle
<@t0xic0der:fedora.im>
11:26:30
Awesome! :D
<@zodbot:fedora.im>
11:26:35
t0xic0der has already given cookies to gwmngilfen during the F43 timeframe
<@jflory7:fedora.im>
11:26:47
Gwmngilfen: I believe all action items should have deadlines! But the deadlines should be agreed upon. Do you think the end of February is reasonable?
<@gwmngilfen:fedora.im>
11:26:52
assign the ticket to me, i'll try not to forget. I don't look at gitlab too often, so the sooner we move it the better )
<@gwmngilfen:fedora.im>
11:26:55
assign the ticket to me, i'll try not to forget. I don't look at gitlab too often, so the sooner we move it the better :)
<@gwmngilfen:fedora.im>
11:27:02
end of feb works for me
<@jflory7:fedora.im>
11:27:07
OK, great.
<@zodbot:fedora.im>
11:27:29
ekidney gave a cookie to gwmngilfen. They now have 26 cookies, 12 of which were obtained in the Fedora 43 release cycle
<@jflory7:fedora.im>
11:28:08
!action @gwmngilfen due:2026-02-27 Migrate the "home" GitLab repo to "tickets" on Forgejo, migrate "docs" GitLab repo to "docs" on Forgejo.
<@gwmngilfen:fedora.im>
11:28:30
afk a min
<@jflory7:fedora.im>
11:28:37
!info Ideally, our next meeting on Thursday, 5 March, will be run from Forgejo instead of GitLab.
<@jflory7:fedora.im>
11:29:24
I think that about covers itβ¦
<@jflory7:fedora.im>
11:29:31
Surely there is more, but for initial steps, I think this is great
<@jflory7:fedora.im>
11:29:44
After we get to Forgejo, it is probably worth taking an audit of our use of labels and milestones
<@jflory7:fedora.im>
11:29:48
But we can get to that in due time
<@jflory7:fedora.im>
11:29:56
For now, the priority is simply to get over there π
<@jflory7:fedora.im>
11:30:31
<del>And feel myself lose three years of stress by having fewer things to look at in GitLab and perpetual SSO logins</del>
<@jflory7:fedora.im>
11:30:52
Oops, did I say that out loud? π
<@jflory7:fedora.im>
11:30:55
_Anywaysβ¦_
<@t0xic0der:fedora.im>
11:31:15
Now that's behind us - Get ready to lose another six years on whatever trap Forgejo lands you into π
<@t0xic0der:fedora.im>
11:31:29
ryanlerch: isn't around - is he?
<@jflory7:fedora.im>
11:31:29
So, I think we can move to the event funding tickets next. I haven't had a chance to see them yet.
<@jflory7:fedora.im>
11:32:22
!topic Ticket #101: Funding Request: 20 Sesja Linuksowa
<@jflory7:fedora.im>
11:32:27
!link https://gitlab.com/fedora/mindshare/home/-/issues/101
<@jflory7:fedora.im>
11:32:40
!info Sesja Linuksowa is one of the oldest FLOSS conferences in Poland, bringing in hundreds of attendees each year. It features two days full of talks and a "middle party" where attendees can get to know each other better.
<@jflory7:fedora.im>
11:32:57
!info Event dates: 25th-26th of April 2026 (Sat-Sun)
<@jflory7:fedora.im>
11:33:11
!info Total Requested Budget: ~140 USD
<@t0xic0der:fedora.im>
11:33:59
!link https://docs.fedoraproject.org/en-US/mindshare-committee/events/requests/small/
<@jflory7:fedora.im>
11:33:59
So, this puts us in Q2. From a Red Hat budget perspective, this is a new quarter, which means we get access to new funds. Folks at Red Hat likely understand this context, but I know it can be confusing for community. One day soon, I will write down how all this is supposed to work.
<@jflory7:fedora.im>
11:34:16
It is a Small Event too, which is fairly easy and simple to fund
<@jflory7:fedora.im>
11:34:41
I'll put some of @suve's answers in the ticket in the meeting log, because I think it helps when looking at a vote:
<@jflory7:fedora.im>
11:34:50
!info **Why is it a good idea for the Fedora Project to have a presence?**: Because the Session is (as far as I know) the biggest community-organized, free to attend FLOSS conference in Poland. Previous editions featured some talks from Fedora community members.
<@jflory7:fedora.im>
11:35:09
!info **Why do you want to represent the Fedora community here?**: Because Fedora has had a presence during previous editions, and I'd like for this to continue.
<@jflory7:fedora.im>
11:35:55
Emma Kidney: Just curious⦠do you have any sort of handy, printable template that someone could put on a table? e.g. "These snacks and beverages sponsored by Fedora" or something like that?
<@jflory7:fedora.im>
11:36:04
If no, is April enough time to make something?
<@jflory7:fedora.im>
11:36:23
I like the event proposal, I am fine funding food, but I'd like people to know that it is coming to them from Fedora, with some links to the project and our social media ideally.
<@jflory7:fedora.im>
11:36:39
Sort of like a mini standing banner, but table-sized and printable from an everyday printer.
<@t0xic0der:fedora.im>
11:36:42
I appreciate the regularity of the event but stating that we want to have it this time around too just because we had it the last time turns no heads.
<@t0xic0der:fedora.im>
11:36:42
Complacent answers, to be honest.
<@ekidney:matrix.org>
11:36:54
no we dont but it should be doable since its 2 months away
<@ekidney:matrix.org>
11:37:34
Will I log a ticket on the design repo for that?
<@t0xic0der:fedora.im>
11:37:38
I would be more into understanding what the conference has to offer Fedora Project this year (and vice versa).
<@t0xic0der:fedora.im>
11:37:38
Since, it is a small event - I do not think it should be an issue but we want regular events like these to lead by example.
<@jflory7:fedora.im>
11:38:58
For a larger event, I would be picky, but I see some names of folks who do a lot of packaging work in the community. I think everyone should have the opportunity to connect and get face-time with others in the community. I like events where newcomers intermix with experienced contributors.
<@jflory7:fedora.im>
11:38:58
<@jflory7:fedora.im>
11:38:58
I wonder if we have an event report handy from the last time. I thought I remember something, it might have been posted on Fedora Discussion. If I am remembering the right one, I definitely want to see more photos next time. The readout, as I recall, makes me think it was worth the low-dollar spend.
<@jflory7:fedora.im>
11:39:38
Emma Kidney: That would be awesome! If you can scope the ticket with a deadline for this specific event, but keep it generic enough that any Small Event could use this, I think it could be a useful asset for events in this category
<@t0xic0der:fedora.im>
11:40:08
It is something that can be retroactively worked towards but is not a blocker.
<@t0xic0der:fedora.im>
11:40:08
Agreed and that is why, while I would note this out - this has no bearings into the actual decision from my end.
<@ekidney:matrix.org>
11:40:16
I'll be honest that the budget still kind of confuses me. I'm happy to vote on events but without knowing the budget its kinda hard since we dont know how picky to be if that makes sense
<@jflory7:fedora.im>
11:41:14
I'm still waiting for the full data from Red Hat on this, and it makes it hard to be transparent when I actually don't know for sure what Fedora has. That said, I have been working on this with shaunm and I hope we can share something more public by the timeline of Flock, perhaps.
<@jflory7:fedora.im>
11:42:00
There are also some interesting conversations happening around the Council Strategy Summit around new vehicles for funding contributors to do useful things, outside of Red Hat dollars. It is a big topic, and I'd encourage anyone curious to go read the Fedora Council Strategy Summit readout topic on Fedora Discussion.
<@jflory7:fedora.im>
11:42:39
!action @ekidney due:2026-04-09 Make a Design Team ticket to create a template for snacks/food/beverage sponsorship for Small Events, with the specific target of providing this as a printable asset for 20 Sesja Linuksowa
<@ekidney:matrix.org>
11:43:09
That would be great. I know you've been asked this before so i appreciate it.
<@jflory7:fedora.im>
11:43:48
Yeah, good to keep me accountable on this one π It isβ¦ really hard, but important nonetheless
<@jflory7:fedora.im>
11:44:22
OK, but for this event, I think we can begin the voting phase here. The ticket was opened with ample time, and from my tentative foresight into Q2 budget for events in Fedora, this is something easy enough to fund.
<@jflory7:fedora.im>
11:44:30
Let me update the ticket metadata really quick.
<@t0xic0der:fedora.im>
11:44:34
!link https://gitlab.com/fedora/mindshare/home/-/issues/101#note_3097389614
<@jflory7:fedora.im>
11:45:49
I put a deadline for our next Mindshare Committee meeting on March 5th. Will be interesting to see whether the Forgejo migration carries that data over or not
<@jflory7:fedora.im>
11:46:27
!action @all Add a vote to Ticket #101 by 5 March 2026
<@t0xic0der:fedora.im>
11:46:50
Hmmm. Would be interesting to see how things work with the GitLab importer. If this was on Pagure then we did implement the milestones importer there as the Fedora QA folks wanted it to be there. Fingers crossed.
<@jflory7:fedora.im>
11:47:22
I think this sufficiently covers Ticket #101
<@jflory7:fedora.im>
11:47:25
Let's get to the next one
<@jflory7:fedora.im>
11:47:34
!topic Ticket #102: Chemnitzer Linux-Tage 2026
<@jflory7:fedora.im>
11:47:38
!link https://gitlab.com/fedora/mindshare/home/-/issues/102
<@jflory7:fedora.im>
11:47:50
!info Since their inception in 1999 the Chemnitzer Linux-Tage have gained a reputation of being the German FLOSS community event attracting more than 3000 visitors over a weekend in March. The event takes place at the faculty of computer science/information technology at the Chemnitz university of technology and countless volunteers make it happen. There are talks, demonstrations, live workshops, community projects and some companies who present themselves. The Fedora Project usually had a physical booth at Chemnitzer Linux-Tage each year since 2007 with the exception of mainly the years of COVID-19 pandemic.
<@jflory7:fedora.im>
11:48:07
!info **Why is it a good idea for the Fedora Project to have a presence?**: Because it's one of the FLOSS community events in Germany (the other one is FrOSCon from my point of view), where mainly users, but also developers, from all over Germany come together. The event targets users, not developers, but users can become developers or contributors over time. Usually all common/large Linux distribution communities attend the event with a booth, while it might be not a good argument. Visitors are looking for somebody to talk about Fedora in person and to raise their questions they might not raise online. Aside of this, people are also even looking for a Fedora booth (see next section for details).
<@jflory7:fedora.im>
11:48:18
!info **Why do you want to represent the Fedora community here?**: Because I really enjoy this event, the people there and I like to help them with all the questions and issues they come up with - and I'm a Fedora ambassador. I wouldn't drive 2x 450 km by car (2x ~5 hours plus traffic jams) about each year if the event wouldn't be worth it. And I'm attending the event, with or without a Fedora booth. When I attended in 2023 and 2024 as a regular visitor without a Fedora booth (unfortunately not enough Fedora people, due to different reasons, to cover the organiser's requirements for a booth), I was really asked often in both years why there is no Fedora booth and whether there will be one again.
<@jflory7:fedora.im>
11:48:28
!info Event dates: 29 March 2026 and 30 March 2026
<@jflory7:fedora.im>
11:48:42
!info Budget estimates: 210 USD
<@jflory7:fedora.im>
11:48:52
So, this puts us into the Medium Event category, but not by much
<@t0xic0der:fedora.im>
11:49:05
Barely crossed the small events frontier by a bit ;P
<@t0xic0der:fedora.im>
11:49:18
!link https://docs.fedoraproject.org/en-US/mindshare-committee/events/requests/medium/
<@t0xic0der:fedora.im>
11:51:14
We have a booth presence here.
<@t0xic0der:fedora.im>
11:51:16
!link https://fedoraproject.org/wiki/Chemnitzer_Linuxtage_2026#Booth
<@jflory7:fedora.im>
11:51:37
So, the ticket is just the hotel for a single person, but Robert is a known contributor, an experienced Ambassador (therefore qualifying for a Medium Event), and he also seems to be running the Fedora booth.
<@jflory7:fedora.im>
11:51:54
The event falls in Q1, but since it is right at the end of March, any reimbursements/payments will happen in Q2
<@jflory7:fedora.im>
11:52:08
Which for our purposes, is better, because Q1 is a very heavy spend quarter on events
<@jflory7:fedora.im>
11:52:23
I like that there is a wiki page
<@jflory7:fedora.im>
11:52:38
I also know some other Fedora folks tend to show up for this. Pretty sure Dan ΔermΓ‘k goes to this.
<@t0xic0der:fedora.im>
11:53:09
Exactly. I did not find one for ticket #101.
<@t0xic0der:fedora.im>
11:53:09
Maybe there was one, but I didn't see it. I am not sure.
<@jflory7:fedora.im>
11:53:14
It also looks like Raphael Groner will be there too
<@jflory7:fedora.im>
11:53:36
For a Small Event, I think a Wiki page could be an optional, but for Medium Events, I definitely think it is valuable IMHO
<@t0xic0der:fedora.im>
11:53:46
Makes sense.
<@jflory7:fedora.im>
11:53:59
The goal for Small Events is to get the ball rolling and build momentum for something bigger, or help us understand whether an event is worth committing more money/time/energy to
<@jflory7:fedora.im>
11:54:15
A Medium Event, even if not by much, does represent a bigger commitment than buying a few pizzas and beverages
<@jflory7:fedora.im>
11:55:11
Anyways, I think the rationale is sound. It seems like we haven't been there in a while, and while I am not an expert in German FOSS events, I spend enough time in Germany to know this and FrOSCon seem to be the two notable events in the country
<@jflory7:fedora.im>
11:55:49
Getting a hotel for Robert seems like an easy commitment, and his past tenure as an Ambassador gives me trust that he knows what he is doing and how to represent the project
<@jflory7:fedora.im>
11:55:56
That said, I'll be keen to see the event report π
<@jflory7:fedora.im>
11:56:03
So, for me, it is a +1
<@jflory7:fedora.im>
11:56:08
Anyone else have questions, thoughts, opinions?
<@t0xic0der:fedora.im>
11:56:18
Nope.
<@t0xic0der:fedora.im>
11:56:26
Conveying my documented +1 as we speak
<@ekidney:matrix.org>
11:56:53
I think the hotel is requested for someone else but yah I agree it looks good
<@jflory7:fedora.im>
11:57:08
Oh heh, you are right!
<@jflory7:fedora.im>
11:57:26
The hotel is for Raphael, not Robert
<@jflory7:fedora.im>
11:58:07
It is a good detail to note, because it is Raphael who will have the obligation of doing the reimbursement, but I don't think it substantially changes the scope of the ticket/event
<@jflory7:fedora.im>
11:58:24
We will want to make sure Raphael reviews https://docs.fedoraproject.org/en-US/mindshare-committee/policy/reimbursements/ before the event
<@ekidney:matrix.org>
11:58:25
it looks like there was a booth in 2025 too https://communityblog.fedoraproject.org/fedora-at-chemnitzer-linux-tage-2025/
<@jflory7:fedora.im>
11:58:26
!link https://docs.fedoraproject.org/en-US/mindshare-committee/policy/reimbursements/
<@t0xic0der:fedora.im>
11:58:41
!link https://gitlab.com/fedora/mindshare/home/-/issues/102#note_3097447508
<@jflory7:fedora.im>
11:59:00
Oh nice. When we get to Forgejo, we should update these issue templates to note if there are past event reports available, and to provide them if so π
<@jflory7:fedora.im>
11:59:02
!link https://communityblog.fedoraproject.org/fedora-at-chemnitzer-linux-tage-2025/
<@jflory7:fedora.im>
11:59:47
Well, the event report here actually does not say muchβ¦ better to do something than nothing, but I have questions about how it went and what questions people asked π
<@jflory7:fedora.im>
11:59:52
It is a teaser post actually!
<@jflory7:fedora.im>
12:00:03
What did people say? What were the questions?! I want to know! π
<@t0xic0der:fedora.im>
12:00:15
Lest we forget.
<@t0xic0der:fedora.im>
12:00:15
Something to populate https://gitlab.com/fedora/mindshare/home/-/issues/104 with after the meeting is through. π€
<@jflory7:fedora.im>
12:00:18
What talks about what topics? π
<@ekidney:matrix.org>
12:01:02
is there a guide for the event reports to help people write more detail?
<@jflory7:fedora.im>
12:01:06
Good call-out. I edited the pending description on #104 so I don't forget π
<@jflory7:fedora.im>
12:01:13
Actually, no, there isn't.
<@jflory7:fedora.im>
12:01:25
I wonder if it could fit for the Digital Ambassadorship topicβ¦ π
<@jflory7:fedora.im>
12:01:35
Oh dang, I lost track of time π«£
<@jflory7:fedora.im>
12:01:37
We are past time!
<@t0xic0der:fedora.im>
12:01:44
Off the top of my head, I have examples but nothing as concrete as documentation to point people to.
<@jflory7:fedora.im>
12:02:01
!action @all Add a vote to Ticket #102 by the next Mindshare meeting on 5 March 2026
<@t0xic0der:fedora.im>
12:02:09
I wonder if this is something we would want to work towards.
<@t0xic0der:fedora.im>
12:02:09
Prolly that would make people WANT to write reports?
<@jflory7:fedora.im>
12:02:36
!idea While it is good that there _was_ an old event report, we should provide feedback on the past event report and our curiosity over what questions were asked, what people wanted to know, what topics were presented, etc.
<@jflory7:fedora.im>
12:03:23
And _maybe_β¦ we could come up with recognition for people who write good event reports π Perhaps a "Mindshare Event Report Author of the Quarter" or something like that.
<@jflory7:fedora.im>
12:03:23
Being able to explain why event reports are valuable and how to write a valuable event report might make it more valuable.
<@jflory7:fedora.im>
12:03:23
<@jflory7:fedora.im>
12:03:27
Just an idea π
<@jflory7:fedora.im>
12:03:33
Well, we are at time, and I know folks are busy!
<@jflory7:fedora.im>
12:03:37
Let's go ahead and wrap up.
<@jflory7:fedora.im>
12:03:43
Sorry we didn't get to the charter-y stuff today.
<@jflory7:fedora.im>
12:03:52
We can try to put that back at the front of the meeting agenda next time.
<@t0xic0der:fedora.im>
12:03:56
Or a badge ;P
<@jflory7:fedora.im>
12:04:04
And hopefully, Forgejo and project boards will help us with that too π
<@jflory7:fedora.im>
12:04:10
I was subtly hinting π
<@jflory7:fedora.im>
12:04:12
Alrighty, folks!
<@jflory7:fedora.im>
12:04:14
Let's wrap!
<@jflory7:fedora.im>
12:04:18
Thanks for being here and taking the time.
<@ekidney:matrix.org>
12:04:23
Thanks everyone!
<@jflory7:fedora.im>
12:04:24
See y'all around in the Fedora-verse!
<@t0xic0der:fedora.im>
12:04:29
Justin Wheeler++ for chairing!
<@zodbot:fedora.im>
12:04:30
t0xic0der has already given cookies to jflory7 during the F43 timeframe
<@jflory7:fedora.im>
12:04:35
!action @jflory7 Write a meeting summary of today's meeting on Fedora Discussion
<@jflory7:fedora.im>
12:04:39
!endmeeting