12:58:14 #startmeeting Fedora CommOps (2018-04-13) 12:58:15 Meeting started Fri Apr 13 12:58:14 2018 UTC. The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:58:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 12:58:15 The meeting name has been set to 'fedora_commops_(2018-04-13)' 12:58:15 #meetingname commops 12:58:15 The meeting name has been set to 'commops' 12:58:15 #nick commops 12:58:19 #topic Agenda 12:58:27 #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next 12:58:27 #info (1) Roll call / Q&A 12:58:27 #info (2) Announcements 12:58:27 #info (3) Action items from last meeting 12:58:28 #info (4) Tickets 12:58:30 #info (5) Open floor 12:58:36 #topic Roll call / Q&A 12:58:44 #info Name; Timezone; Sub-projects/Interest Areas 12:58:44 #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] 12:58:51 If this is your first time at a CommOps meeting, feel free to 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. 12:59:27 Started a little early because I'm finishing something else up before we start. Anyone who is here for the meeting, feel free to chime in :-) 13:04:42 .hello2 13:04:42 x3mboy: x3mboy 'Eduard Lucena' 13:05:03 hi x3mboy 13:05:05 * jwf waves to x3mboy 13:05:08 bt0_: Hey! 13:05:13 #chair x3mboy bt0 bt0_ 13:05:13 Current chairs: bt0 bt0_ jwf x3mboy 13:05:23 hi jwf o/ 13:05:30 Hmmm. This is definitely not the same number of people who filled out the Etherpad for this time. :P 13:05:40 s/Etherpad/WhenIsGood 13:06:00 Oh well – we can go ahead and start, and anyone else can chime in when they arrive. 13:06:13 bt0_, Hi bro! 13:06:40 Oh, right: 13:06:53 #info Justin W. Flory; UTC-4; CommOps, Diversity, Mindshare, Ambassador 13:07:05 #info Alberto Rodríguez Sánchez; UTC-6; CommOps, marketing, dotNet sig, Ambassadors 13:07:50 #info x3mboy is here too :-) 13:07:51 #topic Announcements 13:07:59 #info === "Interviews on the Fedora Infrastructure Hackathon 2018" === 13:07:59 #link https://communityblog.fedoraproject.org/fedora-infrastructure-hackathon-2018/ 13:07:59 #info The Fedora Infrastructure Hackathon is going on this week. Read about some of the goals and plans for the hackathon and what the Infrastructure team hopes to accomplish. 13:08:10 #info === "Top Badgers of 2017: Alberto Rodriguez Sanchez" === 13:08:10 #link https://communityblog.fedoraproject.org/top-badgers-2017-alberto-rodriguez-sanchez/ 13:08:11 #info The next edition of Top Badgers of 2017 is here! Read lroca's interview with bt0 on his success and advice for others on gathering badges from 2017. 13:08:14 bt0++ 13:08:24 #info === "Kernel 4.16 Test Day 2018-04-13" === 13:08:24 #link https://communityblog.fedoraproject.org/kernel-4-16-test-day-2018-04-13/ 13:08:24 #info The Fedora QA team needs your help! The kernel team is working on final integration for Kernel 4.16 for Fedora 28. This version was just recently released, and will arrive soon in Fedora. Come help test it out! 13:08:30 13:08:35 Those are the three announcements I have. 13:08:43 Anyone else have anything? 13:09:01 not from.me 13:09:11 Going once… 13:09:20 Going twice… 13:09:25 And thrice! 13:09:33 #topic Action items from last meeting 13:09:40 #link https://meetbot.fedoraproject.org/fedora-meeting-2/2018-04-02/commops.2018-04-02-14.32.html 13:09:40 #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:09:51 #info === [IN PROGRESS] "jwf Work on first draft of FAD event report, share with team for feedback" === 13:09:52 #action jwf Work on first draft of FAD event report, share with team for feedback 13:10:02 #info === [INCOMPLETE] "jwf Review Contributor Stories draft and schedule in the next week" === 13:10:02 #action jwf Review Contributor Stories draft and schedule in the next week 13:10:13 #info === [INCOMPLETE] "dhanesh95 Finish research into implementation solutions and put together a final proposal for how to move forward with WordPress fedmsg integration by Friday, April 13, 2018" === 13:10:14 #info Dropping action item from meeting agenda, adding comment to ticket to add update when available 13:10:23 #info === [INCOMPLETE] "x3mboy File a new ticket in Mindshare Pagure to propose student pack idea and start discussion in Mindshare Committee" === 13:10:29 x3mboy: Do you want to time-box this one? 13:10:49 Yes, I will need at least one more week to retake everything 13:10:54 * jwf nods 13:11:00 x3mboy: Do you want to set them for next Friday? 13:11:06 Yes 13:11:07 April 20? 13:11:11 Awesome. 13:11:20 #action x3mboy File a new ticket in Mindshare Pagure to propose student pack idea and start discussion in Mindshare Committee by Friday, April 20 13:11:22 Just yesterday I got the casts out, so I can work better this week 13:11:24 :D 13:11:26 #info === [INCOMPLETE] "x3mboy Submit new PR with README for contributor-stories repository" === 13:11:32 #action x3mboy Submit new PR with README for contributor-stories repository by Friday, April 20 13:11:38 Thanks 13:11:41 x3mboy++ Awesome!! Do you have your arms back now? 13:11:53 #info === [COMPLETE] "wesleyotugo Reach out to stickster/pfrields, jperrin, and sinnykumari to interview on the Infrastructure Hackathon" === 13:11:53 #link https://communityblog.fedoraproject.org/fedora-infrastructure-hackathon-2018/ 13:11:53 #info This was published earlier this week. Nice work wesleyotugo, and thanks to nirik, smooge, and sinnykumari for the interview answers! 13:12:03 #info === [COMPLETE] "jwf Update Fedocal for new meeting day and time" === 13:12:03 #link https://apps.fedoraproject.org/calendar/meeting/8732/ 13:12:05 13:12:28 This week, I didn't have much time to work on Fedora things, so I slipped on a lot of my action items 13:12:30 Yeah!!! 13:12:39 I can type with both hands again 13:12:40 amazing 13:12:44 Wiiiii!!! 13:12:50 x3mboy: \o/ That is awesome news. Happy to hear it! 13:13:24 #topic Tickets 13:13:37 #info === Ticket #110: "Fedora Appreciation Week 2017" === 13:13:37 #link https://pagure.io/fedora-commops/issue/110 13:13:37 #link https://screenshots.firefox.com/NDyEhhKzQJ4WpXr4/etherpad.persephone.cloud 13:13:42 #info No new updates: jwf needs to review bt0's draft and schedule. This will be done over this weekend. 13:13:46 Will skip over ticket for today's meeting if no new discussion? 13:13:59 Now I know this ticket is blocking on me, so I will work hard at unblocking it this weekend 13:14:01 +1 13:14:20 Cool, then I will skip ahead… 13:14:29 #info === Ticket #117: "How-to create Onboading guidelines for your team" === 13:14:29 #link https://pagure.io/fedora-commops/issue/117 13:14:38 This was an older ticket in our Pagure that bee2502 filed a while back 13:15:02 I thought now was a good time to revisit, since the docs migration is done. 13:15:35 Some of you might remember the old tickets we had for the sub-project on-boarding discussions 13:16:07 This ticket was intended to be the "successor" to those tickets by creating a set of best practices / guidelines for any Fedora sub-project to on-board new contributors 13:16:34 Kind of like our docs we have here, but generalized: 13:16:34 https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/docs/contribute/join.html 13:17:04 * bt0_ is reading 13:17:08 I thought writing this as a doc would be more useful than a CommBlog post. 13:17:36 I was also thinking of this repository that hasn't gotten a lot of love and action yet: 13:17:37 https://pagure.io/fedora-commops/onboarding-guide 13:17:49 I was thinking this could be a good place to put something like that 13:18:38 .hello amsharma 13:18:39 Amita: amsharma 'Amita Sharma' 13:18:51 * Amita just lurking 13:19:01 * jwf waves to Amita 13:19:22 So, my question to you all is what content you think makes the most sense to include in this guide. 13:19:29 I thought we could do some brainstorming about it here now. 13:19:40 Last week, roca asked about this ticket and then I never got back to him :P 13:21:00 * bt0_ is thinking 13:22:06 Create a telegram channel for your team is a good 1st step 13:22:40 x3mboy: Hmm, interesting. That's not a standardized on-boarding procedure, but I like the idea of suggesting it, so long as there is a bridge 13:22:42 works for anyone without experience in irc 13:22:49 #idea Create a Telegram group bridged to an IRC channel 13:23:07 #idea Give helpful questions for a new contributor to answer in a mailing list introduction 13:24:59 #idea Create "starter / easyfix" tasks for new contributors 13:25:15 #idea Get the easyfix tasks listed on the easyfix page (https://fedoraproject.org/easyfix/) 13:27:14 Sometimes I wonder if it would be helpful to explicitly document how to volunteer for a task too 13:27:21 videos or articles about create a fas account, request access to mailing lists? 13:27:31 I feel that over the years, I often see people hesitant or confused because they don't know how to actually "begin" work on a task or ticket 13:27:53 bt0: Ooh, that could be new content creation. A video tutorial could be helpful. 13:28:12 #idea Creating content for sub-projects: Video on how to create FAS account, subscribe to mailing list, etc. 13:28:40 #idea Explicitly document how a new contributor volunteers or starts working on a task or ticket (commenting in Pagure? speaking up in IRC? asking on the mailing list?) 13:28:49 jwf, I was thinkg on having a podcast session for CommOps, but I feel like we still have stuff to clear up with Mindshare 13:29:02 So I'm not sure if at this point it will be useful 13:30:14 x3mboy: I think the Mindshare FAD cleared things up for me that I've been wondering about for the last two years. :P 13:30:32 x3mboy: For discussion's sake, I am interested to know what you think is unclear – but let's save it for open floor 13:30:56 So, since roca is not here and he was interested in working on this, I'll take some of these #ideas and put them into the ticket. 13:31:18 Maybe it would be easier to start in an Etherpad and then convert to AsciiDoc later 13:31:43 I'll do that later this afternoon when I can swing back around 13:32:48 If nothing else, I'll go ahead and wrap this up 13:33:00 okay 13:33:21 #agreed Will move ideas to the ticket, suggest starting a draft in an Etherpad for a general guidelines doc (and we can edit ideas together into a written AsciiDoc doc) 13:33:46 Those are actually the only two tickets I had selected for today, but I wanted to run some brainstorming at open floor: 13:33:49 #topic Open floor 13:34:03 Before that, x3mboy, did you want to bring up the podcast? 13:34:47 And we also need to talk about the meeting time… 13:35:14 :p 13:35:32 :-( 13:35:48 We can revisit the podcast in a bit 13:36:05 http://whenisgood.net/fedora/commops/spring-2018-meeting/results/h4xp9bq 13:36:22 we don't take in account the overlap with diversity 13:36:40 Yeah, when I put together the WhenIsGood, I was looking at a week when the Diversity Team wasn't meeting 13:36:49 And if I understand right, the Diversity Team is also wanting to move to weekly meetings too 13:37:29 Me, jonatoni, x3mboy, and bexelbie are likely blocked at this time after all 13:37:44 yeah 13:37:46 And that's four of the seven people who entered this time as a good time 13:38:27 I hate to run through this process all over again, so I want to follow up with the Diversity Team if they still wanted to find a new meeting time (but I know it took a while to find a good time for them too) 13:38:31 Something about Friday mornings… 13:38:56 I'm not really sure what to do yet, but I'll try to figure this out and keep everyone in the loop 13:39:26 I also noticed there are some people who had connectivity issues to IRC today and weren't able to participate because it was in IRC 13:39:46 I thought we could take a page from Diversity and run our meetings in #fedora-commops too, so people can still participate via Telegram on mobile. 13:40:05 I thought this was a trivial change, but wanted to get your thoughts on it 13:40:07 +1 13:40:43 Sorry I was on d&i 13:40:57 Oh, well, we are now really clear about what our objective is? 13:41:01 x3mboy: I feel you :-( 13:41:21 x3mboy: I was curious what you felt was unclear because I think that would help drive the conversation 13:41:22 If we have this objective really clear, I want to propose a Podcast Interview following the interview of the D&I 13:41:57 Well, for me it's unclear because I haven't read it anything after the 1st Mindshare report 13:42:29 x3mboy: I think the docs page sums it up best, and since we merged it, I think an interview would almost be a verbal version of the content that's there. https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/docs/commops.html 13:42:45 This was post-FAD too 13:43:22 Oh, that looks good 13:43:28 Sorry that I missed that 13:43:37 However, my challenge is that I will probably not be around in May to help out with the podcast. I still need to figure out how the torch will be passed after I'm gone: 13:43:46 https://blog.justinwflory.com/2018/04/fedora-may-to-august-2018/ 13:43:53 ^^ this is also probably helpful to mention now too. 13:44:10 I won't be around for much of May until August 2018 13:44:11 I read that 13:44:15 omg 13:44:49 But is ok, remember that podcast recording date is not related to release/publish date 13:44:53 * jwf nods 13:44:55 Also true 13:45:02 So, we can secorded just before you go 13:45:10 x3mboy: Could I action you to file a ticket for us to figure out the podcast? 13:45:14 Sure 13:45:25 s/secorded/recorded 13:45:41 * jwf nods 13:45:53 I'm also going to make a note to update the meeting channel to #fedora-commops for the future 13:45:55 * x3mboy still have hope that mizmo will have a time for me to record the next episode about Design team 13:46:16 #agreed Future meetings will be held in #fedora-commops to leverage the Telegram <=> IRC bridge 13:46:46 #info The meeting time conflict with Diversity is a major blocker; need to figure out a plan forward. jwf will follow-up with meeting days/time with Diversity Team 13:47:05 #action x3mboy File a ticket in CommOps Pagure about a new podcast interview / episode on the CommOps team 13:47:15 Does this all sound right? 13:47:31 yes 13:47:33 Yes 13:47:48 Also, I would love to record this one before the D&I session 13:48:02 To do a test about more than 1 person interview 13:48:15 x3mboy: I can't make promises on that if you're wanting to include me. :-( 13:48:34 I'd love to see if we can round up some other folks to participate, like bt0_, wesleyotugo, maybe roca too if he is interested. 13:48:52 I'd love that too 13:48:56 \o/ 13:49:00 Cool, we can move that to the ticket 13:49:02 sound 13:49:10 s great 13:49:39 I wanted to have some brainstorming about new tickets, but I'm not sure if I will have time – I have a one-time in-person meeting in ten minutes I have to get ready for today. 13:49:54 Do we want to postpone to next week, maybe when we find a less-conflicting meeting time? 13:50:07 +1 13:50:19 Okay, cool 13:50:32 Then we can wrap up now and I can get the minutes out to the list before I have to jump out 13:50:50 x3mboy bt0: Thanks for coming out today and participating! Even if attention was a little split :P 13:50:55 We will fix this for next week 13:51:04 See you all in channel or elsewhere in the Fedora universe :-) 13:51:05 #endmeeting