16:02:43 <decause> #startmeeting CommOps
16:02:43 <zodbot> Meeting started Tue Jul 14 16:02:43 2015 UTC.  The chair is decause. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:02:43 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:03:03 <decause> #topic rollcall
16:03:19 <decause> Hi There
16:03:34 <decause> #info decause ET (UTC+5). CommOps, Infrastructure, Council, and Badges
16:04:24 <decause> for rollcall, please post your TimeZone, and which teams/subprojects you participate in already, like so
16:05:00 <decause> nyazdani: welcome
16:05:09 <nyazdani> thank you
16:05:19 <decause> nyazdani: for rollcall, please post your timezone, and what teams you are working with, using #info
16:05:23 <decause> like so:
16:05:28 <decause> #info decause ET (UTC+5). CommOps, Infrastructure, Council, and Badges
16:06:09 <nyazdani> #info nyazdani PT (UTC+7). Infrastructure and CommOps
16:06:20 <decause> for today's meeting, you can find this handy agenda/info page here:
16:06:24 <decause> #link https://fedoraproject.org/wiki/CommOps/intro-meeting
16:06:29 <FranciscoD_> #info ankursinha London (UTC+1) package maintainers, qa, marketing, ambassadors, fedora-join, irc-support, askfedora
16:06:46 <decause> FranciscoD_: welcome :)
16:07:28 <FranciscoD_> hello decause :)
16:08:04 <pingou> #info pingou (UTC+1) package maintainer, infra lad :)
16:08:19 <decause> any FAMSCo folks here too?
16:08:58 <decause> I know it has been a while since FAMSco met, but meeting here during this block was on purpose in hopes that Ambassador leadership would be hanging around
16:09:10 <FranciscoD_> decause: famsco is sort of inactive nowadays :(
16:09:38 <decause> FranciscoD_: def def
16:10:02 <decause> ok, in the meantime though
16:10:06 <decause> #link https://fedoraproject.org/wiki/CommOps/
16:10:21 <decause> #topic Interest Areas
16:10:41 <decause> for those of you who haven't seen the wiki page, CommOps is a portmanteu of Community + Operations
16:11:04 <decause> the idea is that DevOps has risen to prominence as a new model of adminstering infrastructure
16:11:22 <decause> which is mostly characterized by continuous integration, and automated processes
16:11:40 <decause> The idea here, is that community infrastructure can also follow along a similar path
16:12:09 <decause> so that contributors don't have to choose between "building things" and "Building communities that build things"
16:12:50 <decause> One person, Lead or otherwise, cannot possibly know everything that is happening in every corner of a project the size of Fedora, let alone where each of those sub-communities would like to go in the future.
16:13:07 <decause> To do this, we'll need broad participation across many teams and communities
16:13:48 <FedoraUser> #info fedorauser CEST (UTC+2) Ambassadors
16:13:56 <decause> and finding out who here is already involved in which communities, will help us figure out where we need to engage with other subprojects
16:14:40 <decause> eventually, the goal is to have at least one delegate from each subproject, working group, web property, and active SIG
16:15:09 <decause> there'll be one "mothership" style meeting that happens (like today) where everyone who wants to report back to the group as a whole can do so
16:15:37 <decause> but otherwise, delegates will try to surface events/stories/initiatives from within each of their subprojects as async as possible
16:16:26 <decause> for now, there are general areas of interest within commops that have been gathered from a number of places
16:16:38 <decause> requirements designated by the FPL and Engineering Manager
16:16:47 <decause> the job description of the Fedora Community Lead
16:16:59 <decause> and a smattering of suggestions from years of "would be nice" documentation
16:17:09 <decause> and suggestions by contributors since I've arrived on the scene
16:17:22 <decause> those reqs can all be explained here:
16:17:29 <decause> #link https://fedoraproject.org/wiki/CommOps
16:17:58 <decause> generally, interest areas are as follows:
16:18:21 <decause> 1) Messaging - How to explain what Fedora is
16:18:39 <decause> 2) Storytelling - Writing/Curating content for internal/external publications and social media
16:19:03 <decause> 3) Badges - Conceptualizing to Design
16:19:25 <decause> 4) Hubs - The modern online face of the Fedora Community (coming soon)
16:19:41 <decause> 5) Wiki - Gardening/Updating this trove of aging knowlege
16:20:21 <decause> 6) Culture - Helping to maintain a positive environment for new and old members
16:20:37 <decause> 7) Metrics - Collecting and Analyzing statistics about our contributors and users
16:20:59 <decause> 8) Voting - Helping to promote and engage with contributors to vote during elections
16:21:22 <decause> 9) Misc - All the stuff that isn't explicitly covered above
16:22:01 <decause> Those are the general areas where CommOps will operate, likely with more to come from the delegation as we increase capacity
16:22:41 <decause> There is a table on the intro-meeting wiki page where folks can put an "X" in the places they are most interested in, or we can indicate here, and I will fill in the wiki for you
16:23:24 <decause> so, I would put it to those participating in the meeting today, you can do a #info with which areas you are interested in
16:23:53 <decause> #link https://fedoraproject.org/wiki/CommOps/intro-meeting#Interest_Areas
16:24:55 <decause> #topic CommOps ToolBox
16:25:42 <decause> there have already been built a handful of tools and infrastructure to help new contributors understand what types of work/initiatives the CommOps team is interested in delivering on
16:25:49 <decause> you can find that list of tools here:
16:25:59 <decause> #link https://fedoraproject.org/wiki/CommOps/intro-meeting#CommOps_Toolbox
16:26:11 <decause> I will be adding this table to the main wiki page as well
16:26:21 <decause> the tools we have so far are:
16:27:00 <decause> #info 1) wordcloudbot https://github.com/decause/wordcloudbot Create pretty wordclouds from IRC meeting logs. Stack, Python. Issue area, Storytelling, Metrics
16:27:22 <decause> #info 2) longtail longtail-analyze.py longtail-gather.py Measure the ratio of activity/user to approximate burnout Python Metrics
16:27:38 <decause> feedcloud https://github.com/decause/feedcloud Take an RSS feed, or list of RSS feeds, and generate fancy wordlcouds for all/each
16:27:47 <decause> #info 3) feedcloud https://github.com/decause/feedcloud Take an RSS feed, or list of RSS feeds, and generate fancy wordlcouds for all/each
16:28:25 <decause> #info 4) annualgrepper.py. Gather's raw fedmsg totals on topics spanning over 1 year's time.
16:28:51 <decause> #info 5 cardsite. live fedmsg tracker inspired by http://emojitracker.com
16:29:17 <decause> #info 6) meetbot-fedmsg-activity.py. jinja2 template to create links to meetbot activities for each subproject
16:30:08 <decause> #info 7) daily-briefing.py - Template to create a "daily briefing" of Fedora meeting items like #action and #link. Manually curated for now, but will be automated in the future
16:30:36 <decause> The rest of the items on the toolbox list are core pieces of fedora infrastructure that have been built over the past 3 years
16:30:46 <decause> which include:
16:31:17 <decause> #info 8) Fedmsg - https://fedmsg.com - Real-time message bus for all Fedora Community Activity (it is amazing)
16:31:55 <decause> #info 9) datagrepper - http://apps.fedoraproject.org/Datagrepper - Query all fedmsg history by topics
16:32:19 <decause> #info 10) statscache - A daemon to build and keep highly-available fedmsg statistics
16:32:40 <decause> own very own nyazdani is cranking along on statscache this summer as part of his internship
16:33:09 <decause> the last tool in the box is an alpha prototype, but will ultimately be the place where all our content/tools/reports can culminate
16:33:43 <decause> #info 11) Fedora Hubs - Modern, web-based Fedora activity center. https://pagure.io/fedora-hubs/branch/develop
16:33:53 <decause> so
16:34:13 <decause> you can see that many of the tools already here are based on collecting metrics
16:34:39 <decause> Fedmsg already has over 2 years worth of raw messages
16:35:13 <decause> making sense of the history of those messages can help the project move forward, and make sense of what has happened in the past to make informed strategic decisions
16:35:59 <decause> I'm going to pause here for now and see if anyone has any questions about tools or interest areas?
16:36:34 <decause> I realize this is a good bit of information being dumped on you all, and it is going to take some time to internalize what we've got so far
16:36:55 <decause> going once
16:36:59 <striker> #info striker EDT (UTC-4) irc sig
16:37:06 <decause> going twice
16:37:11 <decause> going thrice
16:37:15 <decause> ok, moving on
16:37:29 <decause> #topic Story Queue & Editorial Calendar
16:38:24 <decause> one of the main goals of the CommOps Team is to improve communications--by helping to build a pipeline of info to be tapped into by existing Fedora Teams like Marketing, Ambassadors, and Design
16:39:14 <decause> having a queue of interesting things happening from each existing project that can then be investigated further is a good way to chew away at a large project bite by bite
16:40:03 <decause> Fedora is massive, and the Marketing Team won't know everything that is happening in every corner, or the Design Team cannot imagine each kind of badge that each subproject may want to issue
16:40:45 <decause> CommOps delegates can rep each corner to the whole, and we do this by lowering the barrier of entry to contributing content
16:41:17 <decause> mining meetbot logs for links and actions is one way that we tap into existing infrastructure, and dont' require additional process or tools
16:41:41 <decause> those items can then be entered into a queue of story ideas, which then land on an editorial calendar
16:41:58 <decause> for example
16:42:30 <decause> there is an open request from the Opensource.com team pitching for writers who'd like to contribute their "Linux Story" as part of an ongoing series
16:42:52 <decause> #link https://fedoraproject.org/wiki/CommOps/intro-meeting#Story_Queue_.26_Editorial_Calendar
16:43:05 <decause> you can read the details of that pitch at the link above
16:43:25 <decause> It is under the "Open Floor" section
16:43:32 <decause> so
16:43:50 <decause> speaking of Open Floor, this would be a good time to open it up
16:43:56 <decause> #topic Open Floor
16:44:32 <decause> Again, I know I just dumped a bunch of info on everyone, so if you have questions ask away
16:45:18 <decause> If you don't have questions, then I'm interested in hearing from folks about which areas they are interested in
16:46:15 <decause> this is a super informational meeting, a one-off, that helps to introduce the concept of CommOps, and the tools in the box
16:46:32 <stbnruiz> .fas stbnruiz001
16:46:32 <zodbot> stbnruiz: stbnruiz001 'Esteban Ruiz Diaz Baez' <stbnruiz001@gmail.com>
16:46:37 <decause> there'll likely be another one or two meetings like this that will happen in the coming weeks before FLOCK
16:46:46 <nyazdani> to announce our interests, should we use #info again? and if so in what format?
16:47:21 <roshi> #info roshi (MST) QA and Cloud SIG
16:47:28 <decause> #info decause Messaging, Storytelling, Badges, Hubs, Wiki, Culture, Metrics, Voting, Misc
16:47:37 <decause> nyazdani: like so
16:47:42 <nyazdani> thanks
16:48:18 <nyazdani> #info nyazdani Messaging, Hubs, Metrics, Voting
16:48:25 <decause> I'm interested in all of them, but particularly metrics and storytelling until we get into full-on Hubs mode
16:48:50 <decause> thanks nyazdani
16:49:17 <decause> I can go back into the logs after the fact and add your info to the table on the wiki, or you can add it yourself now or later
16:49:27 <decause> #link https://fedoraproject.org/wiki/CommOps/intro-meeting
16:50:21 <decause> on the regular, folks doing CommOps things are going to be hanging out in #fedora-commops
16:50:43 <decause> so if you are interested in these things, then def join and hang out there :)
16:52:05 <decause> we're getting close to the end of the slot, so I'm going to wrap up a bit
16:52:12 <decause> if no one has anything else for open floor
16:52:24 <decause> going once
16:52:26 <decause> going twice
16:52:28 <decause> going thrice
16:52:35 <decause> #topic Wrap-up
16:53:36 <decause> today, I listed a whole bunch of things
16:53:42 <decause> a whole bunch of pieces
16:54:18 <decause> the idea of commops, is to gather folks who know their corners of the project well, and weave their stories into a larger picture
16:54:37 <decause> Fedora Editions has tried to become more than a just a "bag of bricks"
16:55:07 <decause> gathering the big picture on who are contributors are, and where they need help, that is the ultimate vision
16:55:24 <decause> helping to direct new folks where the help is needed most
16:55:34 <decause> recognizing when difficult tasks are completed
16:55:39 <decause> celebrating the wins
16:56:15 <decause> Fedora is chock-full of rediculously talented hackers and designers and content creators
16:56:36 <decause> those folks are cranking all the time, working really hard
16:56:47 <decause> CommOps isn't meant to be "yet another place to steal cycles from your work"
16:56:57 <decause> it is meant to work like middleware
16:57:02 <decause> wrapping around existing process
16:57:26 <decause> doing so in as automated and integrated of a fashion as possible
16:57:45 <decause> I have been studying and reading and listening for months
16:58:18 <decause> I haven't even really wrapped my head around all the different parts of this vibrant and constantly buzzing hive of activity
16:59:03 <decause> there are many fronts to address, but I think we can break them down into smaller campaigns and projects, and tackle them together
16:59:40 <decause> Please add yourself to the wiki, and join the IRC channel
17:00:00 * FranciscoD_ notes
17:00:06 <decause> we'll be gathering potential delegates and project leads, to help them tell their stories, and drive activity, and reward victories
17:01:05 <decause> my email is decause@redhat if you need to get ahold of me directly
17:01:29 <decause> otherwise, I hope to see you all in #fedora-commops in the meantime, while we spin up
17:01:38 <decause> Thanks everyone for being here
17:01:44 <decause> #endmeeting