17:02:47 <jflory7> #startmeeting CommOps
17:02:47 <zodbot> Meeting started Tue Jan 12 17:02:47 2016 UTC.  The chair is jflory7. Information about MeetBot at
17:02:47 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:02:47 <zodbot> The meeting name has been set to 'commops'
17:02:55 <jflory7> #meeetingname Fedora CommOps
17:02:58 <linuxmodder> .hello corey84
17:02:59 <zodbot> linuxmodder: corey84 'Corey Sheldon' <>
17:03:07 <jflory7> #meeetingname Fedora CommOps
17:03:07 <jflory7> #chair decause jflory7 threebean bee2502 lmacken cproffit mailga danofsatx
17:03:07 <zodbot> Current chairs: bee2502 cproffit danofsatx decause jflory7 lmacken mailga threebean
17:03:10 <jflory7> #topic Roll Call
17:03:10 <aikidouke> .hello aikidouke
17:03:11 <zodbot> aikidouke: aikidouke 'Zach Villers' <>
17:03:15 <jflory7> #info Name; Timezone; Subprojects/Interest Areas
17:03:17 <decause> .hello decause
17:03:18 <zodbot> decause: decause 'Remy DeCausemaker' <>
17:03:21 <jflory7> .hello jflory7
17:03:21 <mailga> .fas mailga
17:03:22 <zodbot> jflory7: jflory7 'Justin W. Flory' <>
17:03:25 <zodbot> mailga: mailga 'Gabriele Trombini' <>
17:03:36 <linuxmodder> late morning to all
17:03:41 <jflory7> #info Justin W. Flory; UTC-5; CommOps / Marketing / Fedora Join / Ambassadors / etc.
17:03:42 <decause> #info decause; UTC-5; CommOps, Council, Ambassadors, *
17:03:48 <jflory7> Morning, all!
17:03:49 <bee2502_> .fas bee2502
17:03:49 <zodbot> bee2502_: bee2502 'Bhagyashree Padalkar' <>
17:04:00 <linuxmodder> .fas corey84
17:04:00 <zodbot> linuxmodder: corey84 'Corey Sheldon' <>
17:04:01 <aikidouke> #info aikidouke
17:04:08 <jflory7> Looking like it will be much more lively than last week. :)
17:04:16 <decause> welcome back everyone :)
17:04:23 <decause> anybody else?
17:04:54 <linuxmodder> dgilmore,  you get my  email about the livemedia-creator ?   would like to start using that more for events and  the planned reboot of  campus | youth ambassadors
17:05:10 <jflory7> decause: I think we should plow on ahead, we have a packed meeting today
17:05:14 <decause> jflory7: agreed
17:05:18 <linuxmodder> decause,  I'm here to  (ws not  able to make last week)
17:05:24 <decause> linuxmodder: welcome back :)
17:05:27 <decause> linuxmodder++
17:05:31 <jflory7> linuxmodder: No worries, it was post-holiday time. :) linuxmodder++
17:05:31 <decause> aikidouke++
17:05:31 <zodbot> decause: Karma for aikidouke changed to 6 (for the f23 release cycle):
17:05:39 <decause> mailga++
17:05:44 <decause> bee2502++
17:06:01 <decause> jflory7: press on
17:06:02 <linuxmodder> decause,  my  fas is  corey84 if that's waht you meant  :)
17:06:02 <decause> :)
17:06:08 <jflory7> #topic Tickets
17:06:13 <decause> corey84++
17:06:14 <jflory7> #info === Ticket #8 - ===
17:06:15 <zodbot> decause: Karma for corey84 changed to 1 (for the f23 release cycle):
17:06:20 <jflory7> #info * CommBlog Article: Flock Call for Bids
17:06:29 <jflory7> Mainly follow-up on this ticket. See my last comment on the ticket.
17:06:41 <dgilmore> linuxmodder: not sure I got your email
17:06:43 <linuxmodder> so this is for flock 16  bids yes?
17:06:53 <jflory7> Do we want to close it or do we want to push for the social media posting a bit more?
17:06:55 <jflory7> linuxmodder: Correct.
17:06:55 <linuxmodder> dgilmore,  after mtg then I guess
17:07:27 <jflory7> The article was written a month or two ago, in late November, I think. We wanted to get an extra push for it in December and got it circulated on a few mailing lists and we have new bids, but we were wanting to do an additional push on social media.
17:07:30 <decause> jflory7: I think we just need to double check the social-media list to make sure that folks with creds are on there. I /think/ I have creds, but I rarely use them manuually
17:07:53 <linuxmodder> the overall theme again for  flock16 ?
17:07:53 <jflory7> decause: Probably something we should check out, yeah. I also CC'd the marketing list with those replies though.
17:08:07 <jflory7> linuxmodder: I'm not sure about the theme as of yet, but we were hoping to get some more bids in the EMEA region.
17:08:09 <decause> jflory7: there is good discussion happening around strategy
17:08:17 <jflory7> I saw that on the marketing list too
17:08:52 <jflory7> #action jflory7 / decause: Make sure people with the social media powers are subscribed to the social-media mailing list
17:08:53 <decause> jflory7: lets just ping bkp directly for now, to get one last tweet out the door today
17:08:57 * jflory7 nods
17:08:59 <decause> jflory7: next
17:09:13 <jflory7> #info === Ticket #15 - ===
17:09:20 <jflory7> #info * Hook up email posting functionality for CommBlog
17:09:26 <jflory7> #action jflory7 Ask puiterwijk about this, see if ticket should be filed in Fedora Infra Trac
17:09:39 <decause> this is an oldie, but a goodie ;)
17:09:50 * puiterwijk reads back
17:09:58 <jflory7> Mainly wanted to follow up on this, was hoping to clarify with puiterwijk about how to set this up.
17:10:02 <jflory7> Hiya Patrick :)
17:10:08 <decause> puiterwijk++
17:10:10 <puiterwijk> hi. Sorry, give me one minute to read back
17:10:13 <jflory7> Sure thing.
17:10:28 <jflory7> Mainly just wanting to look into setting up email-to-blog for Community Blog.
17:10:38 <jflory7> Wanted to know if and how to go about doing that.
17:10:44 <decause> puiterwijk: (I have some FOSDEM/DevConf/configmgmtcamp related questions for you after this meeting, fyi)
17:11:10 <puiterwijk> Ah, okay. I'll need to dig into that. If you assign the ticekt to me, I'll take a look at it
17:11:12 <jflory7> We could file a ticket in the Infra Trac if that's easiest, just wanted to see what your workflow was like. :)
17:11:15 <puiterwijk> (as you will need inbound SMTP and all)
17:11:28 <decause> jflory7: I think we should file on the infra trac, reference comomps ticket, and cc puiterwijk and decause
17:11:31 <puiterwijk> I'll take tickets on the commops trac as well. Just assign to me
17:11:38 <jflory7> decause: Agreed.
17:11:39 <decause> puiterwijk: awesome
17:12:01 <jflory7> #agree Assign puiterwijk Ticket #15 in CommOps Trac, file ticket in Infra Trac, cc puiterwijk and decause
17:12:05 <puiterwijk> jflory7: just commops should be enough. I prefer to have issues in one central point :)
17:12:05 <jflory7> Next ticket?
17:12:11 <decause> net
17:12:12 <jflory7> puiterwijk: Noted
17:12:13 <decause> next*
17:12:14 <jflory7> #undo
17:12:14 <zodbot> Removing item from minutes: AGREED by jflory7 at 17:12:01 : Assign puiterwijk Ticket #15 in CommOps Trac, file ticket in Infra Trac, cc puiterwijk and decause
17:12:15 <linuxmodder> only  immediate issue I see is the spam from  posting  via email like that  Gary skeete idoot on  -docs ml
17:12:24 <jflory7> #agree Assign puiterwijk Ticket #15 in CommOps Trac
17:12:34 <decause> linuxmodder: we'd whitelist addresses likely
17:12:41 <jflory7> linuxmodder: Yeah, it would have very special privileges, no spam for sure. :)
17:12:47 <jflory7> #info === Ticket #17 - ===
17:12:51 <decause> linuxmodder: good call though
17:12:51 <jflory7> #info * Interview Fedora's Diversity and Inclusion Advisor, tatica
17:12:56 <jflory7> Here's a more recent topic!
17:12:58 <decause> woo
17:13:05 <jflory7> We ticketed this in December but haven't had a chance to discuss it yet.
17:13:11 <linuxmodder> like a  established  user/contributor  bar of  entry kinda thing ?
17:13:37 <puiterwijk> decause: and feel free to ping me in any channel at any time :)
17:14:00 <decause> linuxmodder: we have a tool, wordcloudbot, that creates wordclouds of meeting minutes, and it would be nice to have it auto-post those to the commblog with a template
17:14:33 <decause> linuxmodder: it could be used to have our commops members send posts via email as well, yes, but would require special attention to templating
17:15:03 <decause> jflory7: I know tatica wanted to get a few things underway before we heavily promoted her presence, so let us ping her and see how she's doing
17:15:15 <decause> #action decause/jflory ping tatica, invite her to commops list
17:15:23 <linuxmodder> not suretemplating would be the issue even tho as that  dude spamming the docs ml is hardly a  typical template  but  later
17:15:25 <jflory7> decause: Sounds good. How do we want to handle this interview?
17:15:32 <jflory7> Do we want to ask her if she has some things she wants to highlight?
17:15:41 <jflory7> Or do we want to come up with the questions and pose it as an interview?
17:15:51 <jflory7> Well, either way, it's posed as an interview, I suppose.
17:15:57 <decause> jflory7: perhaps creating an "interview template" would be a good idea
17:16:06 <decause> we have similar things in
17:16:07 * decause digs
17:16:07 <jflory7> Guess it just depends if she or us are coming up with the questions, or probably both.
17:16:15 <jflory7> Ooh, that would be a good resource
17:16:17 <jflory7> decause++
17:16:20 <mailga> why dn't we ask her to write a topic and then let users asking questions?
17:16:26 <decause> #link
17:16:55 <jflory7> mailga: Hmmm. What do you mean a topic, like specific kinds of things about her roles and then let users ask questions about those things?
17:16:57 <decause> we can port this to be more Fedora-specific, but it is a good place to start
17:17:05 <linuxmodder> would a AMA style  blog interview be out iof the question re:317
17:17:16 <decause> mailga: an "AMA" would be a cool thing to do at some point, great idea :)
17:17:16 <jflory7> decause: definitely, this is looking like good fuel. I'll read it all later. :)
17:17:23 <mailga> jflory7: exactly
17:17:24 <decause> jflory7: nod nod
17:17:25 <linuxmodder> err,  current ticket
17:17:33 <decause> linuxmodder: took words right out of my mouth :)
17:17:42 <jflory7> mailga++ linuxmodder++ I'm liking the sounds of all of that.
17:17:48 <linuxmodder> great minds think alike  :)
17:18:19 <jflory7> So, what I'm seeing is: we ask tatica_ about some of her thoughts about her role and major areas that might be uncertain, ask CommOps + other list(s) for questions, then aim for CommBlog?
17:18:20 <decause> jflory7: cc her on the ticket in trac, and we'll send her a personal email too
17:18:28 <linuxmodder> I'm great at the thinking part and brainstorm  part  not so much at the content  creation tho :(
17:18:58 <decause> jflory7: I know she's going to want to have some more stuff "done" before we publish her interview, so lets just open a loop, and start gathering the interview questions in general
17:19:12 <jflory7> linuxmodder: No worries - the brainstorming is just as important as the content creation. I can always help out with the content creation too :)
17:19:15 <jflory7> decause: Sounds good.
17:19:19 <linuxmodder> jflory7,   or  even possibly tie it in the  2016  goals  thread --  what  would you like to see yourself  locally regionally  or  more  broadly
17:19:45 <linuxmodder> make it  less Ny  resolution ish
17:19:46 <decause> as far as "big idea" stuff for this: Doing Contributor Profiles (which can be easily ported to Hubs pages) is something that commops will be doing in the 90-120 days from now range if we can get our ducks in a row and things go according to plan
17:19:55 <jflory7> #agree Contact tatica_ about the plans to conduct the interview, begin the process of bringing everything together (cc her on Trac ticket)
17:20:05 <linuxmodder> maybe even make the default for  this year's  interview have that  tie
17:20:08 <jflory7> #action jflory7 CC tatica on Ticket #17
17:20:20 <decause> solid
17:20:24 <jflory7> decause: Contributor Profiles... that sounds awesome.
17:20:27 <jflory7> Looking forward to that!
17:20:31 <decause> jflory7: :)
17:20:36 <decause> we'll get there. Hubs will get there.
17:20:41 <jflory7> Hubs++
17:20:43 <jflory7> Next ticket?
17:20:46 <decause> nod nod
17:20:53 <jflory7> #info === #Ticket #20 - ===
17:21:00 <jflory7> #info * Year in Review - CommOps Retrospective
17:21:04 <jflory7> #link
17:21:21 <jflory7> We began discussing this at the least meeting.
17:21:24 <decause> I've updated the etherpad with more bullets, but I need to get more concrete content in there
17:21:35 <decause> I wanna ship this by Thursday if we can
17:21:35 <jflory7> I'm also planning on really going for it soon too.
17:21:38 <jflory7> Oh, wow!
17:21:40 <jflory7> Okay.
17:21:46 <jflory7> I think we can do that.
17:21:53 <decause> we need our "model" so we can encourage other ones too
17:22:00 <jflory7> Right.
17:22:07 <decause> as an aside, I'm also looking to do one for Council YiR
17:22:20 <bee2502_> arent the fedmsg metrics done with the threebeans gource videos ? or do we have something else in mind ?
17:22:27 <jflory7> #action jflory7 Raise Ticket #20 priority
17:22:59 <jflory7> decause: I'm thinking we try to hammer out the final outline in the Etherpad today, and then begin converting to an article today / tomorrow, then share with list ASAP once finished
17:23:08 <jflory7> Also, gathering input in channel today and tomorrow would also be good
17:23:13 <decause> bee2502_: yeah, those fedmsg/gource vids will be nice supplments to each YiR if we get separate ones, or bullets int he larger YiR aggregate taht we push before Feb
17:23:18 <jflory7> Definitely a hands-on thing for anyone wanting to be involved
17:23:28 <decause> jflory7: that sounds like a good plan to me
17:23:39 <decause> I'll cycle direct with you today if you got time to get that hammered out
17:23:49 <decause> jflory7: let's check in after this
17:23:54 * jflory7 nods
17:24:05 <decause> anyone else is welcome to come hammer out deets as well, we'll meet in #fedora-commops and discuss after meeting
17:24:27 <jflory7> #agree Finish outline for CommOps YiR article today, begin porting to a CommBlog article today / tomorrow, get feedback in channel while working on this and on mailing list once finished
17:24:32 <decause> jflory7: has anyone submitted any YiR content besides us yet?
17:24:38 <jflory7> decause: Not that I've seen.
17:24:40 <jflory7> Hiya, danofsatx!
17:24:46 <decause> sure sure
17:24:51 <decause> danofsatx: welcome back
17:25:02 <aikidouke> are you all wanting yir content from all of the groups?
17:25:07 <decause> jflory7: maybe that is another item for our social-media blast request to Bkp
17:25:09 <jflory7> Any other thoughts on Ticket #20 / CommOps YiR article?
17:25:16 <decause> aikidouke: ideally, yes
17:25:25 <jflory7> aikidouke: Yes, we're encouraging participation from as many subgroups as possible. :)
17:25:26 <decause> jflory7: we should post the request to announce list
17:25:32 <decause> I don't think we did that yet, right?
17:25:38 <jflory7> CommOps is helping make the process as easy and straightforward as possible.
17:25:41 <jflory7> decause: Correct, we did not.
17:25:47 <jflory7> Do we want to add that to the list today?
17:25:52 <decause> jflory7: yes
17:25:55 <aikidouke> k, i could take a stab at something for infra (even tho I haven't been an apprentice all that long)
17:26:05 <decause> #action decause/jflory7 post request for YiR input to announce list
17:26:20 <mailga> jflory7: decause tell me differences between Yir and the retrospective.
17:26:31 <decause> aikidouke: simply dropping an email to infra list, and in IRC, pointing to the commblog post would be helpful
17:26:42 <decause> if you want proofreading, just send commops a draft :)
17:26:43 <jflory7> aikidouke: That would be awesome! The first step would be to open a discussion with the Infra team about it. The main goal is to find three highlights of 2015 and one goal for 2016. Let me find the link to the announcement article!
17:27:02 <jflory7> mailga: I guess technically they're the same thing. Just one way of saying it versus the other.
17:27:02 <aikidouke> will do, our meeting is on thursday, appreciate the link
17:27:07 * mailga still thinks about mktg retrospective... Is it the case to merge things?
17:27:07 <decause> aikidouke++
17:27:19 <decause> mailga: that would be a great thing on it's own too
17:27:19 <jflory7> #link
17:27:25 <jflory7> aikidouke^ see that.
17:27:27 <decause> mailga: and thank you for your input on that thusfar
17:27:33 <decause> mailga: that needs to be higher on my priority list too
17:27:39 <jflory7> aikidouke++ for looking at opening the discussion with Infra :)
17:27:39 <zodbot> jflory7: Karma for aikidouke changed to 7 (for the f23 release cycle):
17:27:45 <aikidouke> yep
17:27:52 <decause> mailga: when do you think we should get that out the door?
17:28:02 <jflory7> mailga: That would go hands-on with the retrospective we were wanting to start!
17:28:08 <jflory7> I totally forgot about that until now.
17:28:08 <jflory7> mailga++
17:28:10 <mailga> decause asap, IMHO
17:28:18 <decause> mailga: let's shoot for EoW
17:28:21 <jflory7> Holiday fog, I can't believe I forgot about that.
17:28:43 <decause> mailga: maybe ping the mktg list one more time, asking for input, and letting folks konw that we want to use it for YiR posts in the next week or two
17:28:51 <decause> mailga: sound good?
17:28:58 <mailga> decause +1
17:29:15 <jflory7> +1 to the idea from me too
17:29:19 <decause> mailga: lets shoot for retrospective done on wiki by EoW, and YiR by EoW next week?
17:29:37 <decause> #info EoW = End of Week
17:29:38 <mailga> decause: a YiR should be the starting point for next year... and the next year just started.
17:29:59 <decause> mailga: as long as we get our YiR content out before Feb, we're on track
17:30:28 <decause> once January is gone though, the content won't be as fresh
17:30:28 <mailga> decause I'll shoot a reminder mail on mktg list today.
17:30:32 <decause> mailga++
17:30:35 <jflory7> mailga++
17:30:35 <jflory7> Anything else for Ticket #20?
17:30:48 <decause> #action mailga ping mktg list again on retrospective to be completed by end of week
17:31:09 <decause> jflory7: we got into a few other loops, but i think we're good. we'll sync after this.
17:31:13 * jflory7 nods
17:31:15 <jflory7> #info === Ticket #22 - ===
17:31:22 <jflory7> #info * Publishing graphics tools / resources via Fedora Magazine Images Repo
17:31:43 <jflory7> See my last comment on that ticket
17:31:43 <jflory7> There is a Magazine page with that info
17:31:49 <jflory7> Although it isn't in an easily viewable location
17:31:54 <jflory7> You have to know it's there or have someone link you.
17:32:06 <jflory7> #link
17:32:27 <jflory7> Perhaps adding a section in the "Writing for the CommBlog" page about featured images and linking to the Magazine about how to make one for an article if you want to?
17:32:39 <decause> I think that we can just make a link in our toolbox wiki section, and basically regex magazine/commblog, and post our own how-to within the "writing for commblog" page?
17:32:45 <jflory7> Still wondering if we should do something beyond that to make it more exposed.
17:32:47 <decause> jflory7: nod nd nod
17:32:52 <jflory7> decause: It's in our toolbox as of yesterday :)
17:32:56 <decause> jflory7: you are reading my mind :)
17:33:16 <decause> jflory7: I don't think it is a big issue that it doesn't have menu real-estate
17:33:29 <aikidouke> just curious, are images from sites like unsplash usuable in fedora content
17:33:37 <decause> I'm not as worried about it being discoverable, as much as we need to be able to point at it when needs be
17:33:41 <jflory7> So basically make the same page on the Magazine our own independent page on the CommBlog?
17:33:41 <aikidouke> i beleive they are CC do what you want with
17:33:52 <jflory7> aikidouke: I think it depends on the licensing - I'm not familiar with Unsplash specificallyu.
17:33:54 <decause> aikidouke: if it is CC, it is potentially usable
17:33:58 <jflory7> s/specificallyu/specifically
17:34:10 <decause> our magazine images repo is specific graphics made for banners by Fedora Design and other contributors
17:34:15 <decause> they could be useful elsewhere too
17:34:32 <jflory7> decause: My main thought on mirroring for the CommBlog is that we don't really have a high barrier for featured images for our articles.
17:34:37 <jflory7> They're nice to have
17:34:44 <decause> jflory7: agreed
17:34:55 <jflory7> But I imagine it might appear intimidating to some who are writing for the first time
17:34:55 <decause> it is also a good candidate for design-team onboarding
17:35:00 <jflory7> Ooh, yeah
17:35:02 <aikidouke> link if ne1 is curious; All photos published on Unsplash are licensed under Creative Commons Zero which means you can copy, modify, distribute and use the photos for free, including commercial purposes, without asking permission from or providing attribution to the photographer or Unsplash.
17:35:04 <aikidouke> oops
17:35:06 <jflory7> Didn't think of it like that
17:35:16 <aikidouke>
17:35:17 <jflory7> aikidouke: I want to say that would be okay to use?
17:35:34 <jflory7> Pretty sure public domain is safe.
17:35:45 <decause> aikidouke: that would be a great resource for folks looking to use graphics within their featured images, yes
17:35:53 <aikidouke> cool
17:36:00 <decause> we can add that to our "writing for commblog" section on graphics perhaps
17:36:11 <jflory7> Ooh, looking at the site now
17:36:15 <jflory7> This is a good treasure trove
17:36:18 <aikidouke> ikr :)
17:36:19 <jflory7> #link
17:36:38 <jflory7> #action jflory7 Add as a resource for finding images to "Writing for CommBlog" page
17:36:45 <jflory7> aikidouke++
17:36:58 <aikidouke> one more if you havent seen it;
17:37:00 <decause> ok, we're just past the half-way point
17:37:03 <decause> timecheck
17:37:14 <jflory7> So beyond our toolbox and CommBlog mention, anything else we want to do with this?
17:37:36 <decause> jflory7: maybe update the ticket with ideas from this meeting, after this meeting
17:37:57 <decause> it's low-prio for me right now, but also not too intense of a task if anyone wanted to pick it up
17:38:01 <jflory7> #agree Fedora Magazine Images repo in CommOps toolbox, to be mentioned / added to "Writing for CommBlog" - still an ongoing discussion, details will be added to ticket for further discussion
17:38:03 * jflory7 nods
17:38:17 <decause> jflory7: next
17:38:17 <jflory7> So I think that will wrap up today's tickets
17:38:22 <decause> awesome!
17:38:26 <jflory7> #topic Wiki Gardening
17:38:26 <mailga> ?
17:38:31 <jflory7> #action NewMembers Add your timezone / interests on CommOps Wiki [ ]
17:38:37 <jflory7> mailga: What's up?
17:38:54 <jflory7> decause: Anything you wanted to add to wiki gardening for today?
17:39:11 <mailga> not really important, but some days ago talking with Paul
17:39:20 <decause> jflory7: I got one
17:39:35 <decause> this is a recently added wiki page:
17:39:38 <decause> #link
17:39:46 <danofsatx> ohhai ;)
17:39:47 <mailga> I didn't understand the raelly diccerences between commblog and magazine posts.
17:40:03 <decause> if there are other leadership positions within Fedora that do not have a wiki page, that is something commops can help with
17:40:06 * mailga sorry very slow.....
17:40:20 <decause> I'm thinking of the D&I advisor specifically, but also, our release manager would be a good one too
17:40:29 <jflory7> mailga: Hmmm - I think if that's something you're a little confused on, then there's likely many others who may feel the same way. We could probably use a little more specific clarification.
17:40:57 <mailga> jflory7: +1 a wikipage?
17:41:02 <jflory7> decause: I did see that wiki page added! Good call for D&I. Who is release manager?
17:41:04 <jflory7> danofsatx: Hiya!
17:41:18 <jflory7> mailga: I think a wiki page would be good. I also like the idea of adding it somewhere obvious to the CommBlog.
17:41:23 <jflory7> To answer your question though--
17:41:23 <decause> mailga: CommBlog and Magazine are two of our official channels of communication. Magazine is specifically focused on User content, whil CommBlog can include more Contributor focused content, and stuff outside of Fedora that is interesting to Fedora.
17:41:27 <decause> jflory7: 6
17:41:27 <jflory7> ^
17:41:29 <jflory7> Or that.
17:41:31 <jflory7> :)
17:41:47 <decause> jflory7: wouldn't be a bad idea to add that description to the commblog toolbox entry
17:41:47 <jflory7> decause: 6?
17:41:53 * jflory7 nods
17:41:56 <decause> jflory7: I missed the shift key ;)
17:42:03 <mailga> decause: jflory7 tnx.
17:42:05 <jflory7> Ahhh, gotcha. :)
17:42:08 <decause> mailga++
17:42:11 <decause> good question
17:42:57 <decause> #action commops create a ticket to create a wiki page for Release Manager, RelEng Lead, and Diversity and Inclusion Advisor (among any other new Fedora Leadership postions not on the wiki yet)
17:43:11 <jflory7> #action jflory7 Add clarification about Magazine vs. CommBlog to our toolbox, add section to Community Blog wiki page about CommBlog vs. Magazine specifically
17:43:16 <decause> jflory7: that is all I got for wiki gardening fo rnow
17:43:16 <jflory7> decause++
17:43:23 <jflory7> I think same for me
17:43:27 <decause> next :)
17:43:28 <mailga> ?
17:43:30 <jflory7> Anything else wiki-related anyone wants to add?
17:43:34 <jflory7> mailga: Go ahead.
17:44:00 <mailga> can we ask to each group to merge pages that need love?
17:44:09 <mailga> such as
17:44:12 <mailga> ?
17:44:14 <jflory7> mailga: I like that idea of decluttering the wiki a good bit.
17:44:27 <decause> mailga: that is exactly what this section of the meeting is for mentioning
17:44:30 <decause> :)
17:45:03 <decause> mailga: Feodra-infra has been tackling "technical debt" this week too, so "housekeeping" in commops land include wiki
17:45:23 <jflory7> Do we want to ticket that?
17:45:39 <mailga> decause: we need people to work on it.
17:45:43 <jflory7> Would be a good topic to open discussion for.
17:45:43 <decause> jflory7: yes, let's file a ticket so mailga can get some help with all that
17:45:49 <decause> mailga++
17:45:55 <jflory7> mailga: Do you want to file the ticket or would you rather me file it?
17:46:01 <mailga> decause: of course.
17:46:10 <decause> nice job laying out the task list, this is a great way for us to get more heat into mktg
17:46:20 <decause> mailga++
17:46:22 <decause> nice work there
17:46:36 <mailga> jflory7: if you can do that I can go to have a dinner :-D
17:46:40 <mailga> ;-)
17:46:41 * jflory7 nods
17:46:43 <jflory7> No problem :)
17:46:44 <decause> jflory7: thanks
17:46:47 <decause> mailga++
17:46:49 <decause> enjoy dinner
17:47:02 <mailga> decause: I have to cook... ;-(
17:47:09 <decause> mailga: :P
17:47:15 <jflory7> #action jflory7 Open ticket on Trac about starting initiative / movement to encourage subgroups to merge related wiki pages (reducing clutter)
17:47:21 <jflory7> Anything else for wiki gardening?
17:47:29 <jflory7> We've got 13 minutes on the clock but I think we can fit the last bit in
17:47:36 <decause> jflory7: specifically a ticket for the mktg updates mailga posted to?
17:47:42 <decause> too*
17:47:51 <decause> I'm good on wiki after that
17:48:01 <bee2502_> This is not exactly a wiki task - the page could surely use some love - but I would like to discuss on this : decause jflory7
17:48:13 <bee2502_> Comes under CommOps right ?
17:48:35 <jflory7> #action jflory7 / mailga: Create and discuss a ticket about the Marketing retrospective and its usefulness for the Year in Review article as well
17:48:37 <jflory7> bee2502++
17:48:38 <jflory7> Yes!!
17:48:40 <decause> bee2502++
17:48:49 <decause> yes, def under comops
17:49:42 <jflory7> We could definitely go through that wiki page and do some updating, especially looking at this article we're looking at preparing too
17:49:43 <decause> bee2502_: I will be moderating a Women in Open Source panel at NYU in the next couple of weeks, so I'd really like to have as much updated info there for the potential new contribs who will be hearing about Fedora then too
17:49:58 <bee2502_> decause does Fedora have any women specific initiatives ? Debian has
17:50:08 <decause> bee2502_: let's open a loop on the mail list, cc tatica and mizmo (who is on leave) and ask folks to update the page?
17:50:13 <jflory7> I think a ticket for this page would definitely be best to help us keep tabs on this
17:50:24 <jflory7> And a discussion on the list too
17:50:29 <decause> jflory7: pointing to the ticket
17:50:35 <bee2502_> jflory7 : yeah , the article is why I started searching :)
17:50:35 <decause> #byourpowerscombined
17:51:03 <jflory7> bee2502_: As far as I know, Outreachy was the first major "initiative", but I really haven't been around for all too long.
17:51:10 <bee2502_> decause - we are having an article out on CommBlog about women in Fedora - sort of - prolly would be helpful
17:51:11 <jflory7> I'm inclined to think something has been done before, though.
17:51:36 <decause> bee2502_: Outreachy is one of the big drivers here for us, but adding tatica to the council will help us do more too
17:51:47 * mailga thinks we need people don't disappear. Yes someone can do the work when he/she can, but someone should take the commitment to be available.
17:52:01 <decause> bee2502_: that page does need to be updated, and I think there are new women to be added to that page also
17:52:08 <jflory7> In the interest of time, I recommend we make a ticket specifically for the wiki article and look at keeping it updated and current.
17:52:38 <jflory7> mailga: Definitely agreed.
17:52:43 <decause> bee2502_: can you file a ticket on the commops tracker to update the women wiki page, and then we cant post to the women/outreach/outreachy lists with a request to update the info before 1/22?
17:53:04 <decause> that is when I'll be moderating at the Women In Tech Conference
17:53:04 <bee2502_> decause - I was thinking we could link the page with CommBlog article to reach more women
17:53:11 <decause> bee2502_: I like that too
17:53:15 <jflory7> +1
17:53:17 <bee2502_> decause sure
17:53:27 <decause> lets start with ticket, get that posted to mail list, and then post basically the same message tohte commblog
17:53:34 <decause> bee2502++
17:53:36 <decause> all sounds good
17:53:51 <jflory7> bee2502_: We could maybe even do a call-to-action at the end of the article to ask women to add themselves to the wiki article too. We can discuss more in channel after meeting. :)
17:53:58 <decause> bee2502++
17:54:04 <decause> bee2502++
17:54:04 <decause> bee2502++
17:54:04 <decause> good eye bee2502
17:54:13 <jflory7> Going to fly through CommBlog really fast, if that's alright?
17:54:19 <decause> go go :)
17:54:21 <jflory7> #topic Community Blog
17:54:26 <jflory7> #info === This Week in CommBlog ===
17:54:31 <jflory7> #info * “Top Badgers” of 2015: Robbie Harwood (rharwood)
17:54:36 <jflory7> #link
17:54:40 <jflory7> #info Total Views (Jan. 7 - 11): 30
17:54:43 <bee2502_> #action bee2502 file a ticket on Commops to update Fedora women wiki page asap
17:54:44 <jflory7> Social media bump?
17:54:49 <jflory7> bee2502++
17:54:51 <jflory7> #info === Coming Up in CommBlog ===
17:54:54 <decause> jflory7: add to our bkp email
17:54:54 <bee2502_> decause i like the sound of it
17:54:55 <jflory7> #info More "Top Badgers" articles scheduled
17:55:04 <jflory7> #info CommOps Year in Review - already discussed in Ticket #20
17:55:15 <jflory7> #info Women in Computing article - discussed earlier
17:55:38 <jflory7> #action jflory7 / decause Add "Top Badger" article to bkp email about social-media
17:55:49 <jflory7> Anything else CommBlog we want to hit?
17:56:05 <bee2502_> gource videos post on CommBlog
17:56:06 <decause> YiR will be top billing for the next week or two
17:56:33 <decause> bee2502_: we could do a "here are all of them" and/or we could add them to each YiR article (or section of big article)
17:56:36 <decause> I'm good either way
17:56:38 <jflory7> bee2502_: Ooh, yeah. I haven't been too up-to-date about that, but I saw you and threebean's discussion.
17:56:54 <jflory7> #info "Year in Review" articles for CommOps and other subgroups is top priority on the CommBlog for the next few weeks
17:57:05 <decause> bee2502_: I think we should start a draft for the big YiR article, and include them all there
17:57:24 <threebean>
17:57:28 <decause> threebean++
17:57:31 <jflory7> threebean++ Nice!
17:57:33 <bee2502_> decause they are not team specific - we could include the aggregate video in the overall YiR article
17:57:38 <bee2502_> threebean++
17:57:49 <decause> #link
17:58:03 <jflory7> threebean: I'll have to tackle downloading some of these when I'm back on the RIT 'net :)
17:58:23 <decause> threebean: does fedora have a vimeo account?
17:58:30 <decause> or a youtube?
17:58:42 <decause> (youtube does cc)
17:58:47 <jflory7> (As an aside, I think we can probably skip over 5tftw in this week's meeting because there's not much that has changed since last meeting about that)
17:58:52 <bee2502_> jflory7 - I tried, broke lobby net :P
17:59:00 <jflory7> Whoops!
17:59:00 <threebean> decause: I don't know.  ;)
17:59:06 * linuxmodder sorry had an  odd d/c and  client  walk-in -- reading scrollback
17:59:07 <decause> threebean: I'll look into it
17:59:12 <jflory7> linuxmodder: No worries@!
17:59:16 <jflory7> * !
17:59:33 <decause> #action decause find out if there is a place for Fedora Videos like YouTube or Vimdeo
17:59:49 <decause> ok, 1 minute :P
17:59:53 <decause> jflory7: any other commblog?
17:59:58 <jflory7> Nope, not from me
18:00:03 <decause> kk
18:00:03 <jflory7> Just noticed your Flock topic
18:00:08 <jflory7> Full steam ahead!
18:00:10 <decause> jflory7: paste it here quick
18:00:17 <jflory7> #topic Flock
18:00:17 <linuxmodder> like the old fudcon  videos  hosted on  infra ?
18:00:23 <bee2502_> no official fedora account on you tube , it seems
18:00:23 <jflory7> #info CommOps will be playing a larger role in Flock Planning this year
18:00:41 <jflory7> decause: What time zone?
18:00:44 <decause> EST
18:00:45 <jflory7> For the 2pm time?
18:00:54 <jflory7> #info Flock-planning meeting call tomorrow at 19:00 UTC. Will report back to list, cc commops list
18:01:07 <linuxmodder> Redhat  has a  official  YT channel  don't see the  reason we couldn't do a  community  channe;
18:01:07 <linuxmodder> channel*
18:01:26 <decause> #info bex will be doing a site visit in Krakow this weekend, will report back with more financial details next week
18:01:44 <decause> jflory7: anything else
18:01:50 <jflory7> Not from me--
18:01:54 <decause> kk
18:01:55 <jflory7> #topic Open Floor
18:01:59 <decause> any other biz
18:02:03 <decause> we've got 4 mins :)
18:02:05 <jflory7> linuxmodder: I like the idea of a Fedora video presence
18:02:05 <bee2502_> nope here -
18:02:26 <decause> jflory7: I /vaguely/ recall us having a youtube... but I gotta check with bkp
18:02:45 <jflory7> decause: Yeah, let's look into that with the bkp email
18:03:00 <jflory7> #action jflory7 / decause Follow up with bkp about if Fedora has a YouTube
18:03:01 <decause> jflory7: we should probably just get a 1x1 with him on the regs :P
18:03:06 <jflory7> Hahah, yeah :P
18:03:12 <jflory7> Other than that, I'm good
18:03:19 <jflory7> Another super packed meeting today!!
18:03:22 <decause> he's asking for content bigtime, and we have a bunch w can share
18:03:28 <jflory7> Ohhh yeah, we have a lot, lol
18:03:34 <decause> yes, great meeting all, lots of good things brought to the table
18:03:44 <bee2502_> whos bkp ?
18:04:09 <decause> what I really like about having meetings is that each of you have items for the agenda that you bring to the table. This is awesome to have contributions, not just a task list to run though :)
18:04:23 <jflory7> aikidouke++ bee2502++ threebean++ linuxmodder++ danofsatx++ decause++ mailga++ Thanks for coming out today, all. :)
18:04:27 <decause> bee2502_: Brian Profitt, social media manager fr OSAS
18:04:31 <decause> thanks all
18:04:52 <jflory7> Shall we close out and continue in #fedora-commops?
18:04:52 <bee2502_> ok :)
18:05:00 <decause> mailga: thanks for the mktg updates
18:05:13 <bee2502_> Marching to CommOps ..
18:05:18 <jflory7> #endmeeting