12:30:15 #startmeeting Mindshare 12:30:15 Meeting started Mon Mar 19 12:30:15 2018 UTC. The chair is bexelbie. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:30:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:30:15 The meeting name has been set to 'mindshare' 12:30:20 #chair bex jflory7 jsmith mleonova nb robyduck x3mboy 12:30:20 Current chairs: bex bexelbie jflory7 jsmith mleonova nb robyduck x3mboy 12:30:22 .hello bex 12:30:23 bexelbie: bex 'Brian (bex) Exelbierd' 12:30:28 .hello jflory7 12:30:29 jwf: jflory7 'Justin W. Flory' 12:30:33 .hello2 12:30:34 jsmith: jsmith 'Jared Smith' 12:30:58 .hello mleonova[m] 12:30:59 mleonova: Sorry, but you don't exist 12:31:04 .hello mleonova 12:31:05 mleonova: mleonova 'Maria Leonova' 12:31:11 cruel zodbot 12:31:12 o/ jwf mleonova 12:31:20 heya, all! 12:31:32 #topic Roll Call 12:31:32 .hello robyduck 12:31:33 robyduck: robyduck 'Robert Mayr' 12:31:36 o/ robyduck 12:31:41 hi! 12:32:11 That leaves jsmith nb x3mboy 12:32:32 I'm here :-) 12:32:38 o/ jsmith 12:33:24 * bexelbie tries that trick again 12:33:28 That leaves nb x3mboy 12:34:45 ok, I'll start down our tickets. This time we will go in numeric order from smallest to largest, as I had intended but failed to do last time :) 12:34:52 #topic README 12:34:54 #link https://pagure.io/mindshare/issue/1 12:35:15 I don't see an update from x3mboy. I propose we convert this to an easyfix, knowing he may still land the update 12:35:28 Can anyone volunteer to be the point of contact for our easy fix tickets? 12:35:52 This would be mostly playing traffic director - you aren't expected to know how to do them all .. just answer email and connect people 12:36:04 For this ticket, I can do that 12:36:19 it's all or none, unfortuantely, in our current easyfix system 12:36:23 but right now this is our only easyfix 12:36:32 Oh! For the easyfix web page? 12:36:35 yeah 12:36:38 Why not list the mailing list instead of an individual? 12:36:52 becasue the idea is that hte person is confidently able to beleive someone will respond 12:37:00 jwf: i think you are eligible also for all tickets? :) 12:37:06 mail to an ML is simultaneiously everyone's responsibility and no one responsibility 12:37:23 so this person ideally directly helps, but if not connects them to the right person to help them 12:37:35 bexelbie: True. I'm less keen on putting an individual's name in an obscure place we will have to remember to keep up to date (e.g. when I step back from May to August) 12:37:43 .hello x3mboy 12:37:44 x3mlinux: x3mboy 'Eduard Lucena' 12:37:50 If nobody else volunteers, I'll do it 12:38:02 jwf, so perhaps you are not a good candidate or we need to just put an action on oru calendar to fix it in May 12:38:08 o/ x3mlinux 12:38:15 sorry o/ x3mboy 12:38:18 * jwf waves to x3mlinux 12:38:24 o/ team 12:38:27 nb is running late and will join us in about 20 min 12:38:34 .thank jwb 12:38:34 x3mlinux thinks jwb is awesome and is happy they are helping! (Please don't forget to jwb++ also) 12:38:35 so jwf do you want to do it until May? 12:38:48 Sure, you can put me down for now 12:38:55 I'm walking to my office 12:38:55 ok, anyone opposed 12:39:09 * jsmith isn't opposed 12:39:18 * robyduck is fine too 12:39:18 * x3mlinux neither 12:39:19 #proposed Set ticket #1 to easy fix knowing x3mboy may still do it. jwf is the point of contact until may 12:39:36 is x3mlinux == x3mboy ? 12:39:42 Yes :-) 12:39:42 Yes 12:39:50 +1 12:39:52 Sorry, I'm on mobile 12:39:59 #agreed Set ticket #1 to easy fix knowing x3mboy may still do it. jwf is the point of contact until may 12:40:13 #action bex to set up the easy fix tag and website 12:40:33 #info Ticket 3 is blocked - https://pagure.io/mindshare/issue/3 12:40:53 #info ticket 5 is the same https://pagure.io/mindshare/issue/5 12:41:07 #topic Research by CommOps 12:41:10 #link https://pagure.io/mindshare/issue/6 12:41:19 jwf, did we get agreement from Commops to do this work? 12:42:02 Yes, we did 12:42:22 Yes. I wasn't able to run our meeting last week because of a work meeting, but hope to bring it up today. I'm not sure if the info is helpful if it's an extra week or two from today for deliverable 12:42:30 cool - jwf or x3mlinux if there is a ticket in commops can you all update our ticket with a link? 12:42:43 Yes, I will do that now. 12:42:44 jwf, it can still inform the resulting discussion 12:42:47 jwf, thank you 12:42:54 other comments on this ticket? 12:43:06 otherwise I crack the whip to the next ticket :D 12:43:09 Not from me 12:43:24 yeah, next 12:43:26 #topic FAD Outbound report 12:43:29 #link https://pagure.io/mindshare/issue/7 12:43:41 * jsmith still needs to give feedback on that, hopefully today 12:43:42 x3mlinux, has posted a fantastic draft. I know that several people have edited it 12:43:55 https://etherpad.gnome.org/p/Mindshare_Report 12:43:59 I see a few open questions, including a major change proposed by me (that affect jsmith) 12:44:54 #proposed let's try to wrap up edits today and post on Wednesday or Thursday? 12:45:03 WORKSFORME 12:45:23 (and for the record, I agree with bexelbie's statement regarding the Ambassador portion) 12:45:33 I won't be able to review until tomorrow, Wednesday works for me 12:45:39 Wednesday or Thursday? :P 12:46:00 * robyduck agrees, but not later than thursday, let's get out to the community what we did. 12:46:16 I am not hearing opposition 12:46:20 I can probably take a closer look on Wednesday too 12:46:31 For publishing Wednesdays, today and tomorrow for reviews and editing 12:46:51 +1 12:46:57 +1 12:47:02 +1 12:47:20 +1 12:47:49 cool 12:48:11 #topic ambassador conversation kickstart 12:48:13 #link https://pagure.io/mindshare/issue/8 12:48:28 jsmith, anything we should know? everthing still looking good for this friday? 12:48:48 bexelbie: I'm a little behind on the draft, but it's my second priority today :-) 12:49:07 cool - please let us know early if things get behind so we can help or make adjustments 12:49:34 #topic open design tickets 12:49:35 #link https://pagure.io/mindshare/issue/9 12:49:40 mleonova, can you update us? 12:50:16 sure! I'm working on the badge and have posted first drafts for the logo 12:50:42 https://pagure.io/fedora-badges/issue/603 - here I would make them different 12:50:51 coo 12:50:55 cool too 12:51:02 https://pagure.io/design/issue/580 this I just started, suggestions welcome 12:51:08 any questions? comments on the specifics requested in the tickets 12:51:59 ok 12:52:02 #topic open floor 12:52:05 assuming the logo will be similarly used https://pagure.io/designassets/blob/master/f/Banners/Wiki_Banners/CommOps_wiki_banner.png 12:52:12 on the wiki 12:52:24 but also can be separate 12:52:25 Let me check the last updates 12:52:34 #undo 12:52:34 Removing item from minutes: 12:52:47 mleonova, or on the docs site? 12:52:56 mleonova: For what it's worth, from your sketches, I really liked the idea of the logo surrounded by the trio of thought clouds 12:53:08 jwf, it's my favorite, too! 12:53:17 This one: https://screenshots.firefox.com/ywZNX855fwDL5SqY/pagure.io 12:53:23 #info Feedback on the design tickets is encouraged in the tickets 12:53:37 bexelbie, exactly :) 12:53:41 and that was not directed at jwf :) 12:53:46 that was for our minutes 12:53:47 LOL 12:53:49 ^_^ 12:53:52 :-) 12:54:03 ok, so any remaining comments? 12:54:12 Not from me 12:54:23 Not from me on the design tickets 12:54:25 .thank mleonova 12:54:25 jwf thinks mleonova is awesome and is happy they are helping! (Please don't forget to mleonova++ also) 12:54:27 * jsmith has nothing. 12:54:30 #topic Open Floor 12:54:46 I have a potential topic: Feedback from reps from teams about how their teams handled our suggestions 12:54:48 * x3mboy dances on the Open Floor!!!! 12:54:50 other potential topics? 12:55:10 bexelbie: I've been blocking on that because I want to share the event report as an introduction to the conversations 12:55:22 Hard to relay everything we did at the FAD over mailing list / IRC 12:55:25 fair point :) 12:55:34 did anyone else share yet? otherwise I'll hold that topic 12:55:34 Marketing is pretty ok about the Mindshare information 12:55:37 ;-) 12:56:05 I communicated concerns to the Design team 12:56:16 we're working on some issues already 12:56:43 * robyduck has one question 12:56:43 cool - any specific feedback we should know about mleonova ? 12:56:49 ! 12:56:52 there's an open ticket to clean up deprecated stuff from wikis, and another one to create a list of approved swag 12:56:53 nope, not for mleonova 12:57:08 jwf is your comment about this topic? 12:57:13 No, different topic 12:57:17 cool 12:57:19 thank you mleonova 12:57:23 robyduck, you're up 12:57:27 I know we are not set foto hand release stuff, but are outreach teams ready for Beta next week or do they need anything? Release Notes? 12:57:34 foto?? 12:57:42 s/foto/to 12:58:04 regarding Release Notes - tickets are open and being worked in docs 12:58:21 beta doesn't really require them, iirc, but we will be publishing them as they finish regardless 12:58:22 CommOps is not waiting / blocking on anything for the release 12:58:28 Or pre-release 12:58:31 (just because websites wtill need to start working on it) 12:58:55 Although, since it came up, I can mention an interesting detail about release schedules 12:59:08 Marketing is working on their normal tasks, I need to ping mattdm about the Release announcenments, but normally the Beta announcenment is up to me (or mailga) so, I need to check on that today 12:59:28 jwf, ? 12:59:53 I forgot to do it on time for Fedora 28, but I always publish this post on the Community Blog because it's our most-read posts every year. Thousands and thousands of views: 12:59:55 #link https://communityblog.fedoraproject.org/?p=5425&preview=1&_ppp=aa1df99942 13:00:06 This one is scheduled for Friday, only because a lot of other content is also landing this week 13:00:26 Not sure if it would make sense to integrate this into some calendaring or workflow 13:00:40 I remember we talked about it briefly at the FAD but I forgot where we with it 13:00:50 * where we went with it 13:00:55 jwf this sounds like somethign that we should get jkurik or his successor to add to the release schedule 13:00:58 as it is release related 13:01:05 not independent 13:01:09 * jwf nods 13:01:23 unrelated/related, I am hoping to start a non-release related dates calendar for things like GSoC, etc. 13:02:01 ! 13:02:07 x3mboy, go 13:02:16 bexelbie: We do have one, although it fell out of use: https://apps.fedoraproject.org/calendar/onboarding/ 13:02:37 jwf, I'll review that 13:02:38 I have an issue related with budget and ambassadors, that I like to bring here 13:03:20 ok, hold that for a moment 13:03:27 anything else on this topic from robyduck ? 13:03:43 no, I think it's all fine, thanks 13:03:50 jwf you were next (then x3mboy ) 13:04:09 #info robyduck checked on beta/pre-release tasks/blockers 13:04:09 If anyone has spare cycles, a review of this PR would be awesome: 13:04:10 https://pagure.io/fedora-commops/pull-request/146 13:04:15 https://bryn.justinwflory.com/commops.html 13:04:29 Thanks bexelbie for taking a look, hoping to dig deeper in later to your feedback 13:04:40 If anyone else has feedback, it's also appreciated and welcome 13:04:42 13:05:31 #info jwf requested reviews of https://pagure.io/fedora-commops/pull-request/146 13:05:31 I hope everyone will put your comments in the PR 13:05:31 x3mboy, you're up 13:06:07 Last year, FLISoL had a lot of budget spent in flights. That's not a problem itself, but it generates a lot of discussion and anger, because it's supossed that there is a per country event. I know that is could/should be solved by the region, but is there a recommendation that we could give them? 13:06:44 The main issue was that people having FLISoL on their countries, got flights to other countries to attend the same event 13:07:01 I am not trying to speak for everyone, but if the flights were international, I'd like to see justification. If they were domestic it could make sense 13:07:19 International flights, I meant 13:07:51 It is not indefensible. If FLISOL represents an opportunity to jumpstart things in a new country. However, we need to know the goals and follow up plans to understand it 13:08:22 I feel the same. I am curious to know the reasoning / justification for an international flight request. 13:08:31 * robyduck agrees with bexelbie 13:08:32 Also, right now there isn't a formal budget passed, so there shouldn't be big allocations happening without council approval anyway 13:08:53 Mmmm ok... 13:09:44 I think the base rule should be: ambassadors -> nearest Flisol event, unless there is a concrete reason and plan to bring a specific person to another country 13:09:47 especially for spending htat exceeds 25% of the original full year budget 13:09:56 not, in the case of LATAM, the budget plus the swag allocation 13:10:07 Well, I have no problems with people flying to attend events, but it really generates a lot of anger. I hope this year people think better about their choices regarding FLISoL 13:10:32 It sounds like there are two problems here 13:10:36 1) Justifications not being clear 13:10:53 2) People getting angry about things. Could their anger also be inappropriate? 13:11:46 My best guess is "yes" and "yes"... 13:11:47 For 1, yes, ther should be beeter justifications, normally tickets about FLISoL get approval without too much hesitation 13:12:34 2) Also yes, people last year was really disconforming with a lot of stuff. I think we addressed a lot of this disconfort with the Latam FAD 13:12:50 I was just trying to get advice before the situation happens 13:13:23 I hope that our contributors in LATAM will consider how quickly approving any FLISOL request without jsutification reflects on whether they should be allowed to run a budget 13:13:59 and some of that may be helped by the ambassadors conversation we are going to be having here 13:14:08 with all of our ambassadors 13:14:22 Ok, good. That's enough for me 13:14:24 eof 13:14:27 other comments on the FLISOL question? 13:14:40 None from me 13:14:42 #info x3mboy asked about whether we had guidance for FLISOL international airfare tickets in LATAM 13:14:45 nope 13:14:49 other open topics? 13:15:27 #proposed close the meeting? 13:15:54 Just one: https://i.imgur.com/GfCTiTS.jpg 13:16:03 :P 13:16:06 +1 to close out 13:16:08 +1 13:16:10 +1 13:16:11 bexelbie: Thanks for chairing 13:16:15 .thank bexelbie 13:16:15 jwf thinks bexelbie is awesome and is happy they are helping! (Please don't forget to bexelbie++ also) 13:16:18 +1 13:16:26 Thank you all! 13:16:29 #endmeeting