17:01:52 <jflory7> #startmeeting CommOps 2016-01-19
17:01:52 <zodbot> Meeting started Tue Jan 19 17:01:52 2016 UTC.  The chair is jflory7. Information about MeetBot at
17:01:52 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:01:52 <zodbot> The meeting name has been set to 'commops_2016-01-19'
17:01:56 <jflory7> #meetingname CommOps
17:01:56 <zodbot> The meeting name has been set to 'commops'
17:02:14 <decauseMovesToNC> #chairs
17:02:17 <decauseMovesToNC> plz
17:02:18 <decauseMovesToNC> :)
17:02:19 <jflory7> #chair decause
17:02:19 <zodbot> Current chairs: decause jflory7
17:02:24 <jflory7> #chair decauseMovesToNC
17:02:24 <zodbot> Current chairs: decause decauseMovesToNC jflory7
17:02:30 <decauseMovesToNC> lol
17:02:34 * jflory7 is pulling up wiki page now
17:02:44 <decauseMovesToNC> #topic Agenda
17:02:51 <danofsatx> .hello dmossor
17:02:51 <zodbot> danofsatx: dmossor 'Dan Mossor' <>
17:03:02 <jflory7> #chair decause jflory7 threebean bee2502 lmacken cproffit mailga danofsatx
17:03:02 <zodbot> Current chairs: bee2502 cproffit danofsatx decause decauseMovesToNC jflory7 lmacken mailga threebean
17:03:12 <jflory7> #info 1. Roll Call
17:03:18 <jflory7> #info 2. Announcements
17:03:20 <jflory7> #info 3. Tickets
17:03:22 * mailga is around (more or less) and vawes commops people.
17:03:23 <jflory7> #info 4. Wiki Gardening
17:03:26 <danofsatx> 4. snax
17:03:28 <jflory7> #info 5. Community Blog
17:03:34 <jflory7> #info 6. Open Floor
17:03:44 <decauseMovesToNC> #toic RollCall
17:03:44 <jflory7> This week's meeting is packed!!
17:03:48 <decauseMovesToNC> .hello decause
17:03:48 <jflory7> .hello jflory7
17:03:49 <zodbot> decauseMovesToNC: decause 'Remy DeCausemaker' <>
17:03:52 <zodbot> jflory7: jflory7 'Justin W. Flory' <>
17:04:04 <danofsatx> since I was premature....
17:04:07 <danofsatx> .hello dmossor
17:04:08 <zodbot> danofsatx: dmossor 'Dan Mossor' <>
17:04:21 <jflory7> #info Justin W. Flory; UTC-5; CommOps, Marketing, Fedora Join, Ambassadors, and more
17:04:24 <jflory7> danofsatx: No worries. :)
17:04:39 <jflory7> danofsatx: Glad you could make it today!
17:04:42 <jflory7> Hi to mailga too. :)
17:04:58 <danofsatx> #info Dan Mossor; UTC-6, CommOps, Ambassador, QA, KDE, Server
17:05:14 <decauseMovesToNC> #info decuase; UTC-5 (But now in Raleigh); CommOps, Mktg, Join, Ambassadors, Council, Outreachy, *
17:05:26 * decauseMovesToNC waves to tatica
17:05:37 <tatica> o/ oi oi
17:05:39 <jflory7> decauseMovesToNC: Glad you made it there safely :)
17:05:41 <jflory7> Hiya, tatica!
17:05:45 <danofsatx> decauseMovesToNC: you permanently in RDU, or just visiting?
17:05:58 <decauseMovesToNC> danofsatx: for the forseeable :)
17:06:01 <decauseMovesToNC> loving it so far
17:06:11 <jflory7> So, only because today's agenda is pretty full, I think we should jump straight in
17:06:11 <decauseMovesToNC> danofsatx: happy to chat after
17:06:16 <decauseMovesToNC> jflory7: nod nod nod
17:06:18 <jflory7> People can do roll call as they come along
17:06:19 <danofsatx> roger, will do
17:06:23 <jflory7> #topic Announcements
17:06:29 <jflory7> #info === Ticket #8 - ===
17:06:33 <jflory7> #info * CommBlog Article: Flock Call for Bids
17:06:39 <jflory7> #info Ticket closed, no longer relevant - official Flock announcement coming soon, to be discussed later in Tickets topic
17:06:44 <jflory7> #info === Ticket #13 - ===
17:06:50 <jflory7> #info * Get a CommOps graphics upgrade
17:06:53 <jflory7> #link
17:06:58 <jflory7> #info Final vote on wiki banner needed to move forward - CommOpsers, please view Design Team ticket and leave your feedback
17:07:03 <jflory7> #action decause View wiki banner ticket in Design Team Trac and give final sign-off
17:07:07 <decauseMovesToNC> jflory7: ack
17:07:12 <jflory7> Anyone is welcome to leave feedback on this too. :)
17:07:18 <jflory7> The more voices, the better!
17:07:39 <jflory7> #info === Ticket #18 - ===
17:07:43 <jflory7> #info * Reduce button size for Categories menu
17:07:48 <jflory7> #link
17:07:53 <jflory7> #info ryanlerch prefers having Community Blog theme issues filed on Pagure - for future reference, file issues with CommBlog theme there
17:07:57 <jflory7> #link
17:08:08 <jflory7> That's all of the announcements I have for now. Anyone else have anything?
17:08:16 <decauseMovesToNC> YiR was published
17:08:26 <decauseMovesToNC> #link
17:08:42 <decauseMovesToNC> congrats team and thanks all for your contributions this past year!
17:08:51 <decauseMovesToNC> EoF
17:08:57 <jflory7> decauseMovesToNC: Oh yeah, right. :) Duh.
17:09:01 <jflory7> How did I forget that?
17:09:05 <jflory7> CommOps++
17:09:11 <decauseMovesToNC> CommOps++
17:09:21 <decauseMovesToNC> jflory7: next
17:09:30 <jflory7> #topic Tickets
17:09:34 <jflory7> #info === Ticket #17 - ===
17:09:45 <jflory7> #info * Interview Fedora's Diversity and Inclusion Advisor, tatica
17:10:01 <jflory7> So, looking at where we left off...
17:10:42 <tatica> jflory7, if you need anything just let me know a date-hour and consider it done
17:10:45 <jflory7> We were hoping tatica might be able to identify a few topics or areas of her position that might be unclear or anything that people might have questions about.
17:10:50 <jflory7> From there...
17:11:11 <jflory7> We were hoping to query the mailing list (CommOps) and maybe another list or two for specific questions from the community for her to answer.
17:11:19 <jflory7> With the areas identified by tatica in mind.
17:11:21 <tatica> just one thing, it's "appointed" not "hired" :)
17:11:24 <jflory7> If that makes sense?
17:11:26 * jflory7 nods
17:11:28 <decauseMovesToNC> jflory7: we can start with a "welcome" post
17:11:35 <jflory7> tatica: Thanks for the clarification.
17:11:41 <decauseMovesToNC> I think that it is totally awesome just to announce she is here
17:11:49 <decauseMovesToNC> we can do another post with an ama
17:11:52 <jflory7> decauseMovesToNC: Yeah, I was thinking it would be a welcome + interview? Or should we separate, do you mean?
17:11:54 <jflory7> Ahhh, gotcha.
17:11:56 <decauseMovesToNC> and we can annouce the Q&A in the welcome
17:11:57 <jflory7> I can agree with that.
17:12:14 <jflory7> It's a totally new position so an announcement sounds like a good idea to me. Can follow up with an interview.
17:12:33 <decauseMovesToNC> Tatica has been around Fedora for a long time, and is a leader in the LATAM FOSS community. it is big news for the project that she is here now, and part of the council as well
17:12:37 <tatica> decauseMovesToNC, do you think we could have the survey done by the time this article comes up?
17:12:52 <tatica> probably would be a nice moment to push the survey since people will be listening about it for the first time
17:13:05 <decauseMovesToNC> tatica: good question. I saw that you sent me the first draft, have yet to look at it (meetings all morning so far)
17:13:08 <tatica> I wouldn't like to go out with just ideas, but with something people can interact with
17:13:26 <danofsatx> I have to respectfully bow out - I need to be at school in 45 mins, and I need to get ready.
17:13:42 <jflory7> danofsatx: Thanks for the heads-up - I'll get the minutes out to the list afterwards. :)
17:13:46 <decauseMovesToNC> danofsatx: kk, thnks for stopping by
17:13:52 * danofsatx will read logs and place appropriate votes in tickets
17:13:56 <jflory7> danofsatx++
17:14:14 <decauseMovesToNC> tatica: we can talk after this meeting too, lemme know in #fedora-commops a rough idea of your availability today
17:14:18 <jflory7> tatica: Are we referring to the User poll mentioned in the CommOps YiR, or is this the survey of our questions to the list?
17:14:29 <decauseMovesToNC> #action decause/tatica set up a regular 1x1
17:14:43 <tatica> I should be available for the next 5 or 6 hours
17:14:51 <decauseMovesToNC> jflory7: we're still figuring out which is which
17:15:01 <tatica> I'm mostly available during office hours, all week
17:15:07 <decauseMovesToNC> tatica: awesome
17:15:17 <decauseMovesToNC> I'm going to lunch after this, but will be available shortly thereafter
17:15:31 <jflory7> decauseMovesToNC: I was meaning the interview questions for the article or the big picture poll that we mentioned in our YiR.
17:15:52 <tatica> jflory7, mostly I want to know what am I dealing with. A survey to determine the wide range of diverse people in our community will provide me more information on those areas we need to improove-help-etc
17:16:00 <decauseMovesToNC> jflory7: tatica: my thinking here is that we just do a really simple "welcome tatica" post, with a background/bio, description of the position, and then do a few direct Qs.
17:16:18 <jflory7> tatica: Gotcha, so the big picture poll. Got it. :)
17:16:25 <tatica> aye
17:16:38 <decauseMovesToNC> in those Q's, we can mention the demographics survey (soon to come, separate post to follow) and an invitation to ask questions on lists/in channel.
17:16:43 <jflory7> decauseMovesToNC: Same article or separate?
17:17:32 <decauseMovesToNC> I don't want to rush our demographics survey, or our user survey (if those end up being different things) but I DO want to rush the "welcome tatica" post
17:17:47 <decauseMovesToNC> tatica: can you make the council meeting on Monday next week?
17:18:12 * jflory7 nods
17:18:13 <jflory7> decauseMovesToNC: Right.
17:18:24 <tatica> sure
17:18:37 <tatica> decauseMovesToNC, just ping me when the time comes, I'm awful with UTC
17:18:37 <decauseMovesToNC> tatica: and by "rush" I mean try to get it announced by next week at the latest
17:18:43 <jflory7> So, consensus on the ticket, I'm thinking: decauseMovesToNC and tatica 1x1 to focus on details, report back to IRC / mailing list later?
17:18:54 <tatica> +1 from me
17:18:56 <jflory7> And roll with it as we progress?
17:19:26 <decauseMovesToNC> tatica: also, I'm going to speak at a Women In computing conference on Friday, and it would be *really* awesome to point possible new contributors to the welcome post
17:19:44 <decauseMovesToNC> it isn't a blocker, but a would be nice
17:20:01 <tatica> fantastic!
17:20:08 <decauseMovesToNC> the blocker will be getting outreachy details as solid as I can before then, which is oging ot happen on a call tomo
17:20:38 <decauseMovesToNC> jflory7: lets all talk in channel later today and lock down the Q&A and draft for the welcome
17:20:47 <decauseMovesToNC> we're eating up ticket time atm, and too many details to work out still
17:21:04 <jflory7> decauseMovesToNC: Ohh, on Friday? You haven't happened to see the draft of "Women in Computing and Fedora" that bee2502 and I were working on? Might be useful, can discuss later on. Could be ready by Friday.
17:21:05 * jflory7 nods
17:21:25 <jflory7> #agreed Later discussion to be held about official welcome for tatica in IRC today
17:21:27 <decauseMovesToNC> jflory7: yes, good good good. I think I mentioned to bee2502 that this was going on, so good timing
17:21:35 <decauseMovesToNC> jflory7: next ticket
17:21:41 <jflory7> #info === Ticket #13 - ===
17:21:46 <jflory7> Err--
17:21:47 <jflory7> #undo
17:21:47 <zodbot> Removing item from minutes: INFO by jflory7 at 17:21:41 : === Ticket #13 - ===
17:21:58 <jflory7> #info === Ticket #23 - ===
17:22:02 <jflory7> #info * Update Fedora Women Wiki page
17:22:31 <jflory7> Hmm. This one was mostly bee2502's ticket. I wasn't sure if we wanted to discuss this more now or if it's something to pass onto next week.
17:23:01 <jflory7> In the Agenda, Ticket #20 is listed as a ticket to be covered, but it's no longer relevant since our YiR is now published. :)
17:23:02 <decauseMovesToNC> again, ideally by Friday we'd have this somewhat updated. Perhaps we can post a quick "invitation to edit" email to the outreachy and women's list, after adding some new tables
17:23:11 <jflory7> Didn't have time to move it out
17:23:16 <decauseMovesToNC> no worries :)
17:23:29 <jflory7> decauseMovesToNC: I like that idea. Are there any specific objectives in terms of updating the list of things we want to see updated / added?
17:24:10 <decauseMovesToNC> jflory7: outreachy interns added, links to OUtreachy resources, links to CommOps/Join
17:24:17 <decauseMovesToNC> I'm open to other ones as well
17:24:24 <jflory7> Maybe encourage women contributors to add themselves to the list or add new external references to recent aritcles, plus Outreachy?
17:24:32 <jflory7> +Join / CommOps too, yes
17:24:34 <decauseMovesToNC> jflory7: yes, we'll etherpad a draft today
17:24:43 <jflory7> So sounds like a good consensus for now then
17:25:12 <decauseMovesToNC> #action decause etherpad an invitation to edit the Women's wiki page to send to women@fp.o, outreach@fp.o
17:25:20 <decauseMovesToNC> jflory7: next
17:25:26 <jflory7> #agreed Women wiki article should have Outreachy interns added, mention Fedora's involvement with Outreachy, link to CommOps and Join pages; women contributors should be encouraged to add themselves to the page too
17:25:42 <jflory7> #info === Ticket #24 - ===
17:25:47 <jflory7> #info * Finish 2015 Marketing Retrospective and share with mailing lists
17:25:49 <jflory7> cc: mailga
17:25:58 <jflory7> So, the Retrospective is finished as far as I am aware
17:26:05 <decauseMovesToNC> #action decause review draft of mktg YiR
17:26:08 <jflory7> I know mailga got a draft of Marketing YiR on the CommBlog.
17:26:11 <jflory7> mailga++
17:26:14 <decauseMovesToNC> mailga++
17:26:19 <decauseMovesToNC> nice work
17:26:25 <jflory7> I had it open last night too but ran out of time to give a full read. Hoping to nail it today too. :)
17:26:35 <decauseMovesToNC> jflory7: link maybe?
17:26:42 <jflory7> Only last question I have is if the wiki portion of the Marketing retrospective is finished.
17:26:48 <jflory7> Let me dig the links up, yes.
17:26:56 <decauseMovesToNC> jflory7: thanks
17:27:14 <jflory7> #action decause / jflory7 Review and edit Marketing Year in Review article for publishing as soon as possible
17:27:22 <mailga> jflory7 decauseMovesToNC that's all from me. There's a lot of things to say, but the YiR is not the right place.
17:27:38 <jflory7> #link
17:27:52 <decauseMovesToNC> mailga: nod nod nod
17:28:15 <jflory7> #link
17:28:35 <jflory7> mailga: It's a lot of good discussion topics for the Marketing meeting. Really looking forward to getting that on track again.
17:28:47 <jflory7> So other than that, I think we're good on this ticket.
17:28:54 <decauseMovesToNC> jflory7: yes, we should pull the trigger on setting the time
17:28:55 <jflory7> Mainly looking at getting their YiR up and ready and published
17:29:12 <jflory7> decauseMovesToNC: Agreed. Hoping to get croberts to fill in the poll too
17:29:16 <decauseMovesToNC> #action commops officially pick a time/date for the mktg meetings due:Friday
17:29:27 <jflory7> He came back yesterday and said he had new energy for Marketing again and wants to be involved with efforts in 2016
17:29:29 <jflory7> croberts++
17:29:40 <jflory7> Anyways, I think next ticket now
17:29:46 <decauseMovesToNC> jflory7++
17:29:50 <jflory7> #info === Ticket #26 - ===
17:29:54 <jflory7> #info * Mailing lists analysis and graphs
17:29:59 <jflory7> This one was more of an update than anything
17:30:04 * mailga thinks we need croberts.
17:30:08 <jflory7> mattdm hit the mailing list with this one, as a request
17:30:10 <jflory7> mailga: Me too.
17:30:32 <jflory7> He was requesting specific metrics about our mailing lists analyzed in a variety of ways, by contributors and specific threads in lists.
17:30:45 <jflory7> He identified a few key lists as part of what the "face" of Fedora MLs should be
17:30:55 <jflory7> Others as extra lists that are good as their own standalone metrics
17:30:59 <decauseMovesToNC> mattdm++
17:31:00 <jflory7> It's a long-term task, I'm thinking
17:31:16 <jflory7> He said it would be nice to have ASAP for decauseMovesToNC and mattdm but I know bee2502 has been busy lately with school applications too.
17:31:28 <decauseMovesToNC> jflory7: we've done /some/ analysis, but we could use some more in depth metrics
17:31:30 <jflory7> Unless someone else was willing to step up to it, I think it will depend on her schedule.
17:31:35 <jflory7> decauseMovesToNC: Agreed.
17:31:44 <jflory7> Maybe a joint project with bee2502 and threebean?
17:31:44 <decauseMovesToNC> #action decause lock down internal metrics presentation for next week before FOSDEM
17:31:55 <jflory7> As far as I know, this one is just aiming for someone willing to jump on it
17:32:03 <jflory7> Its only limit is energy :)
17:32:15 <jflory7> Otherwise, if not ready before FOSDEM, ready in F24 cycle for next Flock
17:32:15 <decauseMovesToNC> jflory7: yeah, there'll be a repo with scripts. We were using a tool from Grimoire that was quite effective, but didn't give us all the data we wanted
17:32:18 <jflory7> Sooner the better, though
17:32:34 <jflory7> decauseMovesToNC: Gotcha, that's good info. Any links to Grimoire?
17:32:39 <decauseMovesToNC> jflory7: this could be a *great* project for an outreachy intern
17:32:45 <jflory7> decauseMovesToNC: For sure!
17:33:28 <jflory7> So, my proposed consensus: ticket is available to be claimed by anyone willing, the sooner it's completed the better, but not an emergency. Absolute deadline Flock 2016?
17:34:18 * decauseMovesToNC has laptop issues, switches to mobile
17:34:24 <decauseMovesToNC> yes
17:34:42 <jflory7> #agreed Ticket can be claimed by anyone willing to take this task on (great project for an Outreachy intern). The sooner it's completed, the better, but it is not absolute emergency to be finished. ABSOLUTE deadline: Flock 2016
17:34:55 <jflory7> Next ticket, and this one will be for you, decauseMovesToNC :)
17:34:56 <decauseMovesToNC> next ticket
17:34:58 <decauseMovesToNC> :)
17:35:01 <jflory7> #info === Ticket #27 - ===
17:35:06 <jflory7> #info * Make official Flock 2016 announcement
17:35:10 <jflory7> #action decause Begin drafting official Flock 2016 article for CommBlog
17:35:14 * jflory7 passes the mic
17:35:35 <decauseMovesToNC> ok, it's not official, but I am going to let a little bit of the cat out of the bag
17:35:53 <decauseMovesToNC> because hey, you folks are here, and commops is going to be a big part of Flock organizing
17:36:25 <decauseMovesToNC> we're looking at 8/2-8/5 as the dates
17:36:42 <decauseMovesToNC> those are not confirmed yet, so don't make any social media announcments
17:36:47 * jflory7 nods
17:36:55 <decauseMovesToNC> #action decause send Thank You emails to all Flock Bidders
17:37:12 * mailga has missed something.... where will be held Flock 2016?
17:37:16 <decauseMovesToNC> jflory7: that announcement is due by 1/27 so we can tell the folks at FOSDEM
17:37:27 <decauseMovesToNC> mailga: I can't say just yet
17:37:41 <decauseMovesToNC> mailga: not until the ink dries on the venue
17:37:48 <jflory7> decauseMovesToNC: Cool - that deadline is currently in the ticket as well.
17:37:53 <decauseMovesToNC> jflory7: great
17:37:53 <mailga> decauseMovesToNC: ah! ok! suspance? :-D
17:37:58 <decauseMovesToNC> mailga: :)
17:38:06 <jflory7> mailga: Suspense indeed...
17:38:20 <mailga> jflory7: :-D
17:38:21 <jflory7> I have my thoughts, but... they are just thoughts!
17:38:29 <decauseMovesToNC> :P
17:38:30 <jflory7> Will be an exciting announcement. :)
17:38:33 <decauseMovesToNC> next ticket
17:38:34 <jflory7> decause++
17:38:46 <mailga> decauseMovesToNC: jflory7 suspense is a mktg strategy.
17:39:20 <jflory7> #agreed decause to help lead writing on Flock announcement, due by 1/27 before FOSDEM so the announcement can get more publicity; discussion will be ongoing, watch mailing list and IRC for more details as they come along
17:39:29 <jflory7> #topic Wiki Gardening
17:39:34 <jflory7> #action NewMembers Add your timezone / interests on CommOps Wiki [ ]
17:39:39 <jflory7> #info Outreachy wiki pages: what updating needs to be done?
17:40:00 <jflory7> I think another one for you, decauseMovesToNC :)
17:40:04 <decauseMovesToNC> jflory7: at the very least we need to add the schedule for the new round (which I think is round #12?)
17:40:16 <decauseMovesToNC> it should be on the upstream wiki page
17:40:19 <jflory7> I think I can find that info on the Outreachy wiki, right?
17:40:23 <jflory7> I can take that responsibility on for today
17:40:34 <jflory7> Unless anyone already had it planned in their cycles.
17:40:45 <decauseMovesToNC> as far as which positions/slots we will have, that is a convo to be had tomo with outreachy team members
17:40:50 * jflory7 nods
17:41:14 <jflory7> Oh, wait, this will be an entirely new Outreachy page too, right? fp.o/wiki/Outreachy/2016 ?
17:41:18 <decauseMovesToNC> #action decause schedule meeting with labbott, threebean, stickster, (hopefully) tatica about Outreachy discussion due:Thurs
17:41:36 <decauseMovesToNC> jflory7: yes, but I believe labbot has already forked it and started fresh
17:41:40 * jflory7 nods
17:41:43 <decauseMovesToNC> she said she was going to yesterday
17:41:51 <jflory7> Sounds good, I will leave it to you all then.
17:41:56 <decauseMovesToNC> we are just going to make sure that she gets support and more details
17:42:27 <jflory7> So, proposed consensus: Outreachy team members to discuss positions and slots, and any final updates to be made to Fedora's Outreachy presence?
17:42:37 <decauseMovesToNC> jflory7: nod nod
17:42:42 <jflory7> s/presence/wiki presence
17:43:05 <decauseMovesToNC> we've already gotten one interested applicant for the next round already on our mailing list :)
17:43:05 <jflory7> #agreed Outreachy team members to discuss positions and slots, and any final updates to be made to Fedora's Outreachy presence; any updates encouraged to be shared to mailing list too
17:43:15 <jflory7> Woot!
17:43:26 <jflory7> I'm super excited for the next round. :)
17:43:51 * jflory7 notes we have about fifteen minutes left, but thinks we're actually doing a little bit ahead of schedule
17:44:00 <decauseMovesToNC> good looking out
17:44:20 <jflory7> Unless there is more wiki gardening to add, I propose we head on to CommBlog
17:44:24 <decauseMovesToNC> nod nod
17:44:28 <jflory7> One new change not listed on the wiki that happened yesterday too
17:44:34 <jflory7> #topic Community Blog
17:44:34 <decauseMovesToNC> jflory7: we didn't do the standard announce though
17:44:38 <decauseMovesToNC> :P
17:44:43 <jflory7> #info === This Week in CommBlog ===
17:44:46 <jflory7> decauseMovesToNC: We did. :)
17:44:54 * decauseMovesToNC missed it
17:44:55 <jflory7> #info * "Top Badgers" of 2015: Piotr Popieluch (piotrp)
17:45:06 <jflory7> #link
17:45:24 <jflory7> decauseMovesToNC: I snuck it in right after the topic change. ;)
17:45:30 <jflory7> #info Total Views (Jan. 12 - 18): 22
17:45:35 <jflory7> #info * "Top Badgers" of 2015: Robert Mayr (robyduck)
17:45:41 <jflory7> #link
17:45:46 <jflory7> #info Total Views (Jan. 14 - 18): 76
17:45:51 <jflory7> Attributed to being latest article when Magazine article was published, bringing extra views to his article?
17:45:56 <jflory7> #info === Coming Up in CommBlog ===
17:46:00 <jflory7> #info More "Top Badgers" articles scheduled
17:46:07 <jflory7> #info CommOps Year in Review - already discussed in Ticket #20
17:46:13 <jflory7> #info Official Flock 2016 announcement - already discussed in Ticket #27
17:46:17 <jflory7> And now the new thing...
17:47:00 <jflory7> #info Fedora Council member Langdon White (langdon) added Fedora Modularization update as new article to CommBlog; currently scheduled for tomorrow morning unless there are objections
17:47:09 <decauseMovesToNC> langdon++
17:47:11 <decauseMovesToNC> nice work
17:47:22 <jflory7> Plus, it's a special video post too... so the featured image... is the YouTube video. I thought it was cool anyways :P
17:47:28 <decauseMovesToNC> yes
17:47:31 <jflory7> langdon++ for getting the CommBlog article drafted :)
17:47:31 <zodbot> jflory7: Karma for langdon changed to 3 (for the f23 release cycle):
17:47:43 <decauseMovesToNC> this is something that we are going to continue doing in 2016 after council meetings I reckon
17:47:50 <jflory7> Council++
17:48:02 <decauseMovesToNC> langdon++
17:48:33 <jflory7> decauseMovesToNC: Since you're in the Council, would be cool if you just gave it once-over and checked to see if there was any other text to be added. It was short and sweet and looked good to me, but might be good for you to glance at it. :)
17:48:39 <jflory7> Otherwise, I think it's ready for publishing tomorrow
17:48:49 <jflory7> It is scheduled so it should pop up bright and early at 8:00 UTC
17:48:58 <decauseMovesToNC> jflory7: yes
17:49:14 <decauseMovesToNC> #action decause review langdon's commblog update draft for modularization objective
17:49:32 <jflory7> #agreed Modularization update to go out as planned on 2016-01-20 at 8:00 UTC pending decause's final check
17:49:48 <jflory7> Any other CommBlog topics or news?
17:49:55 <mailga> ?
17:49:59 <jflory7> mailga: Go ahead.
17:50:02 <mailga> Is it the case to discuss also of the Contributor Classrooms idea?
17:50:06 <jflory7> !!
17:50:09 <jflory7> Good call, mailga
17:50:18 <jflory7> Let's switch to Open Floor
17:50:18 <decauseMovesToNC> topic change to #open floor?
17:50:18 <jflory7> #topic Open Floor
17:50:22 <decauseMovesToNC> jflory7++
17:50:27 <decauseMovesToNC> mailga: go ahead :)
17:50:44 <jflory7> So, mailga and I had this discussion in #fedora-join a good number of days ago. Let me dig for the mailing list thread really fast.
17:50:53 <mailga>
17:50:56 <mailga> :-D
17:51:21 <jflory7> mailga++
17:51:24 <jflory7> #info Idea: Fedora Contributor Classrooms
17:51:27 <mailga> we though if it's the case to think about that kind of project.
17:51:30 <jflory7> #link
17:51:54 <jflory7> For reference purposes, I'm going to #info the five points of my summary in that email to here
17:51:59 <jflory7> #info 1) Online university meets contributing to Fedora (kind of)
17:52:05 <jflory7> #info 2) Join process: Move from wiki to more modern + centralized "course"
17:52:07 <decauseMovesToNC> even though I was on PTO yesterday, I met with spot, Red Hat University Outreach Lead
17:52:11 <jflory7> #info 3) Improve process to jumpstart new contributors
17:52:17 <jflory7> #info 4) Four main questions to answer
17:52:24 <jflory7> #info 5) Opinions / thoughts very welcome
17:52:35 <mailga> it's a long term project but I think it make easier get in touch with people.
17:52:39 <decauseMovesToNC> that summary was super helpful
17:52:54 <jflory7> I like the idea of making it a long-term CommOps objective
17:53:04 <jflory7> The lightbulb moment for me was using Hubs as a way to deploy this
17:53:16 <decauseMovesToNC> 100% agree there
17:53:19 <mailga> jflory7: +1
17:53:23 <jflory7> Can't remember his FAS, but Neville Cross mentioned some prior experience with this in LATAM too
17:53:26 <jflory7> .fas Neville
17:53:27 <zodbot> jflory7: nevillekwa 'Neville Kwa' <> - kompressor 'Neville Makopo' <> - nevillednz 'Neville Dempsey' <> - pkn2 'Paul K. Neville II' <> - yn1v 'Neville A. Cross' <> - jsenneville 'Jean Senneville' <> - neville0015 'NEVILLE NEVILLE' <> - bonnevil 'Steve Bonneville' (1 more message)
17:53:33 <decauseMovesToNC> the infra meeting is this tuesday at 2pm ET
17:53:37 <jflory7> I think yn1v
17:53:53 <decauseMovesToNC> commops should see if we can get an item on their agenda to check in on a hubs instance
17:53:53 <jflory7> #link
17:53:55 <mailga> jflory7: that's the man
17:54:07 <jflory7> That's their earlier attempt at a Fedora "online college"
17:54:09 <jflory7> Good reference
17:54:32 <jflory7> decauseMovesToNC: Neville did mention some major challenges too which would be discuss where possible
17:54:55 <jflory7> A lot of the challenges of building a course and making the digital content. Difficult and hard to produce initially, but potentially long-term benefits and usability
17:55:03 <jflory7> Something I'm sure you're familiar with already from RIT, decauseMovesToNC.
17:55:05 <jflory7> :P
17:55:08 <decauseMovesToNC> indeed
17:55:10 <decauseMovesToNC> :)
17:55:20 <jflory7> So--
17:55:39 <jflory7> Main purpose of mentioning it here now was if this is something we think is reasonable to pursue at this time, and if we have the manpower and resources to pull it off
17:55:50 <jflory7> I like the idea but it's obviously a lot of time, investment, planning, and work
17:56:04 <decauseMovesToNC> jflory7: I think that making University a larger priority is a great goal
17:56:07 <jflory7> If we like the idea of pursuing this, I say we ticket it up nice and pretty :P
17:56:14 <decauseMovesToNC> (that didn't make it into YiR)
17:56:27 <decauseMovesToNC> jflory7: yes
17:56:29 <jflory7> decauseMovesToNC: You mean like the University Involvement Initiative?
17:56:38 <jflory7> I did forget about that for the YiR too
17:56:42 <decauseMovesToNC> jflory7: in addition to that, i think we should claim some wiki space as well
17:56:47 <jflory7> Would have been a great thing to mention, in retrospect
17:57:00 <jflory7> decauseMovesToNC: e.g. CommOps/Fedora_University (?)
17:57:36 <jflory7> Err, I guess just drop the "CommOps/" and categorize the page properly
17:57:39 <jflory7> Cleaner URL
17:57:46 <decauseMovesToNC> jflory7: yes, that
17:57:52 * jflory7 nods
17:57:58 <decauseMovesToNC> I think that EDU/University is a bigger-than-commops thing
17:58:06 <mailga> jflory7: decauseMovesToNC don't forget all the discussion to the fed-join sig we had at Flock...
17:58:13 <decauseMovesToNC> even though commops is the likely home-base for folks who want to do more within it
17:58:33 <decauseMovesToNC> mailga: agreed. we should start collecting links and conversations on the wiki page
17:58:53 <decauseMovesToNC> someday, there will be a very awesome "education" hub or something like that, but for now, we need a depot
17:58:58 <jflory7> #action jflory7 Create ticket for "Fedora University" as a long-term objective to work with CommOps and other sub-projects and SIGs, claim wiki page as a planning pad for solidifying the idea and turning it from a concept into a plan (categorize together: CommOps + Join)
17:59:09 <mailga> decauseMovesToNC: and suggestions (I hope) we need lots of people involved.
17:59:27 <jflory7> mailga: I agree, this would definitely be a big cross-project collaboration
17:59:34 <jflory7> Something that seems a little challenging this moment...
17:59:51 <decauseMovesToNC> jflory7: there is going to be a confab with the RHT EDU team after FOSDEM
17:59:51 <jflory7> But hopefully the work we're doing here can make cross-project collaboration a little less scary :)
18:00:02 <jflory7> Confab?
18:00:29 <decauseMovesToNC> fancy word for powow
18:00:34 * jflory7 nods
18:00:56 <jflory7> mailga: Once I ticket + wiki this, I will hit the CommOps mailing list + cc: Join with the links so we can try to get some early collaboration on the planning stages going.
18:01:12 <decauseMovesToNC> what we can do in the meantime, is point to this wiki page we're creating, on the education list, which is super dormant
18:01:27 <decauseMovesToNC> jflory7: yes, in addition to the above, you got it
18:01:32 <mailga> jflory7: it works for me, but we need a leader on this....
18:01:36 <jflory7> #action jflory7 After creating aforementioned ticket and wiki page, send links to CommOps + Join mailing lists to encourage early collaboration on planning, conceptualization, and organization
18:01:51 <jflory7> mailga: I agree.
18:02:00 <decauseMovesToNC> mailga: I'm the Council EDU Objective lead, but I agree, it would be good for Fedora to have an identified EDU lead as well
18:02:05 <jflory7> decauseMovesToNC: It would be super nice to see the Education list boosted in activity.
18:02:25 <decauseMovesToNC> mailga: I think we're yet to find that additional capacity, and will have to do it as a group for a lil while
18:02:35 <mailga> decauseMovesToNC: not me, but jflory seems the rigt person.
18:03:10 <jflory7> Depending on how things work out over this upcoming summer, I think this would be something I would be interested in pursuing actively
18:04:01 <decauseMovesToNC> mailga: jflory7 is amazing, but we should have a better idea of what we are going to do before we pick a lead, IMHO
18:04:23 <decauseMovesToNC> let's keep updating the depot, and then meet with RHT EDU, and see what kinds of overlap/resources we can find
18:04:23 <mailga> decauseMovesToNC: ack
18:04:23 <jflory7> +1 too. I think getting the details on this over the next couple of months will be a good start and then going from there.
18:04:45 <jflory7> So, we're four minutes over. Any last words or discussion?
18:04:48 <decauseMovesToNC> mailga: I do think that having something ready for fall 2017 would be a good goal
18:05:06 <jflory7> Not a huge rush since we're not bleeding into any other meetings, but we are over anyways if people have things to do or places to go
18:05:12 <decauseMovesToNC> mailga: this is a much larger convo to continue having. Thank you for starting it :)
18:05:13 <mailga> jflory7: decauseMovesToNC my only scare is that this proget get lost in the sea...
18:05:32 <mailga> thank you both guys.
18:05:52 <jflory7> mailga: I am a little afraid of that too, but I definitely want to set this on the map for a big objective in the future. We'll all do our part to keep it on the front and an area to focus on.
18:05:58 <decauseMovesToNC> mailga: I have a particular passion for Hackademia, and want to keep moving forward in this area
18:06:33 <jflory7> I really like the idea of making this a big project for CommOps, using our role as a cross-project force to help make this an effort worked on by many, not just us.
18:06:45 <jflory7> decause++
18:07:01 <mailga> It was not referred to you guys. We have so many ideas that sometimes we can't start one.
18:07:44 <jflory7> mailga: I definitely know what you mean. I definitely believe this is one for us all to push towards. :)
18:08:00 <jflory7> Will be a long process but I think it can happen.
18:08:08 <mailga> :-)
18:08:11 <decauseMovesToNC> mailga: we need to continue growing commops and build additional capacity for this too :)
18:08:20 <decauseMovesToNC> kk
18:08:24 <decauseMovesToNC> we're almost 10 over now
18:08:28 <jflory7> Heheh
18:08:36 <jflory7> Moving back to homebase channel? :)
18:08:41 <decauseMovesToNC> I think we should continue discussion in channel and end meeting
18:08:42 <jflory7> CommOps++
18:08:46 <decauseMovesToNC> homebase
18:08:47 <decauseMovesToNC> yes
18:08:48 <mailga> decauseMovesToNC: probably in the future commops will merge with other groups (or SIG). IMO
18:08:56 <decauseMovesToNC> thanks all for coming out today
18:09:01 <decauseMovesToNC> mailga: I hope so, yes
18:09:03 <jflory7> #endmeeting