13:04:27 <jwf1> #startmeeting Fedora Mindshare Committee meeting - 2022-11-22
13:04:27 <zodbot> Meeting started Tue Nov 22 13:04:27 2022 UTC.
13:04:27 <zodbot> This meeting is logged and archived in a public location.
13:04:27 <zodbot> The chair is jwf1. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
13:04:27 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
13:04:27 <zodbot> The meeting name has been set to 'fedora_mindshare_committee_meeting_-_2022-11-22'
13:04:49 <jwf1> #meetingname mindshare
13:04:49 <zodbot> The meeting name has been set to 'mindshare'
13:05:01 <jwf1> #info About the Mindshare Committee: https://docs.fedoraproject.org/en-US/mindshare-committee/
13:05:09 <jwf1> .members mindshare
13:05:10 <zodbot> jwf1: Something blew up, please try again
13:05:13 <zodbot> jwf1: An error has occurred and has been logged. Please contact this bot's administrator for more information.
13:05:22 <jwf1> Uh oh.
13:05:27 <jwf1> Poor zodbot
13:05:31 <jwf1> #chair bt0
13:05:31 <zodbot> Current chairs: bt0 jwf1
13:07:01 <jwf1> I'm trying to tag people but it isn't working on Element app in Android
13:07:03 <jwf1> Argh
13:07:14 <jwf1> I'll be at regular keyboard shortly, but anyways.
13:07:23 <jwf1> #topic Meeting structure & agenda
13:07:32 <jwf1> #info === 1. Hellos & welcome (~5 minutes) ===
13:07:40 <jwf1> #info === 2. Committee announcements & team read-outs (~5-10 minutes) ===
13:07:47 <jwf1> #info === 3. Ticket-driven review & discussion (remaining time) ===
13:07:49 <jwf1> #info === 4. Open floor (final 5 minutes) ===
13:08:03 <jwf1> #topic Hellos & welcome
13:08:39 <bt0> .hello bt0dotninja
13:08:40 <zodbot> bt0: bt0dotninja 'Alberto Rodriguez Sanchez' <hotgalan@gmail.com>
13:08:46 <bt0> hi o/
13:08:55 <jwf1> Máirín Duffy thunderbirdtr nb davdunc @davdunc:fedora.im howdy folks, are you around today?
13:09:04 <jwf1> Hey hey bt0 :)
13:09:39 <jwf1> It might be a quiet day today. I know for U.S. folks, it is a holiday week, so that could be a factor.
13:09:53 <bt0> the holidays are coming... Hi Justin :)
13:10:12 <jwf1> But in general though, attendance at our meetings has been slim. I'm just wondering if it is the kind of thing that a changed meeting time can fix, or if there is something bigger happening 🤔
13:10:29 <jwf1> Yes, it's true. They are coming, and fast :)
13:11:21 <jwf1> So, to recap from the Mindshare channel, I did not have tickets to cover for today's meeting but I did want to raise some topics for feedback.
13:11:53 <jwf1> #info JWF suggests FOSDEM 2023, Fedora Mentor Summit, and CommOps Mindshare seat as topics for today
13:12:17 <bt0> I think just is the time in the year were the things slow down a little bc holidays
13:13:13 <jwf1> Yes. Maybe this is something we start by revisiting in 2023 around meeting days and times.
13:13:37 <bt0> +1 for the topics for this meeting
13:13:42 <jwf1> Anyways, if it is just the two of us for now, let's prioritize the discussion based on the two of us here.
13:13:49 <bt0> ok
13:14:07 <jwf1> #topic CommOps Mindshare seat
13:14:48 <jwf1> bt0, you have done a great job as our CommOps rep all this time. Now we have a difficult challenge of finding the next person to fill your shoes
13:15:25 <jwf1> I am thinking this is a challenge we are having in a few areas of Fedora with representation in Council and Mindshare
13:15:53 <jwf1> I wanted to brainstorm more on how we could both find a new rep and also someone who would be interested in stewarding CommOps
13:16:22 <jwf1> I'm hoping to help out with CommOps again after a long while. But I don't want to do it alone!
13:16:44 <jwf1> My question here is, do you think it is worthwhile doing an open call for the CommOps chair? Like a CommBlog post, social media, etc.
13:17:08 <jwf1> And then trying to review open applications or some other approach.
13:17:27 <jwf1> Alternatively, we could try to look more within the community. But I'm still getting my feelers for where the right place to look might be.
13:17:35 <jwf1> What do you think, bt0?
13:18:55 <bt0> The open call is a great idea, also I'm thinking in waitingone cicle to finding a new representative, the times on the ticket are very close :S
13:19:26 <bt0> Commblog is great for fisrt open call
13:20:33 <jwf1> Cool.
13:21:22 <jwf1> An "external" search is interesting to me, because it might mean someone without too much knowledge of the past, and that might bring new ideas too
13:21:40 <jwf1> It will take some mentoring work, but I think between you and me, we could help with guidance and pointers as needed :)
13:22:01 <jwf1> But, how do you think we should handle the interest? Ask for comments or self-nominations in Pagure?
13:22:27 <jwf1> Or reach out to you/me directly to ask questions and request nomination?
13:23:18 <jwf1> We might get one or none responses. Maybe we would get ten. I'm wondering how best to handle that interest…
13:23:36 <bt0> yeah or even in ask fedora
13:23:47 <jwf1> Oh, that's a good one actually.
13:23:54 <jwf1> I need to spend more time with Ask…
13:24:07 <bt0> me too
13:24:17 <jwf1> Seems like there are lots of active and engaged folks there.
13:24:42 <bt0> yes, a lot more
13:25:26 <jwf1> @bt0: I am leaning toward someone messaging you and me with questions. Either on email, Discussion, or Matrix. This way, we can have a conversation first instead of pressure to comment in a public ticket as the first step
13:26:09 <jwf1> I also would hope this is a first step to create more interest and excitement about CommOps in general, as a team
13:26:37 <jwf1> What do you think about contact method / how to nominate?
13:27:50 <bt0> that sounds better, a little informal/easy methods will help us with getting reached more people :)
13:28:00 <jwf1> Cool :)
13:28:14 <jwf1> So, let's mark this as #agreed as a course of action
13:28:37 <bt0> yes +1000
13:29:07 <jwf1> We could tag-team the CommBlog post in a shared pad.
13:29:17 <jwf1> Let me get that.
13:29:58 <jwf1> #agreed jwf and bt0 agree to explore an open, "external" search for the next CommOps rep. We will start with a CommBlog post and ask interested people to reach out to jwf and bt0.
13:30:02 <pbokoc> Oh man, jwf1 you should ping everyone on the team when you start a meeting :)
13:30:33 <jwf1> pbokoc: Howdy @pbokoc! Yeah, I need to figure out why zodbot is broken 😕
13:30:50 <jwf1> And then trying to tag people on mobile isn't working for half the folks I know who are in this channel. Sigh!
13:31:31 <jwf1> It is one of "those" days with our community infra tech :P
13:31:38 <jwf1> #chair pbokoc
13:31:38 <zodbot> Current chairs: bt0 jwf1 pbokoc
13:32:07 <jwf1> Anyways, we were just wrapping a discussion about the CommOps seat. Next I wanted to get some feedback about FOSDEM next year.
13:32:44 <jwf1> #action jwf Start a CommBlog draft and edit with bt0 for advertising the CommOps rep seat and the team in general
13:32:53 <jwf1> OK. I think this wraps this topic.
13:32:55 <bt0> cool
13:33:02 <jwf1> #topic FOSDEM 2023
13:33:30 <jwf1> This one, again, lacks a ticket. But I wanted to check in with y'all on my thinking and approach here, because the clock is ticking fast for travel.
13:34:06 <jwf1> I am trying to think about how we approach travel funding for events. We haven't done much in-person other than fund local events for some time.
13:34:36 <jwf1> Local events are easier because we aren't funding travel usually. But when we do, it is more complex
13:34:55 <jwf1> There is also additional context here too
13:35:29 <jwf1> Next year, we are hoping to return to an in-person Flock. This will be the first time we have Flock again after a while, and our budget is definitely going to feel that one!
13:35:49 <bt0> :p
13:36:12 <jwf1> So, I am hoping to strike a good balance between fairness for opportunities to travel, and being conservative with budget so we can do more things like travel sponsorship and VISA support for Flock (since it is highly likely it would be a U.S. Flock again)
13:36:27 <jwf1> So! Here is my question:
13:36:41 <jwf1> What do we think a fair and equitable process for FOSDEM travel funding would look like?
13:37:30 <jwf1> I was trying to decide if we create a new short-term git repo with applications for people to travel. And then the applications are reviewed based on demand and budget available.
13:37:54 <jwf1> Or if we use something like the Mindshare Pagure repo instead.
13:38:08 <jwf1> I'm floating ideas here but I haven't made up my mind on what would be best.
13:38:53 <pbokoc> IIRC we've been using the Mindshare repo for that before
13:38:57 <jwf1> Any thoughts here bt0 or pbokoc? If either of you applied for event travel funding from Fedora, how would you like it to be done?
13:39:00 <pbokoc> https://pagure.io/mindshare/issues?search_pattern=travel&status=Closed
13:39:38 <jwf1> pbokoc: Oh, hmmm.
13:39:41 <pbokoc> That seems to have been working fine. I mean I wouldn't know, I never went through the process
13:39:54 <jwf1> So, this could still work. Although the issue template might need updating.
13:40:26 <pbokoc> We could ask riecatnor, she has tons of experience with this stuff from Mindshare's side
13:40:27 <jwf1> But it might be easier to manage given that's how we have done it before and some folks would already be familiar with the process.
13:40:27 <bt0> umm, +1 a new one, also ask people if they can affort part of they travel, for budapest I pay the half of the travel
13:41:22 <pbokoc> A new repo just for these could be nice, though. So it's all in one place and doesn't mix up with the rest of the backlog.
13:41:30 <jwf1> pbokoc: She does, although it is the first time since FOSDEM 2020 I guess that we are sponsoring a group of folks to go. Mostly I wanted to check if we felt like the existing process still works or if we should experiment and try something new
13:41:56 <jwf1> For example, in the 2018 Docs FAD, we used a special repository for folks who applied for support and travel funding.
13:42:17 <jwf1> Oh, sorry, not FAD, *hackfest* 😉
13:42:33 <jwf1> bt0: Yes, asking about options for sharing the travel cost is a good one.
13:42:43 <pbokoc> jwf1, right. Well, I'm not aware of any big issues with the old process per se, and whether we use the big mindshare repo or a separate one seems like a technicality really, it's a question of sending people the right link
13:42:54 <jwf1> bt0: bt0, you are thinking of a new repo to try this out?
13:43:12 <jwf1> pbokoc: /me nods
13:43:37 <jwf1> It could be a nice opportunity to try out GitLab for this stuff too.
13:43:55 <jwf1> I don't think I've tried making issue templates in GitLab yet.
13:44:56 <pbokoc> Go for it then :)
13:45:30 <jwf1> OK. Fair!
13:46:03 <bt0> yeah, also If we need classificate it in some form we can create new tags or something without impact our current repo
13:46:19 <bt0> we will receipt a lots of requests for this
13:46:29 * jwf1 nods
13:46:47 <jwf1> I think that's a consenting direction.
13:47:11 <jwf1> So, since this is becoming high priority with FOSDEM around the corner, I want to get this set up hopefully this week and start taking applications ASAP
13:47:25 <jwf1> I will also ask some event-specific questions
13:48:38 <jwf1> Like spending some hours to help at the Fedora exhibit booth and possibly helping as a volunteer in the Distro devroom.
13:48:39 <jwf1> Anyways, let me notate this one up in Meetbot and then we can move to the wrap-up
13:49:25 <jwf1> #agreed We will try using a dedicated GitLab repo to handle funding/travel requests for FOSDEM 2023. Anyone can submit an application and the decisions can be made in subsequent Mindshare meetings or asynchronously as deadlines require.
13:49:40 <jwf1> #action jwf Set up a new Mindshare GitLab repo for FOSDEM 2023
13:50:02 <jwf1> Also, BTW. If y'all are on GitLab already, let me know so I can add you to the Mindshare subgroup. This will give you access there.
13:50:16 <jwf1> #topic Open floor
13:50:19 <bt0> awesome
13:50:23 <jwf1> OK! So, we are in the last ten minutes.
13:50:38 <jwf1> I said I wanted to discuss the Mentor Summit too, but I think we are short on time for today
13:51:01 <jwf1> Anyways, this was just to flag that I have forecasted to try that event as an in-person event next year
13:51:15 <jwf1> And to use this as a chance to rally around mentoring and mentorship in Fedora Community
13:51:53 <pbokoc> Sounds good
13:51:59 <jwf1> I don't have a lot of details yet, but I wanted to flag this early thinking for next year as an in-person event we might try. It would be folks who participate in Mentored Projects but hopefully others too who participate in mentoring roles in Fedora
13:52:10 <jwf1> So, that's all I have to share there for now
13:52:20 <jwf1> Anything from either of y'all?
13:52:32 <pbokoc> Re: gitlab group, jwf1, add me plz :) https://gitlab.com/pbokoc
13:52:53 <jwf1> #action jwf Add https://gitlab.com/pbokoc to Fedora Mindshare group
13:52:55 <jwf1> Awesome.
13:53:02 <jwf1> Are you already a member of the Fedora organization?
13:53:12 <pbokoc> jwf1, yup
13:53:21 <jwf1> Super. Then it is very easy to do
13:53:35 <jwf1> I'll get that shortly. I was running this meeting from mobile.
13:53:45 <pbokoc> That sounds painful :))
13:54:09 <bt0> :p
13:54:37 <jwf1> Awkward at times for sure. But I remember trying to set up my IRC bouncer in 2015-2017 to run meetings from mobile, and pretty sure I just gave up back then :)
13:54:47 <jwf1> Element isn't so bad. But… it has its peculiarities
13:55:46 <jwf1> Alrighty folks. Last call for topics today?
13:55:53 <jwf1> Or shall we return a few minutes back to you?
13:55:58 <jwf1> Going once…
13:56:15 <jwf1> Going twice…
13:56:35 <jwf1> Going thrice…
13:57:03 <jwf1> And, sooooooold
13:57:08 <jwf1> Thanks folks for coming out today!
13:57:10 <pbokoc> See ya! o/
13:57:18 <jwf1> Enjoy your week, and for those with the holiday, hope you get some extended time off.
13:57:20 <jwf1> Ciao!
13:57:24 <jwf1> #endmeeting