15:30:09 #startmeeting Fedora CommOps (2018-02-19) 15:30:09 Meeting started Mon Feb 19 15:30:09 2018 UTC. The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:30:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:30:09 The meeting name has been set to 'fedora_commops_(2018-02-19)' 15:30:09 #meetingname commops 15:30:09 #nick commops 15:30:09 The meeting name has been set to 'commops' 15:30:20 #topic Agenda 15:30:27 #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next 15:30:27 #info (1) Roll call / Q&A 15:30:27 #info (2) Announcements 15:30:27 #info (3) Action items from last meeting 15:30:28 #info (4) Tickets 15:30:29 #info (5) Open floor 15:30:44 #topic Roll call / Q&A 15:30:49 #info Name; Timezone; Sub-projects/Interest Areas 15:30:49 #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] 15:30:54 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. 15:31:09 #info Justin W. Flory; UTC-5; CommOps, Diversity Team 15:31:16 #info Alberto Rodríguez S.; UTC-5; CommOps, dotNet, Marketing, Infra, Ambassadors, cats 15:31:26 * jwf waves to bt0_ 15:31:29 #chair bt0_ bt0 15:31:29 Current chairs: bt0 bt0_ jwf 15:31:36 .fas bt0dotninja 15:31:37 bt0_: bt0dotninja 'Alberto Rodriguez Sanchez' 15:31:42 hi o/ 15:31:58 We'll wait a few minutes for some other folks to pop in. :-) I'm going to get some water before we kick off. 15:32:34 #Info Dennis W. Otugo; UTC+1; CommOps, Infra 15:35:35 Hi wesleyotugo! 15:35:38 #chair wesleyotugo 15:35:38 Current chairs: bt0 bt0_ jwf wesleyotugo 15:37:07 I know bee2502 and skamath are away from keyboard today. 15:38:01 Right 15:38:26 Hello jwf 15:39:20 Okay, might be a quiet show today. 15:39:26 Let's go ahead and get started, 15:39:33 #topic Announcements 15:39:38 #info === "EMEA Ambassadors: 2017 Year in Review" – by edgates++ === 15:39:40 jwf: Karma for edgates changed to 1 (for the f27 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:39:43 #link https://communityblog.fedoraproject.org/emea-ambassadors-2017-year-review/ 15:39:43 #info Quick highlights of the EMEA Ambassadors' activity in 2017. Includes goals for improved event report coverage and tracking metrics to measure success. 15:40:12 15:40:29 That's the only thing I had on my list since last week, but I also didn't get a chance to search through the mailing lists 15:40:32 Anyone else have anything? 15:41:03 Going once… 15:41:13 Going twice… 15:41:20 And thrice… 15:41:25 #topic Action items from last meeting 15:41:32 #link https://meetbot.fedoraproject.org/fedora-meeting-2/2018-02-12/commops.2018-02-12-15.30.html 15:41:32 #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. 15:41:50 #info === [INCOMPLETE] "x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors" === 15:41:50 #action x3mboy Open new CommOps ticket with expanded idea on improving communication from public to Ambassadors 15:41:55 #nick x3mboy 15:42:00 #info === [IN PROGRESS] "jwf Work on first draft of FAD event report, share with team for feedback by 2017-02-16" === 15:42:03 #link https://pagure.io/fedora-commops/issue/125#comment-494519 15:42:07 #action jwf Work on first draft of FAD event report, share with team for feedback by 2017-02-23 15:42:12 #info === [COMPLETE] "commops Review Fedora Appreciation Week template to collect contributor stories, leave any feedback in the Etherpad" === 15:42:16 #link https://etherpad.persephone.cloud/p/commops-faw-2018-template 15:42:19 #info Template is ready; need to add template into tooling for Pagure repo 15:42:24 #info === [COMPLETE] "bee2502 jonatoni Start discussion with Fedora Infra on requirements to host our own Happiness Packet site (inc. Python / Django, PostgreSQL, etc.)" === 15:42:28 #link https://pagure.io/fedora-infrastructure/issue/6690 15:42:31 #info Idea generally approved; bee2502 and jonatoni to clarify on hardware needs once we get through the applicant phase of GSoC and Outreachy 15:42:36 #info === [IN PROGRESS] "skamath Finish installing Grimoire on CommOps cloud instance by 2018-02-19, share link to mailing list when finished" === 15:42:40 #link http://commops.fedorainfracloud.org/app/kibana 15:42:44 #action skamath Document log-in instructions to Grimoire on CommOps cloud instance 15:42:48 Planned discussion for later in meeting. 15:42:51 #nick skamath 15:43:16 #info === [COMPLETE] "skamath file an issue in mentored-projects repo for including perceval project in Outreachy" === 15:43:21 #link https://pagure.io/mentored-projects/issue/25 15:43:25 #info === [COMPLETE] "skamath Follow-up with a2batic and sumantro on GSoC projects for Outreachy" === 15:43:29 #link https://screenshots.firefox.com/KcVsMWBWRGi5vS3e/www.outreachy.org 15:43:32 #info Perceval fedmsg plugin and Android projects are officially added as Summer 2018 Outreachy projects 15:43:38 15:43:56 Pretty straightforward this week. We're mostly chugging along to the timeline we outlined at the FAD. 15:44:13 woo, awesome 15:44:20 #topic Tickets 15:44:24 #link https://pagure.io/fedora-commops/issues?tags=meeting 15:44:30 #info === Ticket #137: "New CommBlog article: Fedora accepted into GSoC 2018" === 15:44:31 #link https://pagure.io/fedora-commops/issue/137 15:44:35 #help Great task for beginner. Need to write an announcement that Fedora is participating in Google Summer of Code 2018. Past example is in ticket. 15:44:46 I also put a call out for this on the mailing list last night. 15:45:14 I thought I'd keep it in the meeting agenda if someone wanted to work on it after seeing it in the meeting, but otherwise, we can move forward. 15:45:31 Started drafting on ticket #137 15:45:40 I know bexelbie would appreciate a lot of help on this one :-) 15:45:50 wesleyotugo: Awesome! So you are interested in working on this? 15:46:07 Yes jwf 15:46:42 wesleyotugo: Okay, great. When do you think you could have a first draft ready by? 15:47:05 The earlier the better, but next Monday (Feb. 26) was the original target date. 15:47:07 9pm 15:47:20 Tonight?? 15:47:23 wait.. I mean 8pm GMT 15:47:36 Ahh, okay. If you can swing that, it would be awesome. 15:47:42 wesleyotugo++ 15:47:49 wesleyotugo: Can I action you to write to the mailing list when you're ready for review? 15:48:15 Yes, but I am not good at graphic so I cant create a featured image? 15:48:15 That way, both me, bexelbie, and skamath have a chance to read it and share any feedback. 15:48:18 Okay sure jwf 15:48:27 wesleyotugo: Don't worry on the featured image. :-) I can help with that. 15:48:39 I think I have a generic GSoC image we can use for this type of article 15:49:15 #action wesleyotugo Write first draft of "Fedora accepted into GSoC 2018" on CommBlog; write to mailing list when ready for review (final draft due: 2018-02-26) 15:49:26 Okay that could work. I could just put in the text in the image 15:49:32 Awesome, thanks wesleyotugo for jumping on this. Hopefully this one is more straightforward than the wiki article. 15:49:42 Moving on to the next ticket… 15:49:43 #info === Ticket #110: "Fedora Appreciation Week 2017" === 15:49:48 #link https://pagure.io/fedora-commops/issue/110 15:49:58 And a few more relevant links… 15:49:59 #link https://screenshots.firefox.com/Gahbf6ED4lAVP9b8/etherpad.persephone.cloud 15:49:59 #link https://pagure.io/fedora-commops/contributor-stories 15:49:59 #link https://etherpad.persephone.cloud/p/commops-faw-2018-template 15:50:11 Our timeline, the repo for collecting stories, and the issue template ^^ 15:50:11 Lol I ran through it before the meeting started. it is 15:50:20 #info According to timeline, in February, we create the template for contributors to submit stories and add the template to repo. Template was out for review since last meeting; will move forward to incorporate template into repo 15:50:27 #action jwf Add FAW template in Etherpad as Pagure issue template in contributor-stories repo 15:50:31 Originally, we planned to announce contributor stories or Appreciation Week in a CommBlog post this month. Is this realistic or is someone interested in helping write this? 15:50:38 Otherwise, we can push into March. 15:50:59 * skamath is here 15:50:59 .hello2 15:51:00 skamath: skamath 'Sachin S Kamath ' 15:51:05 I know bee2502 is in exams and probably won't have bandwidth, and I travel for another two weeks starting this Saturday 15:51:11 * jwf waves to skamath 15:51:13 #chair skamath 15:51:13 Current chairs: bt0 bt0_ jwf skamath wesleyotugo 15:51:28 Hello commops o/ 15:51:47 skamath: Metrics ticket up next. :-) 15:52:04 Okay, I am on a really unstable connection. I'm moving a bit to find a better connection 15:52:40 Unless bt0_ is interested in taking this one, I'm inclined to push the first announcement into March. I think our team bandwidth is low to get this done in February. 15:52:45 about the comm blog entry I can do it 15:52:49 :D 15:52:57 bt0_: That would be amazing! 15:53:08 bt0_: Do you understand what the ask is for this article? 15:53:13 s/ask/point 15:53:26 mostly 15:53:45 but I can write a draft soon 15:54:07 What do you think it is? I want to make sure we're on the same page. :-) I know you caught a lot of this during the FAD, but thought it was better to be sure 15:55:59 bt0__: Lost connection? 15:56:07 Not sure if you caught my last message. 15:56:09 yeah 15:56:44 let me change to the Pc 15:57:38 bt0__: Okay, no problem. 15:57:53 bt0__: I was asking what you thought the point of the article was, to make sure we're on the same page. 15:58:57 Yeah, don't worry announcing contributor stories, right ?? 15:59:25 bt0: Yeah, I think it makes sense to introduce contributor stories now, in three pieces for the article: 15:59:28 1. What they are 15:59:37 2. Why we're doing this (hinting to FAW) 15:59:40 3. How to submit 15:59:48 cool 15:59:53 I think 300-500 words, anywhere in that range, is plenty 15:59:57 Sound good? 16:00:02 yeah 16:00:21 #info Contributor stories CommBlog intro: (1) What they are; (2) Why we're doing this; (3) How to submit one 16:00:32 bt0: First draft by next meeting sound good? 16:00:34 Or need more time? 16:00:39 right 16:00:43 :+1: 16:00:48 +1 16:00:58 #action bt0 Write first draft of Contributor Stories article for CommBlog by Monday, Feb. 26 2018 16:01:05 Sweet. We can push on ahead then. 16:01:09 bt0: Thanks for helping here! 16:01:18 #info === Ticket #114: "Use metrics dashboard to visualize fedmsg data" === 16:01:19 #link https://pagure.io/fedora-commops/issue/114 16:01:22 #link https://screenshots.firefox.com/Gahbf6ED4lAVP9b8/etherpad.persephone.cloud 16:01:25 #info Revisiting timeline goals; how do we want to document this information? 16:01:32 skamath: Ping, on a stable connection? 16:01:48 I was thinking about how we document things related to Grimoire for CommOps 16:01:50 On the most stable one I can get here :) 16:02:07 Oh, that's a good question 16:02:12 I was thinking about AsciiDocs in our repo, e.g. "How to use Grimoire on CommOps machine" 16:02:26 Which would include things like authentication instructions 16:02:45 Not sure if that's something extremely sensitive or introduces room for abuse, to publicly share basic read-only login instructions 16:02:57 We only authenticate for SSH. I should figure out a way to limit Kibana 16:03:07 We could manage write-access granular and create an account for someone that wanted to hack on it 16:03:10 Oh. 16:03:14 Right now, Kibana allows only sharing of the entire dashboard in read only mode. 16:03:26 skamath: Are we talking about the web interface or the admin rights on the box? 16:03:34 I have to take my leave now. Would readup and comment on issues lateron 16:03:39 I was talking to Elastic folks and looks like they have a separate app called Guard which lets us to limit Kibana 16:03:42 wesleyotugo: Thanks for joining! See you around. 16:03:45 .thank wesleyotugo 16:03:45 jwf thinks wesleyotugo is awesome and is happy they are helping! (Please don't forget to wesleyotugo++ also) 16:03:47 jwf, Kibana access. 16:04:02 Kibana doesn't come with privilege separation. 16:04:29 We need to plug in an extra tool called Guard by the Elastic folks and set up access 16:04:31 skamath: So there's no way for us to have a global, read-only account that we share publicly, and then "admin" users like `skamath`, `jflory`, etc? 16:04:42 jwf, There is. That's where Guard will help 16:04:46 I see. 16:04:53 I need to read about it. I only know that it can do it. 16:04:56 Sort of annoying that's not included out of the box… 16:05:11 skamath: Okay. So maybe before we think about documenting, we need to think about account access with Guard? 16:05:28 Is researching / possibly implementing Guard something you feel is doable by next Monday? 16:05:37 jwf, I am not sure about the process yet so let's keep documentation blocked on Guard. 16:05:54 +1 to blocking documentation on Guard 16:05:55 jwf, I think I can do it. I'll take an action on that 16:05:59 Awesome. 16:06:36 #action skamath Research (possibly implement) Guard to manage granular permissions between accounts in Kibana by Monday, 2018-02-26 16:06:45 +1 16:06:48 Thanks sir. 16:07:26 #info Documentation is blocked by understanding how we will manage accounts; need to look into third-party plugin by Elastic team called Guard to have advanced permissioning for multiple users in Kibana; skamath to research this by next Monday's meeting 16:07:44 Okay, I think this covers this for now. 16:07:53 skamath: Thanks for making steady progress on this. 16:08:00 Last ticket: 16:08:01 #info === Ticket #133: "Creating summer coding "best practices" docs for mentors" === 16:08:06 #link https://pagure.io/fedora-commops/issue/133 16:08:10 jwf, Did I share creds for dashboard with you? 16:08:13 #info bee2502 mentioned some ideas for advice on supporting mentors in our intern programs; what other helpful topics are there to include? Do we want to champion this task at the 2018 Documentation FAD? 16:08:18 skamath: I do have them in Telegram. 16:08:26 Okay, cool :) 16:08:32 skamath: Maybe an email to me and bex would help too, to keep him in on the loop 16:08:44 jwf, That's the first thing I did. 16:08:48 :P 16:08:59 skamath: Oh, sweet. :-) I must have missed the email, but all is good, I have it in Telegram 16:09:04 Looking at #133… 16:09:17 I mostly wanted to see if anyone had other ideas for helpful tips for GSoC / Outreachy interns 16:09:29 I think half of us still present have interacted or participated in GSoC before now 16:09:49 So I thought we could brainstorm for a bit, and then this ticket could be highlighted at next week's Docs FAD. 16:10:09 Bee had four ideas in the ticket: 16:10:14 #idea Have on-boarding guidelines for selected applicants 16:10:20 #idea Introduce social communication channels for students 16:10:42 #idea Do research + use existing documents from other open source communities (e.g. MetaBrainz has a private communication channel for discussions between mentors) 16:10:43 jwf, something like : http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor/ ? 16:10:56 #idea Highlight work of selected applicants on Commblog 16:10:57 * jwf clicks 16:11:37 We also have little bit of How to work with students here : https://docs.fedoraproject.org/mentored-projects/gsoc/2018/index.html#how-to-work-with-students 16:11:57 skamath: Oh, interesting, this entire guide seems comprehensive, at a general level 16:12:21 jwf, That's the best SoC guide out there. There are docs both for students and mentors. 16:12:51 skamath: So maybe it would make more sense for us to have "internal"-ish docs that have Fedora-specific guidelines, but strongly reference this as a tool for mentors 16:12:58 Makes no sense to reinvent the wheel and the work 16:13:12 Yep, +1 to that 16:13:23 #link http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor/ 16:13:33 #link https://docs.fedoraproject.org/mentored-projects/gsoc/2018/index.html#how-to-work-with-students 16:13:35 +1 16:13:35 We can make some very specific Fedora mentoring things and then a link to this 16:13:55 That's definitely a much more manageable chunk of work than writing an entire guide to mentoring for GSoC 16:14:10 I think this is also a good deliverable for the Docs FAD, but will need to check in with other folks there 16:14:28 I can champion this at the Docs FAD for us then 16:14:49 Are you attending Docs FAD, jwf ? 16:15:27 #info skamath linked a helpful guide written by FLOSS Manuals (sponsored by Google) for mentoring and administering Google Summer of Code. Instead of reinventing the wheel, point this as a reference and only document Fedora-specific details in our own mentor docs 16:15:43 +1 16:15:44 skamath: Yep, I'm flying this Saturday. 16:16:15 #action jwf Bring #133 as a work task to Docs FAD; pre-prep by reaching out on Docs list for feedback (?) 16:16:21 Cool… 16:16:26 I think that wraps things up for us 16:16:30 So Justin is gonna be like : 16:16:36 .moar docs fedora 16:16:36 here fedora, have some more docs 16:16:49 jwf++ 16:17:06 lolol. Sitting in a room full of Fedora contributors hacking on some rad documentation \o/ 16:17:28 Need to get my packing game on soon, but… I'll probably save it for Friday night 16:17:29 :P 16:17:36 Anyways, I think that's all for tickets. 16:17:37 ohhh the docs fad 16:17:40 #topic Open floor 16:17:53 Anyone have anything they would like to mention or bring up? 16:18:01 not from me 16:18:01 I can join in remote when you are writing about SoC 16:18:14 jwf, If it is a possibility, let me know. 16:18:56 skamath: ACK. I will work on keeping the team in the loop for any CommOps-specific tasks during the FAD. 16:19:11 \o/ 16:19:24 Okay, if that's it for today, I'm going to get ready for a work meeting in 10 minutes :P 16:19:43 As always, thanks everyone for sharing some of your energy here for an hour. :-) 16:19:54 Thank you jwf for chairing! 16:19:58 I'm not sure if I'll be around to chair next Monday's meeting, but I will make a best effort. 16:20:06 See you all in #fedora-commops! 16:20:08 #endmeeting