17:33:13 #startmeeting Mindshare (2018-07-03) 17:33:13 Meeting started Wed Jul 3 17:33:13 2019 UTC. 17:33:13 This meeting is logged and archived in a public location. 17:33:13 The chair is jsmith. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:33:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:33:13 The meeting name has been set to 'mindshare_(2018-07-03)' 17:33:15 #meetingname mindshare 17:33:15 The meeting name has been set to 'mindshare' 17:33:34 #topic Welcome and init process 17:34:28 .hello2 17:34:29 jsmith: jsmith 'Jared Smith' 17:34:29 .hello2 17:34:32 x3mboy: x3mboy 'Eduard Lucena' 17:34:49 I am here 17:36:50 (Apologies, my internet connection keeps dropping out) 17:37:21 Alberto Rodríguez Fas: bt0dotninja 17:37:22 One minute — I'm switching to tether to my phone 17:38:42 #chair jsmith sumantro nb x3mboy bt0_ bexelbie 17:38:42 Current chairs: bexelbie bt0_ jsmith nb sumantro x3mboy 17:38:56 #topic Ticket 144 17:39:00 #link https://pagure.io/mindshare/issue/144 17:39:22 I'm +1 for this, especially as they're not asking for budget (as I understand it) 17:39:36 Would still love more detail, but I don't see any reason to deny the request 17:39:48 Ok, I have a doubt here 17:40:00 This ticket looks like an informative: I want to do a RP 17:40:06 It's not asking for anything 17:40:10 Maybe just permission 17:40:15 Is that ok? 17:40:34 Sure... 17:40:38 Every RP or event that doesn't need anything budget-wise needs permission? 17:40:47 And we'll still likely send our typical sticker pack 17:41:01 Mmmm 17:41:04 Ok I get it then 17:41:25 So, the idea is to send the stickt pack, even when is not asking for it. That's why the ticket makes sense 17:41:43 Yeah, I think we try to send sticker packs to all release parties, as I understand it. 17:41:43 Well, if that's it, I'm -1 until more clarification on the event 17:42:04 I'm fine with waiting for more details... Bex already asked for more details a couple of days ago 17:42:34 Yeah 17:42:46 Proposal: Defer to our next meeting, waiting for more details 17:43:00 +1 17:43:07 Also it looks like a past event 17:43:12 This ticket is really confusing 17:43:13 #agreed Defer decision on ticket #144 until our next meeting. 17:43:17 We need clarification 17:43:18 x3mboy: Indeed :-) 17:43:29 * nb is on IRC now 17:43:39 nb o/ 17:43:40 Welcome, nb 17:44:00 #topic Ticket 141: Dealing with events that don't get event reports 17:44:03 #link https://pagure.io/mindshare/issue/141 17:44:05 they just want us to approve it so they can get the badge I think 17:44:08 RE: 144 17:44:49 Ohhh!!!! That makes a lot of sense!!! 17:44:56 nb is on fire! 17:45:11 I think that clarify my doubts 17:45:19 Going back to 141 17:45:25 #topic back to Ticket 141 17:45:43 OK, everyone OK with awarding the badge, and calling it good? 17:45:51 * jsmith is still +1 for the record 17:46:21 +1 17:46:31 +1 17:46:47 @bt0dotninja Thoughts? 17:47:06 +1 17:47:09 Too 17:49:46 #agreed Ticket 141: Award the badge and call that good for the event 17:49:54 #topic Ticket 141: Dealing with events that don't get event reports 17:50:06 #link https://pagure.io/mindshare/issue/141 17:50:47 I'm thinking this proposal sounds pretty good 17:51:09 Which one... there are several in the comments of the ticket 17:51:25 Yeah, need some reviews before be published 17:51:40 bex's proposal 17:52:17 That need some patches 17:52:31 Indeed... I don't think it's perfect, but I'd like to keep pushing it forward. 17:54:06 It's ok, maybe we can discuss the details of some points 17:54:20 That's why I have it on the agenda :-) 17:54:30 Personally, I'm fine with the 30-day bullets 17:55:21 Me too 17:55:36 For part 2, I think 3 events in two years is more reasonable... 17:56:20 jsmith, i'm ok with that 17:56:29 With 2(c) too 17:56:35 We need something firm, but not impossible to climb back out of 17:57:51 Any other discussion? 17:57:54 Thoughts? 17:58:00 Someone want to volunteer to summarize? 17:58:14 But by example 17:59:28 One ambassador alone is challenging to be a helper in another event if not have another ambassadors active in their city/country 17:59:43 Agreed... 18:00:27 Maybe we add some language around "... or otherwise show the Mindshare committee that they are actively involved in Fedora SIGs or other online events" 18:00:42 Sounds better 18:00:44 Thoughts? Concerns? Complaints? 18:00:51 +1 18:03:13 nb? @x3mboy? 18:03:22 well 18:03:51 jsmith, but what if I am involved in Fedora SIGs, don't do a event report, and then say "hey, but the policy says am involved in Fedora SIGs, I want funding again" 18:04:15 maybe we need a mandatory timeout, even if someone is involved in other areas of the project" 18:04:29 i.e. you don't do an event report for 120 days, you can't get funding for 1yr 18:04:31 or something 18:04:34 That's fair... 18:04:56 I thought that was 14 months, at least based on the ticket... 18:05:00 oh yeah, i forgot 18:05:10 I think 2(d) will be moved to the 120 days policy 18:05:11 so I guess my concern is already covered 18:06:33 OK, here's what I'm going to propose. 18:07:00 I propose that somebody volunteer to write up the bullets (like done originally in the ticket), but adjusting for the things we've talking about in the comments and in this meeting. 18:07:12 And that we have that updated in the ticket by Tuesday of next week. 18:07:34 Then we vote on it next Wednesday... when we have all the details in one spot in front of us. 18:09:08 I will do it 18:09:14 Action me please 18:09:17 Fantastic, thanks! 18:09:34 #action bt0_ to write up the details on the ticket, so we can vote next week. 18:09:45 #agreed Ticket 141 -- we'll vote next week 18:10:27 #topic Ticket #139 Add contributors to @fedoracommunity Twitter account for Flock 2019 18:10:37 #link https://pagure.io/mindshare/issue/139 18:14:13 I'm +1 to the idea, but not sure about the logistics... 18:16:59 Right 18:18:52 We need look for already active contributors tagn are also active Twitter users 18:19:02 How? 18:19:37 There's also a Fedora Community Folks group in Facebook -- might be a decent place to start. 18:20:39 Ok, we need to define the bases, right? 18:21:22 Yes 18:22:36 Ok, ideas? 18:24:01 Proposal: Keep discussion moving in the ticket, and make a final decision next week. 18:24:52 (We're almost at one hour, and I have to run to another meeting soon) 18:25:06 Ok 18:25:06 Agree 18:27:26 #agreed for ticket 139, we'll keep the discussion moving in the ticket and vote next week 18:27:35 #topic Open Floor 18:27:48 I wanted to cover ticket 145 as well, but I think it needs further discussion in the ticket and we're out of time 18:28:00 Can I please get a committment from folks to keep the discussion moving there as well? 18:28:05 I promise I will too! 18:30:05 from me , yeah 18:30:29 sorry, i got busy 18:38:07 close? 18:38:17 Going once... 18:38:21 ... going twice... 18:38:31 #endmeeting