16:02:45 <jflory7> #startmeeting Fedora CommOps (2016-05-17)
16:02:45 <zodbot> Meeting started Tue May 17 16:02:45 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:02:45 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:02:45 <zodbot> The meeting name has been set to 'fedora_commops_(2016-05-17)'
16:02:46 <jflory7> #meetingname commops
16:02:46 <zodbot> The meeting name has been set to 'commops'
16:02:50 <jflory7> #nick CommOps
16:02:54 <jflory7> #topic Agenda
16:02:58 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-05-17
16:02:59 <decause> .hello decause
16:03:01 <jflory7> #info (1) Roll Call / Q&A
16:03:02 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
16:03:07 <jflory7> #info (2) Announcements
16:03:15 <jflory7> #info (3) Action items from last meeting
16:03:19 <jflory7> #info (4) Tickets
16:03:23 <jflory7> #info (5) Wiki Gardening
16:03:26 <jflory7> #info (6) Community Blog
16:03:31 <jflory7> #info (7) Release Schedule
16:03:33 <dhanesh95> .hello dhanesh95
16:03:34 <zodbot> dhanesh95: dhanesh95 'Dhanesh Bhalchandra Sabane' <dhaneshsabane95@gmail.com>
16:03:35 <jflory7> #info (8) Open Floor
16:03:39 <jflory7> #topic Roll Call / Q&A
16:03:43 <jflory7> #info Name; Timezone; Sub-projects/Interest Areas
16:03:45 <jflory7> If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.
16:03:50 <c0mrad3> .hello dhanvi
16:03:51 <linuxmodder> .hello linuxmodder
16:03:51 <zodbot> c0mrad3: dhanvi 'Tummala Dhanvi' <dhanvicse@gmail.com>
16:03:54 <zodbot> linuxmodder: linuxmodder 'Corey W Sheldon' <sheldon.corey@openmailbox.org>
16:03:54 <meskarune> .hello meskarune
16:03:55 * linuxmodder quasi here
16:03:58 <zodbot> meskarune: meskarune 'Dolores Portalatin' <meskarune@archwomen.org>
16:03:59 <bee2502> .hello bee2502
16:03:59 <sayan> .hello sayanchowdhury
16:04:00 <zodbot> bee2502: bee2502 'Bhagyashree Padalkar' <bhagyashree.iitg@gmail.com>
16:04:03 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
16:04:06 <jflory7> #info Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Diversity, Join, and more
16:04:07 <decause> #info decause; UTC-4; CommOps, Council, Budget, GSoC, *
16:04:09 <omiday> #info Viorel Tabara; UTC-6; CommOps
16:04:23 <dhanesh95> #info Dhanesh B. Sabane, UTC+5:30, CommOps
16:04:27 <jflory7> #chair c0mrad3 dhanesh95 linuxmodder meskarune decause bee2502 sayan
16:04:27 <zodbot> Current chairs: bee2502 c0mrad3 decause dhanesh95 jflory7 linuxmodder meskarune sayan
16:04:35 <jflory7> Hiya, all! :)
16:04:35 <c0mrad3> #info Tummala Dhanvi ; UTC+5:30; CommOps,Docs,Security,GSoC, *
16:04:44 <bee2502> #info Bee UTC+5.30 CommOps, metrics , GSoC
16:04:47 <omiday> hello
16:04:51 <dhanesh95> jflory7++
16:04:57 <sayan> #info Sayan Chodwhury; UTC+5:30; Commops, Magazine, Ambassadors, Marketing
16:05:00 <GIANT_CRAB> Hello, Huiren -- common ops, ambassador, marketing, UTC+0800
16:05:07 <jflory7> #chair GIANT_CRAB
16:05:07 <zodbot> Current chairs: GIANT_CRAB bee2502 c0mrad3 decause dhanesh95 jflory7 linuxmodder meskarune sayan
16:05:15 <jflory7> Hiya, Huiren!
16:05:21 <GIANT_CRAB> #info Huiren -- common ops, ambassador, marketing, UTC+0800
16:05:33 <bee2502> hi all - made it today after a long time ! Yaay !
16:05:35 <linuxmodder> #info Corey Sheldon utc-4  freemedia docs fedora-join security-team magazine commops marketing ambassadors fedorabugs qa fi-apprentic
16:05:44 <GIANT_CRAB> Hey jflory7 ! On mobile phone, so typing is slow
16:05:50 <jflory7> bee2502: Woohoo, welcome back :)
16:05:51 <decause> GIANT_CRAB: SN: there is a Fedora Magazine article that the editorial team wanted me to ask you about
16:06:02 <jflory7> GIANT_CRAB: No worries! Glad you could make it out, I know it's pretty late for you.
16:06:21 <decause> GIANT_CRAB++
16:06:35 <GIANT_CRAB> decause: the one on the what do you look forward to?
16:06:45 <c0mrad3> hi all :)
16:06:50 <decause> GIANT_CRAB: yep, that's it. stickster wanted me to touch base with you and check in.
16:06:57 <jflory7> #chair omiday
16:06:57 <zodbot> Current chairs: GIANT_CRAB bee2502 c0mrad3 decause dhanesh95 jflory7 linuxmodder meskarune omiday sayan
16:07:11 <GIANT_CRAB> I think it would be good if someone could do it instead, too many school projects righr now. Sorry
16:07:11 <decause> GIANT_CRAB: we wanna push it before the GA, to help build some hype :)
16:07:22 * jflory7 tries to make sure he got everyone
16:07:26 <decause> GIANT_CRAB: that is exactly the type of info I was looking for. can do.
16:07:31 <decause> will report back to FM about that
16:07:39 <GIANT_CRAB> Thanks decause !
16:08:08 <stickster> GIANT_CRAB: Do you already have inputs from various people in the Fedora community that decause could pull together (or work with someone to do it) for the article?
16:08:35 <GIANT_CRAB> There were a few, Ill put them together and send it into fed marketing email list
16:08:43 <jflory7> GIANT_CRAB++
16:08:50 <decause> solid
16:08:57 <jflory7> Alright, I think we're at a fair number. Let's get started. :)
16:09:01 <decause> nod nod nod
16:09:05 <jflory7> #topic Announcements
16:09:09 <jflory7> #info === GSoC project period begins Monday, May 23 ===
16:09:13 <jflory7> #link https://summerofcode.withgoogle.com/how-it-works/
16:09:19 <jflory7> #info The Google Summer of Code project period officially begins on May 23rd. Students will officially begin working on their projects starting next Monday.
16:09:30 <decause> also
16:09:35 <jflory7> I'm a little bit out of the loop this past week, so that's all I have. Anyone else want to add?
16:09:39 <decause> #link http://etherpad.osuosl.org/fedora-gsoc-welcome-2016
16:09:52 <decause> this is a working document where we're collecting information
16:09:57 <decause> that link would be a good one to add
16:09:59 * c0mrad3 clicks
16:10:45 <jflory7> Definitely!
16:11:22 <decause> #action commops add the 'how it works' link above to the etherpad under resources
16:11:43 <jflory7> Done :)
16:11:44 <jflory7> Any other announcements anyone wants to throw out?
16:12:04 <decause> I will be sending out a request for 1x1 and stand-up timeslots in the next day or two to the mentors and students, so keep an eye out for that
16:12:16 <decause> EoF
16:12:20 * jflory7 nods
16:12:30 <decause> #action decause send out timeslot requests for GSoC
16:13:24 <jflory7> Alrighty.
16:13:28 <jflory7> Announcements, going once...
16:13:36 <jflory7> Going twice...
16:13:46 <jflory7> Going thrice...
16:13:52 <jflory7> #topic Action items from last meeting
16:13:57 <jflory7> #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-10/commops.2016-05-10-15.55.html
16:14:02 <jflory7> #info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action it if needed. If no status, we'll try to get a quick update and move forward.
16:14:09 <jflory7> #info === decause fill up the LimeSurvey account with moneydollars ===
16:14:23 <jflory7> Any updates here?
16:14:52 <decause> #action decause add money dollars to limesurvey due:Friday
16:14:56 <decause> next
16:15:09 <decause> I've been in the dashboard a couple of times
16:15:19 * jflory7 nods
16:15:24 <jflory7> #info === [COMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team ===
16:15:28 <jflory7> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/J6MSAW4UBESXPC7PD6C43JCTWZKB2W5B/
16:15:36 <jflory7> Already looks like some interest with the Design Team :)
16:15:41 <jflory7> #info === [COMPLETE] decause / jflory7 File a ticket for exploring how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
16:15:45 <jflory7> #link https://fedorahosted.org/fedora-infrastructure/ticket/5304
16:15:50 <jflory7> #info === CommOps solidify onboarding steps before 5/23 internships begin ===
16:15:55 <jflory7> #action CommOps solidify onboarding steps before 5/23 internships begin
16:15:56 * nb needs to check and see if there are any badges ready to push
16:16:01 <jflory7> #info === decause talk to spot about scheduling an EDU FAD after budget gets settled ===
16:16:21 <jflory7> Re-action or are there new updates here?
16:16:31 <jflory7> Also this is part of today's discussion too with tickets later
16:16:34 <decause> jflory7: re-action, budget technically jsut officially got settled yesterday
16:16:36 * jflory7 nods
16:16:42 <jflory7> #action decause talk to spot about scheduling an EDU FAD after budget gets settled
16:16:47 <jflory7> #info === [INCOMPLETE] jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad ===
16:16:52 <jflory7> #action jflory7 Post to the mailing list with ideas about the FOSS Student Pack, along with links to a planning pad either on the wiki or in an Etherpad
16:16:58 <jflory7> #info === [INCOMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) ===
16:17:03 <jflory7> #action jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
16:17:09 <jflory7> #info === [INCOMPLETE] jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors ===
16:17:14 <jflory7> #action jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors
16:17:19 <jflory7> #info === [COMPLETE] skamath add categories to the Summer Coding 2016 page ===
16:17:24 <jflory7> #link https://fedoraproject.org/wiki/Summer_Coding_SIG
16:17:31 <jflory7> #info === jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
16:17:37 <jflory7> #action jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks
16:17:41 <jflory7> #info === [COMPLETE] jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket ===
16:17:50 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/69#comment:2
16:17:51 <decause> that's a good one
16:17:55 <jflory7> #info === [COMPLETE] jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list ===
16:18:00 <jflory7> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/NIRMPNQI7TV2LNT42IZMAWUSATGSKFGK/
16:18:05 <jflory7> #info === [COMPLETE] dhanesh95 Work on merging the draft changes for the University Involvement Initiative into the main page (including in the section header "Proposed") ===
16:18:09 <jflory7> #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative#Proposed_Program:_Campus_Ambassadors
16:18:22 <jflory7> #info === [COMPLETE] jflory7 / decause Drop ticket comment in #fedora-modularization after meeting ===
16:18:31 <jflory7> There's discussion happening in there now, need to peek back in shortly :)
16:18:37 <jflory7> #info === [COMPLETE] skamath File an issue in the Community Blog repo for adding a footer with licensing information to the bottom of the site ===
16:18:41 <jflory7> #link https://pagure.io/communityblog-theme/pull-request/8
16:18:45 <jflory7> LinuxHippie++
16:18:52 <jflory7> #info === [IN PROGRESS] decause get the tshirt orders in ASAP for PyCon ===
16:18:53 <decause> LinuxHippie++
16:18:57 <decause> nod nod
16:18:57 <jflory7> #info Quotes received, discussion is ongoing about them. By end of day, should be finalized.
16:19:03 <jflory7> #info === [IN PROGRESS] decause get the sticker orders in ASAP for PyCon ===
16:19:08 <jflory7> #info Quotes received, discussion is ongoing about them. By end of day, should be finalized.
16:19:08 <GIANT_CRAB> LinuxHippie++
16:19:09 <zodbot> GIANT_CRAB: Karma for linuxhippie changed to 4 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:19:15 <jflory7> #info === [COMPLETE] LinuxHippie Work on creating a first draft of the PyCon 2016 page on the wiki, drop mail on the mailing list once an initial draft is ready for decause and other attendees to review ===
16:19:19 <jflory7> #link https://fedoraproject.org/wiki/PyCon_2016
16:19:26 <jflory7> #info === [INCOMPLETE] jflory7 Help ship F24 Party article for Thursday morning (Wednesday if possible) ===
16:19:30 <jflory7> #action jflory7 Ship F24 Party article today
16:19:35 <dhanesh95> LinuxHippie++
16:19:35 <zodbot> dhanesh95: Karma for linuxhippie changed to 5 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:19:37 <jflory7> #info === omiday Contact the Infrastructure team in IRC or mailing list about point of contact for Ask Fedora and about adding banners for Magazine and/or CommBlog ===
16:19:40 <danofsatx> oh, we're having a meeting?
16:19:41 <jflory7> omiday: Any updates here?
16:19:44 <danofsatx> .hello dmossor
16:19:45 <jflory7> Hiya, danofsatx!
16:19:45 <zodbot> danofsatx: dmossor 'Dan Mossor' <danofsatx@gmail.com>
16:19:47 <jflory7> #chair danofsatx
16:19:47 <zodbot> Current chairs: GIANT_CRAB bee2502 c0mrad3 danofsatx decause dhanesh95 jflory7 linuxmodder meskarune omiday sayan
16:20:17 <nb> .helo nb
16:20:18 <jflory7> omiday: I kind of remember the discussion in #fedora-admin but I'm fuzzy on the details.
16:20:21 <nb> .hello nb
16:20:22 <zodbot> nb: nb 'Nick Bebout' <nb@nb.zone>
16:20:23 <jflory7> #chair nb
16:20:23 <zodbot> Current chairs: GIANT_CRAB bee2502 c0mrad3 danofsatx decause dhanesh95 jflory7 linuxmodder meskarune nb omiday sayan
16:20:45 <omiday> jflory7: since we talked about theme I came across https://fedorahosted.org/design-team/ticket/199 and followed up on #fedora-design - mleonova suggested that I should email fedora-design ML
16:21:22 <decause> not a bad idea, but ryanlerch is really the official person you wanna bring into the loop
16:21:34 <decause> .fas ryanlerch
16:21:34 <zodbot> decause: dudemcpants 'Dude McPants' <ryanlerch@gmail.com> - ryanlerch 'ryan lerch' <rlerch@redhat.com>
16:21:42 <decause> lololol
16:21:43 <jflory7> lol with the first one
16:21:53 <omiday> email/irc?
16:21:54 <GIANT_CRAB> Lol
16:21:54 <decause> #amaze
16:21:54 <gnokii> hu
16:21:59 <decause> dudemcpants++
16:21:59 <zodbot> decause: Karma for dudemcpants changed to 1 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:22:04 <jflory7> #link https://fedorahosted.org/design-team/ticket/199
16:22:08 <nb> dudemcpants++
16:22:09 <zodbot> nb: Karma for dudemcpants changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:22:25 <GIANT_CRAB> Dudemcpants++
16:22:36 <decause> next?
16:22:50 <jflory7> #info omiday is in the process of following up about placing banners on Ask Fedora. First, the banners will need to be designed by the Design Team. omiday was asked to follow up with the Design Team mailing list (particularly ryanlerch).
16:22:57 <jflory7> Alright. That's all action items!
16:22:59 <jflory7> To tickets.
16:23:05 <jflory7> #topic Tickets
16:23:09 <jflory7> #link https://fedorahosted.org/fedora-commops/report/9
16:23:13 <jflory7> #info === Tickets #34, 49 ===
16:23:17 <jflory7> #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
16:23:23 <jflory7> #info #49: "[Onboarding Series] Infrastructure"
16:23:27 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/34
16:23:30 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/49
16:23:34 <jflory7> #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
16:23:37 <jflory7> A Badges workshop was officially proposed this morning on the CommOps and Design mailing list. This is the first steps to moving forward on these items (since there has been a lull for the past week or two since others have been away / busy). A hack session tonight or tomorrow might be useful to do some moving forward on this ticket, finalizing a Badges workshop with the Design team, and also getting through our own backlog. If a hack session
16:23:37 <jflory7> works well, when do we want to aim for?
16:23:46 <omiday> decause: how does one contact directly? email/irc?
16:24:01 <decause> omiday: email is best, he's in Brisbane TZ
16:24:08 <jflory7> .localtime ryanlerch
16:24:09 <zodbot> jflory7: The current local time of "ryanlerch" is: "02:24" (timezone: Australia/Brisbane)
16:24:11 <omiday> decause: got it
16:24:33 <jflory7> So my ideas for this ticket was putting together a hack session this week
16:24:33 <decause> jflory7: saw that, good loop.
16:24:37 <decause> nod nod
16:24:43 <jflory7> Depending on the people interested–
16:24:53 <jflory7> We could do it tonight or maybe tomorrow morning depending on where peoples' time is.
16:25:02 * c0mrad3 have exams this week!
16:25:12 <jflory7> It might be easier for some in IST, but as c0mrad3 points out, some people are also in exams.
16:25:24 <GIANT_CRAB> c0mrad3: all the best for ur exams
16:25:27 <meskarune> I am free tonight
16:25:28 <jflory7> So I guess the best place to start might be in seeing who is interested in attending one this week?
16:25:36 <jflory7> c0mrad3: Definitely all the best on your exams!
16:25:48 <jflory7> I could also swing one tonight.
16:25:48 <GIANT_CRAB> jflory7: do folks need designing skills?
16:25:55 <decause> GIANT_CRAB: we will, yes
16:25:57 <GIANT_CRAB> Inkscape, GIMP etc
16:26:01 <decause> inkscape
16:26:02 <jflory7> GIANT_CRAB: I know the Badges team definitely could use some extra hands.
16:26:05 <jflory7> Inkscape especially.
16:26:13 <bee2502> i dont know any
16:26:26 <bee2502> :(
16:26:32 * decause is handy with inkscape a decent bit
16:26:44 <decause> has designed a couple of badges
16:27:01 * GIANT_CRAB doesnt know either but could attempt to
16:27:03 <gnokii> !
16:27:03 <decause> the styleguide and templates make it easy-peasy
16:27:10 <jflory7> However, for our hack session, it's mostly going to be trying to tie the ribbon on having a Badges Workshop with the Design Team and also going through some of the backlog for the things we already have. This could be defining YAML files with fedmsg for badges, but can also be other things.
16:27:13 <jflory7> gnokii: Go ahead!
16:27:43 <decause> from our end, the big contribution we can help with in commops is concepts
16:27:47 * jflory7 nods
16:28:04 * GIANT_CRAB nodssss
16:28:04 <decause> some design, sure, and def the yaml, but the concepts are key
16:28:11 <gnokii> decause: I thought you know council ticket #54 and we wanted to do badges on FAD mainly so I am a little bit confused what the badges thingie shall be
16:28:33 <gnokii> eof
16:28:35 <decause> gnokii: mostly getting concepts for the new message types (zanata, bugzilla, etc...)
16:29:06 <decause> gnokii: we want to have the concepts and yaml prepped and ready for Design FAD to help make the next fleet of badges get made
16:29:17 <decause> bugzilla and mailing lists esp
16:29:19 <jflory7> And also going through triaging existing tickets too
16:29:30 <jflory7> I know riecatnor has been doing some of that and we can probably lend a hand too.
16:29:46 <gnokii> decause: if there will be a FAD there is no comment to the ticket
16:29:54 * bee2502 could be helpful with yaml
16:30:20 <jflory7> Knowledge of fedmsg is especially useful for badges, whether it's defining the YAML or just seeing whether a badge is proposal is feasible.
16:30:23 <decause> gnokii: there was talk yesterday in council meeting about the FAD. We didn't update teh ticket, but we want to revisit it next week after Flock selection moves along a bit more
16:30:55 <decause> there are people travelling who's funding is tied to Flock, so that we can hopefully keep the cost of the FAD less than 5K
16:31:16 <decause> but we gotta see who's talks get accepted to see who will likely get travel
16:31:20 <decause> this is on the docket for next week for sure
16:31:27 <gnokii> decause: yeah its me and ryanlerch, otherwise we would have to travel twice around globe
16:31:33 <decause> gnokii: exactly
16:31:50 <jflory7> So for our own hack session, anyone opposed to the "usual" time of 21:00 UTC start time? I am also completely flexible for tomorrow morning if there's folks who want to participate in different time zones.
16:31:58 <decause> gnokii: this hacksession is mostly about finalizing the onboarding series' for each subproject
16:32:18 <gnokii> decause: so its not designing badges?
16:32:23 <decause> jflory7: I'm down tonight, and somewhat tomo (FAMSco is happening too, so I'll be divided somewhat)
16:32:40 <decause> gnokii: it's mostly coming up with concepts, and sequences of badges
16:32:49 * c0mrad3 jflory7 can't attend both the hack sessions this week
16:32:54 <bee2502> 2100 is late for me
16:32:59 <jflory7> I know meskarune said she was free for tonight, I'm free for tonight and tomorrow, decause is free tonight and maybe tomorrow... anyone else interested?
16:33:12 <jflory7> bee2502: If you're free, I'm thinking tomorrow might be the best time to shoot for.
16:33:20 <bee2502> I am free for tomo
16:33:22 <jflory7> c0mrad3: Understandable. You've got some bigger things to tackle. ;)
16:33:23 <decause> jflory7: what time tomo?
16:33:30 <meskarune> Yeah, tonight is ok for me
16:33:34 <jflory7> bee2502: What time tomorrow UTC works for you?
16:33:38 <bee2502> but it should depend on the majority
16:33:46 <gnokii> decause: so means has nothing to do with fad on the end are two pair of shoes
16:33:46 <jflory7> meskarune: Are you open in the morning tomorrow too or just tonight?
16:33:54 <meskarune> tomorrow is fine too
16:33:58 <jflory7> Okay, awesome!
16:34:06 <bee2502> anytime after 0500 UTC tomo
16:34:21 <bee2502> before 2100 UTC hopefully jflory7
16:34:23 <decause> gnokii: I think that one got lost in translation, but yeah, the can both happen separately
16:34:32 <jflory7> Let's say... 14:00 UTC? i.e. 10:00am US EST?
16:34:42 <jflory7> Seem reasonable?
16:34:51 <decause> jflory7: I'll be around, but probably divided
16:34:51 <gnokii> ok, because jflory7 didnt mention what it is exactly
16:35:01 <sayan> 1400 UTC wfm
16:35:02 <jflory7> decause: Ah, shoot, that is the FAmSCo meeting...
16:35:11 <decause> jflory7: that is only an overlap for me
16:35:14 <decause> don't block  on it
16:35:25 <decause> other commops team members it works for
16:35:30 <jflory7> Maybe 13:30 UTC so we can get the gears rolling, and then decause can check out for a bit while we tackle some other things.
16:35:33 <decause> and I'll likely not need to do too much there
16:35:34 <jflory7> Sound a bit better?
16:35:45 <decause> jflory7: that could help, yeah
16:35:55 <bee2502> +1 from me too
16:35:58 <jflory7> sayan / meskarune / bee2502: 13:30 UTC sound good? (9:30am US EST?)
16:36:04 <sayan> +1
16:36:06 <decause> #action jflory7 add morning workshop to fedocal
16:36:26 <decause> #action decause attend morning workshop at 13:30UTC tomo
16:36:31 <jflory7> heheh
16:36:35 * decause adds to calendar
16:36:53 <omiday> I'm available but someone will need to fill me in with details about what we'll be working on
16:37:14 <jflory7> So, I'm going to add that to Fedocal *right now* while I'm thinking about it, so decause, if you could tackle the next ticket while I do that, that would be awesome!
16:37:27 <decause> kk, digging for agenda link
16:37:48 <jflory7> omiday: We're mainly to be looking at finalizing the Badges Workshop idea with the Design team and maybe a little bit of strategic planning for Badges for different sub-projects.
16:37:51 <decause> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-05-17
16:37:52 <jflory7> decause: I can get you started. :)
16:37:54 <jflory7> #info === Ticket #68 ===
16:37:58 <jflory7> #info "Reconstructing the Campus Ambassadors program and campus outreach"
16:38:01 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/68
16:38:06 <jflory7> #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
16:38:09 <jflory7> With Dhanesh's progress on this, a big first step towards centralizing info has been accomplished. Now that it's there, we should identify the next steps of how to reconstruct the program. Is the next step the FAD? Or is there more work that needs to be done in order for us to get to a FAD?
16:38:13 * jflory7 goes to Fedocal really quick.
16:38:33 <decause> I think the next step is proposing a FAD, yes
16:38:38 <decause> and socializing the proposal
16:38:49 <decause> both of the program, and of the FAD itself
16:39:01 <decause> and the FAD will have to have pretty much zero budget
16:39:12 <decause> because we're already very much near the spending limit for the year
16:39:32 <decause> (assuming the design FAD hits the books as planned)
16:39:45 <decause> I'm hoping to keep the budget <1000
16:40:20 <decause> if someone wanted to start the wiki page, based on the FAD template, I could finish it
16:40:30 <decause> but probably after budget week is over, and GSoC planning is done.
16:40:49 <decause> decause prios include: PyCon Swag, budget Follow-up, GSoC Wrangling
16:40:53 <decause> then EDU
16:41:26 <jflory7> Okay, here this is: https://apps.fedoraproject.org/calendar/commops/2016/5/18/#m3910
16:41:43 <sayan> jflory7++
16:41:43 <bee2502> jflory7+
16:41:45 <omiday> jflory7: I don't know antyhing about Badges Workshop - if you are around after meeting we could do a quick follow up on #fedora-commops?
16:42:39 <jflory7> decause: Okay, so a wiki page would be a good next step, right?
16:42:44 <decause> jflory7: agreed, yes
16:42:55 <jflory7> omiday: Yeah, today is actually one of the days where I will have a lot of time after the meeting.
16:43:19 <decause> dhanesh95: since you started the EDU wiki page, perhaps you can fork one of the other FAD's pages for EDU FAD?
16:43:27 <decause> and gut it
16:43:30 <decause> it can be mostly empty
16:43:40 <omiday> jflory7: sounds good
16:43:44 <c0mrad3> dhanesh95++
16:43:47 <jflory7> That would be really cool and taking an existing FAD's page is a good way to have something to start with.
16:43:59 <decause> #link http://fedoraproject.org/wiki/FAD_EDU_2016
16:44:01 <jflory7> If dhanesh95 is up for it, that would be cool, but if not, we can leave it open or I can try to tackle it.
16:44:34 <jflory7> Just don't want to assign it over to him without knowing if he wants to do it too ;)
16:44:41 <decause> #link https://fedoraproject.org/wiki/Template:FAD
16:44:55 <jflory7> Ohhh. I didn't know there was a template.
16:44:59 <jflory7> That's handy.
16:45:04 <decause> nod nod
16:45:11 <decause> we'll likely adapt it a bit, but it's a good start
16:45:36 <decause> if dhanesh95 isn't around, let's add it to my plate I suppose, but I probably won't do it before Friday at the earliest
16:45:38 <jflory7> For now, we can assign it out to CommOps, and if dhanesh95 wants to pick it up, it's all his. :)
16:45:49 <decause> or that, sure
16:46:09 <jflory7> #action CommOps Fork a wiki page for the Education FAD from the template linked previously and begin templating the details for the Education FAD to take place over this summer
16:46:13 <jflory7> Ta-da
16:46:27 <jflory7> I feel like this is good for this ticket.
16:46:27 <decause> kk
16:46:29 <jflory7> Anything else?
16:46:31 <decause> nope
16:46:33 <jflory7> If not, we can hit the next one
16:46:34 <decause> we're at 75%
16:46:35 <jflory7> Alright
16:46:38 <jflory7> Oh, wow, time flies
16:46:44 <jflory7> #info === Ticket #69 ===
16:46:48 <jflory7> #info "Fedora Modularity onboarding"
16:46:51 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/69
16:46:56 <jflory7> #info (1) Someone can review the contents of their on-boarding wiki page and pass feedback about them in the ticket, as compared to other on-boarding methods in Fedora
16:47:01 <jflory7> #info (2) Putting together a badge proposal for membership in the Modularity WG (in the form of a ticket on the fedora-badges Trac)
16:47:07 <jflory7> #info (3) A Community Blog article announcing the presence of the Modularity WG, what they are, what they do, how to get involved (penned by one of the WG members)
16:47:10 * nb wonders how to have many people travel to FAD with <1000 budget
16:47:14 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/69#comment:2
16:47:14 <nb> but i hope it wil happen
16:47:25 <decause> nb: pratically zero, that's the idea
16:47:29 * jflory7 was going to ping langdon, but peeks back in #fedora-modularization just in case
16:47:54 <nb> decause, I am confused? The idea is to have practically zero people travel to the FAD?
16:47:56 <decause> nb: most of the folks on the RHT EDU team are here, and I'm here, and we'd do mostly vFAD. I want to keep the budget as low as possible so that we can maybe do other FADs still this year
16:47:56 <jflory7> Ahh, so there is a Modularity FAS group!
16:48:03 <nb> decause, oh ok
16:48:06 <jflory7> Or in Copr
16:48:08 <jflory7> #link https://copr.fedorainfracloud.org/groups/g/modularity/coprs/
16:48:17 <sayan> decause: makes sense
16:48:19 <nb> decause, so it'll be more of a VFAD than a in-person fad
16:48:23 <decause> nb: nod nod nod
16:48:25 <nb> which i think makes sense to have VFAD
16:48:25 <jflory7> That makes sense.
16:48:27 <langdon> jflory7, im here.. readin
16:48:45 <jflory7> langdon: Mainly just if you had any thoughts, feedback, or ideas based on what we brainstormed for the On-boarding steps for Modularity.
16:49:09 <jflory7> If not, I think we can work on finalizing the Badges.
16:49:19 <langdon> jflory7, i thought it sounded good.. with the comment about copr
16:49:39 <jflory7> langdon: Did that translate to an actual FAS group or just Copr? I wasn't 100% clear after reading.
16:50:04 <langdon> we have both and they are tied together195500
16:50:11 * langdon curses yubikey
16:50:15 <langdon> and fat fingers
16:50:20 <jflory7> Ahhh, yep!
16:50:25 <jflory7> #link https://admin.fedoraproject.org/accounts/group/view/modularity-wg
16:50:30 <jflory7> Awesome.
16:51:02 <jflory7> So I think we can pull this ticket into Ticket #34, which is just an aggregate ticket for the on-boarding steps for all sub-projects in Fedora. The next steps for this ticket is really just doing the Badges, I think.
16:51:22 <jflory7> Does that seem like a solid idea?
16:52:16 <decause> sgtm, add to the pile for workshop tonight/tomo
16:52:41 * jflory7 nods
16:53:31 <jflory7> #agreed Modularity WG gives a +1 to the proposed items; we can begin working on Badges for Ticket #69 (and as a result, it becomes a part of Ticket #34, for on-boarding steps for all Fedora sub-projects)
16:53:38 <jflory7> Okay, last ticket.
16:53:39 <jflory7> #info === Ticket #74 ===
16:53:43 <jflory7> #info "Add license information to the CommBlog footer"
16:53:46 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/74
16:53:51 <jflory7> #info Nice work by LinuxHippie submitting a pull request to accomplish this! The PR is pending review by ryanlerch for merging into the theme. Anyone else is also welcome to review if you are PHP-savvy or want to double-check the correct license is being used.
16:53:54 <jflory7> #link https://pagure.io/communityblog-theme/pull-request/8
16:54:03 <jflory7> This one was more an update. I don't know if much discussion is needed here.
16:54:06 <c0mrad3> linuxhippie++
16:54:06 <zodbot> c0mrad3: Karma for linuxhippie changed to 6 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:54:13 <jflory7> We can probably close it once ryanlerch checks out the PR.
16:54:26 <jflory7> For now, we can also probably remove it from the agenda.
16:54:42 <jflory7> #action jflory7 Remove Ticket #74 from meeting agenda, add info about where to find the pull request for the ticket
16:54:54 <jflory7> Okay, that's all tickets!
16:54:55 <jflory7> #topic Wiki Gardening
16:54:59 <jflory7> #action CommOps New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
16:55:04 <jflory7> Any other wiki gardening to add?
16:55:38 <c0mrad3> !
16:55:45 <jflory7> c0mrad3: Sure!
16:56:11 <jflory7> Oh, and I actually have a page to mention quickly after c0mrad3 too
16:56:21 <c0mrad3> #link https://fedorahosted.org/fedora-commops/ticket/62
16:56:30 <c0mrad3> #link http://etherpad.osuosl.org/fedora-join-page-wiki-gardening
16:56:34 <jflory7> Ahhh, the Join pages, yeah
16:56:42 <jflory7> An Etherpad is a good idea for this.
16:57:12 <c0mrad3> I am working little by little I will send an email to the mailing list about the same :) <eof>
16:57:28 <jflory7> Ah, awesome, was about to suggest the same! c0mrad3++
16:57:39 <jflory7> Thanks for the update, c0mrad3.
16:57:59 <decause> c0mrad3++
16:58:46 <jflory7> #help meskarune started working on a general IRC info page for the Diversity group. It's a general template right now and also has other useful information inside. The rules will be added after the Diversity team agrees on rules for the channel. Any other eyes were asked to look it over and add suggestions or ideas!
16:58:48 <jflory7> #link https://fedoraproject.org/wiki/User:Meskarune/diversity-irc
16:58:58 <jflory7> meskarune++
16:59:14 <c0mrad3> meskarune++
16:59:15 * bee2502 clicks
16:59:24 <bee2502> meskarune++
16:59:24 <zodbot> bee2502: Karma for meskarune changed to 10 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:59:30 <bee2502> comrad3++
16:59:30 <jflory7> Okay, that's all I have for wiki gardening. If nobody else has anything, we can hit the Community Blog really quick.
16:59:38 <jflory7> It's a short update this week.
16:59:57 <jflory7> #topic Community Blog
17:00:00 <decause> meskarune: nice work
17:00:07 <jflory7> #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go!
17:00:12 <jflory7> Popcorn time ;)
17:00:16 <jflory7> #info === This Week in CommBlog ===
17:00:19 * decause gets popcorn
17:00:20 <jflory7> #info (1) "Event Report: Fedora Docs FAD"
17:00:24 <jflory7> #link https://communityblog.fedoraproject.org/event-report-fedora-docs-fad/
17:00:28 <jflory7> #info Total Views (May 12 - May 17): 218
17:00:32 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1511
17:00:36 <jflory7> #info (2) "Fedora 24 Beta Released!"
17:00:40 <jflory7> #link https://communityblog.fedoraproject.org/fedora-24-beta-released/
17:00:44 <jflory7> #info Total Views (May 12 - May 17): 54
17:00:47 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1542
17:00:48 * c0mrad3 docs fad \o/
17:00:51 <meskarune> Thanks
17:00:59 <jflory7> ^^^ makes sense given the big announcement was on the Magazine
17:01:03 <jflory7> #info === Coming Up in CommBlog ===
17:01:07 <jflory7> #info (1) "Fedora 24: Let’s have a party!"
17:01:10 <jflory7> #link https://communityblog.fedoraproject.org/?p=1496&preview=1&_ppp=a34697b353
17:01:14 <jflory7> Going out today.
17:01:18 <jflory7> #info (2) "Fedora at Bitcamp 2016"
17:01:22 <jflory7> #info In progress, jflory7 to assist in writing this one
17:01:24 <jflory7> Going out this week.
17:01:28 <jflory7> #info (3) "DevConfCZ 2016: Event Report"
17:01:32 <jflory7> #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=97da4ae90c
17:01:36 <jflory7> Okay, and that's all
17:01:36 <decause> decausefail
17:01:43 <jflory7> Anything else CommBlog to add in here?
17:01:50 <decause> budget announce
17:02:03 <decause> that'll be happening by Friday
17:02:07 <jflory7> Ooh
17:02:26 <decause> I haven't gotten it drafted yet, but I'm going to start working with mattdm tomo
17:02:40 <jflory7> #info (4) Announcement about the budget (coming Friday, work in progress by decause and mattdm)
17:02:45 <decause> jflory7: there should also be a 'sprint with us at PyCon" post coming too, if I'm on my game
17:03:02 <jflory7> #info (5) "Sprint with us at PyCon" (coming soon before PyCon)
17:03:08 * jflory7 nods
17:03:11 <jflory7> Anything else to add in?
17:03:33 <jflory7> Going once...
17:03:40 <jflory7> Twice...
17:03:50 <jflory7> And thrice...
17:03:57 <jflory7> #topic Release Schedule
17:03:58 <jflory7> #link https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
17:04:19 <jflory7> #info Final Freeze (00:00 UTC), Tuesday, 2016-05-31
17:04:37 <jflory7> That's the next thing on the release schedule.
17:04:47 <jflory7> I think we will have time to compile the release announcement for this
17:04:57 <jflory7> I can't think of anything else to add in here
17:04:58 <decause> #action decause / commops stop by the docs office hours tomo to discuss release notes -> release announce flow
17:05:05 <jflory7> Ahh, good one
17:05:12 <decause> it's during 2 other meetings
17:05:27 <decause> (now 3, I also have a conf call to be on I just saw in my inbox)
17:05:44 <jflory7> Sounds like tomorrow is going to be a busy day for decause ;)
17:05:54 <jflory7> #topic Open Floor
17:05:59 <decause> yeah, it's going to be a long night and day tomo :)
17:06:09 * dhanesh95 is back..
17:06:20 <jflory7> Alrighty, open floor! Anyone have questions they want answered or any other misc. topics to bring up?
17:06:28 <jflory7> Hiya, dhanesh95! Did you catch your earlier pings?
17:06:29 <dhanesh95> Sorry I was AFK for a long time :P
17:06:33 <jflory7> No worries :)
17:06:37 <dhanesh95> Yes jflory7 . I did..
17:06:41 <dhanesh95> I'll do it..
17:06:43 <dhanesh95> :)
17:06:50 <jflory7> Alright, awesome!
17:06:52 <jflory7> dhanesh95++
17:06:54 <decause> we're entering into the heavy conf season for spring/summer, so I'm going to be traveling more in the near future, just FYI
17:07:01 <decause> #action decause add conf schedule to Fedocal
17:07:02 <dhanesh95> You can assign the action item to me
17:07:04 <jflory7> decause: Good to know.
17:07:09 <decause> others who will be should do the same
17:07:22 <jflory7> #action dhanesh95 Fork a wiki page for the Education FAD from the template linked previously and begin templating the details for the Education FAD to take place over this summer
17:07:38 <dhanesh95> jflory7++
17:07:40 <omiday> where are we at with extending meeting time?
17:07:44 <decause> PyCon is 5/27-6/7, then cloud FAd until 6/9, then SELF from 6/10-6/12ish (which is right after the GA)
17:08:04 <jflory7> Anyone else have anything else to add while we're all here? If not, we can head back to channel.
17:08:36 <jflory7> #info PyCon is 5/27-6/7, Cloud FAD until 6/9, Southeast LinuxFest from 6/10-6/12ish (which is right after F24 release)
17:09:01 <decause> I have some parting thoughts if no one else has anything
17:09:04 <jflory7> omiday: I was thinking of starting that next week. I was going to do some mailing list catch-up today and tomorrow.
17:09:21 <jflory7> I wanted to respond to danofsatx's email because I know he had some concerns that should be addressed.
17:09:30 <jflory7> And they're valid concerns too
17:09:39 <danofsatx> huh? which email?
17:09:51 <jflory7> danofsatx: About extending the meeting time. At least, I think that was you.
17:09:57 <danofsatx> oh, ok
17:10:03 <jflory7> Okay, cool.
17:10:10 <jflory7> I'm going to do catch-up today and tomorrow for that.
17:10:18 <dhanesh95> decause: The Education FAD is an interesting prospect and I would like to be involved as much as possible.
17:10:43 <decause> dhanesh95: good good, the wiki page will be a good start
17:11:05 <decause> for the FAD itself next, now that there is a proposal on the books
17:11:10 <decause> ok
17:11:14 <decause> any other open floor
17:11:19 <decause> going once
17:11:21 <dhanesh95> decause: Yes, sure!
17:11:26 <decause> going twice
17:11:29 <decause> going thrice
17:11:31 <dhanesh95> Sold!
17:11:35 <jflory7> dhanesh95++
17:11:36 <decause> #topic Parting Thoughts
17:12:11 <decause> These past few months have been about preparation. Preparing for GSoC, preparing for Budget, preparing for conferences, and for Flock.
17:12:15 <decause> it is important work
17:12:24 <decause> but I'm looking forward to the "doing" parts so much more
17:12:44 <decause> I'm *thrilled* that we're going to have a big influx in the number of interns coming in
17:12:47 <decause> they start next week
17:12:51 <decause> some are already ehre
17:12:56 <decause> but some are going to be new to us
17:13:09 <decause> and CommOps is here to help them get boostrapped and find their way
17:13:15 <jflory7> commops++
17:13:22 <devyani7> decause++
17:13:37 <jflory7> decause++
17:13:37 <decause> I'm very happy with the momentum and energy I'm seeing here, and how everyone is working together to make thigns happen and actually *do* things.
17:14:05 <decause> we can make all the plans in the world, but the best way to help a new person get involved is to *show* them what getting stuff done looks like
17:14:13 <decause> and I'm pround of all the work being done here
17:14:15 <bee2502> decause++
17:14:42 <decause> thank you all for your help
17:14:54 <decause> and with the GA coming, and the GSoC, and the Budget, there are some big milestones ahead
17:15:09 <decause> let's get lots of stuff done this week and next before conferences really kick in :)
17:15:26 <decause> I'll see some of you tonight, and some of you tomo at the hacksessions
17:15:34 <decause> Happy Hacking All!!!
17:15:39 * decause is good now jflory7
17:15:41 <meskarune> \o/
17:15:45 <jflory7> :)
17:15:59 * jflory7 gavels out
17:16:00 <jflory7> #endmeeting