15:31:26 #startmeeting Fedora CommOps (2017-11-27) 15:31:26 Meeting started Mon Nov 27 15:31:26 2017 UTC. The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:31:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:31:26 The meeting name has been set to 'fedora_commops_(2017-11-27)' 15:31:40 #meetingname commops 15:31:40 The meeting name has been set to 'commops' 15:31:42 #nick commops 15:31:44 #topic Agenda 15:31:48 #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next 15:31:57 /me needs to update ^ 15:32:01 #info (1) Roll call / Q&A 15:32:03 #info (2) Announcements 15:32:09 #info (3) Action items from last meeting 15:32:11 #info (4) Tickets 15:32:13 #info (5) Open floor 15:32:15 #topic Roll call / Q&A 15:32:23 #info Name; Timezone; Sub-projects/Interest Areas 15:32:25 #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ] 15:32:28 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:32:45 #info Alberto Rodriguez S; UTC-6;CommOps (Metrics, Community engagement), DotNet (Testing), Infrastructure(Apprentice), Markerting (Contributor) 15:32:46 #info Justin W. Flory; UTC-5; CommOps, Diversity, Ambassador, sysadmin-badges 15:32:52 * jwf waves to bt0 15:32:54 #chair bt0 15:32:54 Current chairs: bt0 jwf 15:33:10 * bt0 waves back to jwf 15:33:16 I'm AFK for a couple more minutes – let's see if anyone else is around too. 15:33:26 it's ok 15:38:45 Okay, back. 15:38:55 #topic Announcements 15:39:06 Anything to share? 15:40:41 It was mostly a quiet week from my POV. 15:40:59 no, very quiet 15:40:59 #info Dhanesh B. Sabane, UTC+5:30, CommOps, Packaging, Python 15:41:21 hai 15:41:31 #info === "Fedora 25 End Of Life" === 15:41:33 Whoops. I was too late on that one 15:41:38 #link https://fedoramagazine.org/fedora-25-end-life/ 15:41:43 dhanesh95: No worries, welcome :) 15:41:45 I have something to share for announcements too o.o 15:41:57 #info === "Kernel 4.14 Test Day 2017-11-30" === 15:42:04 #link https://communityblog.fedoraproject.org/kernel-4-14-test-day-2017-11-30/ 15:42:17 @Rhea: Go for it :) 15:42:39 Given the holiday on Thursday, i'd like to thank y'all for being awesome. 15:42:54 'ts all. 15:43:26 .thank Rhea 15:43:27 jwf thinks Rhea is awesome and is happy they are helping! (Please don't forget to Rhea++ also) 15:43:38 Right back at you! 15:43:41 .thank Rhea 15:43:42 Anything else? 15:43:42 dhanesh95 thinks Rhea is awesome and is happy they are helping! (Please don't forget to Rhea++ also) 15:43:57 Rhea++ 15:43:57 dhanesh95: Karma for rhea changed to 3 (for the f27 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:44:09 * bt0 thinks Rhea is amazing too 15:46:08 #topic Action items from last meeting 15:46:16 #link https://meetbot.fedoraproject.org/fedora-meeting-2/2017-11-20/commops.2017-11-20-15.31.html 15:46: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:47:05 #info === [INCOMPLETE] "jwf Follow up with Pingou about an old patch to support Fedora Badges with Mailman3 / Hyperkitty" === 15:47:17 #action jwf Follow up with Pingou about an old patch to support Fedora Badges with Mailman3 / Hyperkitty 15:47:21 .fas x3mboy 15:47:23 x3mboy: x3mboy 'Eduard Lucena' 15:47:24 Sorry 15:47:33 #info === "bt0 bt0 work on Issue #48 and break the information into smaller actions for Marketing team, file tickets and/or contact Marketing team about it" === 15:47:33 I'm a litte late 15:47:44 Hey x3mboy! No worries. 15:47:53 #chair dhanesh95 x3mboy Rhea 15:47:53 Current chairs: Rhea bt0 dhanesh95 jwf x3mboy 15:48:43 ohh, thats is mine, complete :P 15:48:44 bt0: Any updates? 15:48:52 Awesome! 15:49:15 #info ^ Completed this past week 15:49:25 #info === "jwf Document process in upcoming internal docs writing" === 15:49:34 #action jwf Document process in upcoming internal docs writing 15:49:54 #info === [IN PROGRESS] "jwf With FAD proposal, create a proposal draft and come up with new sub-tasks to divide and conquer among team members" === 15:50:22 I have a draft in the existing template, but haven't gone much further than that. 15:50:36 #action jwf With FAD proposal, finish proposal draft and come up with new sub-tasks to divide and conquer among team members 15:51:10 #info === [COMPLETE] "jwf Announce Mindshare nomination call on mailing list, remove ticket from meeting agenda, choose final candidate and confirm with robyduck on Monday, Dec. 4" === 15:51:32 #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/CZVZEHS5XCZQ3YN5N5GMBSYULQY2IIHT/ 15:51:47 #info === [INCOMPLETE] "jwf Produce the planning flowchart from FPL's template, use for dividing tasks and planning the rest of the FAD (due: 2017-11-27)" === 15:51:59 #action jwf Produce the planning flowchart from FPL's template, use for dividing tasks and planning the rest of the FAD 15:52:27 I underestimated some of my time with the holiday last week. I'm going to be working on these more consistently this week. 15:53:04 That's all the action items – to the tickets. 15:53:05 #topic Tickets 15:53:11 #link https://pagure.io/fedora-commops/issues?tags=meeting 15:53:34 #info === Ticket #114: "Use metrics dashboard to visualize fedmsg data" === 15:53:39 #link https://pagure.io/fedora-commops/issue/114 15:55:36 I'm due for the Grafana / Grimoire comparison. I know skamath was looking into the Perceval plugin if we used Grimoire. 15:56:16 I was wondering if it would be helpful to plan out some of the types of metrics we want to show in an example dashboard. 15:57:08 Knowing what kind of stories we want to show is something that I think is helpful for pre-planning too, and maybe a little more exciting than the technical research. 15:58:14 We could do some brainstorming for that now, to make use of our time together in the meeting since the research isn't ready yet. 15:58:26 jwf need help with FAD proposal? 15:58:29 we have a collection of metric tools that can serve as a reference 15:58:44 @Rhea: Yeah, definitely. I was going to bring that up in the next ticket. :) 15:59:00 is waiting 15:59:06 i'll be more patient 15:59:41 bt0: Hmm, I was thinking less about the tools and more about the data visualizations we want to show. Other than pulling raw fedmsg data, are there trends we want to map? Or would be interesting to see? 15:59:51 @Rhea: I appreciate your enthusiasm nonetheless :D 16:00:37 For example, putting two different data sets together on one graph or chart to make comparisons. 16:01:04 I was trying to think of things in fedmsg that would be helpful to group together like that. 16:01:45 active contributors by group/country/last_seen 16:02:22 For example, the size of the Ambassadors FAS group and the number of badges earned over a period of time (looking at whether more badges means more events, since there are so many event badges). 16:02:31 cross core contributors (members of multiple groups and also core members of that groups) 16:02:39 bt0: Yeah, exactly – things like this. :) 16:02:58 #idea Active contributors by: FAS group, country, last_seen 16:03:35 #idea Ambassadors FAS group membership mapped over time to number of badges (to ask, if there is correlation) 16:04:04 #idea Cross core contributors: Users who are core members of multiple FAS groups 16:04:39 I'm trying to think of questions or problems we want to solve too. 16:04:48 that sounds a little tricky , by example, jwflory was a top badger this week and also member of Ambys but none of that badges is about events 16:04:51 Can we also visualize meeting data through fedmsg? 16:04:59 I wonder if bexelbie is around for this one, I think he's been interested in this before. 16:05:52 +1 for dhanesh95 idea (and dhanesh95++ ) 16:05:52 bt0: Karma for dhanesh95 changed to 1 (for the f27 release cycle): https://badges.fedoraproject.org/tags/cookie/any 16:05:55 bt0: Yeah, maybe filtered down to badges with the 'event' tag. It was kind of a stretch, but I was trying to give an idea of what I was talking about. 16:06:13 dhanesh95: Hmm, what kind of meeting data? Generally, yes! 16:06:35 If you peek in #fedora-commops, we can take all of those types of hooks firing off now. 16:06:45 * bexelbie reads 16:06:49 cool, number of attendees , scheduled vs runned, etc 16:07:00 So maybe we can map the frequency of meetings and the number of active contributors. Maybe there's a correlation there? 16:07:47 bexelbie: tl;dr – we're brainstorming ideas for visualization stories we want to show in the metrics dashboard while we're blocking on some technical research. Curious on your ideas for problems where data visualizations might be helpful. 16:08:26 Average time between earning the starter/new series of badges and earning a "contribution" badge 16:08:33 Meetings as data is kinda meh... 16:08:44 dhanesh95: Active contributors in a FAS group by their meeting activity? Or do you mean all meetings and all contributors? 16:08:47 So far in ... half a year? I've been to one ambassadors meeting. 16:08:52 Rhea: lol :P 16:08:55 The meeting time is "meh" for me. 16:09:05 Ideas about who is active in what areas and across areas - not concerned with the people but are we isolated groups or a large mass that cross-polinates 16:09:14 If I don't need anything from the meeting, I won't attend... 16:09:18 Average time for response on an email list 16:09:43 don't look for visualizations, in my opinion 16:09:49 jwf: I mean active contributors in a FAS group by their meeting activity. Maybe that can help us understand if it has any effect on contributors giving up and becoming inactive. 16:09:50 we don't need pretty charts, we need answers to real questions 16:09:52 imho 16:09:52 Just a thought 16:10:21 dhanesh95, I'd be interested in average time a contributor stays active first 16:10:29 Anyway that was supposed to be a me-example on how meeting times don't exactly capture every active contributor. I'm actieve as ambassador at conferences all over europe, I just don't attend meetings, I never ask for ambassador funding, etc... x_x 16:10:36 is there a pattern of activity that predicts further activity versus inactivity? 16:10:41 #idea Measure of time between earning "beginner" badges and an authentic "contribution" badge 16:11:12 this would go toward "where do we need to stage an intervention" 16:11:16 that idea is awesome 16:11:18 i.e. if we see this pattern - send an email 16:11:27 bexelbie: I love that idea. 16:11:38 #idea Measuring the "distance" between FAS groups: Are contributors active in different FAS groups? Are our sub-projects isolated groups or large mass that cross-polinates? 16:11:50 #idea Average time for response on mailing list 16:12:11 What groups go from new contributor to contribution the fastest and slowest 16:12:36 Rhea " Anyway that was supposed to be a me-example on how meeting times don't exactly capture every active contributor. I'm actieve as ambassador at conferences all over europe, I just don't attend meetings, I never ask for ambassador funding, etc... " tha is my idea of being a great ambassador 16:12:49 map specific event badges to patterns of activity and inactivity amongst recipients (where should we go for engagement) 16:13:09 @Rhea: Right – this is why building these profiles is helpful since not every group or sub-project has the same trends or patterns. 16:14:09 bt0 😄 16:14:12 bexelbie: The last I knew of the pattern of activity was in the three-month lifecycle of a Fedora contributor that bee2502 discovered. 16:14:59 #link https://jflory7.fedorapeople.org/pub/flock/2016/i-contributed-now-what/i-contributed-now-what-slides.pdf 16:15:59 #idea How long it takes a new / beginner contributor to become a core contributor the fastest or slowest (compared against different FAS groups) 16:16:19 hum... 16:16:53 bexelbie++ ooohh, that one is nice, about event badges 16:17:01 Well, for me, it depends on what a "core contributor" means? 16:17:37 #idea "Do we go back or not?": Measuring users who get an event badge against activity in the project (are people we engage with getting into our community after the event?) 16:17:37 What do you consider a core contributor? 16:17:38 For example, I don't call myself a "core contributor", I don't develop or package anything, I just write a lot and love the terminal 16:18:17 For me a core contributor is one that contribute to make the distro great and better 16:18:28 x3mboy, @Rhea: This is something that would be specific for each FAS group, I think. Some groups may not have a way to effectively measure a core contributor or not (for example, I think of Marketing). 16:18:39 Is spreading the word considered a core task to a distro? 16:18:57 It's one idea that may fit well for some profiles, but not for others. 16:19:19 Seeing how active you are, I'd say you are well within the core 😄 16:20:01 Do either of you have ideas on how to measure a core contributor for a group? figuring that out would be helpful too, even if it's specific to only one or two groups. 16:20:49 @Rhea: Heh, ask me about that after December… exams and traveling take a lot of my time 16:20:52 Core Contributor is defined in mattdm's talks as the top 10% of contributors in a category 16:20:58 without regard to type of contribution 16:21:14 let's use the definition mattdm uses to avoid confusion 16:21:41 Okay, fair. 16:21:51 I do not think that we can figure out the exact measurement that would apply to everyone (even if we take the 10% - who is the 10% and how do you measure it?) 16:22:00 We can come up with rough generic guidelines at best.. 16:22:20 #info Core contributors: Top 10% of contributors in a category (https://mattdm.org/fedora/2017flock/2017-State-of-Fedora.pdf) 16:24:14 I guess defining the category is the next thing to wrangle. But I think this gives us a fair start to ideas on the dashboard. I'll get these organized and add a comment after the meeting. 16:24:26 Anything else someone wants to throw out before going to the next ticket? 16:24:45 Going once… 16:24:55 Going twice… 16:25:00 Going thrice… 16:25:07 #info === Ticket #125: "[TRACKER TICKET] Organize a CommOps FAD" === 16:25:11 \o/ 16:25:12 #link https://pagure.io/fedora-commops/issue/125 16:26:17 So, I obviously didn't get much work done on this over the last week, but it's something that has a finite time to complete. I think it would be helpful if we figured out some of the tasks we wanted to split up now. 16:26:53 I'm still working through the things I actioned to myself earlier, but I think there's some things we could start doing independently 16:27:03 Hmm... sorry just a one more question to previous... is the dashboard supposed to just display the data, or also come to some conclusions? 16:27:17 Since we were talking about core contributors, did we drift off topic? 16:27:19 Like the logistical planning of location, estimating travel costs / budget, etc. 16:27:35 If we're just displaying the data, we don't care about who's the core contributor, that would be more of a use-case for the dashboard. 16:27:37 jwf: Is #108 still on the table?? 16:28:01 @Rhea: Hmmm… at a minimum, display the data. But if we do it well, come to conclusions too. :) 16:28:43 Then we should note that it should be easily extended per-fas-group, so every fas group should be able to better define their core contributor "requirements" 16:29:00 Or something along those lines? 16:29:03 dhanesh95: Hmmm, we haven't looked at it in a while. If you're interested, we could cover it quickly next. 16:29:11 Maybe not fas group but... category was the term used? 16:29:33 jwf: I was thinking maybe we can include it in our FAD. 16:29:37 we need to build something that can easily answer questions 16:29:41 @Rhea: That sounds right to me. That's what I had in mind too. 16:29:44 don't lock us in 16:29:51 we don't know the questions we will have in many cases 16:30:10 dhanesh95: Oh, yeah. If we could integrate the Magazine and the CommBlog into FAS, that would be legendary 16:30:26 +1 16:30:47 dhanesh95: It would probably take a little bit of research into PHP and WordPress plugins, but if someone felt confident in it, we can make it a target ticket 16:31:14 Actually, yeah, even identifying the tickets we want to focus on is something we can do independent of the other action items 16:31:21 jwf: When you say integration of Magazine and CommBlog into FAS, what exactly do you mean by that? 16:31:41 FAD, not FAS I believe typo 16:32:38 And if it wasn't typo then I'm confused 😛 16:32:47 dhanesh95: fedmsg events for when new articles published, including their authors, any other accounts that edited the article, its category, and any tags; when an article is edited and by whom; when an article receives a certain number of views (if possible) 16:33:24 Wait, d'oh 16:33:29 I said FAS… but meant fedmsg 16:33:39 * jwf sighs 16:33:43 hee hee 16:33:47 jwf: Me and skamath had a chat long time ago and he mentioned that we'll be needing Python for this. I think WordPress already has a REST API documentation. 16:33:56 #link https://developer.wordpress.org/rest-api/ 16:34:07 dhanesh95: Yeah, actually, that's right! For a few versions now. So probably even with Python then. 16:34:14 I think this would be a good candidate ticket. 16:34:32 (the #link is not quite in the right topic...err... ticket) 16:34:36 jwf: fedmsg integration would really be legendary 16:34:44 #idea Ticket #108: Metrics for CommBlog / Fedora Magazine; integrating WordPress sites into fedmsg bus (events for when new articles published, including their authors, any other accounts that edited the article, its category, and any tags; when an article is edited and by whom; when an article receives a certain number of views) 16:35:03 * dhanesh95 was about to hit undo when jwf posted the idea 16:35:23 I think it's relevant, I'll snag it and put it into the ticket as a reference later 16:37:25 For location and dates, I thought after DevConf / before FOSDEM in Brno would be the best option for the FAD. Dates being anywhere from Jan. 29 — Feb. 1. 16:37:52 For the Diversity FAD, it was held in the Red Hat office in Brno, a short distance from the DevConf venue 16:38:59 It was cost-affordable and saved us money for bringing more people together. 16:39:20 Start on Sunday 28 maybe? 16:39:42 Like afternoon when devconf is kinda sorta over... 16:39:53 One of the tasks we can start now is researching the dates and location to estimate a budget 16:39:56 Actually I'll need to know asap about the dates. 16:40:02 So I can book a room 16:40:09 The time around devconf is always busy as hell 16:40:56 we got luck last year with rooms - we may need to look at an offsite location this year 16:41:18 * jwf nods 16:42:31 #help Research for logistical planning (location, travel, budget, dates, etc.) needed 16:43:29 Yeah I can take care of it either way, on-or-off site 16:43:49 Just gib a "GO!" :] 16:44:29 :) We'll try to start earlier than later on that. 16:44:34 Anyone else have anything to throw out here? 16:45:00 bexelbie but last year we had one whole building less 😉 😉 😄 16:46:33 yes, but there are some new meetings this year :) 16:46:37 Heheh, I forgot there's a new one now too 16:46:39 #topic Open floor 16:46:49 and given the huge number of internal meetings, limited places an external meeting can be held 16:46:54 how many people are we talking? 16:46:58 5, 10, 15? 16:47:12 Not more than 10 for sure... 16:47:19 We would fit into the smallest rooms 16:47:24 bexelbie: It would be between 5-10 16:48:52 Anyone have anything to share during open floor? 16:49:07 Otherwise, we can wrap up a few minutes early. 16:49:10 Nothing worth sharing to share o.o 16:49:11 not this time 16:49:54 Well, not from me 16:50:05 I will work on the Hacking session to take some ticket 16:50:10 But for now, nothin 16:50:13 Alrighty, then I think we're good to close up. As always, thanks everyone for coming! 16:50:15 Nothing* 16:50:17 Oh, yes, the hack session 16:50:47 I will be around 30 minutes late again because of a commute I have to do for two more weeks right before the hack session 16:50:52 But I'll be there. :) 16:51:03 Happy Monday to you all! 16:51:04 #endmeeting