commops
LOGS
15:29:17 <jwf> #startmeeting Fedora CommOps (2017-12-04)
15:29:17 <zodbot> Meeting started Mon Dec  4 15:29:17 2017 UTC.  The chair is jwf. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:29:17 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:29:17 <zodbot> The meeting name has been set to 'fedora_commops_(2017-12-04)'
15:29:17 <jwf> #meetingname commops
15:29:17 <zodbot> The meeting name has been set to 'commops'
15:29:17 <jwf> #nick commops
15:29:27 <jwf> #topic Agenda
15:29:32 <jwf> #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next
15:29:33 <jwf> #info (1) Roll call / Q&A
15:29:33 <jwf> #info (2) Announcements
15:29:33 <jwf> #info (3) Action items from last meeting
15:29:33 <jwf> #info (4) Tickets
15:29:38 <jwf> #info (5) Open floor
15:29:42 <jwf> #topic Roll call / Q&A
15:29:46 <jwf> #info Name; Timezone; Sub-projects/Interest Areas
15:29:46 <jwf> #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
15:29:51 <jwf> 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:30:00 <jwf> #info Justin W. Flory; UTC-5; CommOps, Diversity, Ambassador, sysadmin-badges
15:30:05 <bt0> #info Alberto Rodriguez S; UTC-6;CommOps (Metrics, Community engagement), DotNet (Testing), Infrastructure(Apprentice), Markerting
15:30:23 <bt0> hi o/
15:30:27 * jwf waves to bt0
15:30:29 <jwf> #chair bt0
15:30:29 <zodbot> Current chairs: bt0 jwf
15:30:39 <Rhea> #info Rhea the Bunny; UTC+1; CommOps, Diversity, Ambassador and all things C#/.NET
15:30:44 * Rhea grins
15:30:51 <jwf> Rhea: Afternoon! :)
15:30:52 <jwf> #chair Rhea
15:30:52 <zodbot> Current chairs: Rhea bt0 jwf
15:31:17 <jwf> Oh, I have to add the Mindshare ticket to the agenda, forgot about that one since it's due for today
15:31:30 * jwf makes quick adjustment
15:32:28 <jwf> While we wait another 3-5 minutes for some others… either of you gearing up plans for the holidays this month?
15:33:17 <Rhea> I am.... riding in snow.
15:34:17 <jwf> Rhea: Are you still able to ride the bike in heavy snow? I've never thought about that before.
15:34:19 <bt0> In Mexico this holidays are a strong religious and familiar thing
15:34:40 * bt0 see that videos Rhea++
15:34:50 <Rhea> jwf just you wait for the video from Sunday... when I get the chance to edit that :D I went like 20km out of Brno and spent another hour climbing up a hill...
15:34:58 <Rhea> Just for 2 minutes of ride down :D
15:35:04 <jwf> bt0: I've seen pictures of Christmastime in Mexico – the pictures always look beautiful!
15:35:09 <jwf> Rhea: Looking forward to it. :)
15:35:38 <bt0> Yeah :)
15:36:17 <jwf> Okay, anyone else who arrives can chime in later. Let's get started!
15:36:23 <jwf> #topic Announcements
15:36:28 <jwf> #info === Last day for election nominations ===
15:36:32 <jwf> #link https://communityblog.fedoraproject.org/autumn-elections-2017/
15:36:36 <jwf> #info Election nominations end on Dec. 4, 2017 at 23:59 UTC. If you have any nominations to make, be sure to get them in for the Council, FESCo, or Mindshare Committees now!
15:36:41 <jwf> #link https://fedoraproject.org/wiki/Council/Nominations
15:36:44 <jwf> #link https://fedoraproject.org/wiki/Mindshare/Nominations
15:36:47 <jwf> #link https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
15:37:16 <jwf> It's not too late to make a nomination… I challenge all of you to reach out to one or two people and consider nominating them. :)
15:37:20 <jwf> #info === "Fedora 27 Atomic Offers Multi-Arch Support, Workstation, Containerized Kubernetes, and More" ===
15:37:23 <jwf> #link https://fedoramagazine.org/fedora-27-atomic-offering/
15:37:27 <jwf> #info New features from the Fedora 27 Atomuc Host. Helpful if you want a quick overview to what's new and happening in the Fedora Atomic world.
15:37:33 <jwf> #info === "LISA17 Event Report" ===
15:37:37 <jwf> #link https://communityblog.fedoraproject.org/lisa17-event-report/
15:37:43 <jwf> #info nb, codeblock, bethlynn, and quaid attended the 2017 edition of LISA. Learn more in the event report on the Community Blog.
15:38:35 <jwf> nb++ codeblock++ bethlynn++ quaid++ LISA sounds like it was a good time. :) Did any of you get pictures? I would have loved to see some from the conference, I've always wanted to go to this one.
15:38:35 <zodbot> jwf: Karma for nb changed to 3 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:38:38 <zodbot> jwf: Karma for codeblock changed to 2 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:38:41 <zodbot> jwf: Karma for bethlynn changed to 1 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:38:45 <zodbot> jwf: Karma for kwade changed to 1 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:38:47 <jwf> <eof> from me on announcements!
15:39:01 <jwf> bt0, Rhea: Either of you have anything to share?
15:39:06 <bt0> no
15:39:16 <Rhea> Hmm.Nope
15:39:25 <jwf> Cool. Then forwards and onwards!
15:39:26 <jwf> #topic Action items from last meeting
15:39:32 <jwf> #link https://meetbot.fedoraproject.org/fedora-meeting-2/2017-11-27/commops.2017-11-27-15.31.html
15:39:33 <jwf> #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:39:44 <jwf> #info === [COMPLETE] "jwf Follow up with Pingou about an old patch to support Fedora Badges with Pagure commits" ===
15:39:44 <jwf> #link https://pagure.io/fedora-badges/pull-request/579
15:40:10 <jwf> As it turns out, three bean submitted a patch for this, but there's some other work required under the hood
15:40:29 <jwf> Comments are in that PR, but there's a ways to go still, if we want to get it to work in the right way. I have an eye on this ticket.
15:40:44 <jwf> #info === [POSTPONED] "jwf Document process in upcoming internal docs writing" ===
15:40:44 <jwf> #info Won't have the bandwidth to actively tackle docs efforts until after FAD planning is finished
15:41:17 <jwf> This one is obviously important, but I also realized that the FAD planning needs to happen first before I will have bandwidth to give this the attention it deserves. So on the backlog, but definitely not forgotten
15:41:30 <jwf> #info === [IN PROGRESS] "jwf With FAD proposal, create a proposal draft and logic model flowchart, create new sub-tasks to divide and conquer FAD planning" ===
15:41:30 <jwf> #action jwf With FAD proposal, create a proposal draft and logic model flowchart, create new sub-tasks to divide and conquer FAD planning
15:41:47 <jwf> And I made a start here, want to finish the logic model during the hack session today. My only objective :P
15:42:21 <jwf> <eof> on action items. Guess I only remembered to assign myself items last week, need to add some more variety. :)
15:42:26 <jwf> #topic Tickets
15:42:29 <jwf> #link https://pagure.io/fedora-commops/issues?tags=meeting
15:42:33 <jwf> #info === Ticket #114: "Use metrics dashboard to visualize fedmsg data" ===
15:42:36 <jwf> #link https://pagure.io/fedora-commops/issue/114
15:42:45 <jwf> #info Last week, we brainstormed ideas for questions to answer and made a final decision on Grimoire Labs. Next steps are installing Grimoire into the CommOps cloud and figuring out the fedmsg plugin for Perceval.
15:43:26 <jwf> I tried updating our CommOps box from F25 to F27, and all went well. I'm aiming to get Grimoire installed on there in the coming future, as a playground for us.
15:44:05 <jwf> skamath was the person who knew more about the Perceval plugin, but he's not here. I wanted to get a timeline for what we imagined the work to be.
15:44:25 <bt0> we have a commops cloud O.o
15:44:37 <jwf> I can action that to him, to try and help us understand what the work will be.
15:45:28 <jwf> bt0: Heh, yeah. Even I forgot about it until recently. When we had the CommOps GSoC slot two years ago, skamath had that box to play with statscache things. It's what he used to build his gsoc-stats project.
15:45:58 <jwf> I think skamath and bee2502 have used it for a few other smaller things in the meanwhile, but now it'll get some more action again
15:46:09 <jwf> At least, until we feel good about making a proposal to infrastructure for Grimoire
15:46:20 <jwf> But that's a ways off, not until we get the Perceval plugin
15:46:49 <jwf> Since skamath isn't here, I'm going to action him to give a rough estimate on a timeline for this
15:46:55 <jwf> I don't have much else to say on this one…
15:47:46 <jwf> #info The CommOps cloud machine is now upgraded to F27. Plan is to install Grimoire on our cloud machine to use as a playground and test environment for the Perceval fedmsg plugin.
15:47:47 <bt0> that is cool because the principal bottlenet on the FAS/Datagreapper is the slow response (or my bandwidth )from the servers
15:48:10 <jwf> #help A timeline to understand the work on the Perceval plugin is helpful, so we can make accurate estimates for how much work is required and roughly how long it will take
15:48:18 <jwf> #nick skamath
15:49:16 <jwf> #action skamath Add comment to ticket #114 (Grimoire ticket) that estimates a timeline for the Perceval fedmsg plugin development. What is required? About how much work is involved? Do you foresee any possible blockers?
15:49:52 <jwf> bt0: Yeah, exactly. statscache was the vision to help make that better. Although… I have a lot of reading up to do on all the tools.
15:50:39 <jwf> Okay, that's all I have for this…
15:50:45 <jwf> Going once…
15:50:55 <jwf> Going twice…
15:51:00 <jwf> Going thrice…
15:51:05 <jwf> #info === Ticket #120: "Elect a CommOps Mindshare representative" ===
15:51:09 <jwf> #link https://pagure.io/fedora-commops/issue/120
15:51:18 <jwf> #info Two weeks passed since the nomination opened. We agreed to finalize the seat in this meeting. As of now, jwf is the only candidate. This ticket will be closed and the seat will be confirmed with robyduck.
15:51:40 <jwf> Not sure if anyone else wants to add something here or not. This was mostly a quick update to follow up on our discussion two weeks ago.
15:51:51 <Rhea> Hmm.
15:52:07 <bt0> no, jwf is fine for me ...
15:52:35 <bt0> as candidate i mean
15:52:51 <Rhea> yup, jwf is fine for me ...
15:52:56 <Rhea> as a friend i mean huahuahua..
15:53:06 <bt0> LOL
15:53:08 <Rhea> :D
15:53:31 <jwf> :)
15:53:40 <jwf> Thanks for your support, as always.
15:53:52 <jwf> I'll move forward with confirming the seat to robyduck. That's all I have on this ticket!
15:54:00 <jwf> #info === Ticket #125: "[TRACKER TICKET] Organize a CommOps FAD" ===
15:54:01 <jwf> #link https://pagure.io/fedora-commops/issue/125
15:54:26 <jwf> Sadly, this one is still in the same spot as it was last week, albeit some offline progress I made over the weekend.
15:54:38 <jwf> But this is my sole objective for today's hack session… :P
15:55:13 <jwf> I will create the first draft of the logic model today, and then I expect the pace to quicken.
15:55:52 <jwf> It's like that one, big task that blocks the progress of other tasks, and then you spend too much time yakshaving on other things…
15:56:12 <jwf> Also, not sure if you have seen matt dm's explanation of yakshaving, but it's pretty great. :)
15:56:50 <jwf> "One minute with @fedora Project Leader @matt dm explaining yak shaving. #flock17" @marinaz https://twitter.com/marinaz/status/903791388285964289
15:56:55 <Rhea> So I booked a 10-peeps room for sunday-wednesday after devconf.cz in RH Brno, cause they're in high demand, I'll adjust the booking after we decide if we hold it here or not, and which days.
15:57:03 <jwf> Oh, yeah, let's get that in!
15:57:07 <jwf> Rhea++
15:57:07 <zodbot> jwf: Karma for rhea changed to 6 (for the f27 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:58:14 <jwf> #info Rhea booked a room from Sunday, Jan. 28 to Wednesday, Jan. 31 in the Red Hat Brno office to help ensure we get a room (since they're in high demand). Our space is guaranteed for Brno.
15:58:38 <jwf> #info The logic model flowchart is due by end of day today (at hack session)
15:58:54 <jwf> <eof> for me…
15:59:14 <jwf> Anyone else want to add anything?
15:59:20 <jwf> Going once…
15:59:30 <jwf> Going twice…
15:59:35 <Rhea> I want to...
15:59:40 <Rhea> I asked in the ticket
15:59:49 <jwf> Oh, d'oh, did I miss the comment??
15:59:59 <Rhea> https://pagure.io/fedora-commops/issue/125#comment-481645
16:00:47 <jwf> Oh, oops, I missed that
16:00:55 <jwf> Rhea: Good question
16:00:57 <jwf> So…
16:01:04 <Rhea> As I said in the comment I can take care of the organization of things in Brno, if we go with it, from food to accomodation (all things budget)
16:01:18 <Rhea> etc etc
16:01:37 <Rhea> Research costs meaning? Because I don't think that any other location will turn out cheaper.
16:01:52 <Rhea> We already save money by having people here for devconf and having empty week til FOSDEM
16:02:08 <Rhea> And the other location there, Brussels, is obviously not gonna be cheaper :D
16:02:28 <Rhea> So I don't know what's there to research, what other alternatives could be competing with this opportunity...
16:02:33 <jwf> Rhea: That would be incredibly helpful. For cost research, I see that as hotel costs for the duration of the FAD, airfare for attendees, and some budget for food, if we go out as a team for dinner somewhere nice one night
16:03:03 <jwf> Also, I think we were considering making GrimoireCon a part of our FAD too, but I need to sync up properly with skamath for his feedback on that one
16:03:41 <jwf> Okay, so I see two tasks now that come out of this:
16:03:52 <jwf> (1) Get wiki page up, confirm attendee list
16:03:55 <Rhea> where/when is that
16:04:10 <jwf> (2) Start looking into hotel options over the next week
16:04:24 <jwf> I can do #1 since I have confirmed with some people, but need to get that in public
16:04:51 <jwf> Rhea: If you wanted to begin on #2, I could use help finding a hotel for us to stay in, ideally not too far from DevConf venue.
16:04:53 <Rhea> 1) can do
16:04:55 <Rhea> 2) can do
16:04:59 <Rhea> 3) can do
16:05:01 <Rhea> next?
16:05:19 <jwf> Rhea: Heh, if you want the wiki page too, you can go for that. That would actually be a lot of help too. You could use the Diversity FAD as a template for copypasting, and then update minor details.
16:05:32 <jwf> Rhea: I can help with the bigger things like the Goals section, once I have the logic model
16:05:54 <Rhea> mkay
16:06:01 <jwf> Rhea: But the act of creating the page and updating the basic details, like dates and building an attendee list, can happen now. :) I can write those actions for you.
16:06:21 <jwf> #action Rhea Create the wiki page for the CommOps FAD, using the 2017 Diversity FAD page as a base
16:06:38 <jwf> #action jwf Reach out to CommOps members and confirm participants, add to wiki page
16:07:03 <jwf> #action Rhea Research hotel costs in Brno for the duration of the FAD (preferably near DevConf venue, but not required)
16:07:36 <jwf> Cool, so we did get some actions out of that, awesome. :)
16:07:45 <bt0> :D
16:07:53 <jwf> This takes a little bit more work off of me, which helps me out a lot too… this is my final week of classes this week
16:08:19 <jwf> Okay, now that's all I really have. Anything else?
16:08:39 <Rhea> Q: hotel evailability - with devconf or without (starting friday night ending thursday, or starting sunday night)
16:08:40 <jwf> Going once…
16:08:58 <Rhea> Prices fad only, starting sunday... right
16:09:28 <jwf> Rhea: My idea was only covering the nights of the FAD and attendees could pay their way if they wanted to go to DevConf. I didn't want to impose on budget, but I need to follow up with Brian to get an idea if it's reasonable to build that into the budget or not.
16:09:59 <Rhea> yup of course on budget only since sunday, but i mean just availability, so you know... stuff
16:10:19 <jwf> If there's a sizable portion of event budget left, it would be more reasonable to add two more nights for DevConf. If you want to check dates for both, with and without DevConf, that would be helpful
16:10:41 <jwf> I'll work on getting a more definite answer.
16:11:36 <jwf> Rhea: For me personally, I know I would need a room for during DevConf, and ideally I could avoid the hotel hop after DevConf to somewhere else for the FAD. :)
16:12:42 <Rhea> We need to book these asap too. Devconf takes sizeable amount of hotels as well.
16:13:46 <jwf> Yeah, duly noted
16:14:07 <jwf> Okay, I think we're good to switch over to open floor.
16:14:15 <jwf> Rhea++ your help here is super appreciated, srsly
16:14:18 <jwf> .thank Rhea
16:14:18 <zodbot> jwf thinks Rhea is awesome and is happy they are helping! (Please don't forget to Rhea++ also)
16:14:21 <jwf> #topic Open floor
16:14:40 <jwf> Anyone else have anything to throw out?
16:14:53 <jwf> Oh, I have one other thing to note:
16:16:02 <jwf> I'm making major headway at clearing out the CommBlog. I was blocking myself on writing an article, and finally got that done. So now, I'm trying hard to go through the queue of drafts and publish what's relevant, or clear out things to the "on hold" category if they need work.
16:16:25 <jwf> I want to have at least 75% of all drafts either published or cleared out by the end of the month
16:16:29 <jwf> We're currently at 25 drafts
16:16:44 <jwf> Anyways, just a short update on the CommBlog from me
16:16:59 <jwf> Either of you two have anything, or is that a wrap?
16:18:15 <bt0> no, nothing from me
16:18:27 <Rhea> nop
16:18:48 * bt0 is looking the commblog queue ...
16:19:28 <jwf> bt0: I appreciate those emails, by the way. I think we need to move more drafts to pending review, but it needs follow-up with the authors.
16:19:56 <jwf> bt0: Actually, do you have some extra time this week? I could use a lot of help with reaching out to authors with drafts in the CommBlog to confirm if they want it published still.
16:20:09 <jwf> Obviously, you don't have to get all of them
16:20:19 <bt0> yeah, no problem
16:20:24 <jwf> But even 10 this week and another 10 next week would be incredible
16:20:51 <jwf> bt0: Awesome!! Thanks. I will write you an action for that. Do you have a goal you want to set? 50% of drafts? All of them? What do you think you can handle?
16:21:02 <bt0> 50% is fine
16:21:20 <bt0> if i can do more i do more :)
16:22:03 <jwf> #action bt0 For 50% of all drafts in CommBlog, reach out to authors and confirm if they want their articles published or discarded (due: 2017-12-11)
16:22:24 <jwf> bt0: Yeah, exactly – set the bar at a reasonable level, and if you have time, more is always welcome. :)
16:22:26 * skamath is super late
16:22:29 <jwf> That will be so helpful
16:22:32 <jwf> .thank bt0
16:22:33 <zodbot> jwf thinks bt0 is awesome and is happy they are helping! (Please don't forget to bt0++ also)
16:22:37 * jwf waves to skamath
16:22:58 <jwf> skamath: We can actually wrap up here and move to the CommOps channel. I think we just wrapped up, but we can use your help on something. :)
16:22:58 <bt0> hi skamath
16:23:06 <skamath> Hi all :)
16:23:08 <skamath> Sure.
16:23:16 <jwf> Okay, last call for open floor…
16:23:20 <jwf> Going once…
16:23:30 <jwf> Going twice…
16:23:32 <Rhea> SOLD!!
16:23:35 <jwf> Going thrice…
16:23:38 <jwf> Sold :D
16:23:38 <Rhea> >_<
16:23:54 <jwf> Thanks all of you for coming out today, I appreciate your time :)
16:23:58 <jwf> See you all in channel!
16:24:00 <jwf> #endmeeting