15:55:00 <jflory7> #startmeeting Fedora CommOps (2016-05-10)
15:55:00 <zodbot> Meeting started Tue May 10 15:55:00 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:55:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:55:00 <zodbot> The meeting name has been set to 'fedora_commops_(2016-05-10)'
15:55:02 <jflory7> #meetingname commops
15:55:02 <zodbot> The meeting name has been set to 'commops'
15:55:07 <jflory7> #nick CommOps
15:55:12 <jflory7> #topic Agenda
15:55:17 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-05-10
15:55:21 <jflory7> #info (1) Roll Call / Q&A
15:55:26 <jflory7> #info (2) Announcements
15:55:30 <jflory7> #info (3) Action items from last meeting
15:55:34 <skamath> .hellomynameis skamath
15:55:34 <jflory7> #info (4) Tickets
15:55:35 <zodbot> skamath: skamath 'Sachin S Kamath ' <sskamath96@gmail.com>
15:55:39 <jflory7> #info (5) Wiki Gardening
15:55:43 <jflory7> #info (6) Community Blog
15:55:47 <jflory7> #info (7) Release Schedule
15:55:51 <jflory7> #info (8) Open Floor
15:56:00 <jflory7> #topic Roll Call / Q&A
15:56:00 <jflory7> #info Name; Timezone; Sub-projects/Interest Areas
15:56:03 <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.
15:56:19 <jflory7> #info Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Join, and more
15:56:23 <jflory7> #chair skamath
15:56:23 <zodbot> Current chairs: jflory7 skamath
15:56:25 <jflory7> Hiya, skamath :)
15:56:27 <skamath> #info Sachin S. Kamath; UTC +5.30; Metrics, CommOps,
15:56:28 <decause> .hello decause
15:56:31 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
15:56:34 <skamath> Hi jflory7
15:56:35 <jflory7> #chair decause
15:56:35 <zodbot> Current chairs: decause jflory7 skamath
15:56:37 <drewmeigs> #info Drew Meigs; UTC -4; CommOps, Docs, FreeMedia
15:56:46 <jflory7> #chair drewmeigs
15:56:46 <zodbot> Current chairs: decause drewmeigs jflory7 skamath
15:56:47 <bkp> #info Brian Proffitt; UTC-4; Social Media
15:56:50 <jflory7> #chair bkp
15:56:50 <zodbot> Current chairs: bkp decause drewmeigs jflory7 skamath
15:56:59 <jflory7> Hiya, all!
15:57:00 <mizmo> .hello duffy
15:57:01 <zodbot> mizmo: duffy 'Máirín Duffy' <fedora@linuxgrrl.com>
15:57:03 <jflory7> #chair mizmo
15:57:04 <zodbot> Current chairs: bkp decause drewmeigs jflory7 mizmo skamath
15:57:32 <decause> #info decause; UTC-4; CommOps, Council, Budget, GSoC, *
15:57:38 <linuxmodder> .hellomynameis linuxmodder
15:57:39 <zodbot> linuxmodder: linuxmodder 'Corey W Sheldon' <sheldon.corey@openmailbox.org>
15:57:49 <jflory7> #chair linuxmodder
15:57:49 <zodbot> Current chairs: bkp decause drewmeigs jflory7 linuxmodder mizmo skamath
15:57:51 <danofsatx> .hello danofsatx
15:57:52 <zodbot> danofsatx: Sorry, but you don't exist
15:57:55 <nb> .hello nb
15:57:56 <zodbot> nb: nb 'Nick Bebout' <nb@nb.zone>
15:57:59 <nb> danofsatx, .hello dmossor
15:58:03 <decause> jflory7: coming up in commblog include Docs FAD report?
15:58:06 <jflory7> #chair danofsatx nb
15:58:06 <zodbot> Current chairs: bkp danofsatx decause drewmeigs jflory7 linuxmodder mizmo nb skamath
15:58:09 <jflory7> decause: Yep, got that one :)
15:58:13 <decause> jflory7+
15:58:16 <decause> jflory7++
15:58:17 <LinuxHippie> Hello...my first meeting....will be in and out, I'm at work
15:58:33 <mizmo> welcome LinuxHippie !
15:58:33 <skamath> Hi LinuxHippie
15:58:46 <jflory7> Hiya, LinuxHippie! No worries, that's fine. Welcome to the meeting! You can do a quick introduction by typing the following: #info Name; Timezone; Sub-projects/Interest Areas
15:59:59 <jflory7> Hey omiday!
16:00:04 <trishnag> .hello trishnag
16:00:05 <zodbot> trishnag: trishnag 'Trishna Guha' <trishnaguha17@gmail.com>
16:00:14 <LinuxHippie> #info Tim Apple; Central; commops/ambassadora
16:00:17 * trishnag is late
16:00:22 <sayan> .hello sayanchowdhury
16:00:24 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
16:00:26 <omiday> hello everyone!
16:00:31 <jflory7> trishnag: No worries, we're just getting started. :)
16:00:34 <omiday> #info Viorel Tabara; UTC-6; CommOps
16:00:38 <jflory7> #chair trishnag omiday sayan
16:00:38 <zodbot> Current chairs: bkp danofsatx decause drewmeigs jflory7 linuxmodder mizmo nb omiday sayan skamath trishnag
16:00:44 <trishnag> jflory7, Cool :)
16:01:04 <skamath> Nice attendance \o/
16:01:19 <sayan> Hi everyone :)
16:01:31 <jflory7> Definitely a full house :)
16:01:32 <skamath> sayan, o/
16:01:41 <omiday> finally
16:02:07 <jflory7> We'll wait just a couple more minutes for any latecomers and then jump into the agenda.
16:02:12 <jflory7> Which is here: https://fedoraproject.org/wiki/Meeting:CommOps_2016-05-10
16:02:31 <jflory7> Also, if anyone has general Q&A, now is a good time to ask questions as well :)
16:02:34 <sayan> #info sayanchowdhury; UTC+5:30; CommOps, Marketing, Ambassador, GSoC
16:02:39 <omiday> anyone using irssi around here?
16:02:53 <skamath> omiday, decause is an irssi fan
16:03:03 <linuxmodder> (/me is  partially here --dealing with other beta stuff, ping me if needed directly)
16:03:08 <sayan> skamath: o/
16:03:23 <skamath> linuxmodder, how are the servers doing?
16:03:25 <decause> omiday: I've been known to use it occassionally, sgood?
16:03:26 <omiday> skamath: thanks I'll bug him
16:03:50 <omiday> decause: quick pointer on how to create an alias for the '#info' command?
16:03:56 <linuxmodder> skamath,  mirrormanager is  still coming back from an earlier  derpy derp  but  seeders are  kicking  buttt
16:04:12 <skamath> \o/ I am seeding
16:04:52 <jflory7> Alrighty, I think we're ready to get started. :) To announcements!
16:04:57 <jflory7> #topic Announcements
16:05:00 <linuxmodder> same  here  (all x64) Desktops Server  WS  Astronomy Scientific Security
16:05:03 <jflory7> The obvious...
16:05:04 <jflory7> #info === "Fedora 24 Beta released!" ===
16:05:08 <jflory7> #link https://fedoramagazine.org/fedora-24-beta-released/
16:05:13 <jflory7> #info Today is the day! Wait no more! F24 Beta is rolling out to mirrors near you soon! The F24 Beta is out. Thanks to all who helped contribute to the release announcement!
16:05:22 <skamath> fedora++
16:05:26 <decause> nice work all
16:05:30 <jflory7> #help Please share the release announcement on your social media channels! Facebook, Twitter, Google+, etc.
16:05:30 <trishnag> \o/
16:05:30 <decause> commops++
16:05:40 <jflory7> commops++
16:05:41 <jflory7> #info === "Fedora’s Love For Python Continues" ===
16:05:45 <jflory7> #link https://communityblog.fedoraproject.org/fedoras-love-python-continues/
16:05:51 <jflory7> #info New brochures about Python in Fedora are available for Ambassadors and other interested groups. Feel free to take them and print some of your own! mizmo++ bkp++ pythonSIG++
16:05:56 <jflory7> #info === Fedora Diversity team meetings ===
16:06:01 <jflory7> #link https://fedoraproject.org/wiki/Diversity_Adviser
16:06:07 <jflory7> #info The Fedora Diversity team, led by tatica, meets every other Tuesday at 12:30 UTC. The next meeting will be May 24 2016, 12:30 UTC. If you are interested in contributing or learning more, join #fedora-diversity and join the mailing list.
16:06:11 <jflory7> #link https://lists.fedoraproject.org/admin/lists/diversity.lists.fedoraproject.org/
16:06:16 <jflory7> #info === Fedora Women Day ===
16:06:19 <jflory7> #link https://fedoraproject.org/wiki/Fedora_Women_Day_2016
16:06:24 <jflory7> #info Fedora Women Day is a virtual event for the weekend of July 15-17. Planning is still underway, but if you are interested, please follow the wiki page.
16:06:32 <jflory7> And that's all I got. Anyone else have any other announcementS?
16:06:48 * decause typing
16:07:11 <decause> #info GSoC, Outreachy, and Red Hat Interns clock-in on 5/23 officially
16:07:17 <linuxmodder> possible poll article pitch  for  Server coming up ( rolekit retirement  >   ansible?  )
16:07:44 <jflory7> linuxmodder: I could see that as a good one for the CommBlog! +1 from me.
16:07:47 <decause> #info Fedora infra and project members will be attending pycon and running a special event at Sprints
16:07:56 <decause> #link http://us.pycon.org
16:08:08 <linuxmodder> that wasn't really a pitch but okay :)
16:08:15 <skamath> decause++
16:08:25 * jflory7 will be watching for PyCon stream(s)
16:08:33 <decause> #info Fedora Docs FAD 2016 was very productive. CommBlog article coming very soon (see later meeting items)
16:08:52 <linuxmodder> jflory7,   danofsatx and I  will be reviewing it
16:09:08 <jflory7> linuxmodder: Sounds good. Looking forward to seeing it!
16:09:12 <jflory7> DocsFAD++
16:09:27 <decause> EoF
16:10:05 <jflory7> Great! Any other announcements before moving on?
16:10:13 <jflory7> Going once...
16:10:20 <jflory7> Going twice...
16:10:23 <linuxmodder> !
16:10:27 <jflory7> linuxmodder: Go for it!
16:10:37 <linuxmodder> any edits to  docs.fp.o  articles  highly  encouraged
16:10:57 <linuxmodder> repo @  https://pagure.io/group/fedora-docs/
16:11:16 <linuxmodder> decause,  speaking of  did we ever get fedora-mktg  fixed up ?
16:11:25 <jflory7> #help Any edits or review for the Fedora Documentation is welcome and appreciated!
16:11:26 <jflory7> #link https://pagure.io/group/fedora-docs/
16:11:30 <jflory7> Awesome. Anything else?
16:11:40 <jflory7> Going once...
16:11:40 <linuxmodder> !
16:11:46 * jflory7 pauses
16:12:06 <linuxmodder> Ideas requested for  F25  and  deadline for  change requests is  july  7
16:12:11 <linuxmodder> eof
16:12:11 <decause> linuxmodder: we're working on it, I asked pingou yesterday, i think there was some kinda hiccup with restoring it from a backup or something?
16:12:38 <decause> #link http://pagure.io/docs-fp-o
16:12:53 <linuxmodder> for server / ws  ideas for  F25  you  can  reach out to danofsatx  or I
16:13:09 <dhanesh95> #info Dhanesh B. Sabane, UTC+5.30, Commops
16:13:15 <jflory7> #info Deadline for Change Requests for Fedora 25 is July 7th - if you want to get the next big change into Fedora, this is the process you need to follow for getting the change incorporated into Fedora.
16:13:17 <jflory7> #link https://fedoraproject.org/wiki/Changes/Policy
16:13:20 <jflory7> #chair dhanesh95
16:13:20 <zodbot> Current chairs: bkp danofsatx decause dhanesh95 drewmeigs jflory7 linuxmodder mizmo nb omiday sayan skamath trishnag
16:13:22 <jflory7> Hiya dhanesh95!
16:13:38 <dhanesh95> Hello jflory7 ! Late, ain't I? :P
16:13:41 <omiday> decause: it was a perms issue after restore iiuc
16:13:48 <linuxmodder> decause,  wrong link for  the  docs
16:13:49 <jflory7> dhanesh95: No worries, just wrapping up on announcements :)
16:14:09 <linuxmodder> #link https://pagure.io/group/fedora-docs
16:14:32 <linuxmodder> Gudies / Docs  for publish  are  ^
16:14:33 <jflory7> Any other announcements?
16:14:41 <linuxmodder> nfm
16:14:41 <decause> linuxmodder: I was digging for the link related to the FAD, took me too long
16:14:45 <jflory7> Going once...
16:14:49 <jflory7> Going twice...
16:14:56 <jflory7> Going thrice...
16:14:59 <dhanesh95> Sold!
16:15:08 <jflory7> #topic Action items from last meeting
16:15:14 <jflory7> #link https://meetbot.fedoraproject.org/fedora-meeting/2016-05-03/commops.2016-05-03-15.55.html
16:15:18 <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:15:25 <jflory7> #info === [INCOMPLETE] decause / jflory7 create a quick pointer to the DOCs FAD Wiki for commblog ===
16:15:36 <jflory7> #info Deadline passed for announcement about Docs FAD - event report is in progress, however!
16:15:41 <jflory7> #info === decause fill up the LimeSurvey account with moneydollars ===
16:15:42 <decause> #wontfix
16:15:45 <decause> err
16:15:53 <jflory7> Re-action for this one?
16:15:57 <decause> yes
16:16:05 <jflory7> #action decause fill up the LimeSurvey account with moneydollars
16:16:09 <jflory7> #info === [INCOMPLETE] jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team ===
16:16:12 <jflory7> #action jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team
16:16:17 <jflory7> #info === [INCOMPLETE] decause / jflory7 File a ticket for exploring how to subscribe the social-media mailing list to the RSS feed of Community Blog ===
16:16:22 <jflory7> #action decause / jflory7 File a ticket for exploring how to subscribe the social-media mailing list to the RSS feed of Community Blog
16:16:27 <jflory7> #info === CommOps solidify onboarding steps before 5/23 internships begin ===
16:16:32 <jflory7> #action CommOps solidify onboarding steps before 5/23 internships begin
16:16:37 <jflory7> #info === decause talk to spot about scheduling an EDU FAD after budget gets settled ===
16:16:45 <jflory7> Any updates here?
16:16:53 <decause> reaction, EDU just posted budget this week
16:17:08 * jflory7 nods
16:17:14 <jflory7> #action decause talk to spot about scheduling an EDU FAD after budget gets settled
16:17:20 <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:17:24 <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:17:30 <jflory7> #info === [INCOMPLETE] jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going) ===
16:17:35 <jflory7> #action jflory7 Open discussion on the mailing list about Ticket #71 and centralizing Ambassador resources (to get brainstorming going)
16:17:40 <jflory7> #info === jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors ===
16:17:45 <jflory7> #action jflory7 Write Bitcamp 2016 article on CommBlog and point to individual event reports by other Ambassadors
16:17:59 <jflory7> Lots more incompletes from me than I wanted :P
16:17:59 <jflory7> #info === skamath help with gardening of Summer Coding wiki ===
16:18:07 <skamath> It's done jflory7
16:18:11 <jflory7> skamath++
16:18:16 <decause> jflory7: we didn't do a hacksession last week to catch up
16:18:17 <dhanesh95> skamath++
16:18:37 <jflory7> skamath: This page, right? https://fedoraproject.org/wiki/Summer_Coding_SIG
16:18:39 <decause> with beta release and FAD and budget, things have been a bit busy
16:18:40 <drewmeigs> skamath++
16:18:40 <zodbot> drewmeigs: Karma for skamath changed to 12 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:18:46 * jflory7 sees recent edits on this one for GSoC 2016 :)
16:19:05 * skamath has also compiled the names here : https://fedoraproject.org/w/index.php?title=Summer_coding_2016
16:19:14 <jflory7> :thumbs_up:
16:19:28 <linuxmodder> jflory7,  at this point  blog  post for  bitcamp is  kinda irrelevant
16:19:32 <jflory7> #link https://fedoraproject.org/wiki/Summer_Coding_SIG
16:19:38 <jflory7> #link https://fedoraproject.org/wiki/Summer_coding_2016
16:19:48 <jflory7> skamath: Can you add the categories to the page?
16:20:04 <jflory7> See for examples here: https://fedoraproject.org/wiki/GSOC_2016
16:20:05 <skamath> #action skamath add categories to the Summer Coding 2016 page
16:20:11 <jflory7> skamath++
16:20:19 <jflory7> #info === CommOps start a stub for a vFAD over the summer (before Flock) ===
16:20:24 <jflory7> #info This item is already a ticket
16:20:30 <jflory7> #info === [INCOMPLETE] jflory7 Bring the CommOps vFAD ticket back up to the table, make a wiki page, do the metadata planning-esque type of tasks ===
16:20:40 <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:20:52 <jflory7> #action jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket
16:20:56 <jflory7> Oops
16:20:57 <jflory7> #undo
16:20:57 <zodbot> Removing item from minutes: ACTION by jflory7 at 16:20:52 : jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket
16:20:58 <jflory7> #info === [INCOMPLETE] jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket ===
16:21:00 <jflory7> #action jflory7 Request feedback from Modularity WG on on-boarding feedback in ticket
16:21:05 <jflory7> #info === [COMPLETE] jflory7 Schedule "Python + Fedora brochures" article for Thursday ===
16:21:09 <jflory7> #link https://communityblog.fedoraproject.org/fedoras-love-python-continues/
16:21:16 <jflory7> #info === [COMPLETE] jflory7 Check in with gnokii about when to ship the F24 Release Parties article ===
16:21:33 <gnokii> hu
16:21:34 <jflory7> #info This should be going out ASAP this week
16:21:46 <decause> jflory7: nod nod
16:21:49 <jflory7> #info === [COMPLETE] jflory7 Ping mailing lists about F24 Beta Release Announcement again, deadline: Friday ===
16:21:54 <jflory7> decause++
16:21:57 <jflory7> #link https://pagure.io/fedora-mktg/blob/master/f/release-announcements/f24/beta
16:22:00 <linuxmodder> jflory7,  Final release parties not beta right?
16:22:02 <jflory7> #info === [INCOMPLETE] jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + list ===
16:22:05 <jflory7> linuxmodder: Correct.
16:22:07 <decause> linuxmodder: yeah, final
16:22:10 <jflory7> #action jflory7 Pitch the idea of pushing CommOps meeting by 30 minutes, "officially", in ticket + lis
16:22:14 <jflory7> #info === [INCOMPLETE] drewmeigs check in with decause and jflory7 on meeting agendas and Meetbot ===
16:22:17 <jflory7> This one was on jflory7
16:22:21 <jflory7> #action jflory7 Pass information to drewmeigs about preparing next week's meeting agenda
16:22:25 <decause> reaction, we'll get there
16:22:35 <jflory7> Okay! That's all the action items from last meeting
16:22:38 <linuxmodder> jflory7,  pushing as in  timeslot or  +30 mins to  slot
16:22:47 <jflory7> I've got a lot of catching up to do from the backlog
16:23:07 <decause> jflory7: so do I, but we've got your back :)
16:23:10 <jflory7> linuxmodder: +30 minutes is what I was going to pitch.
16:23:13 <jflory7> decause: :)
16:23:18 <jflory7> Okay, let's go to tickets!
16:23:22 <jflory7> #topic Tickets
16:23:26 <jflory7> #link https://fedorahosted.org/fedora-commops/report/9
16:23:31 <jflory7> #info === Tickets #34, 49 ===
16:23:36 <jflory7> #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
16:23:40 <jflory7> #info #49: "[Onboarding Series] Infrastructure"
16:23:44 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/34
16:23:49 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/49
16:23:53 <jflory7> #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
16:23:56 <jflory7> Mostly working through previous items and getting up to speed (not much new to report). Last action item was to refine our own Join process as the testing bed for the onboarding process badges. Do we want to do any other planning now or continue to work through the existing queue of tasks?
16:24:08 <jflory7> We're pretty much in the same state as before with this one.
16:24:32 <decause> it seems like we need 2 hack sessions: one for catch-up, and one for badges in specific
16:24:38 <jflory7> The relevant action for this ticket is: [12:16:32] <jflory7> #action CommOps solidify onboarding steps before 5/23 internships begin
16:24:44 <skamath> decause, have you used fedmsg-meta before?
16:24:47 <dhanesh95> jflory7: What do we mean by refining our joining process?
16:24:49 <decause> and by 'we' I mean 'not you jflory7' because you have finals
16:25:19 <decause> skamath: a bit, yes
16:25:30 <skamath> decause, Cool. I'll ping you after the meeting
16:25:39 <decause> skamath: #fedora-apps is a great place to ask
16:25:43 <jflory7> dhanesh95: That's a good question. Refining our Join process is more towards making it friendly towards a Badges model so we can identify key tasks that people complete for getting involved in CommOps, and creating badges for those items.
16:25:52 <jflory7> e.g. mailing list activity, participating in meetings, etc.
16:25:57 <jflory7> Some of these badges already exist.
16:26:01 <dhanesh95> jflory7++
16:26:02 <jflory7> Some are already proposed.
16:26:20 <jflory7> The hack session decause mentioned for Badges is where we want to try to tackle that :)
16:26:32 <decause> nailing down the new ML badges for instance will have broad impact in the onboarding system (nearly all the series' and Join processes require ML actiivty)
16:26:44 <dhanesh95> jflory7 :thumbs-up:
16:26:57 <dhanesh95> decause: +1
16:27:11 <jflory7> So I think this ticket is really just backlog.
16:27:20 <linuxmodder> tbh  badges inclusion should be  last thing  imo
16:27:33 <dhanesh95> The hack session will effectively close this ticket I suppose
16:27:36 <jflory7> Getting the "general" badges through for things like mailing list activity is one of the more important badge proposals
16:27:43 <decause> linuxmodder: we have the Join process, this is specifically to figure out which pieces don't have badges.
16:27:44 <jflory7> dhanesh95: It should complete Ticket #49 :)
16:28:03 <linuxmodder> decause,  why must  EVERY step have a bloody badge seriously?
16:28:07 <decause> linuxmodder: but I agree, the flow is more important that the badge itself
16:28:19 <linuxmodder> getting  13 for a fully  completed  fas profile is  still beyond me
16:28:21 <decause> linuxmodder: not every step does, this is figuring out which ones don't/won't
16:28:28 <skamath> linuxmodder, lol
16:28:31 <jflory7> I feel like this is just going to lead to bikeshedding, this is a discussion that's happened for the past couple of weeks
16:28:37 <linuxmodder> skamath,  no joke
16:28:53 <decause> linuxmodder: we want to be able to keep track of where people are in the process, because lots of folks "fall off" after their initial contact with a team
16:29:00 <linuxmodder> only  ones imo that  matter enough are  gpg key  / ssh key timezone
16:29:04 <decause> or the team doesnt' realize that a person has gone through the steps
16:29:20 <skamath> linuxmodder, badges are part of my GSoC :p
16:29:22 <decause> linuxmodder: we can get into the particulars later, for now we should keep moving
16:29:30 <linuxmodder> decause,  and imo badges is a shitty way to metric that but  whatever
16:29:40 <jflory7> dhanesh95: One thing of note too, when it comes to badges, it's better to propose badges that have a far-reaching impact on all sub-projects as compared to just one. This puts a lighter load on the Design Team and makes the work for the badge benefit more than just one group.
16:29:43 <linuxmodder> skamath,  I know
16:30:03 <decause> linuxmodder: duly noted, as you have mentioned more than once, in each meeting when we talk about badges. I'm interested to hear about alternatives.
16:30:09 <dhanesh95> linuxmodder: Whatever decause said and new contributors feel awesome when they receive more and more badges.
16:30:15 <dhanesh95> jflory7++
16:30:18 <jflory7> linuxmodder: This is a discussion that has happened for numerous meetings and we always reach the same conclusion. You said you were going to work on a proposal for this about an alternative to badges and you would get it to us when ready.
16:30:28 <skamath> linuxmodder, It can make the metrics easier, don't you think?
16:30:50 <linuxmodder> jflory7,  and beta  stuff came up  sorry I still paln to
16:30:52 <jflory7> I really don't want to go into more discussion about this again because it's just going to lead to bikeshedding imp
16:30:53 <jflory7> * imo
16:31:01 <linuxmodder> skamath,   yes but in its  current  state no
16:31:11 <jflory7> Then let's reconvene on your point once we have an alternative that can be pitched.
16:31:55 <jflory7> Otherwise, for this ticket, I believe that we're in same position as before and we can work through the backlog at our next hack session.
16:32:04 <jflory7> Anything else anyone wants to add to this ticket?
16:32:11 <decause> nod nod, we need to schedule the hack session for realz
16:32:13 <jflory7> Going once...
16:32:17 <jflory7> decause: Agreed
16:32:19 <jflory7> Going twice...
16:32:22 <dhanesh95> jflory7: Completing #49 will cover a major chunk of the refining process, imo
16:32:26 <jflory7> Going thrice...
16:32:38 <jflory7> dhanesh95: It will definitely make it easier for other sub-groups once we have one down :)
16:32:48 <dhanesh95> jflory7: +1
16:32:50 <dhanesh95> Sold!
16:32:59 <skamath> jflory7, https://fedorahosted.org/fedora-commops/ticket/74
16:33:00 <jflory7> #agreed There are current tasks that have already been identified for this ticket. We plan to work on the general badge proposals at the next hack session and have more to report then!
16:33:09 <jflory7> #info === Ticket #68 ===
16:33:13 <jflory7> #info "Reconstructing the Campus Ambassadors program and campus outreach"
16:33:18 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/68
16:33:22 <jflory7> #link http://etherpad.osuosl.org/fedora-EDU-refresh
16:33:26 <jflory7> #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative
16:33:30 <jflory7> #link https://fedoraproject.org/wiki/Objectives/University_Involvement_Initiative/draft
16:33:34 <decause> dhanesh95++
16:33:34 <jflory7> dhanesh95 has made a lot of awesome progress already and sent a request for feedback to the mailing list. Should be ready to merge into the main page. If no objections, this can be done ASAP.
16:33:36 <decause> nice post to the list
16:33:44 <jflory7> I'm +1 to seeing the pages merge :)
16:33:51 <dhanesh95> +1
16:34:01 <jflory7> skamath: Acknowledged, will get that one added to the agenda now
16:34:04 <decause> I would just be sure to include the "Proposed" in the title for sure
16:34:33 <skamath> I was about to add it to the agenda, but the meeting had started by then
16:34:53 <dhanesh95> skamath has been waiting for a long time for #74
16:35:21 <skamath> dhanesh95, I love licenses :p
16:35:50 <dhanesh95> decause++ and jflory7++ for #68
16:35:56 <jflory7> dhanesh95: I'm +1 to seeing the pages merged, and with decause's feedback too, I think it's ready to happen.
16:36:05 <jflory7> Do you want to work on adding the draft changes in to the main one?
16:36:19 <dhanesh95> jflory7: Yay!
16:36:21 <jflory7> I would just put the "Proposed" part in the header for the section.
16:36:27 <dhanesh95> jflory7: Is it possible to complete it in 15 min? :P
16:36:34 <jflory7> Heh, maybe :P
16:36:39 <jflory7> Will action anyways ;)
16:36:50 <dhanesh95> I'll do it :P
16:37:04 <jflory7> #action dhanesh95 Work on merging the draft changes for the University Involvement Initiative into the main page (including in the section header "Proposed")
16:37:18 <jflory7> Awesome! I think that's all for this ticket. There will likely be some more momentum rolling on this soon.
16:37:30 <jflory7> Anything else for this ticket today?
16:37:32 <jflory7> Going once...
16:37:41 <jflory7> Going twice...
16:37:47 <jflory7> Going thrice...
16:37:57 <jflory7> #info === Ticket #69 ===
16:37:58 <jflory7> #info "Fedora Modularity onboarding"
16:38:02 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/69
16:38:06 <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:38:11 <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:38:18 <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:38:24 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/69#comment:2
16:38:28 <jflory7> Progress was made at the last hack session, but follow-up is needed with the Modularity WG to hear their feedback on our ideas and plans. A blog post announcing the WG is also forthcoming.
16:39:02 <jflory7> I believe langdon was going to work with the Modularity WG on the Community Blog article, but there's not a huge "rush" for that at the moment, especially with F24 taking up a lot of people's time
16:39:28 <jflory7> decause and I worked on this at our last hack session but we need to follow up with Modularity on the ideas / changes we made
16:39:35 <jflory7> decause: Want to take an action here to get more feedback?
16:39:49 * dhanesh95 is going away. Will catch up later. \m/
16:39:58 <jflory7> dhanesh95: See ya around! Thanks for coming out.
16:40:01 <skamath> See ya dhanesh95
16:40:11 <decause> jflory7: ship sooner than later, ping the WG in channel with it right after this meeting?
16:40:22 <jflory7> decause: Sounds like a plan to me!
16:40:53 <jflory7> #action jflory7 / decause Drop ticket comment in #fedora-modularization after meeting
16:41:09 <jflory7> Okay, not sure what else to do for now until we get some more feedback.
16:41:17 <jflory7> Should be good for this ticket for now?
16:41:32 <jflory7> Going once...
16:41:42 <jflory7> Going twice...
16:41:48 <jflory7> Going thrice...
16:42:16 <jflory7> #agreed Feedback is needed on existing changes / ideas, so jflory7 and decause will follow up with Modularity WG
16:42:19 <jflory7> #info === Ticket #71 ===
16:42:24 <jflory7> #info "Centralizing Ambassadors / Events resources and utilities"
16:42:28 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/71
16:42:33 <jflory7> This ticket has to do with bringing together several different resources and tools for Ambassadors and events into a single place. zoltanh721 also left feedback on this ticket (was originally filed in the Marketing Trac). jflory7 was to open discussion on the list at last meeting (but was unable to do so before the meeting).
16:42:44 <jflory7> Honestly haven't had time to tackle this one this week.
16:43:18 <decause> jflory7: again, things are crazy right now, we can just keep moving
16:43:20 <jflory7> I want to get some feedback to Zoltán soon since he's been waiting for a while
16:43:23 <jflory7> Yeah
16:43:30 <jflory7> I'll try to drop a comment in the ticket this week
16:43:37 <jflory7> I have an action for this already from previous action items
16:43:41 <jflory7> So I'll use that
16:44:04 <jflory7> #agreed More discussion is needed about this topic; jflory7 will follow up in the ticket as soon as possible
16:44:12 <jflory7> #info === Ticket #74 ===
16:44:17 <jflory7> #info "Add license information to the CommBlog footer"
16:44:21 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/74
16:44:34 <jflory7> So! This one has an easy answer, I think. :)
16:44:37 * jflory7 does some link digging
16:45:03 <skamath> #link https://creativecommons.org/licenses/by-sa/3.0/
16:45:28 <jflory7> skamath: The place for changes to the theme for the Community Blog is on Pagure. The entire theme is open source, and the designer, ryanlerch, looks there for feedback on changes that might need to be made, e.g. a footer.
16:45:43 <jflory7> I think we could change this from the front-end ourselves, but if we ever deploy a new version, that change would be overwritten
16:45:46 * jflory7 thinks, anyways
16:45:48 <jflory7> #link https://pagure.io/communityblog-theme
16:46:00 <jflory7> skamath: Think you could file an issue there for ryanlerch?
16:46:11 <skamath> jflory7, Will do
16:46:15 <jflory7> Awesome!
16:46:37 <jflory7> #action skamath File an issue in the Community Blog repo for adding a footer with licensing information to the bottom of the site
16:46:44 <skamath> jflory7++
16:46:47 <jflory7> I think that should cover that ticket.
16:47:00 <jflory7> Time check at 3/4 mark
16:47:08 <skamath> easyfix ;)
16:47:09 <jflory7> I also think that covers all the tickets for today.
16:47:14 <jflory7> :)
16:47:21 <jflory7> With that, let's head on to wiki gardening...
16:47:22 <jflory7> #topic Wiki Gardening
16:47:27 <jflory7> #action CommOps New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
16:47:32 <jflory7> #help Fork the PyCon 2015 event page and udpate it with the latest info
16:47:39 <jflory7> decause: Did you have specific links for this one?
16:47:50 * decause digs
16:48:00 * LinuxHippie will do
16:48:10 <decause> old link: https://fedoraproject.org/wiki/PyCon_2015
16:48:17 <decause> new link should go to : https://fedoraproject.org/wiki/PyCon_2016
16:48:59 <decause> #action decause update the PyCon_2016 wiki page with latest info
16:49:30 <jflory7> LinuxHippie: This would be a good one decause could use some help on too :)
16:49:52 <jflory7> For the most part, it's taking the 2015 content, moving to 2016 wiki page, and checking for current info, right, decause?
16:49:58 <jflory7> #link https://fedoraproject.org/wiki/PyCon_2015
16:50:02 <jflory7> #link https://fedoraproject.org/wiki/PyCon_2016
16:50:16 <decause> jflory7: exactly
16:50:22 <LinuxHippie> Ok
16:50:39 <decause> once the stub is there, we can post to pythonSIG/ambassadors and see if folks are going who we don't know about yet
16:50:57 <decause> #action decause get the tshirt orders in ASAP for PyCon (this could maybe use a ticket)
16:51:05 <decause> #action decause get the sticker orders in ASAP for PyCon (this could maybe use a ticket)
16:51:19 <jflory7> It would be nice to see the PyCon 2016 wiki page follow this format for events: https://fedoraproject.org/wiki/RIT_BrickHack/2016
16:51:24 <decause> we know that kushal, lmacken, threebean, and decause will be there
16:51:52 <jflory7> decause: For stickers, you should file a ticket in the FAmNA Requests Trac, I believe. I know FAmNA does not have any shirts
16:52:04 <decause> jflory7: this is not going to come out of Ambassadors
16:52:08 <jflory7> Ahh, I see
16:52:28 <decause> this is coming out of OSAS budget (saving ambassadors some loot, high-level project objective)
16:52:40 <jflory7> LinuxHippie: For this one, I think the best course of action would be take this page ( https://fedoraproject.org/wiki/RIT_BrickHack/2016 ), copy its contents, and then update it for PyCon 2016.
16:52:46 <jflory7> Sound reasonable?
16:52:56 <decause> and because the stickers/shirts will not be region-specific, and will go to other PyCon places too
16:53:21 <jflory7> LinuxHippie: Event description does not have to be very verbose, it can just be copied + pasted from the website or even a link to a longer description somewhere else.
16:53:29 <jflory7> decause: Gotcha, makes sense.
16:53:34 <decause> jflory7: yes and no. We are not sponsoring this event officially, or spending travel money to get people there out of fedora public budget
16:53:47 <LinuxHippie> OK...will try to get cracking on it tonight
16:53:49 <decause> jflory7: I'm all for "merging" the best of both worlds
16:54:39 <jflory7> LinuxHippie: Okay, that's awesome! If you have any questions or need help, you can ask in the mailing list or on IRC. Like decause is saying, I think you can snip out a lot of the budget sections from the BrickHack page since it's a little bit different for budget items in PyCon.
16:54:57 <LinuxHippie> Ok
16:55:03 <decause> LinuxHippie: if you get it started, I'll make sure to get it filled out properly
16:55:14 <LinuxHippie> Sounds good
16:55:25 <decause> LinuxHippie: there'll be some very exciting design elements to add to it as well, (ticket #431 files on design-trac)
16:55:43 <jflory7> #action 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:55:46 <decause> I've been working with mizmo today to get the designs finalized
16:55:52 <jflory7> LinuxHippie++ Thanks for offering to help out with this one. :)
16:55:52 <zodbot> jflory7: Karma for linuxhippie changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:55:52 <mizmo> yo
16:56:01 <decause> mizmo++
16:56:18 <jflory7> Want to hit the CommBlog now?
16:56:25 <decause> jflory7: yeah, popcorn time
16:56:26 <jflory7> If nothing else for wiki gardening.
16:56:31 <jflory7> Heheh
16:56:39 <jflory7> Okay. Let's go!
16:56:40 <jflory7> #topic Community Blog
16:56:46 <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!
16:56:53 <jflory7> #info === This Week in CommBlog ===
16:56:57 <jflory7> #info (1) "Fedora's Love For Python Continues"
16:57:01 <jflory7> #link https://communityblog.fedoraproject.org/fedoras-love-python-continues/
16:57:05 <jflory7> #info Total Views (May 5 - May 9): 102
16:57:10 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1470
16:57:15 <jflory7> #info === Coming Up in CommBlog ===
16:57:20 <jflory7> #info (1) "Fedora 24: Let’s have a party!"
16:57:25 <jflory7> #link https://communityblog.fedoraproject.org/?p=1496&preview=1&_ppp=a34697b353
16:57:45 <jflory7> #action jflory7 Help ship F24 Party article for Thursday morning (Wednesday if possible)
16:57:45 <jflory7> #info (2) "Event Report: Fedora Docs FAD"
16:57:51 <jflory7> #link https://communityblog.fedoraproject.org/?p=1511&preview=1&_ppp=b48bef9a25
16:57:58 <jflory7> #info (3) "Fedora at Bitcamp 2016"
16:58:03 <jflory7> #info In progress, jflory7 to assist in writing this one
16:58:07 <jflory7> #info (4) "DevConfCZ 2016: Event Report"
16:58:11 <decause> lolsob
16:58:12 <jflory7> #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=97da4ae90c
16:58:21 <jflory7> That's all I have.
16:58:25 <jflory7> decause: ;)
16:58:31 <jflory7> Any other Community Blog business?
16:58:42 <jflory7> Oh, when do we want to ship that Docs FAD article?
16:58:44 <decause> #info (5) "Fedora 24 Beta is Live!"
16:58:51 <decause> today pointer article
16:59:00 <jflory7> Ahh! Yeah, that would be excellent.
16:59:21 <decause> and docs FAD can ship tomo, unless we wanna ship the F24 party one
16:59:28 <decause> whichever day we don't ship the part post
16:59:34 <decause> we ship the Docs FAD post
16:59:44 <decause> s/part/party
16:59:45 <jflory7> I'm okay with doing Docs FAD a little bit later to keep things a little bit separated
17:00:00 <jflory7> We have better metrics when we space articles out
17:00:10 <decause> jflory7: mattdm wants to point to Docs FAD in 5tftw
17:00:15 <jflory7> Ahhh.
17:00:18 <decause> which, do we have an etherpad for, right?
17:00:30 <decause> let's fill that up for mattdm a lil bit with some links if we got em
17:00:32 <jflory7> we do, hold on
17:00:40 <jflory7> #link https://www.piratepad.ca/p/5tftw
17:00:40 <decause> jflory7 digs deep
17:01:00 <jflory7> ;)
17:01:12 <jflory7> Thank you unique browser history string
17:01:51 <decause> :P
17:01:58 <jflory7> So I'm thinking Docs FAD... tomorrow... and F24 Party... maybe Monday or Tuesday? I really want to make sure both articles get their proper exposure and promotion
17:02:58 <jflory7> decause: Although anything going out tomorrow, I don't know if I'll have the cycles to review tonight
17:03:27 <decause> jflory7: I think that we need to just have a promotion strategy that reposts them, more than waiting on these ones in particular because: 1) F24 release parties need time to plan
17:03:43 <decause> jflory7: no worries
17:03:53 <jflory7> A more consistent promotion strategy would also be a good idea
17:04:00 <decause> nod nod nod
17:04:07 <jflory7> Mailing list highlights for some of these articles too would be useful
17:04:10 <decause> this is def a way that commops members can help for sure
17:04:21 <jflory7> Release parties => Ambassadors, Docs FAD => Docs list, ???
17:04:29 * LinuxHippie has to run..time to pull some cable.
17:04:34 <decause> subscribing to social-media, where we post the "please help promote this link/article/announce' type messages
17:04:35 <jflory7> In either case, we can probably discuss this in channel
17:04:40 <jflory7> LinuxHippie: Thanks for coming out, see ya around!
17:04:52 <decause> nod nod nod
17:05:00 <jflory7> decause: Cool, we will push then
17:05:04 <skamath> Have a great day LinuxHippie :)
17:05:13 <omiday> promote on ask fedora - a banner at the top etc.?
17:05:17 <jflory7> That should be it for CommBlog discussion
17:05:22 <decause> jflory7: nod nod nod
17:05:30 <decause> omiday: I didn't know we could put banners on Ask
17:05:41 <jflory7> omiday: Ask Fedora would be a cool place to promote the Magazine / CommBlog if there's a way we can put something in there!
17:05:53 <LinuxHippie> Thanks...catch y'all later.
17:05:59 <omiday> there is always a way :)
17:06:13 <omiday> we should open a ticket
17:06:23 <omiday> I can look into it
17:06:38 <skamath> omiday, ask.fp.o is already cluttered in my opinion. I don't see a space for banner anywhere there
17:06:44 <jflory7> omiday: That would be awesome. I was trying to see who the point of contact for Ask is, but I can't find anything
17:06:56 <jflory7> There's also a big redesign that GSoC student from last year did
17:07:04 <jflory7> Not sure if that's deployed or close to being deployed
17:07:12 <jflory7> omiday: I would follow up with the Infrastructure list
17:07:19 <jflory7> Want to take on that task?
17:07:26 <omiday> jflory7: sure
17:07:50 <skamath> #link https://suchakra.wordpress.com/2015/01/20/ask-fedora-ux-redesign-updates-1/
17:07:57 <jflory7> #action 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
17:08:14 <jflory7> skamath: Yep, that's the new UI.
17:08:18 <jflory7> So looks like it isn't deployed yet.
17:08:28 <jflory7> We will check in on this one next week. :)
17:08:29 <jflory7> #topic Release Schedule
17:08:39 <jflory7> #link https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
17:08:41 <skamath> jflory7, I don't think it's complete
17:08:43 <jflory7> Sooooo, F24 Beta today
17:09:01 <jflory7> skamath: Hopefully someone in Infra has a better idea of where that is.
17:09:10 <omiday> skamath: I'm not sure either where but thought about just making it work because ask fedora is a very busy place
17:09:30 <jflory7> I don't think much else is on the release schedule for us right now. Next up is really just the final release.
17:09:47 <jflory7> For that reason, I'm just going to switch over to Open Floor
17:09:52 <jflory7> #topic Open Floor
17:10:18 <jflory7> Okay, we're a little bit over... as usual. ;) Anyone have any other questions or topics they want to bring up before we close out?
17:10:54 <jflory7> If not, we'll close out in another three minutes.
17:11:00 <decause> jflory7: let's just plan on posting a thread to officially add +30 mins to commops meeting
17:11:04 <decause> ?
17:11:18 <jflory7> decause: Heh, yeah, I'm all for it. Meant to do that over the weekend
17:12:26 <omiday> +1
17:13:26 <jflory7> Okay, done
17:13:55 <jflory7> Thanks for coming out today everyone!
17:14:04 <jflory7> See you all next week. :)
17:14:08 <jflory7> #endmeeting