13:09:57 #startmeeting Fedora Diversity (2018-06-22) 13:09:57 Meeting started Fri Jun 22 13:09:57 2018 UTC. 13:09:57 This meeting is logged and archived in a public location. 13:09:57 The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:09:57 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:09:57 The meeting name has been set to 'fedora_diversity_(2018-06-22)' 13:09:58 meetbot.meeting.start -- jflory7 started meeting "Fedora Diversity (2018-06-22)" in #fedora-diversity 13:10:03 #meetingname diversity 13:10:03 The meeting name has been set to 'diversity' 13:10:13 #topic Agenda 13:10:14 meetbot.meeting.topic.update -- The topic of jflory7's "Fedora Diversity (2018-06-22)" meeting changed to "Agenda" in #fedora-diversity 13:10:21 #info (1) Roll call / Q&A 13:10:22 meetbot.meeting.item.info -- jflory7 raised a point of information in the "Fedora Diversity (2018-06-22)" meeting in #fedora-diversity: "(1) Roll call / Q&A" 13:10:23 #info (2) Announcements 13:10:23 meetbot.meeting.item.info -- jflory7 raised a point of information in the "Fedora Diversity (2018-06-22)" meeting in #fedora-diversity: "(2) Announcements" 13:10:27 #info (3) Action items from last meeting 13:10:27 meetbot.meeting.item.info -- jflory7 raised a point of information in the "Fedora Diversity (2018-06-22)" meeting in #fedora-diversity: "(3) Action items from last meeting" 13:10:29 #info (4) Tickets 13:10:29 meetbot.meeting.item.info -- jflory7 raised a point of information in the "Fedora Diversity (2018-06-22)" meeting in #fedora-diversity: "(4) Tickets" 13:10:31 #info (5) Open floor 13:10:31 meetbot.meeting.item.info -- jflory7 raised a point of information in the "Fedora Diversity (2018-06-22)" meeting in #fedora-diversity: "(5) Open floor" 13:10:34 .hello amsharma 13:10:35 Amita: amsharma 'Amita Sharma' 13:10:37 I'll quiet fm-diversity… 13:10:53 #topic Roll call / Q&A 13:11:01 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:11:06 .hello jflory7 13:11:07 jwf: jflory7 'Justin W. Flory' 13:11:08 #chair Amita 13:11:08 Current chairs: Amita jwf 13:11:12 o/ 13:11:15 Hello.. 13:11:28 .hello x3mboy 13:11:40 * jwf waves to Amita, recursedd, and x3mboy 13:11:48 #chair recursedd x3mboy 13:11:48 Current chairs: Amita jwf recursedd x3mboy 13:11:57 Sorry, I will be by telegram 13:12:38 hello everyone 13:12:49 Hey :) I'm here but working at the same time, so if you need my feedback please ping me 13:13:29 :+1: 13:13:30 .hello bee2502 13:13:31 bee2502_: bee2502 'Bhagyashree Padalkar' 13:13:38 #chair jonatoni bee2502 bee2502_ 13:13:38 Current chairs: Amita bee2502 bee2502_ jonatoni jwf recursedd x3mboy 13:13:47 o/ everyone 13:14:41 I think the only thing on the agenda today is for FWD 13:15:04 I think we have enough of us to start 13:16:03 #topic Announcements 13:16:25 Anyone have anything to share? 13:17:07 nope 13:17:18 #info We recorded Fedora Diversity and Inclusion team podcast in early June. The podcast will be now edited and posted by x3mboy soon. 13:17:34 #info Fedora Elections ended for Council, Mindshare, and FESCo last week 13:17:36 #link https://admin.fedoraproject.org/voting/archives 13:17:55 x3mboy++ Can't wait to hear it! 13:18:45 Any other announcements? 13:18:53 no 13:18:56 Going once… 13:19:05 Going twice… 13:19:15 And thrice! 13:19:27 #topic Action items from last meeting 13:19:51 #link https://meetbot.fedoraproject.org/teams/diversity/diversity.2018-06-15-13.02.html 13:20:06 #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:20:19 One second while I organize them 13:21:07 #info === [IN PROGRESS] "Amita jonatoni jflory7 other members .. please submit a contributor story saying thanks or showing appreciation towards Fedora community members soon" === 13:21:51 #info On-going. If you haven't submitted a contributor story yet, please do that soon so we have more examples to use and promote for others from the community to write their own stories too. 13:22:18 #info === "bee2502 open a new ticket in Mindshare pagure to discuss logistics on Fedora Women stickers allocation to Mindshare" === 13:22:57 bee2502_: Does this need a re-action or do you want to open this up for someone else to file? 13:23:25 jwf I will do it before next meeting 13:23:33 Okay, I'll re-action. 13:23:54 #action bee2502 Open a new ticket in Mindshare Pagure to discuss logistics on Fedora Women stickers allocation to Mindshare 13:24:11 #info === "team Publish a Community Blog post introducing Fedora Event Guidelines rough draft and asking for feedback from community through offline channels and at FLOCK.." === 13:24:36 I'm not yet done with writing a pitch for this.. 13:24:40 I don't think this is done, but it's probably something we want to publish closer to Flock? 13:24:47 I'll complete it during the weekend.. 13:24:51 @recursedd: Ah, awesome, you are working on this? 13:25:13 Okay, great. Let's time box this action item and revise it a bit. 13:25:31 I am trying to create a pitch so that we can ask others for a feedback on this during flock 13:25:36 @recursedd: Do you want to set a deadline for Wednesday, June 27 to have a pitch complete for the article? 13:25:52 And then we can work on the full article after? 13:26:09 Yeah.. that should be a good enough chunk of time 13:26:42 Okay, awesome. If you get it done over the weekend, that's great too, but we'll leave some extra days in case :-) 13:26:46 #nick recursedd 13:27:23 #action recursedd Write a pitch for an article introducing Fedora Event Guidelines rough draft and asking for feedback from community by Wednesday, June 27 13:27:28 Thanks recursedd! 13:27:53 Oops, I missed the next action item: reCursedd start a pitch for introducing Fedora Event Guidelines on Community Blog before FLOCK 13:28:01 So I will just skip it since we answered it now. 13:28:36 #info === "jwf followup with RH internal on workshop for first time speakers at FLOCK 2017 - Is it happening again this year? Is it open to non RH community members?" === 13:29:35 I did follow up on this, but I'm curious what you all think we should do 13:29:59 #link https://lists.fedoraproject.org/archives/list/flock-planning@lists.fedoraproject.org/thread/S3VSDN34VMEFQW5OVUWJZFXXSRAPZPYI/ 13:30:22 #link https://lists.fedoraproject.org/archives/list/flock-planning@lists.fedoraproject.org/thread/EVC5RKTQAPUKNTR2AVVT3WAF4MWZMCE6/ 13:30:57 So it looks like there is an interest by the RH team from last year to do this again 13:31:50 The response from Lenka is in the second link, you have to open the reply in Brian's forwarded message to see it 13:32:18 I think jonatoni mentioned this before that she wasn't sure if we would have bandwidth to do this for this year's Flock 13:32:38 And the first Flock CFP round is already started 13:33:11 So I think it's best if we focus in on our content and planning for Flock this year 13:33:17 And plan for our sessions 13:33:25 What do you all think? 13:34:39 I thinkwhat we discussed in the last meeting was we dont have the bandwidth to do this on our own, but if we dont need to support much for this collaboration - we can do it. I am not sure how these sessions are communicated but maybe we can do a Community Blog post about it. 13:34:40 +1.. we should plan it up 13:34:42 Per the next action item, we can encourage wider publicity about it, but I don't know if we should make a commitment to be a part of the feedback 13:34:51 * jwf nods 13:35:02 Okay, I think we're on the same page 13:35:15 when the result will be out? 13:35:17 s/feedback/speaker feedback sessions 13:35:39 Amita: For selected talks? We would probably need to ask in #fedora-flock 13:35:48 I would guess before the next round begins on July 2 13:35:53 ok 13:36:12 we should do publicity only after that I guess 13:36:37 Amita yes I think it would be after mid July 13:36:47 ok 13:36:50 #info We will not commit to participating / running a speaker feedback session with our team because of low bandwidth, but will follow-up with Red Hatters organizing this to work on better publicity closer to Flock 13:36:53 ^ sound good? 13:37:19 speaker feedback session? 13:37:36 also, since its done in Brno - maybe we suggest them to run a virtual session for it or just stream the existing one using Jitsi etc 13:37:41 It was called something else 13:38:06 Amita: I'm not sure what it will be called, but I'm referring to what Lenka Bocincova mentioned in the flock-planning thread 13:38:17 If we know what that means, then it's okay 13:38:17 during the session, is it the speaker deliver their talk first and then get feedback? 13:38:36 bee2502_: Last year, if I recall, they did both virtual and in-person 13:38:47 Amita: As I understand, that is how it worked last year 13:38:51 jwf, but if we need to do publicity we need to know exectly what it is 13:38:53 We'd have to ask Lenka for specific details 13:38:59 ok 13:39:16 let us clear everything before we start going out about it 13:39:23 so that we can answer any queries 13:39:26 Amita: We will have to follow-up with Lenka for what and how it will be run. If we help with publicity, it will probably be the two weeks before Flock. 13:39:45 I think we should let the Red Hat team handle the logistics and planning for this. We can support them by writing a CommBlog post 13:39:56 Otherwise, I don't think we should get as involved so we can effectively plan our sessions for Flock 13:40:13 Or, we can suggest they write the CommBlog post 13:40:15 Which may be easier 13:40:23 They may not be aware of that as a method to promote the session 13:40:36 Amita: I think they are waiting for accepted content and sessions too, so we will only know after the first round. 13:40:57 I think we should suggest them best practices for awareness, but we can follow up on this later in July. 13:41:05 ok 13:41:18 I'm going to move on so we have time to cover the FWD topics :-) 13:41:45 #nick diversity-team 13:42:18 #action diversity-team Follow up with Lenka Bocincova in late July about Flock speaker feedback workshop to suggest best practices for publicizing the workshop 13:42:31 I also had a standing item to make a Fedocal for today's meeting, which I didn't do :-( 13:42:37 Sorry… 13:42:51 Okay, to the ticket for today: 13:43:13 #topic Ticket #66: Fedora Women Day 2018 13:43:15 #link https://pagure.io/fedora-diversity/issue/66 13:43:28 I need to step away for a moment – bee2502_, do you want to chair for this topic? 13:43:46 yes, okay 13:44:24 We had a planned timeline for Fedora Women Day and we are very behind on it 13:44:50 I think recursedd has a FWD Marketing Pitch ready for some time now and we have had enough time to drop comments on it. 13:45:13 #link https://etherpad.gnome.org/p/FWD_Marketing_Pitch 13:45:24 The dates portion is not decided on it.. do we want to cut that out and publish it?? 13:46:34 Here is the proposed timeline: 13:46:56 === APRIL === 13:47:06 New ticket for Fedora Women Day 2018 with proposed goals 13:47:12 Start the discussion with other subprojects i.e. Mindshare, Marketing, Ambassadors, CommOps to help with different parts of event. 13:47:24 Connect and establish relationships with female contributors in Fedora community. 13:47:35 === MAY === 13:47:43 Create different resource packages(based on event goals) to offer organizers i.e. for FWD organizers with an aim to increase Fedora contributor/user base or Fedora <3 Py package for Pyladies 13:47:50 Have a way to assimilate attendees in Fedora community after the event so we do not lose impact. 13:47:58 Modify event activities to better support onboarding new contributors i.e. Have hackathons or small activity sessions 13:48:17 I think we can still do these if we divide these tasks and work faster 13:48:40 recursedd: I think we can set the dates in this meeting or soon :) 13:49:07 I feel its important to have dates like deadline to submit proposals for organizers in this email.. 13:49:10 Yea.. it would be helpful for the organizers and participants 13:50:13 we leave the exact dates for event upto the organizers with some dates in September as suggestions.. 13:50:54 I think we should start the discussion with other subprojects about this 13:50:57 Okayy.. what can be a probable date for submission of proposals? 13:51:26 *deadline for 13:51:26 recursedd let's decide the dates in a few minutes.. 13:51:47 Okay..😋 13:52:27 I think we should definitely send an email to Ambassadors mailing list with the pitch to see if there is interest to organize one in their local community 13:53:20 I can do this :) 13:53:58 Hmm – since it's almost the end of June, I think we should give a deadline date for any email or post we write 13:54:08 I think it's important we time box anything we send now 13:54:14 +! 13:54:15 +1 13:54:17 +1 13:54:26 I think the deadline for this could be be next week as the pitch is ready 13:54:35 (I may need to rush now, sorry, I will be on telegram) 13:54:44 What date gives us enough time to comfortable receive and process applications for FWD? 13:54:58 bee2502_: I think a week isn't long enough 13:55:13 I think we should try to leave 2-3 weeks for the applications, at minimum 13:55:32 Maybe end of July? Or maybe even Flock? 13:55:40 I think we should have at least a month's time after we send out calls for organizers 13:55:51 I would say mid of August 13:56:01 so we can promote it at Flock too 13:56:04 jwf I think one week for sending out the email to Ambassadors, and they can submit the proposals before the date we decide for everyone else. 13:56:38 +1 13:56:57 before posting to the Ambassadors ML we should have the article published 13:58:04 If we do a mid August deadline, then the event can only be in last week of September 13:58:34 or late September 13:58:54 I feel like organizers need atleast a month to know feedback on their proposal and plan their event 13:59:23 I saw these original times in the Etherpad: Call for proposals for FWD organizers - June 1st 13:59:23 Deadline for submission - July 20th ---- (Keeping this gap bigger to ensure maximum participation and proposals) 13:59:23 Acceptance deadline - August 1st ---- (So that we have enough time to ship out goodies or swags to required areas) 13:59:33 because they might also have to organize speakers and workshop sessions, do outreach about the event etc. 13:59:41 We could push the submission deadline to the end of July if we publish the article in June 14:00:01 We can push the acceptance deadline to Flock perhaps, so we can work on these during out D&I team sprint too 14:00:09 Especially if it for 1/2 a day at Flock 14:00:54 We can do rolling acceptances, and deadline can be after FLOCK so we can promote it at FLOCK like jonatoni said 14:01:20 Ya.. I made those deadlines up.. 🙈 14:01:53 Rolling acceptances could work 14:01:59 so we can review the proposals submitted before FLOCK during our sprint and still leave it open for new organizers.. 14:04:23 So how about : Deadline for submission: Thursday, 16 August 14:04:30 a week after FLOCK 14:04:48 +1 14:05:12 Acceptance deadline: Rolling acceptance + final deadline: Wednesday 22 August 14:06:14 Event dates: Late September, organizers can decide on their availability, suggested dates: 22 or 23rd September 14:06:38 jonatoni recursedd amisha3 jwf 14:06:42 what do you think? 14:06:58 +1.. rolling acceptance should be flexible 14:07:08 +1 14:07:36 Here is an etherpad for our internal planning: https://etherpad.gnome.org/p/FWD2018 14:07:51 #link https://etherpad.gnome.org/p/FWD2018 14:08:42 I think we have one already started: 14:08:44 #undo 14:08:44 Removing item from minutes: 14:08:46 #link https://public.etherpad-mozilla.org/p/FWD 14:09:25 Let's vote on the proposed dates 14:09:40 #proposed Dates for FWD planning 14:09:57 Deadline for submission: Thursday, 16 August 14:10:06 Acceptance deadline: Rolling acceptance + final deadline: Wednesday 22 August 14:10:14 Event dates: Late September, organizers can decide on their availability, suggested dates: 22 or 23rd September 14:10:43 or we can even do last week of September as suggested dates 14:10:44 I'll add them in the pitch 14:10:58 To clarify, acceptance deadline is when we have processed all applications and delivered feedback, right? 14:11:03 yes jwf 14:11:06 Okay 14:11:07 +1 14:11:27 so when will FWD happen? 14:11:37 last week of September? 14:11:40 recursedd jonatoni amita? 14:11:53 jonatoni: The suggested days are Sept. 22-23, but like last year, it can be any time in September based on organizer availability 14:12:08 I think some were even in beginning of October if I remember right 14:12:17 So there is some flexibility built in 14:12:17 yes jwf 14:12:41 Do we want to write it to the minutes? 14:12:54 Keeping a larger box should be better.. 14:13:11 Like entire September or October 14:14:44 I think +/- 15 days of suggested events is good 14:14:56 recursedd, that makes it one month 14:15:40 Yes.. perfect 14:17:20 So, how about this #proposed: 14:18:15 I will publish it in 2 weeks 14:18:37 The podcast I mean 14:19:03 #proposed FWD planning dates: [Thu, 16 August] Submission deadline for organizers to D&I team for budget; [Wed, 22 August] Acceptance deadline for D&I team to organizers; [22-23 Sept.] Suggested dates for FWD event (with flexibility for dates in September) 14:19:07 Votes? 14:19:26 +1 14:19:27 +1 from me 14:19:41 +1 14:19:44 @x3mboy: Awesome! Can't wait for it. 14:20:00 Going once… 14:20:10 Going twice… 14:20:20 And thrice! 14:20:26 #agreed FWD planning dates: [Thu, 16 August] Submission deadline for organizers to D&I team for budget; [Wed, 22 August] Acceptance deadline for D&I team to organizers; [22-23 Sept.] Suggested dates for FWD event (with flexibility for dates in September) 14:20:45 Okay. So in this next week, we can work on publishing the post @recursedd has worked on 14:20:56 @recursedd: Did you want to port it over to the CommBlog next? 14:20:59 Cool 14:21:52 Yes if everyone agrees to 14:22:00 +1 14:22:02 can we set a hard deadline for publishing this posr 14:22:18 and communication with ambassadors 14:23:01 @recursedd: Yep. I think you are good to add it as a draft to the CommBlog now. Any other edits will be small – you've done awesome work with this :-) 14:23:06 bee2502: +1 14:23:23 How about next Thursday for the CommBlog post? 14:23:34 Okayy will do that 14:23:46 Communication with Ambassadors can be any time after – I think @jonatoni said she could help with that 14:24:01 @recursedd: Thanks! 14:25:11 yes 14:25:17 I can do that jwf 14:25:27 Awesome 14:25:34 Then we can write actions for these too 14:25:45 Can someone walk me through the steps of it?? 14:25:53 #action recursedd Move FWD marketing pitch Etherpad draft as a new post to the Community Blog 14:26:17 #action jwf Work on publishing FWD article on CommBlog on Thursday, June 28 14:26:42 #action jonatoni Promote FWD organizing on the Ambassadors mailing list after CommBlog post publishes (either Thu, June 28 or Fri, June 29) 14:26:44 Sound good? 14:26:51 @recursedd: Yep! One sec— 14:27:01 https://communityblog.fedoraproject.org/writing-community-blog-article/ 14:27:11 I found this .. I think this should be helpful 14:27:13 @recursedd: Yep, I was about to link that! 14:27:26 That should be helpful for you to walk through the steps 14:27:42 If you have questions about the CommBlog, you can ask for help in #fedora-commops / @fedoracommops. 14:27:48 Yay nice.. thanks.. 😊😊 14:27:51 Okay 14:28:03 Excellent! 14:28:09 jwf: yes, thanks 14:28:14 So I think we have a good plan of action for moving forward on FWD 14:28:30 We're about 90 minutes past our start time – do we want to wrap it here? 14:28:43 Anything else for FWD? 14:28:45 #chair 14:28:45 Current chairs: Amita bee2502 bee2502_ jonatoni jwf recursedd x3mboy 14:29:03 Going once… 14:29:09 Nothing I have presently on Monday 14:29:11 Mind* 14:29:15 Going twice… 14:29:16 I want to discuss 14:29:31 more abotu FWD but we csn do it next week 14:29:33 :) 14:29:37 * jwf nods 14:29:46 I think we have enough to get started with for now. 14:29:53 Definitely more to cover, but we can break it up 14:29:56 #topic Open floor 14:30:05 Anyone else have anything they want to mention now? 14:30:55 https://pagure.io/accessibility-guide 14:31:05 does anyone know about this? 14:32:19 bee2502_: Looks like an accessibility guide produced by GNOME / KDE 14:32:24 #fedora-docs is probably the best place to ask 14:32:32 It's something with Fedora OS documentation 14:33:09 thanks! 14:34:57 Yep! 14:35:03 Okay, I think I will close out the meeting now. 14:35:09 Thanks everyone for coming and participating! 14:35:21 See you around in the Fedora universe :-) 14:35:23 #endmeeting