17:00:21 <jflory7> #startmeeting CommOps
17:00:21 <zodbot> Meeting started Tue Nov 24 17:00:21 2015 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:21 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:00:21 <zodbot> The meeting name has been set to 'commops'
17:00:27 <jflory7> #topic Roll Call
17:00:48 <jflory7> Welcome to the CommOps meeting, everyone. To introduce yourself, format your intro like this:
17:01:19 <bee2502_> #info bee (bee2502) UTC+5.30 Metrics.Elections.Badges.
17:01:19 <jflory7> #info name, timezone, interest areas / subgroups
17:02:10 <jflory7> #info Justin W. Flory (jflory7); UTC-5; CommOps (Messaging / Communication / etc.), Marketing (Magazine), Ambassadors
17:03:13 <jflory7> We're waiting a few minutes for everyone to start rolling in.
17:04:05 <keekri> #info keekri ; UTC+5:30 ; Commops
17:04:32 <mailga> #info Gabriele Trombini (mailga); UTC+1; Ambassadors, CommOps (connecivity amongst groups, metrics), Websites, Marketing, Fedora.join SIG, Docs
17:06:02 <decause> .hello decause
17:06:03 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
17:06:34 <mailga> hello guys!
17:06:36 <decause> #info decause, UTC-5, all-the-commops-things
17:06:46 <jflory7> #chair decause lmacken threebean mattdm
17:06:46 <zodbot> Current chairs: decause jflory7 lmacken mattdm threebean
17:08:12 <decause> #topic agenda
17:08:18 <decause> #link http://etherpad.osuosl.org/commops-112415
17:08:45 <decause> 1) WikiGardening
17:09:01 <decause> 2) CommBlog
17:09:08 <decause> 3) 5tftw
17:09:15 <decause> 4) plumbing
17:09:24 <decause> 5) Outreachy
17:09:34 <decause> 6) OpenFloor
17:09:36 <mailga> !
17:09:50 <decause> #topic WikiGardening
17:10:00 <mailga> decause: also elections.
17:10:17 <jflory7> I think the Elections will fit into the CommBlog section. :)
17:10:17 <decause> 7) elections
17:10:22 <decause> but yeah, def
17:10:26 <decause> jflory7: agreed
17:10:38 <mailga> jflory7: decause agreed
17:10:47 <decause> Nice work thusfar everyone on the elections wiki info
17:11:09 <decause> I was using it yesterday to keep up with candidates
17:11:26 <decause> I think each race was fulll, except for the envs/stacks WG
17:11:26 <jflory7> Seems like the wiki has been hopping with new stuff for the Elections. jkurik mentioned it in channel too not too long back.
17:11:34 <decause> that may have changed since today though?
17:12:00 <decause> jflory7: it is the tradtional channel
17:12:22 <jflory7> If bee2502_'s EtherPad was from today, I think the Envs&Stacks election is in the same boat.
17:12:51 <decause> jkurik: we are at your disposal for more candiate information gathering and publication
17:13:08 <decause> jflory7: link for beetherpad?
17:13:12 <jflory7> #link http://etherpad.osuosl.org/fedora-election-metrics
17:13:37 <bee2502_> jflory7 : current info
17:14:04 <decause> bee2502_: way solid
17:14:12 <mailga> jkurik and bee2502_ are trying to get in touch with env&stack people....
17:14:19 <mailga> ups, sorry too late.
17:14:35 <decause> #action commops promote envs&stacks nomination on commblog
17:14:36 <jkurik> decause: what you need to know about the Elections ?
17:15:17 <bee2502_> decause : I am assisting FESCo candidates with CommBlog interviews and campaign stuff, jkurik with FAMSCo and keekri most prolly with Council. Env & Stacks position is sad.
17:15:17 <decause> jkurik: we want to help you do the things, so if you're willing to coordinate with us, we can help run tasks
17:15:48 <decause> bee2502_: it isn't uncommon for a specific sig to need some extra time for nominations
17:16:09 <decause> envs and stacks is more niche of a role than say, council or famsco
17:16:21 <decause> bee2502_: we'll likely have enough candidates soon
17:16:52 <decause> jkurik: it sounds like you're already battle-planning with commops, so just continue keeping us in the loop
17:16:53 <jkurik> decause: bee2502_ an keekri are already helping
17:17:20 <decause> jkurik: nod nod. please cc me and keep me posted so I can report back to council and community folk
17:17:25 <decause> :)
17:17:27 <decause> jkurik++
17:17:30 <decause> bee2502++
17:17:30 <bee2502_> decause : yaay ; but there have been no fresh candidates in Env & Stacks for a long time - niche agreed.
17:17:32 <decause> keekri++
17:17:44 <jflory7> Cookies for everyone!
17:17:53 <decause> ok
17:17:58 <decause> any other wiki related things?
17:18:07 <decause> going once
17:18:08 <jflory7> Outside of elections, I have nothing right now
17:18:12 <decause> going twice
17:18:14 <jkurik> zodbot: do you hear ? Cookies for everyone!
17:18:17 <zodbot> jkurik: Error: You don't have the do 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:18:21 <jflory7> lol!
17:18:27 <decause> zodbot: !!!
17:18:30 <decause> zodbot++
17:18:42 <decause> going thrice
17:18:43 <decause> ok
17:19:14 <decause> #action newmembers Update your listing on the commops wiki
17:19:38 <decause> #link https://fedoraproject.org/wiki/CommOps
17:19:47 <decause> #topic CommBlog
17:20:05 <decause> My first item is the final call for FLOCK bids
17:20:16 <decause> I reckon this went out in the weee hours of the morning today though
17:20:25 <jflory7> Went out this morning, actually.
17:20:29 <jflory7> I was up pretty late
17:20:45 <jflory7> I was up after the maintenance finished, added the pretty Flock image, and scheduled it for the "golden time"
17:20:57 <decause> jflory7: nod nod nod
17:21:06 <jflory7> So we could probably hit the social media outlets with it pretty hard this week
17:21:13 <decause> and for those following along, when is the golden time specifically?
17:21:21 <decause> jflory7: agreed
17:21:32 <jflory7> 8:00-9:00 UTC. Actually, I'll info that with the reason too
17:21:48 <decause> jflory7++
17:22:15 <jflory7> #info "Golden Time" for Publishing Articles: 7:00-8:00 UTC. Was discussed in OpenSource.com meetings that this time is ideal for reaching the most possible people in a global audience across multiple timezones. Important, but not make-or-break factor!
17:22:24 <decause> other than the call for FLOCK bids, there are a couple of priorities for us in the near future:
17:22:30 <decause> 1) Election Interviews
17:22:30 * danofsatx-n6 is here temporarily
17:22:35 <jflory7> o/
17:22:48 <decause> 2) Year in Review posts
17:23:02 <bee2502_> #info Campaign period has been extended till Dec 7
17:23:08 <decause> 3) Council reports (new item)
17:23:24 <jflory7> Ooh, that's right, forgot about the extension
17:23:38 <decause> until elections are done, consider us CSPAN
17:23:40 <decause> ;)
17:23:45 <jflory7> Hahah!
17:24:06 <bee2502_> Nominees can publish till Dec 7 now, so that gives us more time in hand . CSPAN ?
17:24:16 <decause> #info CSPAN is a cable network on american television dedicated to following politics and public sector news
17:24:23 <decause> bee2502++
17:24:27 <danofsatx-n6> #info danofsatx, utc-5, ambassador/QA/KDE/Server/commops
17:24:46 <decause> danofsatx-n6: welcome welcome :)
17:25:09 <jflory7> As far as I am aware, it seems like the interviews are being tackled by the trio: bee2502_, keekri, and jkurik. So I think we should be covered there as long as we're on track with appropriate deadlines. Definitely a time sensitiveness on that.
17:25:12 <jflory7> danofsatx++
17:25:16 <jflory7> Welcome danofsatx-n6!
17:25:17 <decause> so yeah, we're all elections all the time, and ther'll be plenty of editing work for us to help keekri and bee2502_ with
17:25:17 <danofsatx-n6> I think I did that right.
17:25:21 <jflory7> You did :)
17:25:33 <decause> danofsatx++
17:25:41 <jflory7> Year in Review posts... that's new on my radar. What's the plan with those?
17:25:49 <jflory7> Do we have a specific area or breadth that we want to cover?
17:25:53 <decause> jflory7: this is new
17:25:59 <bee2502_> Council reports sounds interesting too :)
17:26:03 <danofsatx-n6> I'm on my Nexus 6 in the Dr. office waiting room, so....
17:26:05 <jflory7> Indeed ^^
17:26:24 <decause> jflory7: personally, I have a *ton* of raw content from conferences and events this year that I'll be on the hook for boiling down
17:26:42 <decause> #action decause start compiling your personal year-in-review report
17:26:49 <decause> but outside of me personall
17:26:52 <jflory7> How many of these do we want to do?
17:26:52 <decause> but outside of me personally
17:27:06 <jflory7> A single one or maybe different posts for different areas worth mentioning?
17:27:10 * jflory7 thinks
17:27:29 <decause> it'd be somewhat painless for us to query datagrepper in meaningful way
17:27:50 <jflory7> It would actually be *really* cool if we could encourage subgroups to share a brief summary of what's happened this year
17:27:51 <decause> at the very least, we can use the proper time-delta and look at fedmsg traffic YoY
17:28:29 <decause> jflory7: agreed. If we can provide them with "hey, here is your fedmsg stats and a shiny chart to start with. add in whatever narrative you'd like"
17:28:40 <bee2502_> fedmsg , datagrepper *perks up*
17:28:54 <decause> bee2502_: :)
17:29:36 <jflory7> decause: Think a call-to-action sort of thing would be nice here for first week of December? We could get something up on the CommBlog, and then if bee2502_ was up for it, we could also try to compile some stats to have ready by then too.
17:29:39 <decause> I don't want this to be *super* intensive, and it is likely a series for after the elections
17:29:45 <decause> just getting it on the radar for now
17:30:04 <decause> jflory7: that timing sounds just about right
17:30:04 <jflory7> Okay, I see.
17:30:22 <decause> jflory7: maybe a week later than the first week (elections are done Dec 7th)
17:30:27 <bee2502_> jflory7 , decause : timing sounds right . and yes, I am interested :)
17:30:43 <decause> #info Year in Review posts to begin rolling out week after elections
17:30:44 <bee2502_> decause : elections are done on 15th
17:30:54 <decause> err, the week after then ;)
17:31:04 * decause calendars incorrectly
17:31:08 <danofsatx-n6> so, the week before Christmas
17:31:12 <jflory7> decause: Cool. Because of the general slowdown associated with the holidays (thanks to bee2502_'s stats), I'm wondering if we should make this an ongoing sort of thing into January that subgroups are encouraged to share.
17:31:41 <decause> danofsatx-n6: I don't expect them all to be done, just to be the general focus from then through the new year
17:31:55 <decause> jflory7: exactly :)
17:31:59 <danofsatx-n6> how about start the process in December, to be published week 2 of New Year
17:32:18 <decause> danofsatx-n6: that sounds quite reasonable yes
17:32:29 <decause> what we need to do is have 2 things for them:
17:32:34 <bee2502_> yes, by week 2 the traffic picks up too
17:32:43 <decause> 0) Template email for reaching out
17:32:44 <jflory7> #action jflory7 draft a call-to-action article to announce and encourage subgroups / teams to share a summary of their years in review on the CommBlog (target: early December?)
17:33:09 <decause> 1) Datagrepper query that cover's all that subprojects fedmsg traffic in the proper time delta
17:33:30 <decause> 2) a link to the /charts api to generate a pretty picture
17:33:47 <decause> that should give them a great start where they can look at it by topic
17:33:52 * decause digs up a link
17:34:15 <decause> #link https://github.com/decause/decks/blob/master/floss-community-metrics-preso.pdf
17:34:54 * danofsatx-n6 will dig that up later
17:35:12 <decause> danofsatx-n6: really, it's just the visuals I'd like to reference
17:35:22 <danofsatx-n6> roger that
17:35:37 <decause> in the hubs prototype slide in there, there is a multi-category stacked bar chart of fedmsg activity
17:36:07 <decause> instead of that being queried by user, we can query by team/topic
17:36:55 <decause> 3) Caveat: we don't wanna overload datagrepper server by having everyone blast it with year-long fedmsg queries. It will time-out after 60 seconds
17:37:32 <decause> so, if it is  a particularly active group, we may have to curl the infrastructure internally (this is a nasty hack until statscache is fully deployed)
17:37:45 <jflory7> Not sure if I'm jumping too far ahead, but are the Council reports similar to the Year in Review articles?
17:38:01 <jflory7> Just a Council-specific version?
17:38:09 <decause> jflory7: council reports are a narrative account of what happened at council each week
17:38:18 <jflory7> Oh, so a regular series?
17:38:32 <bee2502_> Do council reports also include the new proposals ?
17:38:37 <decause> jflory7: yep. IN theory, we could be doing it for other teams/meetings too
17:38:46 * jflory7 nods
17:38:49 <decause> but council is the first one that I've got requirements for
17:39:11 <decause> bee2502_: new objective proposals, yes, when they happen.
17:39:43 <jflory7> Are we looking at spinning this up in December or into the New Year?
17:40:10 <decause> bee2502_: basically, the minutes/logs are good for reference, but not very informative. Not every week has big exciting decisions being made, but the council decided to NOT create their own blog, and to use the commblog as their official communication channel :)
17:40:15 <decause> that is a win for us :)
17:40:23 <decause> we're helping big time ;)
17:41:01 <decause> just a few sentences and some bullet points on what happened at council this week is what we're looking to compile
17:41:12 <bee2502_> CommBlog++(theoretically) decause++ CommOps++ Also FAMSCo could be interesting in this apect too- since we are currently focusing on getting more volunteers onboard
17:41:29 <decause> there'll likely be a template, with some regular commentary and quotes from me (cause i gotta be there anyways ;) )
17:41:50 <jflory7> #info Year in Review posts: Subgroups encouraged to write summaries of what's been going on in year, three steps necessary to do this:
17:41:53 <jflory7> #info 1) Template email for reaching out
17:41:56 <decause> bee2502_: yes, any leadership body really would be great to have regular "beats" for
17:42:04 <jflory7> #info 2) Datagrepper query that cover's all that subprojects fedmsg traffic in the proper time delta
17:42:12 <jflory7> #info 3) a link to the /charts api to generate a pretty picture
17:42:42 <decause> jflory7: the reason I like having the charts is to help them tie narrative to data
17:43:03 <decause> "Oh yea, that HUGE spike in October was us gearing up for the release"
17:43:12 <danofsatx-n6> pictures say 1024 words, or something like that
17:43:26 <decause> danofsatx-n6: nod nod nod
17:43:43 <decause> ok
17:43:44 <jflory7> #info Council Reports: New series to share weekly happenings in Council with community; aims to provide short summaries of high-level Fedora decisions; will appear on CommBlog!
17:43:53 <decause> that, generally, is the themes of commblog upcoming
17:44:01 <jflory7> decause: I agree, data + narrative is the best way to go.
17:44:10 <jflory7> decause: Do we have an ETA for Council Reports?
17:44:14 <decause> we've still got a few items, so I'm gonna move on
17:44:19 <jflory7> December or the New Year?
17:44:34 <decause> jflory7: they're gonna start starting next week
17:44:45 <jflory7> #info Council Reports: Aiming for next week, stay posted for more info!
17:44:46 <decause> it's a new req, mostly on my plate, but I would welcome help
17:44:52 * jflory7 nods
17:44:53 <decause> jflory7++
17:45:01 <decause> ok
17:45:05 <decause> #topic 5tftw
17:45:22 <decause> if we have stuff for this, be sure to add it to the pirate pad
17:45:33 <jflory7> Haven't seen anything come out recently, thinking mattdm may have been slammed :)
17:45:35 <decause> #link https://www.piratepad.ca/p/5tftw
17:45:41 <danofsatx-n6> my finals are done, and no $dayjob in sight, so I seem to have a lot of free time on my plate.
17:45:54 <decause> danofsatx-n6: \o/
17:46:19 <bee2502_> danofsatx-n6 : lucky you , I am in the midst of finals and already tired.
17:46:31 <decause> jflory7: we are helping mattdm with this now, so he's likely waiting on us. Let's follow up with him and check in.
17:46:32 <jflory7> I think in terms of immediate upcoming urgency, we should be set for whenever the next 5tftw post comes out. But we can definitely keep adding to it.
17:46:44 <decause> jflory7: we wanna keep the weekly cadance alive
17:46:49 <jflory7> decause: Yeah, followup is good, the queue in the Etherpad should cover a week and a half from now
17:46:55 <decause> jflory7: good good
17:47:20 <decause> ok
17:47:22 <decause> moving on
17:47:23 <jflory7> Want me to send some mail over the ML and direct?
17:48:04 <decause> #action jflory/decause ask mattdm if he needs help/content, link him to pirate pad, cc commops list
17:48:10 * jflory7 nods
17:48:14 <decause> next
17:48:21 <decause> #topic plumbing
17:48:43 <decause> we're still in need of hooking up some of our infrastructure. Jetpack seems to be working though now.
17:48:48 <jflory7> Indeed
17:48:49 <decause> that is all I wanna say for that for now
17:48:56 <decause> #topic Outreachy
17:49:01 <decause> ok
17:49:11 <decause> so good news bad news
17:49:28 <decause> good news: We hired devyani as our Hubs Intern for the winter cycle
17:50:01 <decause> bad news: we were unable to officially hire commops interns for this cycle due to new eligibility requirements from upstream
17:50:07 <decause> unofficially though
17:50:39 <decause> I will continue helping/mentoring any outreachy applicants as if they were hired, in preparation for the next cycle
17:51:06 <bee2502_> decause++
17:51:16 * jflory7 is also happy to help with that as well
17:51:30 <jflory7> My inbox is always open :)
17:52:17 <decause> thank you to all the applicants who put in so much time and effort during the application period
17:52:36 <jflory7> bee2502++
17:52:38 <jflory7> keekri++
17:52:56 <decause> your work is appreciated, and I will do everything I can to help prepare you for the next round
17:53:13 * decause is here to help anyone here to help
17:53:22 <decause> #topic Hubs
17:53:40 <bee2502_> decause : link to Hubs ?
17:53:47 <decause> with Fedora Hubs on the horizon, this is something we can all start getting excited about.
17:54:06 <decause> #link https://pagure.io/fedora-hubs/
17:54:15 <decause> Hubs is not deployed in staging or production yet
17:54:21 <decause> it is still under active development
17:54:38 <decause> but, as soon as we have a staging instance, this is going to be a place where commops can truly shine
17:54:50 <jflory7> Hype!
17:54:58 <bee2502_> Excited
17:55:20 <jflory7> Looking forward to seeing a staging instance. Do we have an estimated arrival point for when we can watch for it?
17:55:40 <decause> imagine that each time we're editing a wiki for a particular person or project, we could be editing a web presence that also looks great on mobile, and has embeddable content that can be used outside of the website it was posted to!
17:56:05 <decause> we're going to help hook up all the plumbing, and gather the one-time content, and connect the dots between all the sub-projects
17:56:16 <decause> it's still a bit of a ways off, but we're getting closer all the time
17:56:36 <decause> jflory7: we can file a ticket with infra if we wanna force the issue :)
17:56:53 <decause> jflory7: I've had a local instance on my laptop for months
17:57:03 <decause> that is what I've been using to dev/experiement with it
17:57:03 <jflory7> decause: Sounds good. If it's at a point of basic stability, I think it's something to get on the radar for December
17:57:20 <jflory7> Maybe check up on this next meeting?
17:57:24 <decause> jflory7: agreed. we also want to work closely with devyani on this (The OUtreachy Hubs intern)
17:57:29 <jflory7> In terms of ticketing for a staging instance
17:57:30 * jflory7 nods
17:57:45 <decause> jflory7: agreed, once she's oriented a bit, commops is going to help
17:57:53 <jflory7> Sounds good.
17:58:07 <decause> #action jflory7 add Hubs Check-in to next weeks agenda
17:58:27 <decause> #topic Open Floor
17:58:43 <decause> We have a couple of minutes left today in the meeting block
17:58:51 <mailga> decause jflory7 is not the case to parse the tickets in our meetings? Just to know their state or if they're still valid.
17:58:55 <decause> anybody have anything to bring to the floor?
17:58:57 <jflory7> I think we effectively hit Elections earlier on
17:59:12 <jflory7> decause: Any status on Trac admin?
17:59:13 <bee2502_> Since the nomination period is over, should we do a quick summary article
17:59:18 <bee2502_> *?
17:59:21 <cprofitt> did we cover Flock 2016 at all?
17:59:23 <decause> mailga: we have a trac, but we're not using it to it's fullest potential yet, you're right.
17:59:31 <jflory7> mailga: Trac is kind of an ongoing process now. Ideally, yes, we do want to move to ticket-based meetings!
17:59:48 <jflory7> cprofitt: Yep, we did earlier. The article went out this morning. :)
17:59:48 <decause> jflory7: what was the action needed from last time?
17:59:57 * cprofitt nods and smiles
18:00:03 <decause> cprofitt: yeah, we mentioned it during #topic commblog
18:00:07 <decause> cprofitt: thanks for those edits :)
18:00:10 <decause> cprofitt++
18:00:16 <cprofitt> yw decause
18:00:17 <jflory7> decause: You were going to look into setting me as an admin on Trac so I could configure it a little more extensively.
18:00:25 <jflory7> cprofitt++
18:00:36 <decause> #action decause add jflory to trac admin
18:00:40 <decause> anyone else?
18:00:45 <jflory7> bee2502_: I like the idea of a wrap-up post
18:00:54 <jflory7> Not sure if wrap-up is better, or maybe announcing the next step
18:01:00 <jflory7> Maybe a hybrid
18:01:06 <mailga> decause jflory7 my proposal is to insert the ticket revision in the next agenda. There are few tickets, so it needs not too much time.
18:01:07 <jflory7> "Here's who's elected, here's what's next"
18:01:27 <jflory7> mailga++ Actually, yeah, you're right, we do have tickets we can hit on in the meetings to check in on
18:01:30 <cprofitt> +1 mailga
18:01:31 <decause> mailga: agreed. That is how Design-team does their meetings, and it works *really* well for them
18:01:37 <decause> I def wanna emulate their example :)
18:01:40 <jflory7> Let's definitely add that to our agenda for next week
18:01:53 <bee2502_> wrap up for nominations - these are nominated people - so many nominations for so many seats and linking the Campaign period
18:02:03 <cprofitt> decause: the doc team and security team did the same in meetings I attended this week.
18:02:06 <bee2502_> something to keep the community involved
18:02:15 <mailga> decause also emea ambassadors meeting is doing that.
18:02:16 <jflory7> bee2502_: I'm a fan!
18:02:25 <decause> bee2502_: yeah, more or less the first section of your etherpad could make for a </nominations> wrap-up post
18:02:33 <decause> we can include the call for env/stacks nominees in that too
18:02:55 <decause> mailga: EMEA ambassadors do a lot of things right :)
18:02:55 <jflory7> +1, yeah
18:03:23 <decause> ok
18:03:25 <decause> we're 2 over
18:03:28 <decause> any last minute things?
18:03:29 <bee2502_> decause : yeah
18:03:37 <jflory7> At the NA Ambassador meeting next week, I'll share news of elections news on CommBlog
18:03:39 <mailga> jflory7: if you need help in order to handle the ticketing system, ping me.
18:03:39 <danofsatx-n6> regarding trac, I've run extensive production instances in the past if y'all need help with something.
18:03:43 <jflory7> Was well-received at last meeting.
18:03:46 <jflory7> mailga++ Noted!
18:04:05 <jflory7> danofsatx-n6: We're mainly looking at getting it fully configured, we can discuss in main channel after meeting :)
18:04:20 <jflory7> Fresh ideas for making our Trac awesome are welcome!
18:04:36 <jflory7> Anyways, we are over time, so I'm okay with moving this discussion to channel.
18:04:42 <jflory7> Motion to close?
18:04:52 <danofsatx-n6> and I need to drive home.
18:04:59 <danofsatx-n6> secondef
18:05:01 <decause> kk
18:05:08 <decause> thanks all for coming out today
18:05:11 <jflory7> decause++
18:05:19 <decause> #endmeeting