14:29:15 #startmeeting Fedora CommOps (2017-10-30) 14:29:15 Meeting started Mon Oct 30 14:29:15 2017 UTC. The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:29:15 The meeting name has been set to 'fedora_commops_(2017-10-30)' 14:29:15 #meetingname commops 14:29:15 The meeting name has been set to 'commops' 14:29:15 #nick commops 14:29:22 #topic Agenda 14:29:30 #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next 14:29:37 #info (1) Roll call / Q&A 14:29:42 #info (2) Announcements 14:29:46 #info (3) Action items from last meeting 14:29:52 #info (4) Tickets 14:29:56 #info (5) Open floor 14:30:01 #topic Roll call / Q&A 14:30:07 #info Name; Timezone; Sub-projects/Interest Areas 14:30:12 #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] 14:30:19 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. 14:30:48 #info Justin W. Flory; UTC-5; CommOps, Diversity, badges-sysadmin, Ambassador 14:32:02 * bexelbie is lurking 14:32:24 * jwf waves 14:32:41 .hello2 14:32:42 x3mboy: x3mboy 'Eduard Lucena' 14:32:47 jwf, o/ 14:33:12 #chair bexelbie x3mboy 14:33:13 Current chairs: bexelbie jwf x3mboy 14:33:26 .hello bex 14:33:29 bexelbie: bex 'Brian (bex) Exelbierd' 14:33:45 .hello2 14:33:46 skamath: skamath 'Sachin S Kamath ' 14:33:53 I anticipate today being a quiet and quick meeting. bt0 is on honeymoon and bee2502 moved back to Germany this weekend. 14:34:01 * jwf waves to skamath 14:34:03 #chair skamath 14:34:03 Current chairs: bexelbie jwf skamath x3mboy 14:34:13 * skamath waves to all 14:34:15 :D 14:34:42 Don't forget to #info introduce yourself as well. :) 14:34:49 #info Name; Timezone; Sub-projects/Interest Areas 14:34:59 bexelbie, Do you know if Redhat started collaborating with Bitergia? 14:36:05 bexelbie, You might want to look into https://communityblog.fedoraproject.org/metrics-docs-flock-2017/#comment-5756 It's a very valid point IMO 14:36:27 Okay, cool, we can go ahead and get started: 14:36:28 #topic Announcements 14:36:34 #info === "Fedora Classroom Session: Fedora QA 101" === 14:36:38 #link https://fedoramagazine.org/fedora-classroom-session-fedora-qa-101/ 14:36:46 #info sumantrom leads a Fedora Classroom for Fedora QA on November 7th, 15:00 UTC. Learn how to get started with Fedora QA and help test new releases of Fedora. 14:36:52 #info === "What I have found interesting in Fedora during the week 43 of 2017" === 14:36:56 #link https://communityblog.fedoraproject.org/found-interesting-fedora-week-43-2017/ 14:36:59 * skamath is yet to get magazine badge for the post :p 14:37:00 #info Fedora 27 no-go, Mindshare, and Autumn Elections 14:37:06 #info === "Teaching metrics and contributor docs at Flock 2017" === 14:37:10 #link https://communityblog.fedoraproject.org/metrics-docs-flock-2017/ 14:37:15 #info Quick overview over what CommOps covered at their work session at Flock 2017. 14:37:17 14:37:21 Anyone else have any announcements? 14:37:40 skamath, RH has been collaborating with bitergia for a while 14:37:55 * bexelbie goes to look at the comment 14:38:00 skamath: Are you sure? Look again. ;) 14:38:19 bexelbie / skamath: I actually wanted to talk about that during this meeting specifically for the ticket 14:38:39 * jwf thought he added 'meeting' tag, goes to do that now 14:38:42 Oh sweet :D 14:38:44 Thanks 14:38:58 I read your mind, jwf :3 14:39:37 Any other announcements? 14:39:40 Going once… 14:39:50 Going twice… 14:39:55 Going thrice… 14:40:07 #topic Action items from last meeting 14:40:14 #link https://meetbot.fedoraproject.org/teams/commops/commops.2017-10-16-14.31.html 14:40:22 #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. 14:40:31 #info === [IN PROGRESS] jwf Follow up with sayan about Fedora Badges related to Fedora Infrastructure (i.e. fedora-badges #434, #441, #442); update Infrastructure on-boarding ticket once new info is available (DUE: 2017-10-23) === 14:40:38 #info Comments left in ticket, but need follow-up; re-actioning to keep on agenda 14:40:43 #action jwf Follow up with sayan about Fedora Badges related to Fedora Infrastructure (i.e. fedora-badges #434, #441, #442); update Infrastructure on-boarding ticket once new info is available 14:40:49 #info === [IN PROGRESS] bt0 work on Issue #48 and break the information into smaller actions for Marketing team, file tickets and/or contact Marketing team about it. === 14:40:56 #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/ML53D7YORTQMUS3D55QNP6DCSPETMUP6/ 14:41:02 #action bt0 work on Issue #48 and break the information into smaller actions for Marketing team, file tickets and/or contact Marketing team about it 14:41:08 #info === [COMPLETE] jwf File a new ticket against Fedora Hubs with research on Marketing team for designing the Marketing Hub later on === 14:41:13 #link https://pagure.io/fedora-hubs/issue/404 14:41:20 #info === [INCOMPLETE] bee2502 open a new ticket for F27 Release party badge. === 14:41:25 #action bee2502 open a new ticket for F27 Release party badge 14:41:32 #info === [COMPLETE] bee2502 open a new ticket to gather tickets, information CommOps wants to port to Fedora Docs. Add a link to ticket 102 === 14:41:37 #link https://pagure.io/fedora-commops/issue/118 14:41:45 #info === [INCOMPLETE] jwf Initialize the Asciidoc environment in the Fedora CommOps repo === 14:41:50 #link https://pagure.io/fedora-commops/issue/123 14:42:12 bexelbie: This ^^ was one thing I wanted to ask you about. Do you have the time to help with setting this up in a Fedora Docs-friendly style? 14:42:29 I know we ran through this at Flock, but… I should have taken better notes. :) 14:42:48 I have your picture from Flock :P 14:43:38 skamath: Oh no… not that one!! Hahahahah 14:44:25 jwf, yes, I do 14:44:25 I really need to look into the metrics. Final year in college is really hard :/ 14:44:35 I'm hardly getting any time 14:44:41 jwf, can you create a blank repo and give me admin rights where you want it? 14:44:41 bexelbie: Awesome – can I action you for this? 14:44:44 I'll setup a template 14:44:47 yes 14:44:52 bexelbie: I was hoping to do it in fedora-commops itself 14:44:55 or remind me where hte one we did for flock was 14:44:57 that is fine 14:44:58 pagure.io/fedora-commops 14:44:59 can I push there? 14:45:12 just keep in mind, that docs assumes all content htere is docs 14:45:15 I guess anyone in commops fas group can 14:45:22 you don't have to publish everything though 14:45:24 +1 14:45:37 skamath: Only me, you, Bee, and Brian have push access to the repo. 14:45:41 So bexelbie should be alright. 14:45:59 Although, I wouldn't mind seeing it as a pull request just to take a better look at it and to reference it for other projects 14:46:14 there is a template directory I use, but I will send a PR 14:46:19 * jwf nods 14:46:21 .thank bexelbie 14:46:21 jwf thinks bexelbie is awesome and is happy they are helping! (Please don't forget to bexelbie++ also) 14:46:25 I need to document hti sprocess 14:46:29 this process 14:46:34 bexelbie++ 14:46:39 #action bexelbie Initialize the Asciidoc environment in the Fedora CommOps repo 14:46:46 Okay, moving forward… 14:46:54 #info === [COMPLETE] bt0 start an email thread linking ticket 103 that we need feedback on voting badge and AMA idea or any more ideas === 14:46:59 #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/KGETPOLZV7ILSJD7EDYXNBBGJJXFLWSN/ 14:47:04 #info === [COMPLETE] bt0 send bi-weekly reminders for pending CommBlog posts on mailing list and IRC === 14:47:10 #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/ML53D7YORTQMUS3D55QNP6DCSPETMUP6/ 14:47:16 #info === [COMPLETE] bee2502 open new ticket where we can discuss how we can actions/suggestions for making CommBlog better. === 14:47:21 #link https://pagure.io/fedora-commops/issue/119 14:47:23 14:47:31 That's all the action items I had noted from last week. :) 14:47:37 #topic Tickets 14:47:40 #link https://pagure.io/fedora-commops/issues?tags=meeting 14:47:44 #info === Ticket #103: "Improving Fedora Elections Process: Improving Voter Participation" === 14:47:48 #link https://pagure.io/fedora-commops/issue/103 14:47:57 * jwf has to refresh on this ticket 14:49:14 Yeah, so we discussed this on the list… 14:49:16 #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/KGETPOLZV7ILSJD7EDYXNBBGJJXFLWSN/ 14:49:52 b ex is in 2 different meetings right now. Wow 14:50:21 Yeah, sparing him some mercy for this one. :) 14:50:28 Okay, right, so we split this discussion off into two ways 14:50:41 One with the badge option for voting and the other being the AMA idea 14:51:05 There was some mild interest in the AMA, although jkurik would need help for that since he doesn't frequent those platforms (Twitter or Reddit) 14:51:12 Don't we have a voting badge already? 14:51:23 The badge for voting is still a tough one because it requires changes to pagure.io/elections 14:51:31 skamath: For wallpapers, but not community elections. 14:52:02 jwf, Or, we can put a claim link after someone has finished elections. There might be people who don't want the badge 14:52:10 This way, both the problems are solved. 14:52:12 #help Badge for voting requires changes to Elections app (to let someone click a link after voting or click a box to receive badge after voting): https://pagure.io/elections 14:52:15 (in an easy way) 14:52:23 skamath: Yeah, in the Nuancier-style. 14:52:27 Aye. 14:53:09 For the Elections app, I think the best thing we can do is file a RFE ticket against the project to support badges 14:53:09 jwf, What's the stack on which the app is built? Python? 14:53:15 skamath: All Python. 14:53:23 I can help then :D 14:53:37 skamath: If there was ever an app that needs some development love, it would be this one. :) 14:53:50 Even if you broke the changes up gradually over time, it would still make a big difference. 14:53:56 I'll be happy to look into this one. 14:54:10 I updated the README docs for creating the development environment, but you can see the heart of the features needed in the issue tracker. 14:54:23 Sweet. You can assign me on this 14:54:41 skamath: Could you file the RFE ticket against the Elections app for badge support? 14:54:51 I'll do that. 14:54:54 And I can leave a comment in our ticket saying that you are working on some of these. 14:54:57 skamath++ 14:54:58 jwf: Karma for skamath changed to 6 (for the f26 release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:55:09 Oh, wow, I didn't give you a cookie this cycle?!? Whaaaaaat?! 14:55:19 Anyways… 14:55:27 #action skamath file a RFE ticket against the Elections app for badge support 14:55:27 You have now ;) 14:55:43 skamath: Do you want to set a first milestone date to check in on development? Like late November? 14:56:07 jwf, November mid seems fine 14:56:11 * jwf nods 14:56:53 #info skamath going to spend some time development time to improve the Elections app and try to implement some of the RFEs filed against project; will check in on development progress on 2017-11-20 meeting 14:57:05 +1 14:57:07 jwf++ 14:57:33 As for the AMAs, it's late for us to fit this into this cycle… but we can revisit after this election to prep for next summer. 14:57:55 nod nod. I think AMAs are cool 14:57:56 #info Too late to have AMAs for this election cycle, but we can revisit next election (start planning in spring) 14:58:03 Me too. 14:58:30 Okay, I think that's all for this ticket… going to leave it to skamath to file the badge support RFE and then I'll flag this ticket for follow-up on Nov. 20th. 14:58:45 #agreed Will follow up again on this ticket on 2017-11-20 14:59:08 #info === Ticket #107: "Automated Fedocal reminders to send to all mailing lists for upcoming Elections" === 14:59:13 #link https://pagure.io/fedora-commops/issue/107 14:59:57 jkurik seems to be on board with the calendar events for the election, and an election schedule seems to have solidified for this cycle now too 15:00:27 Looks like he's already offline for the day, though. 15:00:47 This one is just creating the events in Fedocal, setting up reminders for a couple of lists. 15:00:55 I can try to do this one in the next week. 15:01:47 I can take this one, if you need thelp 15:01:55 s/thelp/help/g 15:01:58 jwf, This can be done by setting up a meeting and adding list of MLs to the notification fields right? 15:01:58 x3mboy: If you have the time and cycles… that would be awesome. :) 15:02:13 skamath: Yep, comma-separated list works fine for the mailing lists, I think. 15:02:19 jwf, ok, give it to me 15:02:24 .thank x3mboy 15:02:24 jwf thinks x3mboy is awesome and is happy they are helping! (Please don't forget to x3mboy++ also) 15:02:39 #action x3mboy Set up Fedocal events for the upcoming F27 election cycle, set up automatic reminders for mailing lists mentioned in ticket #107 (due:2017-11-06) 15:02:50 I think that's all that is left for this ticket… 15:03:07 Once the events are created, I think we will be good to close the ticket 15:03:29 jwf, Should i report closing on the ticket? 15:03:29 #agreed Ticket can be closed once Fedocal events are set up 15:03:49 x3mboy: I'll leave a comment about what we discussed in the meeting, and once you create the events, you can go ahead and close it. :) 15:03:59 Ok 15:06:16 * jwf is doing ticket comment catch-up now 15:09:36 Okay, done. :) 15:09:45 #info === Ticket #114: "Use GrimoireLab tools to centralize metrics" === 15:09:50 #link https://pagure.io/fedora-commops/issue/114 15:10:02 skamath: I haven't had a chance to look at this more since we talked about it in #fedora-commops. 15:11:30 #link https://communityblog.fedoraproject.org/metrics-docs-flock-2017/#comment-5756 15:11:53 This is also the one where bexelbie may be interested too. 15:12:05 The comments there are new and interesting to me 15:12:19 I wonder if Grafana is something that would still enable us to have the same results with a metrics dashboard 15:12:38 * jwf has worked with Grafana before too, which makes it easier for /me to help with this 15:13:38 #info We received feedback in our CommBlog Flock 2017 article about Grimoire Labs and a recommendation to consider other projects that offer better long-term viability. 15:14:06 I respect the comment and the validity of it 15:14:08 #info Other alternatives to Grimoire Labs could be Grafana, Chronograf, and plenty of other types of dashboard / metric visualization suites… 15:14:08 Oh yes 15:14:15 I think we should look toward Project CHAOSS 15:14:20 part of hte Linux Foundation 15:14:30 and we need to think about both how to load our data and then what metrics make sense 15:14:43 Garfana looks really nice 15:14:44 #link https://www.linuxfoundation.org/blog/chaoss-project-creates-tools-to-analyze-software-development-and-measure-open-source-community-health/ 15:14:51 I haven't heard of chaoss 15:14:54 * skamath clicks 15:14:56 based on what skamath has said, I wonder if we couldn't pick a mature project (grimoire or others) and then get down to figuring out what we want to know 15:15:08 I wouldn't want to block on tooling here as that is the less "interesting" bit long term 15:15:26 bexelbie, Since we haven't started on anything yet, I am open to options 15:15:39 +1 to option exploratoin without long term blocking 15:16:03 I see a (possibly) potential blocker in Grimoire 15:16:18 I guess this ticket is more of a "research needed" status. 15:16:30 If there is a huge change in Kibana, I don't think Kibiter will be able to handle it 15:16:33 What does fedmsg store metrics in the backend with? Is it PostgreSQL? 15:16:40 jwf, Yes. 15:16:53 #info fedmsg stores metrics / data in PostgreSQL database 15:16:57 #link https://github.com/fedora-infra/datanommer 15:19:02 Okay, cool… 15:19:29 I can do some more research / homework into this one to weigh pros / cons 15:19:31 skamath, I am ok with any reasonable tool 15:19:36 I'll have to look into CHAOSS 15:19:40 bexelbie, me too :P 15:19:41 I think we need to get hte data in a format that can be worked on ASAP 15:19:46 so we can figure out hte metrics that matter 15:20:05 also, I met some folks from CHAOSS at OSS EU and they may be interested in looking at our data too 15:20:06 I'll help jwf with the research 15:20:22 I'll dig into it :) 15:20:31 and we may have an academic who wants to work with us on engagement for research purposes who might use fedmsg to test theories if we try them out 15:20:35 so lots of fun options going on here 15:20:37 :) 15:20:38 skamath: If you want to add a comment to the ticket with the blocker you were worried about, that would be helpful. 15:20:46 jwf, I will do that 15:20:54 bexelbie: I wouldn't be surprised to know some academia hackers that are interested in the data. 15:21:21 #action skamath Add comment to ticket #114 about possible blocker with Grimoire / Kibiter 15:21:33 +1 15:21:34 jwf, honestly the ones I met were shocked we had this rich data set 15:21:46 I suspect this may become part of my professional goals next year if I am not careful 15:21:50 #action jwf Research and compare pros / cons between Grafana and Grimoire Labs, add overview comparison to ticket #114 15:21:56 this means we have to all work together so we can share the love on conference talks :P 15:22:08 bexelbie: Everyone I meet that is interested in data and open source communities is always amazed by what we have 15:22:12 * bexelbie doesn't want this to be the bex shows off data show - this is the community's 15:22:23 bexelbie, Yes, this is more like a hidden public dataset 15:22:31 yes 15:22:39 super "please please look at this" secret 15:22:40 :) 15:22:41 Yeah, we need @bee2502 to do some awesome collaboration there too ;) 15:22:57 Anyways, anything else to note in #info or #action for this ticket? 15:22:57 :D 15:23:32 I'll dump my thoughts on the ticket 15:24:05 sweet. 15:24:16 Moving onwards and forward… 15:24:32 #info === Ticket #117: "How-to create Onboading guidelines for your team" === 15:24:36 #link https://pagure.io/fedora-commops/issue/117 15:25:00 This is the lingering work of our old on-boarding tickets 15:25:05 There's a relevant repo for this ticket too 15:25:15 #link https://pagure.io/fedora-contribution-howto 15:25:57 Hmm, for this ticket, I think the best way to make progress is to get our own contributor docs up and running in our repo 15:26:09 This ticket can probably have a dependency relationship on some of those docs tickets 15:26:21 I'm going to have dinner. 15:26:27 jwf, action me if there is anything :) 15:26:35 I think the best "next step" will be moving our "Join" page and maybe any other valuable docs we have on the wiki into the AsciiDoc format. 15:26:42 skamath: Yup, no problem! Enjoy dinner. :) 15:26:57 For this one, I'm going to do some metadata magic 15:27:53 #info Next best step for this ticket is to get our own docs published and created, then we can try to document the process for helping other sub-projects and teams do this too; jwf is already working on this in other tickets, so ticket dependency metadata will be updated and will be removed from meeting agenda 15:30:49 I've put a PR in for the adoc docs repo 15:31:36 Oh! Fantastic. 15:31:38 bexelbie++ 15:31:55 Cool! 15:32:01 I didn't see this 15:32:17 Oh, False 15:32:33 bt0 comment us in the Mktg meeting something about it 15:32:39 It looks pretty good 15:32:56 Okay, added a comment to #114 15:33:23 x3mboy: Yeah, Marketing is a team that I definitely see benefiting from this type of work… I'd like to work with you all after we figure it out in CommOps. :) 15:33:58 #agreed Will follow up with this ticket after #114 ("Porting CommOps Information to Fedora Docs") is closed 15:34:21 #info === Ticket #120: "Elect a CommOps Mindshare representative" === 15:34:25 #link https://pagure.io/fedora-commops/issue/120 15:34:31 So, this is a completely *new* ticket 15:35:07 There's a few different things happening in this ticket, actually. 15:35:15 1) Determining active / inactive members of our FAS group 15:35:22 2) Establishing a process for selecting a Mindshare representative 15:35:29 3) Selecting a Mindshare representative for F27 15:35:34 15:36:07 Oh, and I forgot to update the original ticket, our representative is required by Dec. 5th, not Nov. 7th 15:36:55 Thanks to bt0, we have a list of CommOps contributors who have not contributed to Fedora at all in some time, which will help in making a review of our FAS group members 15:37:04 I'd like to try to go through that in the next week or so 15:37:11 In the meanwhile, though— 15:38:20 For choosing our representative, I like keeping it simple. Anyone can choose to run, then anyone who is a sponsored member of the FAS group can vote for whoever decides to run. 15:38:22 * bexelbie wonders if bt0 would be willing to do that for some other fas groups ... 15:39:05 I also like the idea of keeping a caveat where if there are two people who want to run for the seat, and one just completed the last cycle, the other person gets to serve as the representative 15:39:21 Just to help keep fresh perspective and voices in the seat, give others a chance to participate, etc. 15:39:38 bexelbie: Probably, I forget the tool used to do that. :) 15:40:11 Since skamath just ran out, and bt0 and bee2502 are both away, I can put my proposal into a ticket comment. 15:40:17 We have some time for this now, which is nice 15:40:20 So not a huge rush 15:40:49 #action jwf Outline CommOps Mindshare seat nomination process in ticket #120 15:41:11 #action jwf Review inactive CommOps FAS group members, send personalized emails to inactive accounts, remove from FAS group 15:41:23 I'll aim to do that over the weekend 15:41:47 I don't want to spend too much time on this ticket since folks are missing, so we can move on ahead… 15:42:01 #info === Ticket #125: "[TRACKER TICKET] Organize a CommOps FAD" === 15:42:05 #link https://pagure.io/fedora-commops/issue/125 15:42:40 For a chance of pace, this is also a new ticket. :) But I'd like to try to organize a CommOps FAD in this fiscal year for us to work through tickets and issues we've been stuck or blocking with for some time 15:42:51 As well as establish a plan for 2018 on what we want to accomplish. 15:43:09 The ticket establishes some more of the background behind this. 15:43:46 The tl;dr of what's next to plan the FAD: beginning a round-up of tickets / tasks we want to work on in person there, doing some preliminary homework on those tasks, and then putting together the FAD proposal 15:44:13 Maybe not exactly in that sequential order, but all three of those things need to be done for a successful FAD proposal 15:44:24 And a successful event itself. 15:44:49 Again, since we're at low attendance, I'll save discussion here, and add a comment in the ticket to explain a little bit about what's next… 15:45:27 #help Need to begin highlighting long-term tickets / major tasks for FAD, figuring out what "pre-work" needs to be accomplished for a FAD, put together a proposal to fit into this fiscal year, before 2017 March 1 15:46:24 Okay, so that's all the tickets that were highlighted for the meeting… and we're just almost at full time. 15:46:26 #topic Open floor 15:46:35 Who do we still have left? :D 15:47:12 We might have worn everyone out :P 15:47:27 Okay, in that case, I'll use the last 10 minutes of this meeting time to update tickets and the mailing list 15:47:49 Thanks all for participating today! skamath++ bexelbie++ x3mboy++ 15:48:07 And bt0++ for a happy honeymoon, bee2502++ for a happy plane ticket to Germany :) 15:48:16 See you all around in the Fedora universe. 15:48:17 #endmeeting