13:00:12 #startmeeting Fedora Diversity (2018-04-06) 13:00:12 Meeting started Fri Apr 6 13:00:12 2018 UTC. The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:00:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:00:12 The meeting name has been set to 'fedora_diversity_(2018-04-06)' 13:00:12 #meetingname diversity 13:00:12 The meeting name has been set to 'diversity' 13:00:13 meetbot.meeting.start -- jflory7 started meeting "Fedora Diversity (2018-04-06)" in #fedora-diversity 13:00:25 #topic Agenda 13:00:33 #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-diversity-meeting-next 13:00:33 #info (1) Roll call / Q&A 13:00:33 #info (2) Announcements 13:00:33 #info (3) Action items from last meeting 13:00:33 #info (4) Tickets 13:00:34 #info (5) Open floor 13:00:41 #topic Roll call / Q&A 13:00:48 If this is your first time at a Diversity meeting, please introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask. 13:00:51 .hello jflory7 13:00:52 jwf: jflory7 'Justin W. Flory' 13:00:59 isn't this supposed to be in fedora-meeting? 13:01:15 .hello bex 13:01:19 bexelbie: bex 'Brian (bex) Exelbierd' 13:01:23 .hello amsharma 13:01:24 Amita: amsharma 'Amita Sharma' 13:01:29 bexelbie: Read scrollback a bit, some of us were tied up with other commitments and wanted to use the Telegram bridge to participate for today. 13:01:32 (partially here) 13:01:34 ahh, the fedocal entry is incorrect 13:01:39 ahh, ok 13:01:42 Today was an exception than the norm 13:01:47 we should announce that in #fedora-meeting 13:01:52 * jwf waves to both bexelbie and Amita by the way :-) 13:01:55 Okay, I can drop a note. 13:02:06 * bexelbie did it 13:02:12 bexelbie++ 13:02:15 #chair Amita bexelbie 13:02:15 Current chairs: Amita bexelbie jwf 13:02:27 We can wait a couple more minutes before getting started. 13:02:32 .members diversity-team 13:02:33 jwf: Members of diversity-team: a2batic @amsharma @bee2502 chhavi cprofitt @jflory7 @jonatoni +marinaz +meskarune paulmellors rhea @tatica x3mboy 13:02:47 ^ meeting time, if you all are around :-) 13:03:09 reCursedd: Now is a good time to introduce yourself, if you would like. 13:03:31 Hello everyone, I am new here and I want to be a part of diversity as the idea is very intriguing to me. I like to code for my living and I like to read, sing and play table tennis. 13:04:07 nice 13:04:11 welcome reCursedd 13:04:20 I'm here 13:04:23 This is my first time as a participant of an open source community and it feels great to be here. :) thanks all of you 13:04:25 hi x3mboy 13:04:34 Hi Amita 13:05:03 @reCursedd: Awesome, welcome! What name do you prefer, Dyuti? 13:05:09 * jwf waves to x3mboy 13:05:11 #chair x3mboy 13:05:11 Current chairs: Amita bexelbie jwf x3mboy 13:05:29 .hello2 13:05:30 x3mboy: x3mboy 'Eduard Lucena' 13:05:33 jwf, o/ 13:05:38 yeah :) 13:05:48 @reCursedd: Okay, great! 13:05:56 Bien 13:05:57 We can go ahead and get started with the agenda. Any one else who arrives can chime in when they arrive. 13:06:09 #topic Announcements 13:06:12 Ooops, wrong window 13:06:27 Agh, my desktop just froze AGAIN 13:06:50 Can someone look at the agenda and post the two announcements in the notes while I reboot again? 13:07:56 #info === "Mindshare Monthly Report – FAD and First Actions" === 13:07:57 #link https://communityblog.fedoraproject.org/mindshare-monthly-report-fad-first-actions/ 13:07:57 #info The Mindshare Committee is running a monthly column on the Community Blog. See the results and outcome from the FAD and what is ahead for Fedora outreach teams. 13:07:57 #info === "Top Badgers of 2017: Alessio Ciregia" === 13:07:57 #link https://communityblog.fedoraproject.org/top-badgers-2017-alessio-ciregia/ 13:08:10 * bexelbie will brb have to step away for 5 min 13:10:27 bexelbie: Thanks, I am back now 13:10:29 Those were the only two announcements I had in advance. 13:10:33 Anyone else have anything to share before moving to action items? 13:10:46 ! 13:10:57 x3mboy: Go for it! 13:11:00 === Podcast Episode 004 is out === 13:11:19 #link https://fedoramagazine.org/fedora-podcast-004-fedora-documentation/ 13:11:21 eof 13:11:50 x3mboy++ Awesome work, as always :-) 13:12:04 .thank x3mboy 13:12:04 jwf thinks x3mboy is awesome and is happy they are helping! (Please don't forget to x3mboy++ also) 13:12:05 I'm pretty exited about next episode 13:12:12 x3mboy: Who is next? 13:12:17 Paul 13:12:23 Magazine 13:12:28 Ahh, that should be a good one :-) 13:12:36 And next should be diversity, but we can discuss it in the ticket 13:12:40 ;) 13:12:42 * jwf nods 13:12:44 * bexelbie is back 13:12:46 Any other announcements? 13:12:52 Going once… 13:13:01 Going twice… 13:13:06 And thrice! 13:13:10 #topic Action items from last meeting 13:13:14 #link https://meetbot.fedoraproject.org/teams/diversity/diversity.2018-03-23-13.07.html 13:13:19 #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action if needed. If no status, we'll try to get a quick update and move forward. 13:13:28 #info === [COMPLETE] "jwf Work with chhavi_ on getting video source to upload to YouTube" === 13:13:29 #link https://youtu.be/4gwRPetwUYs 13:13:29 #info Video is now uploaded to the Fedora YouTube channel; will do a follow-up with a Fedora Magazine soon 13:13:33 chhavi_++ 13:13:41 #info === [COMPLETE] "jwf Prepare draft of primary / secondary goals, impact from larger pad of team goals, prepare in format for a potential FAD proposal" === 13:13:41 #link https://etherpad.persephone.cloud/p/diversity-fad-2018 13:13:41 #info Bee worked on a draft and needs review; will discuss during ticket section of meeting 13:13:51 #info === [COMPLETE] "diversity-team Cast vote for sticker request in #59: https://pagure.io/fedora-diversity/issue/59" === 13:13:51 #link https://pagure.io/fedora-diversity/issue/59#comment-503318 13:13:51 #info Stickers produced, ticket closed. 13:14:04 Those were the only three action items I could dig out from the last meeting. 13:14:15 So we can keep on ahead. :-) 13:14:20 #topic Tickets 13:14:24 #link https://pagure.io/fedora-diversity/issues?status=Open&tags=meeting 13:14:46 There are five tickets on the agenda, which is a lot – let's see what we can get through! 13:14:52 #info === Ticket #24: "Wiki gardening" === 13:14:52 #link https://pagure.io/fedora-diversity/issue/24 13:14:56 Needs a look through the updated pages 13:15:06 Let me see if I can get a link to the updated changes 13:16:09 #link https://fedoraproject.org/w/index.php?title=Diversity&type=revision&diff=512240&oldid=505632 13:17:23 I think bee2502 mostly wanted us to review the changes she made, since we discussed them in depth before 13:17:35 I can't find anything more recent than this link with revisions. 13:17:54 I think this is done, so we can close it as complete. 13:18:13 I put this one up front first because I thought it would be a quick one. 13:19:06 Checking link 13:19:46 Ok 13:19:50 Good to close 13:19:52 +1 13:19:53 @amisha3: Let us know if you have any comments, I just closed the ticket since it looks done. 13:19:55 #info === Ticket #48: "Diversity Team Goals - From Jan, 2018 to Jan, 2019" === 13:19:56 #link https://pagure.io/fedora-diversity/issue/48#comment-503687 13:19:56 #link https://etherpad.persephone.cloud/p/diversity-fad-2018 13:20:06 This is probably the biggest item on the agenda today 13:20:42 bee2502 wrote up team goals to focus on for the remainder of 2018 and put together a timeline of the work for each goal 13:21:27 There was some chatter on the mailing list, but I don't think it was discussed in depth: 13:21:29 #link https://lists.fedoraproject.org/archives/list/diversity@lists.fedoraproject.org/thread/QBPWXDOYXNT3NQQD2OBAY2PL3DIO653Q/ 13:22:01 What do you all think of the write-up, did you get a chance to review before the meeting? 13:22:17 I read it 13:22:26 But not completely 13:22:37 I felt that the goals were scoped well, but I thought it was a lot of work for this team to accomplish all together. 13:22:38 I liked the way it is written 13:22:45 And the details 13:22:54 O agree 13:22:59 I think we could keep the timelines @bee2502 put together, but I think we have enough bandwidth to only focus on one thing fully at a time 13:23:09 But we can spread them for more than a year 13:23:25 I thought we could focus in on Fedora Women Day now leading up to Flock because that is the most urgent task and will be immediately after Flock 13:23:47 We should definitely want to come back to the rest which we can't complete in this year 13:23:54 @amisha3: Right, I think it makes more sense to stagger them a little more. 13:24:02 Nice point 13:24:06 I agree 13:24:21 Little steps are always better 13:24:25 @amisha3: I think some of these things might be best to wait for 2019 before we invest the time and effort. I think FWD will take up most of our time and we also have a month of following up with event reports too. 13:24:25 Than a huge one 13:24:42 I to totally agree Justin 13:24:44 Anyone else have any opinions or had a chance to read through too? 13:24:45 #chair 13:24:45 Current chairs: Amita bexelbie jwf x3mboy 13:24:51 We can revisit 13:24:59 * bexelbie added a bunch of notes and now needs to read the replies 13:25:28 Oh! I didn't know there were replies. 13:25:35 I need to read it. It's on my list for today's readings 13:25:43 I read it and got some pointers on where we are headed. 13:26:53 I didn't know there were new comments in the Etherpad. I am going to take a quick scroll-through now for a moment. 13:27:02 x3mboy: Understandable – your feedback is always welcome! 13:27:13 However, I am very in favor of focusing on one thing to ensure we do it great and only adding more if we know for sure we have enough people. contributor attention is our most constrained resource :D 13:27:27 Yipp 13:27:33 Hi! 13:27:36 @reCursedd: I'm glad you were able to read through it and it all made sense! I think that is a good sign. :-) 13:27:46 I got stuck in a work meeting but I am here now 13:27:52 * jwf waves to @bee2502 13:27:57 bexelbie: +1. 13:27:59 So glad meeting is happening in channel 13:28:00 @bee2592 o/ 13:28:12 Same here 13:28:32 I think we can do something about it that we can join meetings via telegram 13:28:57 Just reading through logs now.. 13:29:19 @bee2502 / @amisha3: If this is helpful, we can make this a permanent change too. Can discuss that at open floor too 13:29:22 yes. though I need to check certain things. 13:29:34 Sure 13:29:59 My overall take on the goals is that I think we should follow through with the Fedora Women Day (FWD) timeline @bee2502 drafted, but I think we should stagger some of the other work. 13:30:17 ,+1 13:30:21 I will not be active in Fedora from May until August, so I cannot contribute much time to helping during the summer months 13:30:34 Ok 13:31:50 How much bandwidth do we need just to put emergency kits and flyers at FLOCK? 13:32:18 bexelbie: Not sure if you saw the comments yesterday in channel about some of the Flock questions 13:32:19 Or do we assume that the organizers/hotel will already have them. 13:32:23 It's not about just that 13:32:38 I think 13:32:45 It's about making a norm 13:32:52 For all the future events 13:33:17 jwf I did not 13:33:23 bexelbie: Quick recap: https://paste.fedoraproject.org/paste/bLJEA2~-a~~dJxzsQClz2A 13:33:31 @amisha3 I think we can start small. It's good to show a good example to community about why it is useful.. before we go around publishing a document 13:33:50 bee2502, that needs to be defined. As an event organizer am I required to audit the emergency kit? 13:33:55 provided by a third party I mean 13:34:36 Hmm I would say no 13:34:57 @reCursedd: re, if there is anything you are curious about or want clarification, we are happy to do that too. 13:34:58 re: Flock - I am happy to work from a draft document to try and test it while trying to implement it 13:35:42 and this goes to the point I just added about quiet rooms. The room contract is set. Should we be forced to negotiate the extra costs (if it is even possible) to add a quiet room? Are we forced to cancel and start over because we don't have one? What if there is no extra space in the facility? 13:36:05 actually I didn't get much time before the meeting. I will let you know about the questions in another 8-10 hours. 13:36:14 bee2502, then we need to cleanly define that. Are we saying that if a facility doesn't have an emergency kit, say for liability reasons, are we requiring that the event owner take on that liability? 13:36:22 I think we can definitely do a draft document to test at flock with our bandwidth. I can take responsibility for it. 13:36:32 bee2502, this isn't blokcing, but we need to find some logical edges 13:36:58 @reCursedd: That's fine too. :-) 13:37:29 Time check, we have about 25 minutes left 13:37:31 thanks.. :) 13:37:37 I understand what logical edges ..the questions you have just asked bex 13:37:58 To drive back to the ticket topic about the goals, what do we think we can realistically accomplish then, if we want to keep some event organizing guidelines in scope before Flock? 13:38:00 @amisha3 can you rephrase that? 13:38:05 So may be bex can put all those questions in the doc 13:38:20 bexelbie I understand. Your points are valid and we need to discuss this in depth. I also feel that we shouldn't miss flock as an opportunity because I don't think it would be right to launch a common guidelines without actually testing it. 13:38:37 I meant ..do you mean the questions you just asked are the logical edges you mentioned 13:38:48 @amisha3 I have, afaik 13:38:55 Ok 13:38:59 @bee2502 huge +1 13:39:56 How should we scope these goals in the context leading up to Flock? 13:40:14 I think at Flock, we can aim to have a similar session to last year and reevaluate where we are then for the next few months 13:40:21 @amisha3 yes 13:40:32 So for now, I think we should try to effectively scope what we want to accomplish leading up to Flock / FWD 2018 13:41:00 Right 13:41:15 Kind of 6 months plan 13:41:44 jwf I think we can work on a draft doc this month and bex can add his perspective as a former flock organizer and current FCAke 13:42:26 @bee2502: Is what you have in the Etherpad not the draft? 13:42:29 I can help in that 13:42:50 jwf I was talking about the event inclusion guidelines 13:42:53 Not overall goals 13:43:00 I think she means to answer questions 13:43:09 Ahh, got it 13:43:09 @amisha3 yes 13:43:31 I think the FWD timeline is something we can stick too, although I also agree with bexelbie's comment at the top: 13:43:31 https://screenshots.firefox.com/mHAajjsCGKt6gjLF/etherpad.persephone.cloud 13:44:04 @bee2502: Do you want to take an action item to re-scope the event guidelines by the next meeting? 13:44:12 Also, since flock is soon.. I guess it can be our priority for this month. I assume it will take less time after May 13:44:59 Ok 13:45:01 jwf yes, I will create a draft for event guidelines and bex can tear it apart. 13:45:15 @bee2502 I'll only provide gentle feedback and guidance :D 13:45:16 Also @amisha3 and I can do this together? 13:45:50 @bee2502: I can action both of you for the event guidelines if that works for @amisha3? 13:46:05 I will also try to recap some of the discussion for the minutes. Correct me if anything seems incorrect. 13:46:45 Bex I would prefer if you tear it apart. The draft can go over multiple iterations but once it is out to community .. 13:46:56 #agreed Fedora Women Day 2018 timeline seems realistic for what Diversity Team can accomplish leading up to Flock 2018; will adopt bee2502's timeline for planning and make modifications if needed as we go 13:47:03 @bee2502 I was kidding. It will receive the fullest attention I can give it 13:47:51 #agreed Event guidelines need some re-consideration for logical considerations if we want to run a test-case at Flock 2018; will work on a draft to share for review with FCAIC (bexelbie) leading into May 13:48:07 Yes u can jwf 13:48:14 #agreed Will revisit other goals and plan for following months at a planning session at Flock 2018 13:48:21 #nick bee2502 13:48:23 #nick Amita 13:48:46 @bee2502 @amisha3: When do we want to set the first deadline on this action item? 13:48:56 Next meeting 13:49:08 Fine 13:49:20 Okay – we didn't discuss yet if we want to switch to weekly meetings or continue with every other week for meetings. 13:49:27 When is the next meeting? 13:49:27 April 13 or April 20? 13:49:32 Then 2 weeks 13:49:39 * jwf nods 13:49:42 oh okay! 13:50:15 #action bee2502 Amita: Create a first draft of event guidelines for testing at Flock 2018; share with bexelbie for feedback (DUE: 2018-04-20 meeting) 13:50:22 @reCursedd usually the meeting is after 2 weeks 13:50:39 yeah just got that! 13:50:41 @bee2502: Do we also want to discuss really quick some of the outreach for FWD this month? 13:51:00 I see you filed the ticket already 👍 13:51:03 Does anyone have a hard stop after one hour? 13:51:07 I do 13:51:27 Me too 13:51:41 I also wanted to save the last five minutes for checking in on meeting frequency and location 13:52:05 We can coordinate more for FWD on the mailing list / in channel after the meeting? 13:52:05 Till next meeting, I think we should concentrate on event inclusion draft 13:52:13 And podcast questionare 13:52:16 ! 13:52:26 Yes, I need to talk about the Podcast 13:52:29 Please 13:52:30 @bee2502: Okay. Does the timeline for FWD need changes? 13:52:41 x3mboy: Okay, we can switch topics really fast for end of time, thanks for the reminder 13:52:48 We can jump back around to this after meeting 13:52:55 #info === Ticket #64: "Diversity Team Podcast session" === 13:52:55 #link https://pagure.io/fedora-diversity/issue/64 13:52:56 Needs ideas, suggestions for podcast 13:52:58 x3mboy: Go for it! 13:53:21 jwf not really, I don't think those are hard deadlines for those tasks and it still seems manageable 13:53:47 @bee2502: Sounds good to me 👍 13:54:17 Independent of the topics, If you really want to be the next episode (April 27th) we need to do the interview at most the week before that 13:54:26 To have one week for editing 13:54:36 That's the timing I'm managing with the podcast 13:54:55 I commented that on the ticket 13:54:57 Oh, I didn't realize this was so soon 13:55:09 I see. How about the episode after? 13:55:22 I think the questionare will need time for feedback 13:55:45 x3mboy do u have a slot in may for us? 13:56:00 I have May free 13:56:01 Yeah, +1 if May is not impossible to do. :P 13:56:09 End of April will challenging 13:56:41 x3mboy: We can work on getting that drafted this month for you then, and then work with you on a date at the next meeting in two weeks? 13:56:44 Does that sound okay? 13:56:48 May 11th and 25th should be the dates of publishing 13:56:54 Perfect 13:57:02 We can target may 11 13:57:04 So, the same, recording the week before the publishing date 13:57:17 At the most, if we can do it before, then better 13:58:04 If we have meetings every week, earlier will definitely be manageable 13:58:05 #agreed Diversity Team will work on questions / focus for podcast on Fedora Diversity in April; aiming for publish date of 11 May, which means a preferred due date of 30 April 13:58:25 ^^ all, does this sound alright? 13:58:28 jwf draft is due next week :) 13:58:32 I want to cover our meetings before I have to jump out 13:58:37 And feedback and revision one week 13:58:40 +1 13:58:46 @bee2502: Oh! Are you working on that too? 13:58:46 And then filming? 13:58:49 I can action you for it 13:58:59 I started it 🙈 13:59:11 Okay, we can work with you on the draft 13:59:28 I will send an email with etherpad link :) 13:59:45 #action bee2502 Work on podcast questionnaire / interview draft for x3mboy podcast by next week, 13 April 2018; work with Diversity Team on collecting feedback 13:59:52 Going to switch to open floor really quick! 13:59:54 #topic Open floor 13:59:58 I wanted to bring up two topics: 14:00:12 1) Do we want to permanently host our meetings in #fedora-diversity from now on for the Telegram bridge? 14:00:13 And: 14:00:25 2) How often should we meet? Once a week or once every other week? 14:00:43 1) Yes for me 14:00:44 A caveat about #2, I didn't realize but the new CommOps meeting time intersects with our Friday meeting time, so I will be split attention 14:00:50 2) Bi-weekly for me 14:00:51 #1 is a +1 for me too 14:01:05 #2, I am flexible for either, but I think our workflow is largely meeting / ticket-driven 14:01:12 So I could see weekly working well for us 14:01:34