16:55:32 <jflory7> #startmeeting Fedora CommOps (2016-02-23)
16:55:32 <zodbot> Meeting started Tue Feb 23 16:55:32 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:55:32 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:55:32 <zodbot> The meeting name has been set to 'fedora_commops_(2016-02-23)'
16:55:36 <jflory7> #meetingname commops
16:55:36 <zodbot> The meeting name has been set to 'commops'
16:55:42 <jflory7> #topic Agenda
16:55:51 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-02-23
16:55:56 <jflory7> #info 1. Roll Call
16:56:01 <jflory7> #info 2. Announcements
16:56:05 <jflory7> #info 3. Action items from last meeting
16:56:10 <jflory7> #info 4. Tickets
16:56:34 <jflory7> #info 5. Wiki Gardening
16:56:39 <jflory7> #info 6. Community Blog
16:56:43 <jflory7> #info 7. Open Floor
16:56:47 <jflory7> #topic Roll Call
16:56:52 <jflory7> #info Name; Timezone; Sub-projects/Interest Areas
16:56:57 <jflory7> .hello jflory7
16:56:58 <zodbot> jflory7: jflory7 'Justin W. Flory' <me@justinwflory.com>
16:57:12 <jflory7> #info Justin W. Flory; UTC-5; CommOps, Marketing (Magazine), Ambassadors, Join, and more
16:57:21 <jflory7> We'll let roll call roll for a bit :)
17:00:01 <Southern_Gentlem> .hello jbwillia
17:00:01 <zodbot> Southern_Gentlem: jbwillia 'Ben Williams' <vaioof@yahoo.com>
17:00:27 <jflory7> o/
17:00:30 <jflory7> #chair Southern_Gentlem
17:00:30 <zodbot> Current chairs: Southern_Gentlem jflory7
17:01:01 <jflory7> We'll wait five more minutes for anyone else to come in
17:01:12 <jflory7> #chair bee2502_
17:01:12 <zodbot> Current chairs: Southern_Gentlem bee2502_ jflory7
17:01:14 <bee2502_> .info bee2502
17:01:14 <zodbot> bee2502_: Error: You don't have the rss 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.
17:01:35 <bee2502_> .fas bee2502
17:01:36 <zodbot> bee2502_: bee2502 'Bhagyashree Padalkar' <bhagyashree.iitg@gmail.com>
17:01:48 <Southern_Gentlem> .hello bee2502_
17:01:49 <zodbot> Southern_Gentlem: Sorry, but you don't exist
17:01:56 <Southern_Gentlem> .hello bee2502
17:01:59 <zodbot> Southern_Gentlem: bee2502 'Bhagyashree Padalkar' <bhagyashree.iitg@gmail.com>
17:02:34 <bee2502_> hi,everyone :)
17:02:55 <jflory7> Hi hi!
17:03:18 <jflory7> I'll ping decause really quick
17:04:27 <bee2502_> #info bee2502 UTC +5.30 Metrics, Elections, Badges , CommBlog
17:05:07 <keekri> .hello keekri
17:05:09 <zodbot> keekri: keekri 'Keerthana Krishnan' <contactkeerthana@gmail.com>
17:05:15 <jflory7> #chair keekri
17:05:15 <zodbot> Current chairs: Southern_Gentlem bee2502_ jflory7 keekri
17:05:24 <decause> .hello decause
17:05:25 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
17:05:29 <jflory7> #chair decause
17:05:29 <zodbot> Current chairs: Southern_Gentlem bee2502_ decause jflory7 keekri
17:05:29 * decause was deep in drafts
17:05:32 <decause> thanks all
17:05:40 <jflory7> Hi, keekri!
17:05:45 * decause waves to errbody
17:05:46 <jflory7> decause: No worries. :)
17:05:54 <jflory7> We're five after, so let's go ahead and press on to the agenda
17:05:59 <keekri> hi jflory7! decause! bee!
17:06:02 <jflory7> For reference: https://fedoraproject.org/wiki/Meeting:CommOps_2016-02-23
17:06:05 <decause> taker-away jflory7
17:06:07 <decause> :)
17:06:11 <jflory7> #topic Announcements
17:06:24 <jflory7> #info === No tickets closed in the past week ===
17:06:31 <jflory7> Anyone have anything to add?
17:06:34 <decause> Yes
17:06:58 <jflory7> Shoot. :)
17:07:03 <decause> Outreachy application period is open for summer. We have one position for kernel hacking avialable.
17:07:35 <decause> eol
17:07:45 <jflory7> #info Outreachy application period is open for summer. We have one position for kernel hacking available.
17:07:50 <jflory7> decause++
17:07:52 <jflory7> cool cool.
17:07:58 <jflory7> And GSoC will get its own area of discussion
17:08:02 <jflory7> Anything else?
17:08:04 <decause> #link https://fedoraproject.org/wiki/Outreachy/2016
17:08:19 <fale> .hello fale
17:08:20 <decause> jflory7: that is all for me
17:08:20 <zodbot> fale: fale 'Fabio Alessandro Locati' <fabio@locati.cc>
17:08:25 <jflory7> #chair fale
17:08:25 <zodbot> Current chairs: Southern_Gentlem bee2502_ decause fale jflory7 keekri
17:08:26 * decause waves to fale
17:08:32 <jflory7> Announcements, going once--
17:08:38 <jflory7> Going twice--
17:08:40 * fale waves back
17:08:48 <Southern_Gentlem> *** F23-20160222 updated lives available: http://tinyurl.com/live-respins (.iso & .torrent)  Thanks to the community of maintainers and seeders. Addt'l seeders always welcome. ***
17:08:49 <jflory7> Going thrice--
17:08:57 <jflory7> Welcome, fale! :)
17:09:00 <jflory7> Southern_Gentlem++
17:09:28 <jflory7> Alright, moving over to last week's action items:
17:09:29 <jflory7> #topic Action items from last meeting
17:09:35 <jflory7> #link https://meetbot.fedoraproject.org/fedora-meeting-2/2016-02-16/commops.2016-02-16-16.55.html
17:09:36 <keekri> Guys, my connection is a bit spotty, did you get a link I just put ?
17:09:49 <jflory7> keekri: I didn't see anything there.
17:09:54 <jflory7> #info How This Works: Completed action items from previous week are not brought up; action items with unclear or incomplete status are brought up again for an update or to be given an #action again
17:10:06 <keekri> #link https://fedoraproject.org/wiki/CommOps/Join
17:10:13 <decause> keekri++
17:10:16 <decause> yeah!
17:10:17 <decause> nice
17:10:21 <jflory7> keekri: Yep, see it now. :) keekri++
17:10:29 <keekri> I had said, We Have A Join Page Draft People! :D
17:10:50 <bee2502_> yaay ! keekri++
17:10:59 <decause> :D
17:11:11 <jflory7> Oh, wow, it's done! Let's definitely get that in Ticket #37. We'll hit that one in just a few. :)
17:11:19 <decause> nod nod
17:11:21 <jflory7> #info === jflory7 Start draft on Trac 101 article in Community Blog ===
17:11:27 <jflory7> #info Article draft created, content not started; still intending for completion by end of month
17:11:33 <jflory7> #info === decause create an onboarding series ticket on commops trac for Fedora Infra, based on cfgmgmtcamp slide deck ===
17:11:38 <jflory7> Any updates?
17:12:05 * Southern_Gentlem fixing mailing list  link on join commops page
17:12:10 <decause> jflory7: onboarding series hackfest end of this week. I'm budget site sprinting for now.
17:12:17 <decause> Southern_Gentlem++
17:12:27 <jflory7> Cool cool. Will re-action to you
17:12:30 * fale prepared the page https://fedoraproject.org/wiki/Python_Events_2016
17:12:31 <decause> jflory7: maybe thursday?
17:12:35 <decause> fale++
17:12:39 <jflory7> #action decause create an onboarding series ticket on commops trac for Fedora Infra, based on cfgmgmtcamp slide deck
17:12:40 <decause> saw that! nice work!
17:12:42 <jflory7> fale++
17:12:45 <keekri> Southern_Gentlem++
17:12:45 <zodbot> keekri: Karma for jbwillia changed to 4 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:12:45 <jflory7> Southern_Gentlem++
17:12:49 <decause> #undo
17:12:49 <zodbot> Removing item from minutes: ACTION by jflory7 at 17:12:39 : decause create an onboarding series ticket on commops trac for Fedora Infra, based on cfgmgmtcamp slide deck
17:12:52 <keekri> fale++
17:12:54 <zodbot> keekri: Karma for fale changed to 6 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:12:55 <decause> jflory7: make that due friday plz
17:12:59 * jflory7 nods
17:13:14 <decause> press 'up' key, and then add 'due friday'
17:13:16 <decause> :P
17:13:18 <Southern_Gentlem> karma for jbwillia please :)
17:13:23 <jflory7> #action decause Create an onboarding series ticket on CommOps Trac for Fedora Infra, based on cfgmgmtcamp slide deck [DUE: Friday, 2/26]
17:13:25 <jflory7> #info === decause/fale/pravins schedule a g11n vFAD organizing meeting for 2/22 or nearby ===
17:13:25 <decause> jbwillia++
17:13:31 <jflory7> jbwillia++
17:13:40 <jflory7> decause: I think this one can be deferred to Ticket #29
17:13:47 <jflory7> Was intended for today's meeting, I believe
17:13:53 <decause> kk, keep it rollin
17:13:55 <jflory7> I opt we skip ahead and save discussion for the ticket
17:13:55 <decause> :)
17:13:57 <jflory7> +1
17:14:01 <jflory7> #info === keekri open a ticket for updating join/intro pages in the wiki ===
17:14:08 <decause> keekri: :)
17:14:10 <jflory7> keekri: Saw your email this morning, haven't had a chance to reply back yet.
17:14:38 <jflory7> We can get on that my today / your tomorrow.
17:15:06 <keekri> jflory7: it's ok, kinda my fault too..
17:15:12 <jflory7> #action jflory7 Get back to keekri's email about the Join pages Trac ticket
17:15:24 <jflory7> keekri: No worries, we'll get it done. :)
17:15:29 <jflory7> #info === decause update onboarding (bootstrapping) ticket on fedora-badges trac. add concept proposal... ===
17:15:33 <keekri> Cool! :)
17:15:34 <jflory7> Related to earlier line, decause?
17:15:52 * mailga around but still working. I may not pay attention enough.....
17:15:58 <decause> jflory7: not done, maybe will do this by friday, likely will do it next week
17:16:09 <jflory7> #chair mailga
17:16:09 <zodbot> Current chairs: Southern_Gentlem bee2502_ decause fale jflory7 keekri mailga
17:16:14 <decause> I want all of the onboarding steps tickets first on commops trac
17:16:23 <jflory7> mailga: No worries, if you can't stick around, we'll get the minutes out too :)
17:16:26 * jflory7 nods
17:16:27 <decause> lets see how for we get with hacksession
17:16:36 <jflory7> decause: Will reaction verbatim for Friday
17:16:42 <decause> kk
17:16:57 <jflory7> #action decause update onboarding (bootstrapping) ticket on fedora-badges trac. add concept proposal... [DUE: Friday, 2/25]
17:17:03 <jflory7> Okay, that's all action items.
17:17:05 <jflory7> To tickets!
17:17:09 <jflory7> #topic Tickets
17:17:15 <jflory7> #link https://fedorahosted.org/fedora-commops/report/9
17:17:28 <jflory7> #info === Ticket #2 - https://fedorahosted.org/fedora-commops/ticket/2 ===
17:17:34 <jflory7> #info * "Request for a tool to converge tickets from the main teams to commops ticketing"
17:17:37 <jflory7> This ticket is beginning to stall. Do we want to put a request into motion for a tool to be developed for this? Or is it better to close the ticket as "wontfix"? What do we want to do?
17:17:44 <jflory7> decause: Saw your comment on the ticket pre-meeting
17:18:08 <decause> jflory7: yeah, see my response
17:18:12 <jflory7> I replied. ;)
17:18:16 <decause> kk, word
17:18:20 <jflory7> Anyways--
17:18:33 <jflory7> My question was how would this info be relayed to us by the sub-projects?
17:18:41 <decause> short description goes in the #halp message
17:18:49 <jflory7> Also, context to this discussion was decause's idea in the ticket, comment towards the bottom
17:18:50 <decause> jflory7: via commblog draft
17:19:03 <decause> #link https://fedorahosted.org/fedora-commops/ticket/2#comment:5
17:19:14 <jflory7> I see, so the tooling for sub-projects to get info on our radar is with Meetbot #help and CommBlog.
17:19:22 <jflory7> And the regular channels like IRC and mailing list
17:19:38 <decause> yeah, in general
17:19:39 * mailga thinks there's still the problem of duplicates. If folks don't use two tickets something could be lost.
17:20:01 <decause> in specific, i want to advertise that we are tracking the #halp fedmsg's, assuming that we actually track them ;)
17:20:09 <decause> this is likely a good job for the metrics team
17:20:13 <jflory7> mailga: decause's suggestion was to avoid two tickets. Instead, we would work in the specific sub-project's Trac and use things like MeetBot and CommBlog to help stay on tack
17:20:15 <decause> who already grok fedmsgs
17:20:16 <jflory7> * on track
17:20:28 <decause> jflory7: mostly right
17:20:50 <jflory7> decause: Yeah, I think finding a way to better track the #help messages would be useful to broadcast to the rest of Project that CommOps is listening
17:20:55 <mailga> jflory7: decause this could be the perfect solution, not sure the easiest.
17:21:46 <decause> so, instead of copying over all the tickets from an upstream trac to the commops trac (which seems like what was proposed) I suggested that teams (while having their IRC meetings) use the #help or #halp tag, to link to a ticket, and provide a description. This will "get it on our radar" because we (eventually) are going to have a tool that aggregrates all of those help messages and adds them to a queue of soem kind that we can then triage as comm
17:21:58 * jflory7 wonders... do we want something like an email to the list at the end of a group's meeting with any #help messages? Or do we want a website to serve this info?
17:22:36 <jflory7> I think best course of action for today is determine how we want to handle the #help data and make sure that it gets to us, and isn't accidentally missed in IRC
17:22:38 <decause> jflory7: we already have datagrepper and fedmsg. perhaps posting those messages (raw at first) to a mailing list would be good? At least having them show up in a file somewhere.
17:22:54 <jflory7> decause: I like the idea of automated emails to the list, personally
17:23:11 <jflory7> Like at the end of a meeting, all #help messages with a link to the møte log could hit our list
17:23:18 <decause> jflory7: I don't /think/ the #help messages are too noisey
17:23:21 <jflory7> I think trying to get something like that running would be preferential
17:23:36 <jflory7> decause: I don't think so either, as bee2502_ showed, they are one of the least used commands too.
17:23:44 <decause> jflory7: yeah, and python's smtplib or something simliar would be a pretty low barrier to entry
17:24:04 <jflory7> Probably not too difficult to program with the existing infrastructure at our disposal.
17:24:07 <decause> a simple tweak to the zodbot is likely the way to go?
17:24:17 * jflory7 is thinking so
17:24:23 <jflory7> Any other comments to add?
17:24:28 <jflory7> Otherwise, let's put it to vote as a proposal
17:24:34 <decause> zodbot already emails the logs places, maybe we could have it parse out the help messages and email those specifically to us?
17:24:41 <decause> orrrrrr
17:24:55 <decause> we can use FMN to give us IRC notifications AND email notifications
17:25:01 <decause> FMN is the tool to use I reckon
17:25:03 <decause> yes
17:25:23 <bee2502_> FMN ?
17:25:44 <jflory7> I'm not familiar with FMN either
17:25:51 <jflory7> Or maybe I am, but didn't know what its name was
17:26:00 <decause> https://apps.fedoraproject.org/notifications
17:26:04 <decause> #link https://apps.fedoraproject.org/notifications
17:26:05 <jflory7> Ahhh, that
17:26:19 <decause> the only issue is that I think you can only sign up for emails related to a fAS account
17:26:28 <jflory7> Had a sneaking suspicion that's what it was
17:26:48 <decause> perhaps we can create a new FAS (CommOpsBot or something) and list it's mailing address as the commops mail list as a hack?
17:26:52 <decause> this is a hack though
17:26:55 <decause> but would be easy :)
17:27:03 <decause> let's move on though, and update the ticket with ideas from today
17:27:09 <decause> we're at half past now
17:27:18 <decause> whatever we decide, we should def advertise on the commblog afterwards
17:27:25 <jflory7> Yeah, this sounds doable to me.
17:27:32 <jflory7> Let's discuss technical details in ticket or on the list
17:27:35 <jflory7> Let's vote on this proposal real fast
17:27:36 <jflory7> #proposed To help keep #help MeetBot messages on CommOps radar, the best course of action is to begin developing or request a tool that will take those notifications at the end of a meeting and email a list of #help messages and møte URL to CommOps mailing list
17:27:37 <jflory7> +1
17:27:41 <decause> SideNote: Event Report Hack Session will be hacksession #2 this week :P
17:28:07 <decause> +1, with the addition of "posting to IRC" if possible
17:28:16 <jflory7> Will revise proposal to include that
17:28:36 <bee2502_> +1
17:28:44 <jflory7> Going once--
17:28:49 <jflory7> Going twice--
17:28:56 <jflory7> Going thrice--
17:29:00 <jflory7> #agreed To help keep #help MeetBot messages on CommOps radar, the best course of action is to begin developing or request a tool that will take those notifications at the end of a meeting and email a list of #help messages and møte URL to CommOps mailing list and IRC
17:29:07 <jflory7> info === Ticket #11 - https://fedorahosted.org/fedora-commops/ticket/11 ===
17:29:10 <jflory7> #info === Ticket #11 - https://fedorahosted.org/fedora-commops/ticket/11 ===
17:29:15 <jflory7> #info * "Infra + Websites Collaboration: Budgeting Site"
17:29:19 <jflory7> Three months since ticket was last updated. decause want to give any updates on the status of this or how other CommOpsers can help?
17:29:25 <jflory7> Mostly an update to be given by decause :)
17:30:23 <jflory7> Some extra comments were added to the ticket earlier as well
17:30:36 * decause digs for comments link
17:30:52 <decause> #link https://fedorahosted.org/fedora-commops/ticket/11#comment:5
17:31:07 <decause> tl;dr - I have a working dev encvironment
17:31:33 <jflory7> Heheh, I missed the screenshot
17:31:37 <decause> anyone who wants to help can clone the websites repo, and check out the 'budget' branch
17:31:43 <decause> NOTE
17:32:00 <decause> the master branch of the websites repo is used in production...
17:32:01 <decause> so
17:32:10 <decause> DO NOT HACK ON THE MASTER BRANCH ZOMG
17:32:14 <decause> :P
17:32:18 <jflory7> heheh
17:32:19 <decause> I have never been more scared of git in my life
17:32:21 <jflory7> decause: Link to repo?
17:32:21 <decause> :P
17:32:36 <decause> #link ssh://git.fedorahosted.org/git/fedora-web.git
17:33:03 <decause> #info PLEASE talk to the websites team to get started on this, there is a process you should go through to become a member
17:33:29 <jflory7> #info decause has a working development environment of the Budget website; progress is ongoing, as mentioned above, if you want to get involved, work with the Fedora Websites team for more info on getting involved
17:33:32 <decause> #info this repo is quite large (hundreds of MB), and will likely be moved to pagure.io in the near future
17:33:34 <jflory7> Cool. Next ticket?
17:33:43 <decause> jflory7: yes, let's keep it rolling
17:33:54 <jflory7> #info === Ticket #17 - https://fedorahosted.org/fedora-commops/ticket/17 ===
17:33:59 <jflory7> #info * "Interview Fedora's Diversity and Inclusion Advisor, tatica"
17:34:02 <jflory7> Checking in on status of tatica and if we're clear to send to the announce list
17:34:07 <decause> jflory7: negative
17:34:11 <jflory7> Gotcha.
17:34:36 <decause> tatica unfortunately had *another* death in the family, and we want to keep her plate empty for a while longer :/
17:34:43 <jflory7> #info Announce email deferred; will check in again next week
17:34:45 <jflory7> :(
17:34:48 <jflory7> That's awful...
17:34:51 <decause> yeah :'(
17:34:54 <jsmith> :-(
17:35:05 <jflory7> I'll be keeping my thoughts with her this week
17:35:15 <jflory7> #info === Ticket #29 - https://fedorahosted.org/fedora-commops/ticket/29 ===
17:35:22 <jflory7> #info * "G11n - proposal for the group revitalization"
17:35:26 <jflory7> Last week, we opted to make today's meeting the planning session for the G11n vFAD / other relevant activities.
17:35:39 <jflory7> Not sure if any of the G11n people happen to be lurking in here now?
17:35:46 <decause> noriko?
17:35:51 <decause> pravins?
17:36:23 <jflory7> Looks like pravin disconnected from the net half an hour ago
17:36:24 <decause> I know that there is a thread somewhere (telegram maybe??) talking about using the EMEA ambassador meeting as a place where g11n planning can be done a lil bit
17:36:35 <jflory7> decause: It was the EMEA Telegram, yeah
17:36:46 <decause> telegram is a non-ideal channel for these conversations for exactly this reason
17:36:55 <jflory7> not sure what his FAS is, but someone wanted to head that
17:36:56 <jflory7> yeah
17:37:10 <decause> jflory7: let's just open a good-ole-fashioned email loop with the two of them, see if we can't get them into a hack session?
17:37:19 <decause> (unlikely considering the time difference)
17:37:22 <decause> unless...
17:37:23 <jflory7> decause: noriko and pravins?
17:37:33 <decause> we hack *really* late, so that it is their morning time :)
17:37:40 <jflory7> True. Maybe it's possible!
17:37:46 <decause> .fasinfo noriko
17:37:47 <zodbot> decause: User: noriko, Name: Noriko Mizumoto, email: noriko.mizumoto@gmail.com, Creation: 2006-06-01, IRC Nick: noriko, Timezone: UTC, Locale: en, GPG key ID: F45683CA, Status: active
17:37:49 <jflory7> Want to take that action?
17:37:50 <zodbot> decause: Approved Groups: cla_fedora cla_done docs l10n-commits cvsfedora @cvsl10n fedorabugs docs-writers cla_fpca
17:38:11 <decause> noriko is only in UTC?
17:38:18 <decause> .fasinfo pravins
17:38:19 <zodbot> decause: User: pravins, Name: Pravin Satpute, email: psatpute@redhat.com, Creation: 2007-11-14, IRC Nick: pravins, Timezone: Asia/Kolkata, Locale: en, GPG key ID: 3EDF779F, Status: active
17:38:20 <jflory7> She's in Japan, I thought
17:38:23 <zodbot> decause: Approved Groups: fedorabugs cla_fedora cla_done @cvsredhat-config-language packager @svnsystem-config-language gitenglish-typing-booster @svnitranslit svnlohit @gitibus-rawcode @gitibus-sayura +gitliberation-fonts @gitindic-typing-booster cla_fpca @gitibus-indic-table provenpackager ambassadors marketing
17:38:28 <jflory7> .localtime Tokyo
17:38:29 <zodbot> jflory7: User "Tokyo" doesn't exist
17:38:34 <jflory7> Hmm
17:38:37 <decause> .localtime noriko
17:38:38 <zodbot> decause: The current local time of "noriko" is: "17:38" (timezone: UTC)
17:38:47 <decause> .localtime pravins
17:38:48 <zodbot> decause: The current local time of "pravins" is: "23:08" (timezone: Asia/Kolkata)
17:38:57 <jflory7> It's 2:38am in Tokyo right now. We might catch her if she is in Japan right now
17:39:12 <decause> so, if we hack until 10pm-ish, I think we'd be able to catch both of them maybe?
17:39:28 * decause isn't mathing very hard right now
17:39:31 <jflory7> In terms of time zones, it makes sense
17:39:42 <jflory7> More likely for noriko over pravins, I think it might be very early for him
17:39:44 <decause> kk, lets invite them to the hacksessions this week
17:40:01 <jflory7> #nick pravins
17:40:04 <jflory7> #nick noriko
17:40:12 <mailga> I also spoke with aeng sonme time ago about the revilisation of the group. Maybe he's available.
17:40:15 <decause> jflory7: I don't think #nick is a command?
17:40:16 <jflory7> #action jflory7 / decause Get pravins and noriko invited to a CommOps hack-session this week
17:40:25 <jflory7> decause: It is. :)
17:40:28 <decause> orly?
17:40:38 <jflory7> decause: It registers the name of a person even if they aren't actually present in the meeting
17:40:39 * decause is learning things everyday
17:40:49 <decause> solid
17:40:52 <jflory7> I was digging through the MeetBot docs and learned that one. It's an obscure one but useful
17:40:54 <jflory7> Anyways...
17:40:55 <jflory7> Next ticket?
17:40:57 <decause> yes
17:41:02 <decause> we're almost at 75%
17:41:04 <jflory7> #info === Ticket #37 - https://fedorahosted.org/fedora-commops/ticket/37 ===
17:41:08 <jflory7> #info * "Making a "Join" series on the wiki"
17:41:13 <decause> \o/
17:41:13 <jflory7> #info 8-step process was approved in the ticket; jflory7 needs to begin drafting the CommOps Join page and get that going
17:41:16 <jflory7> Actually--
17:41:17 <jflory7> #undo
17:41:18 <zodbot> Removing item from minutes: INFO by jflory7 at 17:41:13 : 8-step process was approved in the ticket; jflory7 needs to begin drafting the CommOps Join page and get that going
17:41:19 <decause> now is your time to shine keekri
17:41:32 <jflory7> #info 8-step process was approved in the ticket; keekri already drafted and got the Join page up on the wiki!
17:41:46 <jflory7> keekri++
17:41:53 <jflory7> #link https://fedoraproject.org/wiki/CommOps/Join
17:42:20 <decause> keekri++
17:42:23 <decause> next
17:42:24 <jflory7> I think all that's left for this ticket is getting it integrated across the rest of the wiki.
17:42:33 <jflory7> So a little wiki gardening and final review of the Join page, /me thinks
17:42:38 <decause> nod nod nod
17:42:44 <jflory7> I can take that one on
17:43:02 <jflory7> I had a window on a $COMPUTER that had all the pages that it would need to be added to
17:43:07 <jflory7> I'll find it
17:43:27 <jflory7> #action jflory7 Work on getting the CommOps Join page integrated with the rest of the wiki's Join series for different sub-projects
17:43:35 <jflory7> Really, I think that's all that's left for that ticket
17:43:48 <jflory7> keekri did the last real bit of work that it needed :)
17:44:14 <jflory7> #info Thanks keekri for getting that page up!
17:44:16 <jflory7> Next ticket?
17:44:19 <decause> next
17:44:25 <jflory7> #info === Ticket #39 - https://fedorahosted.org/fedora-commops/ticket/39 ===
17:44:29 <jflory7> #info * "CommOps and Google Summer of Code"
17:44:34 <jflory7> #info Fedora has applied for another year of GSoC, making this our eleventh year participating in the program
17:44:38 <jflory7> Any new updates to share? What else is on the horizon for GSoC? Any questions from other CommOpsers?
17:44:47 <decause> jflory7: I heard that we missed one actually :/
17:44:54 <jflory7> :(
17:45:08 <decause> well, we still applied, so we attempted to participate
17:45:12 <jflory7> Soooo, technically this is our tenth anniversary then... :P
17:45:12 <decause> :P
17:45:18 <jflory7> Anyways--
17:45:25 <jflory7> Any formal updates on this year's progress with GSoC?
17:45:28 <jflory7> Additionally--
17:45:35 <jflory7> What is the next deadline on the horizon?
17:45:46 <decause> #info GSoC will notify us by Feb 29th with how many slots they have allotted to us
17:45:46 <jflory7> can this ticket be dropped from meeting agendas until $DATE?
17:45:50 <jflory7> Ahhh
17:45:59 <jflory7> So next Monday
17:46:00 <decause> #info CommOps will then draft a commblog post if we got >0 slots
17:46:10 <jflory7> So this one is staying on the agenda
17:46:30 * fale is new to the GSoC thing... are mentors needed before or after the Feb29th deadline?
17:46:40 <decause> jflory7: yes, since it is a general, "all the gsoc things" ticket
17:46:59 <decause> fale: before, during, and after :)
17:47:23 <decause> fale: #fedora-summer-coding in IRC, and summer-coding@fp.o mail list, IIRC
17:47:25 <jflory7> decause: Is there an actual hard deadline or distinguishment for mentors being added to the GSoC page?
17:47:40 <jflory7> Or is it more of a mentors available to help in Fedora sort of thing?
17:47:51 * jflory7 knows there are specific project mentors and general mentors (in a sense)
17:48:03 <decause> I guess there is a distinction between GSoC Mentors, and general "i'm available to help people" mentors
17:48:04 <fale> thanks
17:48:05 <jflory7> Any Fedoran can be involved with the GSoC program over IRC and the mailing lists
17:48:21 <decause> I will find out more information, they changed the program since last I participated
17:48:24 <jflory7> decause: Yeah, cool, that's what I was thinking.
17:48:24 <decause> the answer is likely here:
17:48:35 <decause> #link http://summerofcode.withgoogle.com/
17:48:49 <jflory7> We can look deeper into that, it's a good question.
17:48:56 <jflory7> I think that really wraps up this ticket?
17:49:00 <jflory7> Until next week, anyways
17:49:04 <jflory7> Next topic?
17:49:10 <jflory7> That was our last ticket
17:49:17 * jflory7 notes we're in the final ten minutes...
17:49:31 <jflory7> Going once--
17:49:38 <jflory7> going twice--
17:49:42 <bee2502_> I think you apply to be a GSoC mentor
17:49:53 <jflory7> Going thrice--
17:50:19 <jflory7> #topic Wiki Gardening
17:50:21 <decause> bee2502_: yes, mentors will be able to apply within our organization if/when we are accepted
17:50:27 <jflory7> #nick NewMembers
17:50:28 <jflory7> #action NewMembers Add your timezone / interests on CommOps Wiki [ https://fedoraproject.org/wiki/CommOps ]
17:50:39 <jflory7> Any other links or pages needing some cleaning?
17:50:49 <decause> yes...
17:50:53 <decause> something from council...
17:50:57 * decause tries to remember
17:51:11 <decause> nope, not gonna bock on it. LIkely the budget.next page
17:51:16 <decause> s/bock/block
17:51:25 <jflory7> I remember mattdm saying in channel about adding a column to a page. :)
17:51:29 <jflory7> But it's slipping me too
17:51:29 <bee2502_> https://developers.google.com/open-source/gsoc/resources/mentors jflory7 fale
17:51:33 <decause> jflory7: we did that already
17:51:38 <jflory7> decause: mhmm
17:51:39 <decause> ;)
17:51:41 <decause> mattdm++
17:51:45 <jflory7> bee2502++
17:51:55 <jflory7> bee2502_: I think that's exactly it
17:52:05 <bee2502_> Should we add a link to fedora-stats-tools repo to commops page ? It has some really interesting stats tools
17:52:05 <jflory7> I will actually make sure that link gets added to the GSoC ticket
17:52:19 <jflory7> #action jflory7 Add GSoC mentors page to the GSoC Trac ticket
17:52:25 <jflory7> bee2502_: It's not there already?
17:52:30 <decause> #info /me is pleased to see OpenHatch getting a shout-out on the GSoC mentors info page
17:52:31 <bee2502_> https://fedoraproject.org/wiki/CommOps
17:52:33 <jflory7> If not, then I definitely give a +1!
17:52:58 <jflory7> It sure isn't
17:52:59 <jflory7> Huh.
17:53:01 <decause> bee2502_: I think stats-tools is listed in our toolbox section?
17:53:09 <decause> if not, yeah, def
17:53:09 <bee2502_> #action add fedora-stats-tools to CommOps Toolbox
17:53:22 <bee2502_> decause - it's not
17:53:23 <decause> even if it is, there are now multiple tools within stats-tool repo too :)
17:53:32 <decause> nice! good catch bee2502
17:53:52 <jflory7> bee2502_: Try #action bee2502 add fedora-stats-tools to CommOps Toolbox :)
17:54:23 <bee2502_> #action bee2502 add fedora-stats-tools to CommOps Toolbox :)
17:54:26 <jflory7> After that, we can do a three minute CommBlog blast
17:54:33 <jflory7> Wiki gardening, going once--
17:54:36 <bee2502_> jflory7 : I see :)
17:54:38 <jflory7> Going twice--
17:54:47 <jflory7> Going thrice--
17:54:55 <jflory7> #topic Community Blog
17:54:58 <jflory7> Alright--
17:54:59 <jflory7> here
17:54:59 <jflory7> we
17:55:00 <jflory7> go
17:55:04 <jflory7> #info === This Week in CommBlog ===
17:55:08 <jflory7> #info * "Flock 2016 update: Submissions and lodging"
17:55:12 <jflory7> #link https://communityblog.fedoraproject.org/flock-2016-update-submissions-and-lodging/
17:55:17 <jflory7> #info Total Views (Feb. 18 - Feb. 23): 82
17:55:21 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1023
17:55:28 <jflory7> #info * "Fedora Infrastructure projects in IndiaHacks 2016"
17:55:32 <jflory7> #link https://communityblog.fedoraproject.org/fedora-infrastructure-projects-indiahacks-2016/
17:55:36 <jflory7> #info Total Views (Feb. 23): 53
17:55:41 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1033
17:55:46 <jflory7> The Telegram announcement channel is a useful tool…
17:55:51 <jflory7> #info === Coming Up in CommBlog ===
17:55:57 <jflory7> #info * "Heroes of Fedora (HoF) – F23 Beta" - Scheduled 2015-02-25, 8:00 UTC
17:56:02 <jflory7> #link https://communityblog.fedoraproject.org/?p=1045&preview=true
17:56:06 <jflory7> #info * "Campus Ambassadors Initiative" - Pending review
17:56:10 <jflory7> #link https://communityblog.fedoraproject.org/?p=759&preview=1&_ppp=285396513b
17:56:15 <jflory7> #action jflory7 Move forward with updating Campus Ambassadors criteria, update article, and set this on the schedule (lots of exposure will be needed on this one!!)
17:56:22 <jflory7> eof
17:56:22 * decause would really like to greenlight the campus ambassadors one before posting plz
17:56:40 <jflory7> decause: Definitely, this is a high-impact one
17:56:45 <decause> There should be *3* event reports coming from me this week for commblog...
17:56:53 <decause> plus budget site
17:56:53 <jflory7> decause: Did you happen to see my wiki rewrite of the Campus Ambassadors page?
17:56:57 <decause> plus onboarding series tickets
17:57:04 <decause> those are the top 3 priorities for hack session this week
17:57:10 <decause> jflory7: not yet
17:57:45 <decause> link?
17:58:01 <jflory7> decause: It's also related to the article, was thinking of replacing it over the weekend before we publish the article
17:58:01 <jflory7> decause++ looking forward to reading them :)
17:58:12 <jflory7> Whoops, think I timed out there for a second
17:58:14 <jflory7> Fetching now
17:58:30 <jflory7> #link https://fedoraproject.org/wiki/User:Jflory7/Scratchpad/Campus_Ambassadors
17:59:07 <decause> jflory7: this is detailed!
17:59:09 <decause> nice work
17:59:26 * decause will give it a proper read soon
17:59:30 <jflory7> Most of it is just a slightly reworked version of the original
17:59:40 <jflory7> Some important changes in how it's structured, though
17:59:41 <decause> nod nod, but still a great place to start from
17:59:49 <jflory7> Much more independent from current ambassadors program than it is now
17:59:58 <jflory7> Anyways, if that's all, I say we devote whatever time is left to open floor.
18:00:02 <jflory7> CommBlog... going once?
18:00:08 <decause> fale: your python events work will figure into our strategy here also
18:00:11 <jflory7> Going twice--
18:00:15 <decause> jflory7:
18:00:19 * jflory7 holds
18:00:38 <decause> We should do a "Fedora <3's Python: Upcoming Events" post next week
18:00:44 <jflory7> Oooohhh
18:00:46 <jflory7> +1
18:00:50 <fale> +1
18:00:57 <decause> where we just list the python conferences from fale's list, plus a few more we pull from the official calendars
18:01:18 <decause> I'm working on getting the Engineering Team's housing for PyCon 2016 together
18:01:21 <decause> which reminds me
18:01:27 <jflory7> #action jflory7 / fale / decause Collaborate on an article for the CommBlog highlighting upcoming Fedora and Python events
18:01:29 <fale> decause: if we can find more events, we can just add to the list I prepared
18:01:35 <decause> #action decause talk to jzb/stickster tomorrow about booking pycon housing
18:01:47 <decause> fale: your list is a great place to start
18:01:48 <fale> my list is only a point to start. I'm sure there are many more events
18:02:06 <jflory7> Okay, final call for CommBlog once more.
18:02:08 <jflory7> Going once--
18:02:11 <decause> fale: it isn't meant to be an exhaustive list, but a list of possible python events where Fedora people will be :)
18:02:14 <jflory7> Going twice--
18:02:17 <decause> because Fedora <3's Python :)
18:02:23 <jflory7> Going thrice--
18:02:25 <jflory7> #topic Open Floor
18:02:51 <jflory7> fale: Seriously, nice work on putting the Python page together :)
18:02:57 <jflory7> Will be a helpful and useful resource going forward
18:02:59 <decause> #info decause wants to super shout-out fale and keekri and bee2502's work this past week
18:03:09 <decause> obv jflory you've been busy too :)
18:03:09 <jflory7> +100 ^
18:03:13 <decause> really, all around
18:03:28 <jflory7> CommOps has had a good week :)
18:03:38 <bee2502_> link to the python page please ? fale
18:03:40 <decause> we're continuing to deliver on the things that commops does, and the council meeting this week was a lot of fun for me to point to the great work folks have been doing
18:03:49 <jflory7> fale++ keekri++ bee2502++ decause++
18:03:54 <decause> jflory7++
18:04:02 <bee2502_> fale++
18:04:06 <bee2502_> keekri++
18:04:10 <decause> jflory7: which nights are best hack nights for you?
18:04:17 <bee2502_> jflory7++ decause++
18:04:37 <fale> bee2502_: https://fedoraproject.org/wiki/Python_Events_2016
18:04:44 <decause> bee2502_: did you link to your FOSDEM metrics work at all here in this meeting?
18:04:48 <decause> because you totally should :)
18:05:01 <jflory7> decause: Definitely I think Tuesday nights, maybe Wednesday evenings too
18:05:16 <jflory7> Thursday nights are good but I'd like to avoid them if possible
18:05:32 <decause> jflory7: no prob, and Friday is not great for me either
18:05:39 <decause> let's plan on tonight and tomo?
18:05:50 <jflory7> Tonight works for me, 6pm til whenever
18:05:55 * jflory7 converts
18:06:05 <decause> jflory7: we've got that 8pm meeting after
18:06:08 <decause> right?
18:06:11 <jflory7> 23:00 UTC
18:06:14 <jflory7> decause: Ah, yeah!
18:06:29 <jflory7> 23:00 UTC = 18:00 US EST
18:06:48 <decause> #action decause/jflory7 attend BrickHacks sponsorship meeting tonight
18:06:59 <jflory7> Want me to Fedocal general hack-session tonight from 18:00 - 20:00?
18:07:03 <jflory7> And one for Wednesday?
18:07:05 <bee2502_> #info Metrics to analyse impact of Fedora Events like FOSDEM : https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/G6UI6IJI26KVHKND2S345K467RDEAISN/
18:07:12 <jflory7> bee2502++
18:07:16 <decause> #action decuase/jflory invite noriko/pravins to wednesday hack session
18:07:31 <decause> bee2502++
18:07:38 <decause> fantastic work there
18:07:43 <Southern_Gentlem> bee2502++
18:07:45 <zodbot> Southern_Gentlem: Karma for bee2502 changed to 9 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
18:07:48 <decause> I screwed up and didn't get the FOSDEM badge yet though :P
18:08:01 <decause> I don't think...
18:08:01 * jflory7 is super excited about those metrics and applying those methods to BrickHack
18:08:15 <jflory7> decause: Heheh, sounds like you might have to ping someone. ;)
18:08:19 <bee2502_> hehe, decause - I hope you get it soon
18:08:22 <decause> and all the other events in 2016!!
18:08:38 <jflory7> #action jflory7 Create Fedocal entry for tonight, 18:00 US EST - 20:00 US EST
18:08:43 <jflory7> decause++ for sure
18:08:45 <decause> ok, we're like almost 10 over now... timecheck :P
18:08:50 <fale> decause: I can give you the links after if you need them
18:08:52 <jflory7> Hahah, yeah
18:08:58 <jflory7> decause: One last action, for tomorrow--
18:09:01 <decause> kk
18:09:06 <decause> shoot
18:09:08 <jflory7> decause: When are you free tomorrow, local time?
18:09:13 * jflory7 wants to pop that on Fedocal too
18:09:13 <decause> yeah...
18:09:18 <decause> for hacksession?
18:09:26 <bee2502_> me too - decause
18:09:32 * jflory7 notes Marketing meeting runs from 22:00 UTC - 23:00 UTC
18:09:35 <jflory7> i.e. 5pm US EST
18:09:40 <jflory7> decause: Yeah
18:09:42 <decause> after mktg meeting at 5-6pmEST
18:09:54 <jflory7> Shoot until 9pm EST?
18:10:00 <decause> would like to pop-into the latam ambassador meeting too
18:10:02 <jflory7> ...formally, anyways
18:10:06 <decause> yeah, that sounds right to me
18:10:08 <jflory7> Ahh, yeah, forgot that was tomorrow
18:10:09 <jflory7> Cool
18:10:21 <jflory7> #action jflory7 Create Fedocal entry for tomorrow, 18:00 US EST - 21:00 US EST
18:10:29 <jflory7> Okay, so now I'm done
18:10:32 <decause> latam will just be a quick poke to remind folks to update the 'transport from airport to venue' section of the FUDCon proposal
18:10:37 <decause> kk
18:10:39 <jflory7> Anything else anyone wants to #info or #action or related?
18:10:48 <jflory7> Otherwise, I say we close out. :)
18:10:49 <decause> thanks all for coming today
18:10:54 <decause> folks are doing great work!
18:10:56 <jflory7> decause++
18:11:05 <decause> jflory7++
18:11:07 <decause> commops++
18:11:12 <jflory7> commops++
18:11:13 <jflory7> #endmeeting