14:49:32 <bt0__> #startmeeting Fedora CommOps (2018-07-30)
14:49:32 <zodbot> Meeting started Mon Jul 30 14:49:32 2018 UTC.
14:49:32 <zodbot> This meeting is logged and archived in a public location.
14:49:32 <zodbot> The chair is bt0__. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:49:32 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:49:32 <zodbot> The meeting name has been set to 'fedora_commops_(2018-07-30)'
14:49:46 <bt0__> #meetingname commops
14:49:46 <zodbot> The meeting name has been set to 'commops'
14:49:56 <bt0__> #nick commops
14:50:08 <bt0__> #topic Agenda
14:50:22 <bt0__> #link https://infinote.fedoraproject.org/cgit/infinote/tree/meeting-templates/fedora-commops-meeting-next
14:50:42 <bt0__> #info (1) Roll call / Q&A
14:50:49 <bt0__> #info (2) Announcements
14:50:58 <bt0__> #info (3) Action items from last meeting
14:51:05 <bt0__> #info (4) Tickets
14:51:11 <bt0__> #info (5) Open floor
14:51:19 <bt0__> #topic Roll call / Q&A
14:51:39 <bt0__> #info Name; Timezone; Sub-projects/Interest Areas
14:51:51 <bt0__> #action commops New members, make sure you introduce yourself on the CommOps mailing list [ https://fedoraproject.org/wiki/CommOps/Join ]
14:52:00 <bt0__> 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:52:50 <dhanesh95> #info Dhanesh B. Sabane, UTC+5:30, CommOps, Join SIG, Packaging, Python SIG
14:53:03 <dhanesh95> bt0__: o/
14:53:20 <bt0__> #info Alberto Rodriguez Sanchez; UTC-5; CommOps, Marketing, Infra Apprentice, DotNet and more
14:53:36 <bt0__> hi Dhanesh
14:53:45 <dhanesh95> Hey Alberto.
14:53:51 <dhanesh95> Just the two of us, I think.
14:53:52 <bt0__> #chair dhanesh95
14:53:52 <zodbot> Current chairs: bt0__ dhanesh95
14:54:29 <bt0__> Yes probably
14:55:26 <dhanesh95> If it's just the two of us, I think it'd be safe to skip it.
14:55:30 <bt0__> Let's wait a little
14:55:30 <fcommops-tg2> <bee2502> hi!
14:55:45 <dhanesh95> @bee2502: Hey! o/
14:55:51 <bt0__> hi bee o/
14:56:00 <fcommops-tg2> <bee2502> o/ bt0 and shanesh95
14:56:06 <fcommops-tg2> <bee2502> o/ bt0 and dhanesh95
14:57:15 <bt0__> dhanesh95: or just a quick meeting
14:58:02 <bt0__> #topic Announcements
14:58:13 <commopsbot> fedocal.meeting.update -- pfrields updated the "Workstation WG" meeting from the "workstation" calendar https://apps.fedoraproject.org/calendar/meeting/6411/
14:58:24 <bt0__> #info === Call for Outreachy mentors for Winter 2018 ===
14:58:33 <bt0__> #link https://communityblog.fedoraproject.org/outreachy-mentors-winter-2018/
14:59:46 <bt0__> i don't have any more announcements :(
14:59:59 <dhanesh95> bt0__: Flock schedule is out
15:00:38 <jwf|m> I am a little bit here too
15:00:51 <dhanesh95> jwf|m: o/
15:00:52 <bt0__> hi jwf o/
15:01:19 <jwf|m> o/
15:02:23 <bt0__> #info === Flock 2018 schedule is released ===
15:02:30 <bt0__> #link https://flock2018.sched.com/
15:02:33 <bt0__> awesome
15:04:13 <jwf|m> \o/
15:04:27 <jwf|m> I have no additional announcements than what has already been said 🙂
15:04:35 <bt0__> someone has another announcement?
15:04:52 <dhanesh95> Nothing from my side
15:05:27 <bt0__> cool, next topic
15:05:30 <bt0__> #topic Action items from last meeting
15:06:41 <bt0__> #link https://meetbot.fedoraproject.org/fedora-commops/2018-07-16/commops.2018-07-16-14.37.html
15:06:50 <bt0__> #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:07:00 <bt0__> #info === [In Progress] jwf will finish the article "CommBlog article: Appreciation Week announcement" ===
15:07:19 <bt0__> #link https://pagure.io/fedora-commops/issue/110
15:07:38 <bt0__> Re-action, right?
15:07:39 <jwf|m> By Wednesday for sure
15:08:08 <jwf|m> Yes please, just to keep it on the next meeting agenda for follow-up
15:08:20 <jwf|m> Semi-related, I also made some minor tweaks to the contrib. stories template
15:08:28 <bt0__> #action jwf will finish the article "CommBlog article: Appreciation Week announcement"
15:08:28 <jwf|m> s/template/issue template
15:09:00 <bt0__> #info === [COMPLETED] "bt0 will send email asking about the final plan of FLOCK 2018 workshop" ===
15:09:12 <bt0__> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/message/VBEFALOYI26AJR7WGKVAKPXBR5NEWDCJ/
15:09:36 <bt0__> just for documentation ;)
15:10:01 <jwf|m> Thanks bt0, I did see that
15:10:07 <dhanesh95> jwf|m: Need your inputs on this one
15:10:10 <jwf|m> Thanks for opening that topic up, it's also on my list to reply there
15:10:21 <dhanesh95> We were a bit confused at the last meeting.
15:10:50 <jwf|m> Yeah – if it's marked for a ticket discussion, we can discuss this meeting
15:10:56 <jwf|m> Real-time chat would be helpful for this
15:11:17 <jwf|m> Especially since we have both of you two here now, and you won't be able to attend Flock this year
15:11:43 <dhanesh95> +1
15:12:26 <bt0__> +1
15:12:41 <jwf|m> Cool, let's revisit during tickets 👍
15:12:46 <bt0__> let me jump to the tickets
15:12:59 <bt0__> #topic Tickets
15:13:03 <dhanesh95> bt0__: Those are the only past action items?
15:13:14 <bt0__> yes
15:13:44 <jwf|m> Sweet
15:13:45 <bt0__> #link https://meetbot.fedoraproject.org/fedora-commops/2018-07-16/commops.2018-07-16-14.37.html
15:14:35 <bt0__> wait, one more but it´s about the next ticket
15:14:39 <bt0__> so...
15:14:59 <bt0__> #link https://pagure.io/fedora-commops/issues?status=Open&tags=next+meeting
15:15:11 <bt0__> #topic Ticket #110: "Fedora Appreciation Week 2017"
15:15:22 <bt0__> #link https://pagure.io/fedora-commops/issue/110
15:15:31 <bt0__> #link https://screenshots.firefox.com/ZTV0ZlHbq16vevZt/etherpad.persephone.cloud
15:15:39 <bt0__> #link https://communityblog.fedoraproject.org/?p=5376&preview=1&_ppp=dbe0f8ee96
15:16:32 <bt0__> maybe i need update some of those links
15:17:39 <jwf|m> The contrib. stories is happily published 🙂
15:17:40 <jwf|m> The Google Doc for the article in progress is probably helpful to link
15:17:56 <jwf|m> I can't pull it up because #FirewallProblems
15:18:59 <jwf|m> Hah, but it's in my browser history:
15:19:00 <jwf|m> #link https://docs.google.com/document/d/1CZbKirCS7OWY2pxjoI0-twA59n__gWqjjNaa3JyNIAQ/edit
15:19:15 <bt0__> cool
15:19:24 <jwf|m> bt0: Did you have anything you wanted to focus on here specifically?
15:20:42 <bt0__> we need some strategies to "double the number of contributor stories by November"
15:21:39 <bt0__> we have this:
15:21:48 <bt0__> #link https://flock2018.sched.com/event/Fjdd/thank-the-fedora-community-launching-fedora-appreciation-week
15:22:15 <bt0__> that is awesome
15:23:00 <jwf|m> Yes 🙂 algogator++
15:23:12 <jwf|m> bt0: I think it might be helpful to follow-up on this post-Flock?
15:23:29 <jwf|m> I think the intro article to be published before Flock combined with actual outreach at Flock may help
15:23:51 <jwf|m> Depending on how it goes, I may try to collect stories from people and file issues on their behalf
15:23:55 <jwf|m> But haven't thought about it too much yet
15:24:00 <jwf|m> I think algogator's session will help
15:24:11 <bt0__> sure
15:24:21 <jwf|m> #nick jwf
15:24:58 <bt0__> and about how do we kick off the event?
15:25:24 <jwf|m> I havne't thought about it in depth, but I started to when I outlined the draft
15:25:27 <jwf|m> * haven't
15:25:49 <jwf|m> I think promotion the week before is the most important, with CommBlog + social media coverage
15:26:03 <jwf|m> During the week of, I think it would be helpful to publish contributor stories daily
15:26:15 <jwf|m> (Writing and scheduling these in advance should make it possible)
15:26:25 <jwf|m> Technically we already have enough to schedule one per day
15:26:44 <jwf|m> Some outreach to the announce@ mailing list the week before might also be helpful
15:26:57 <jwf|m> Maybe nb can show us the neat trick to make zodbot speak in every channel it's in too
15:27:14 <bt0__> (and i don't know if the cupcake idea beats the package/box idea)
15:27:31 <jwf|m> #idea Promotion the week before with CommBlog reminder (a pointer post, doesn't need to be long) and social media promotion
15:27:41 <bt0__> the broadcast idea is amazing
15:27:45 <jwf|m> #idea Daily posts during FAW with contributor stories on the Community Blog
15:28:06 <jwf|m> #idea Also posting to announce@ mailing list the week before
15:28:22 <jwf|m> #idea On Day 1 of FAW, use secret zodbot command to post a FAW reminder in all of its channels
15:28:29 <jwf|m> And then, lastly, I think the real work is at the end
15:28:44 <jwf|m> I think the next week, we should do a wrap-up or retrospective
15:29:03 <bt0__> +1
15:29:17 <jwf|m> Highlight some of the things people said, thank people for participating, etc.
15:29:23 <jwf|m> Doesn't need to be a monster blog post, but something short and sweet, like "Hey we did it and it was fun, let's do it again next year, you all rock, etc."
15:29:51 <jwf|m> #idea Post-FAW follow-up the week after with quick retrospective post highlighting what people said, thanking people for participating, reminder to see you again next year
15:30:19 <jwf|m> So now I've thought about it a little more in-depth 🙂
15:30:32 <bt0__> cool
15:30:36 <jwf|m> Think these ideas sound like a good idea for a launch?
15:30:41 <jwf|m> Or any other suggestions / improvements to previous ideas?
15:31:19 <jwf|m> I'm split attention trying to write Python exceptions so I'm talking off the top of my head
15:33:18 <bt0__> that ideas can will be discused in the ticket
15:33:58 <jwf|m> bt0: If you like these ideas too, it would be great if you could summarize them as a bulletpoint list in the ticket 🙂
15:34:01 <nb> jwf|m, no, no, no, announce is disabled
15:34:18 <bt0__> let me update #110 with this ideas and request comments in the mailing list
15:34:25 <nb> jwf|m, it is throttled so much to make zodbot not crash, so then it takes a long time, and it makes zodbot not respond until it is finished with every channel
15:34:46 <nb> jwf|m, maybe we could give you access to .say and you could make it announce in one channel at a time
15:36:16 <bt0__> nb, we can tempt you with some traditional Mexican candies
15:36:24 <bt0__> maybe?
15:36:46 <jwf|m> nb: Oh, sorry, I don't know the exact commands. It's okay if it's throttled, though. Is this possible at all?
15:36:46 <jwf|m> To echo a string in all channels?
15:36:50 * nb will try to get permission to give jwf|m access to .say
15:36:59 <jwf|m> Without crashing zodbot?
15:37:05 <nb> .say #fedora-commops like this
15:37:05 <zodbot> like this
15:37:07 <jwf|m> nb: It would be really, really super if we could do this
15:37:20 <jwf|m> nb: Can we file a ticket somewhere to help you keep track of this item?
15:37:37 <nb> hmm, i guess infra pagure since it involves bot permissions
15:37:39 <jwf|m> nb: Is that echoing in every channel zodbot is in?
15:37:52 <jwf|m> Okay, cool, I can file a ticket for that
15:37:54 <nb> jwf|m, no, and it won't do that
15:38:05 <jwf|m> Ohhhhh
15:38:16 <nb> you could script something to .say in whatever channels you want
15:38:32 <jwf|m> So basically, the zodbot announce functionality is permanently broken?
15:38:33 <nb> but i do't think we need everywhere, plus that is not technically possible at the moment without hanging zodbot
15:38:41 <jwf|m> Oh, yeah, if I could script a list of channels and just point zodbot at that list…
15:38:46 <nb> jwf|m, well, .announce is not designed for bots as big as ours
15:39:00 * bt0__ is taking notes
15:39:01 <jwf|m> Yeah, admittedly, that's fair
15:39:05 <jwf|m> So not really broken
15:39:13 <nb> you'd have to script your irc client to issue .say commands individually
15:40:06 <jwf|m> nb: Could we use `.say` to, say, echo a string in a channel we aren't in?
15:40:27 <nb> yes
15:40:35 <jwf|m> Brb, need to step away from keyboard for 2-3mins
15:40:36 <nb> it will do it in any channel that zodbot is in
15:40:46 <nb> jwf|m, do it once to test, i can't remember if it needs permissions or not
15:40:57 <nb> .search defaultcapabilities
15:40:57 <zodbot> nb: There were no matching configuration variables.
15:41:00 <nb> .search defaultcapability
15:41:01 <zodbot> nb: There were no matching configuration variables.
15:41:08 <nb> .search default
15:41:08 <zodbot> nb: supybot.capabilities.default, supybot.commands.defaultPlugins, supybot.commands.defaultPlugins.addcapability, supybot.commands.defaultPlugins.capabilities, supybot.commands.defaultPlugins.disable, supybot.commands.defaultPlugins.enable, supybot.commands.defaultPlugins.help, supybot.commands.defaultPlugins.ignore, supybot.commands.defaultPlugins.importantPlugins, supybot.commands.defaultPlugins.list, (1 more message)
15:41:15 <nb> .config supybot.capabilities.default
15:41:15 <zodbot> nb: True
15:41:21 <bt0__> wow
15:41:25 <nb> i guess i should do this in PM
15:42:19 <dhanesh95> .say #GlitterGallery Test
15:42:19 <zodbot> dhanesh95: Error: You don't have the say capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified.
15:42:25 <nb> ok yeah
15:43:24 <dhanesh95> Seems like it does need permissions.
15:43:24 <bt0__> ok, returning to the ticket ...
15:44:39 <jwf|m> I think we can figure this out later on too, but good to know it's a possibility
15:44:51 <jwf|m> I have a hard stop soon
15:44:57 <jwf|m> Maybe wrap up here and switch to Flock prep?
15:44:58 <bt0__> #action bt0 will update the ticket #110 with the ideas of the meeting and request comments in the ML
15:45:21 <bt0__> it's fine for me +1
15:45:31 <bt0__> open floor?
15:46:05 <dhanesh95> +1
15:46:12 <jwf|m> Maybe Flock ticket?
15:46:19 <dhanesh95> Wait, flock ticket.
15:46:26 <dhanesh95> We need to clear all doubts.
15:49:17 <bt0__> #topic ticket #160: "Plan a CommOps session for Flock 2018"
15:49:31 <bt0__> #link https://pagure.io/fedora-commops/issue/160
15:52:13 <bt0__> ok, let's do it
15:54:21 <bt0__> #link https://flock2018.sched.com/event/FjdQ/fedora-community-operations-hack-the-planet
15:56:36 <jwf|m> Hey, yep
15:57:03 <jwf|m> Generally, FAW and hopefully Grimoire will be items for the session
15:57:11 <jwf|m> @skamath will also be at Flock
15:57:27 <jwf|m> So I'm hoping we can make a game plan for how we want to tackle #114 for the next six months to a year
15:57:51 <jwf|m> For my "vision", I hoped the CommOps session would be a continuation of what we started at the FAD
15:57:59 <jwf|m> Or like a retrospective opportunity
15:58:09 <jwf|m> And try to dial in what our focuses should be for the next few months
15:58:36 <jwf|m> At the FAD, we planned until the end of 2018, but it might be helpful to revise that timeline based on reality of today and then try to modify it for where we want to go next
15:58:53 <jwf|m> ^^ all things in the back of my mind, but not at all finished thoughts
15:58:54 <dhanesh95> +1
15:59:06 <jwf|m> bt0 dhanesh95 I really wanted to know your thoughts here too
15:59:14 <jwf|m> I'm going to push if we can get remote dial-in possibilities
15:59:17 <bt0__> can we have a bluejeans or something??
15:59:28 <jwf|m> It would be great to have you present virtually, but we have had awful luck at doing this before at Flock
15:59:48 <jwf|m> bt0__: I think getting the BlueJeans is easy, but conference network is the unknown variable
16:00:09 <jwf|m> So, I wanted to ask both of you, and any other team members not at Flock, what is on your minds
16:00:15 <jwf|m> What you would like to see covered
16:00:38 <jwf|m> Any thoughts, concerns, ideas, or anything you want repped on your behalf at the sessio
16:00:40 <jwf|m> * session
16:00:45 <jwf|m> If remote dial-in is not possible
16:01:16 <jwf|m> For what it's worth, next CommOps FAD is going to have be in Mexico so we can actually get bt0__ 😜
16:01:59 <dhanesh95> jwf|m: When I was thinking about this, my thoughts were similar to yours. We should cover some ground on the FAW and Grimoire.
16:02:24 <dhanesh95> But I was also thinking to include the FM metrics into it.
16:03:37 <bt0__> the next year i can travel without problems ;)
16:04:20 <dhanesh95> I'm not sure if it can be covered with the available time but it is definitely something I would like to see some progress on.
16:04:55 * dhanesh95 is unsure when his first Flock will be.
16:05:33 <bt0__> I just want to know if I can help in something to prepare the workshop :)
16:06:43 <jwf|m> dhanesh95: The FM metrics is something my knowledge on is less. If I can rep something for you there, I'm happy to swim through people and ask questions or get feedback
16:06:44 <jwf|m> Or cover it in the session
16:07:00 <jwf|m> Hmm, we should track this somewhere
16:07:15 <jwf|m> I'm back and forth for a bit, but will be great to at least log these as #idea notes for now
16:07:16 <jwf|m> And can follow-up later
16:07:31 <jwf|m> bt0__: Is there a side of the CommOps house you're wanting to dig into? Technical or non-technical?
16:08:08 <jwf|m> Loosely, very loosely, I was wanting to try to put some more love into the technical side of the house with the metrics wheelhouse, also since some of my technical chops are a lot better than they were when this CommOps party kicked off three years ago
16:08:18 <dhanesh95> jwf|m: It'd be awesome if you can rep something for me there. I can come up with a quick list of question that I need answers on.
16:08:21 <bt0__> ohh , i love technical things
16:08:41 <nb> jwf|m, can you connect to your IRC-side client, and try .say #fedora-commops test
16:08:47 * nb thinks you have permission now
16:09:01 <bt0__> nb++
16:09:11 <jwf|m> dhanesh95: Definitely. If you can put something together for me in the ticket, that will be the best way to help us at Flock to pick it up for you 🙂
16:09:27 <jwf|m> bt0__: I'm wanting to get into some more metrics-y and data things… someday :D
16:09:38 * jwf|m has been saying this to himself for eight months
16:09:55 <jwf|m> nb: Oh, awesome! IRC ports are blocked for me on my work desktop, but I can try on my laptop later
16:10:04 <jwf|m> nb: Thanks for jumping on this.
16:10:06 <jwf|m> nb++
16:10:13 <nb> jwf|m, ok, let me know how it goes
16:10:41 <nb> jwf|m, actually, i think it should work if you do it on that client (the |m one)
16:10:55 <dhanesh95> #action dhanesh95 Put down questions which need answers for progressing FM and CB metrics - #108
16:11:02 <nb> I set the hostmask to *!*@rit/foss/captain/fedora.jflory7 so it should match
16:12:05 <jwf|m> .say Hello world!
16:12:05 <zodbot> Hello world!
16:12:21 <jwf|m> dhanesh05++ Thanks for that, sir
16:12:22 <jwf|m> Neat!
16:12:32 <dhanesh95> jwf|m: Try .say #GlitterGallery test
16:12:33 <jwf|m> nb: Looks all good to me
16:13:17 <jwf|m> .thank nb
16:13:17 <zodbot> jwf|m thinks nb is awesome and is happy they are helping! (Please don't forget to nb++ also)
16:13:33 <jwf|m> .say #GlitterGallery Testing zodbot command on behalf of dhanehs95 in #fedora-commops
16:13:33 <zodbot> jwf|m: Error: You must be in #GlitterGallery to "say" in there.
16:14:02 <dhanesh95> Ooohhh.. So jwf|m will have to be in every channel to use .say
16:14:16 <jwf|m> bt0__: If you're thinking about technical things, it might be great to round up a list of metrics wishlist items
16:14:19 <jwf|m> bt0__: And we can try to evaluate their doability at Flock
16:14:24 <jwf|m> And then later on in the year, slice them into bite-sized pieces
16:14:24 * jwf|m is thinking aloud
16:14:25 * jwf|m has to step back from keyboard again
16:14:50 <bt0__> sounds great
16:15:07 <bt0__> well, open floor?
16:15:17 * dhanesh95 needs to drop off now. Dinner time.
16:15:26 <bt0__> enjoy
16:15:34 <dhanesh95> bt0__: Thanks for chairing!
16:15:46 <bt0__> #topic Open floor
16:15:49 <dhanesh95> jwf|m: Thanks for taking out time from your busy schedule and allowing us to pick your brain.
16:15:56 <bt0__> thanks for attend
16:16:03 <dhanesh95> Aloha everyone! See you around!
16:16:15 * dhanesh95 drops mic
16:19:03 <nb> jwf|m, :( I thought it'd let you direct it anywhere
16:19:08 <nb> .say #glittergallery test
16:19:08 <zodbot> nb: Error: You must be in #glittergallery to "say" in there.
16:19:57 <jwf|m> Nothing for me for open floor
16:20:04 <jwf|m> Will be helpful to get some of this discussion into tickets 🙂
16:20:07 <jwf|m> bt0++ thanks for chairing!
16:20:52 <bt0__> well, I will close in 5
16:20:57 <bt0__> 4
16:20:59 <bt0__> 3
16:21:02 <bt0__> 2
16:21:05 <bt0__> 1
16:21:07 <bt0__> 0
16:21:10 <bt0__> #endmeeting