15:56:39 <jflory7> #startmeeting Fedora CommOps (2016-04-12)
15:56:39 <zodbot> Meeting started Tue Apr 12 15:56:39 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:56:39 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:56:39 <zodbot> The meeting name has been set to 'fedora_commops_(2016-04-12)'
15:56:44 <jflory7> #meetingname commops
15:56:44 <zodbot> The meeting name has been set to 'commops'
15:56:49 <jflory7> #topic Agenda
15:56:54 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-04-12
15:56:57 <jflory7> #info (1) Roll Call
15:57:02 <jflory7> #info (2) Announcements
15:57:07 <jflory7> #info (3) Action items from last meeting
15:57:11 <jflory7> #info (4) Tickets
15:57:16 <jflory7> #info (5) Wiki Gardening
15:57:20 <jflory7> #info (6) Community Blog
15:57:28 <jflory7> #info (7) Release Schedule
15:57:32 <jflory7> #info (8) Open Floor
15:57:44 <jflory7> The agenda is a little bit incomplete today :( Still working on CommBlog section
15:57:55 <jflory7> #topic Roll Call
15:58:00 <jflory7> #info Name; Timezone; Sub-projects/Interest Areas
15:58:03 <jflory7> If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello!
15:58:19 <jflory7> #info Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Join, and more
15:59:07 <decause> .hello decause
15:59:08 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
15:59:21 <decause> #info decause; UTC-4; CommOps, Council, Flock, *
15:59:27 <nils> .hello nphilipp
15:59:28 <zodbot> nils: nphilipp 'Nils Philippsen' <nphilipp@redhat.com>
15:59:38 <decause> nils++
15:59:38 <zodbot> decause: Karma for nphilipp changed to 2 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:59:39 <decause> welcome
15:59:48 <c0mrad3> #info Tummala Dhanvi; UTC+5:30; CommOps,Docs,Security,*
15:59:53 <c0mrad3> .hello dhanvi
15:59:54 <zodbot> c0mrad3: dhanvi 'Tummala Dhanvi' <dhanvicse@gmail.com>
16:00:15 <jflory7> #chair decause c0mrad3
16:00:15 <zodbot> Current chairs: c0mrad3 decause jflory7
16:00:26 <jflory7> Hello all!
16:00:28 <GIANT_CRAB> hello
16:00:36 <trishnag> .hello trishnag
16:00:36 <nils> hi!
16:00:36 <zodbot> trishnag: trishnag 'Trishna Guha' <trishnaguha17@gmail.com>
16:00:38 <c0mrad3> Hello
16:00:45 <GIANT_CRAB> .hello woohuiren
16:00:46 <zodbot> GIANT_CRAB: woohuiren 'Woo Huiren' <giantcrabby@gmail.com>
16:01:09 <jflory7> #chair trishnag GIANT_CRAB
16:01:09 <zodbot> Current chairs: GIANT_CRAB c0mrad3 decause jflory7 trishnag
16:01:48 <jflory7> We can wait a few more minutes for some more people to come in, and then we'll get started :)
16:01:58 <Dimuthu> hi guys
16:02:01 <Dimuthu> :)
16:02:03 <GIANT_CRAB> would be good to have this promoted - http://www.meetup.com/Fedora-in-Singapore/events/230285000/
16:02:10 <GIANT_CRAB> on Fedora's twitter or something
16:02:20 <jflory7> GIANT_CRAB: You should drop a line to the social-media mailing list!
16:02:29 <jflory7> Hi, Dimuthu!
16:02:31 <jflory7> #chair Dimuthu
16:02:31 <zodbot> Current chairs: Dimuthu GIANT_CRAB c0mrad3 decause jflory7 trishnag
16:02:42 <linuxmodder> .hellomynameis corey84
16:02:42 <linuxmodder> .fas corey84
16:02:43 <zodbot> linuxmodder: corey84 'Corey Sheldon' <sheldon.corey@gmail.com>
16:02:46 <zodbot> linuxmodder: corey84 'Corey Sheldon' <sheldon.corey@gmail.com>
16:03:05 <jflory7> Don't forget to introduce yourself with #info Name; Timezone; Sub-projects/Interest Areas
16:03:15 * linuxmodder will be  asent for a few minutes tieng up a mtg
16:03:15 <jflory7> This way it is placed into the meeting minutes after we close :)
16:03:39 <decause> nod nod nod
16:03:54 <nils> #info Nils Philippsen; Europe/Berlin; Fedora Modularization
16:04:11 <linuxmodder> #info Corey84 UTC -5 , ambassadors,campus-ambassadors,docs,commops,mktg,security
16:04:14 <nils> or should this be the FAS name?
16:04:16 <decause> agenda link jflory7 ?
16:04:26 <decause> nils: ircnick is best
16:04:27 <linuxmodder> nils,  either
16:04:37 <jflory7> decause: https://fedoraproject.org/wiki/Meeting:CommOps_2016-04-12
16:04:41 <decause> jflory7++
16:04:43 <jflory7> It's not fully complete :(
16:04:44 <linuxmodder> if signed in with your fas  it  will link up
16:04:44 <nils> okay, repeat
16:04:50 <jflory7> I use real name personally
16:04:54 <jflory7> Either way is fine in my opinion
16:04:59 <jflory7> Meetbot adds your nick too
16:05:07 <nils> #info nphilipp/Nils Philippsen; Europe/Berlin; Fedora Modularization
16:05:10 <jflory7> So for the #info line it has your nick at the end as the user :)
16:05:21 <linuxmodder> mine shows as  linuxmodder corey84 shared link ...........
16:05:26 <decause> jflory7: right
16:05:28 <decause> :P
16:05:33 <linuxmodder> both nicks are searchable and linked in fas
16:05:44 <decause> the fedmsg is what I'm thinking of too, but not many people use that ;)
16:06:02 <decause> anywhooo
16:06:18 <jflory7> Okay, let's get started in announcements. decause, want to take this one while I finish up on CommBlog stats wrangling?
16:06:24 <decause> ok, sure
16:06:26 <jflory7> #topic Announcements
16:07:00 <decause> #info Fedora Budget Adjustment period is underway as of yesterday's council meeting
16:07:22 <decause> #help Ambassadors Submit your Proposals/Reports/Delegation Selections before 4/13
16:08:08 <decause> #info Flock CFP results are in! We had nearly 150 submissions from 107 speakers!
16:08:27 <decause> the selection committee will be reviewing over the next couple of weeks
16:08:51 <danofsatx> sorry, was speaking to a class.
16:08:55 <danofsatx> .hello dmossor
16:08:55 <zodbot> danofsatx: dmossor 'Dan Mossor' <danofsatx@gmail.com>
16:08:56 <decause> CommOps will likely publish something "quick-n-dirty" about the results of the CFP in the near future
16:08:59 <decause> danofsatx++
16:09:03 <decause> you're good :)
16:09:11 <decause> welcome welcome
16:09:13 <decause> back
16:09:41 <decause> those are the decause-specific announcements
16:09:48 <danofsatx> #info Dan Mossor, dmossor, UTC-5, CommOps, {Campus}Ambassadors, KDE, Server, QA
16:09:50 <decause> oh
16:09:54 <decause> and
16:10:37 <decause> #info GSoC Slot requests have been submitted. Mentors and admins will be finalizing their projects starting tomo, to be annouced by 4/22
16:10:37 <jflory7> #chair danofsatx
16:10:37 <zodbot> Current chairs: Dimuthu GIANT_CRAB c0mrad3 danofsatx decause jflory7 trishnag
16:11:12 <decause> jflory7: you good now, or should I keep going?
16:11:29 <jflory7> Just finished.
16:11:32 <decause> kk, word
16:11:35 * decause passes the baton
16:11:36 <jflory7> decause++
16:11:39 <elioqoshi> .fas elioqoshi
16:11:40 <zodbot> elioqoshi: elioqoshi 'Elio Qoshi' <ping@elioqoshi.me>
16:11:43 <elioqoshi> Hi there!
16:11:47 <jflory7> Exciting about all of the submissions for Flock!
16:11:50 <jflory7> #chair elioqoshi
16:11:50 <zodbot> Current chairs: Dimuthu GIANT_CRAB c0mrad3 danofsatx decause elioqoshi jflory7 trishnag
16:11:53 <jflory7> Hiya, elioqoshi!
16:12:08 <jflory7> #topic Action items from last meeting
16:12:08 <Dimuthu> Hi elioqoshi :)
16:12:12 <decause> jflory7: yeah, we'll likely to a proper breakdown of type and category at some point soon
16:12:13 <jflory7> #link https://meetbot.fedoraproject.org/fedora-meeting/2016-04-05/commops.2016-04-05-15.56.html
16:12:30 <jflory7> decause: That would be icing on the cake.
16:12:37 <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:12:44 <jflory7> #info === [INCOMPLETE] jflory7 Send link to social-media for Flock CFP deadlines as a reminder with the deadline fast approaching ===
16:12:52 <jflory7> Too late for follow-up now, deadline has passed :(
16:12:58 <jflory7> #info === decause Work with jzb to create the account for LimeSurvey (due: end of week) ===
16:13:14 <jflory7> Any news or updates here?
16:13:31 <decause> #action decause JFDI the LimeSurvey Account, cleared with jzb
16:13:40 <jflory7> decause++
16:13:41 <jflory7> #info === [INCOMPLETE] jflory7 Get back with c0mrad3 about what is needed to be updated, how to go about doing it, etc. (make the game plan) ===
16:13:47 <jflory7> #action jflory7 Get back with c0mrad3 about what is needed to be updated, how to go about doing it, etc. (make the game plan)
16:13:52 <jflory7> #info === [COMPLETE] decause review copy-edits with design team before EoW ===
16:14:00 <jflory7> #link https://fedorahosted.org/marketing-team/ticket/219#comment:15
16:14:06 <jflory7> #info === [INCOMPLETE] jflory7 / decause Check in with pravins and noriko for any closing items for Ticket #29 ===
16:14:12 <jflory7> #action jflory7 / decause Check in with pravins and noriko for any closing items for Ticket #29
16:14:16 <decause> jflory7++ thanks for parlaying those last week
16:14:19 <jflory7> #info === [INCOMPLETE] jflory7 / decause re-ping designlist with speak-up series proposal, ask for feedback ===
16:14:27 <jflory7> #action jflory7 / decause re-ping designlist with speak-up series proposal, ask for feedback
16:14:36 <decause> mizmo: ^
16:14:39 <jflory7> #info === decause Work on migrating the raw University Involvement Initiative notes from the Etherpad into a more parseable, digestible format (whether wiki or other format) ===
16:14:46 * linuxmodder back
16:14:48 <jflory7> Still in progress?
16:14:49 <decause> jflory7: action me that plz
16:14:53 <decause> yeah, in progress
16:15:00 * mizmo looks
16:15:02 <jflory7> #action decause Work on migrating the raw University Involvement Initiative notes from the Etherpad into a more parseable, digestible format (whether wiki or other format)
16:15:04 <decause> design team is blocking on that one too
16:15:10 <jflory7> #info === [COMPLETE] jflory7 Schedule "Call for Contributors: F24 Release Notes" for Wednesday @ 8:00 UTC ===
16:15:16 <jflory7> #link https://communityblog.fedoraproject.org/fedora-24-release-notes/
16:15:22 <jflory7> #info === [COMPLETE] jflory7 Review / edit "Document Freedom Day 2016: Singapore" for publication soon ===
16:15:28 <decause> woot
16:15:30 <decause> saw that today
16:15:31 <jflory7> #link https://communityblog.fedoraproject.org/document-freedom-day-2016-singapore/
16:15:39 <jflory7> GIANT_CRAB++
16:15:45 <decause> nice GIANT_CRAB
16:15:45 <jflory7> #info === [COMPLETE] jflory7 Finish all BrickHack 2016 write-ups, we're nearing a month since the event happened ===
16:15:50 <jflory7> #link https://communityblog.fedoraproject.org/brickhack-2016-event-report/
16:15:55 <decause> decause is guilty too
16:15:56 <jflory7> #info === [INCOMPLETE] jflory7 Begin writing and compiling project profiles of BrickHack 2016 participants (three replies so far, need to keep communication channels open) ===
16:15:57 <GIANT_CRAB> you know what's nicer? the brickhack one :P
16:16:06 <jflory7> #action jflory7 Begin writing and compiling project profiles of BrickHack 2016 participants (three replies so far, need to keep communication channels open)
16:16:17 <jflory7> #info === commops add the "link to the mailing list" into the signature on commops list ===
16:16:22 <jflory7> What was this one again?
16:16:47 <mizmo> jflory7: i dont see a post on design-team list re: speak-up series
16:16:51 <GIANT_CRAB> that means have a URL of the common ops mailing list as a signature attached to all emails
16:16:53 <decause> jflory7: in the mailman config, we can add the URL for the mailing list into message signatures so that when you're reading it in a client, it's easy to find the archives
16:16:55 <linuxmodder> the mailman  link in the sig
16:16:56 <decause> very useful
16:16:58 <linuxmodder> jflory7,  ^
16:16:59 <GIANT_CRAB> or something?
16:17:01 <jflory7> mizmo: I didn't post yet, hoping to get it today!
16:17:22 <jflory7> decause: I can take this one to Infra
16:17:26 <jflory7> Or do we have permissions for that?
16:17:28 <mizmo> oh okay cool
16:17:28 <decause> mizmo: sorry, pulled the trigger too soon :P
16:17:36 <decause> jflory7: we do it ourselves
16:17:37 * mizmo always happy to help
16:17:43 <decause> i think you're an admin too ?
16:17:43 <GIANT_CRAB> I think the owner/admins of common ops mailing list can edit it
16:17:45 <jflory7> decause: Hmm, I don't think I have permissions
16:17:48 <jflory7> I think I'm a moderator
16:17:52 <jflory7> Not an admin
16:17:57 <decause> #action decause up jflory7's privs on commops admin list
16:18:15 <jflory7> #action jflory7 Update CommOps mailing list signature once the permissions are set
16:18:20 <jflory7> #info === [INCOMPLETE] decause / jflory7 ping mktg list about alpha->beta release announcement research for May 3rd ===
16:18:25 <jflory7> #action decause / jflory7 ping mktg list about alpha->beta release announcement research for May 3rd
16:18:28 <linuxmodder> jflory7,   you wanna  tag team the  bitcamp post ?
16:18:31 <jflory7> #info === [INCOMPLETE] jflory7 Create a WhenIsGood for determining an ideal hack time for the future ===
16:18:37 <jflory7> #action jflory7 Create a WhenIsGood for determining an ideal hack time for the future
16:18:54 <jflory7> linuxmodder: cydrobolt was going to tackle that one as the event owner. He has some progress down but I need to pass him pictures.
16:19:08 <jflory7> linuxmodder: He was open to getting a little help too :)
16:19:17 <jflory7> Okay, this is all the previous action items from our last meeting
16:19:25 <jflory7> I didn't get nearly as much done as I wanted :(
16:19:33 <linuxmodder> #info spam  like it was cool there
16:19:33 <jflory7> Going to try to catch up this week
16:19:59 <decause> jflory7: tonight is not a good hacksesh time for me, but tomo is
16:20:05 <jflory7> I can swing tomorrow
16:20:09 <jflory7> Tonight wasn't good for me either
16:20:09 <jflory7> #topic Tickets
16:20:10 <decause> tomo I will def be hack sesshing
16:20:15 <jflory7> #link https://fedorahosted.org/fedora-commops/report/9
16:20:21 <jflory7> #info === Ticket #29 ===
16:20:28 <jflory7> #info "G11n - proposal for the group revitalization"
16:20:34 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/29
16:20:35 <linuxmodder> usual time tom   gents?
16:20:41 <jflory7> #info The I18n test day is happening today. Next step to close this ticket is a summary of the vFAD and what happened as an update to the community? It seems like a lot of good things happened during this event and it would be a good idea to update the community via the CommBlog about how it went and all progress that was achieved.
16:20:42 <decause> linuxmodder: likely, yeah
16:20:46 <jflory7> #link https://communityblog.fedoraproject.org/time-test-fedora-24-internationalization/
16:20:54 <jflory7> pravins: Ping, happen to be around still?
16:21:00 <linuxmodder> decause,  if im appearing dormant   ping me
16:21:02 <pravins> jflory7: yes :)
16:21:03 <GIANT_CRAB> Yeah, we need promote more i18 stuff
16:21:06 <jflory7> Could possible do a 2-for-1 right now for action items
16:21:07 <linuxmodder> for hack session
16:21:08 <jflory7> Awesome!
16:21:15 <decause> pravins pinged me last night about pushing something to hte commblog
16:21:41 <pravins> aha, right. We have not updated #29 ticket.
16:21:41 <jflory7> pravins: We were wanting to follow up with Ticket #29 and if anything was still needed for it on the G11n side of things. We also wanted to check in about the idea of a summary of the vFAD for the rest of the Fedora community.
16:22:02 <jflory7> decause: That was for the I18n test day, pravins pinged me to get it out last night but I dropped the ball on that one. :/ Someone else seems to have gotten it this morning.
16:22:21 <decause> nod nod
16:22:46 <decause> that is why we do things in lists, and proof our team against raptors
16:23:00 <decause> aka, single points of failure or bottlenecks of action
16:23:20 * jflory7 nods
16:23:23 <pravins> before some hours, i pitched idea for having article in magazine regarding gains from Translation vFAD.
16:23:41 <decause> pravins++
16:23:51 <pravins> As far as i think, this is biggest virtual translation sprint in Fedora with 50+ participants.
16:24:01 <jflory7> That's really awesome to hear. :)
16:24:03 <decause> pravins: :) :) :)
16:24:04 <GIANT_CRAB> pravins++
16:24:04 <zodbot> GIANT_CRAB: Karma for pravins changed to 11 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:24:19 <Dimuthu> pravins++
16:24:19 <zodbot> Dimuthu: Karma for pravins changed to 12 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:24:22 <jflory7> Y'know, I think a Magazine article would be a good idea, to update our community of users about the progress made about the translation status of Fedora
16:24:26 <decause> pravins: yeah, we def will run something in commblog if FM doesn't, or in addition-to if they do
16:24:45 <jflory7> Normally I would say CommBlog, but I think this is a good item for the Magazine, with a pointer article (like the stickers one) on the CommBlog.
16:24:47 <pravins> sure.
16:24:52 <decause> nod nod nod
16:24:57 <pravins> Just thinking presently, how can we make article more attractive :)
16:25:04 <decause> pravins: let us know how the pitch is received, we'll def keep up
16:25:27 <decause> pravins: have you awarded the events badges for it?
16:25:30 <jflory7> pravins: Magazine team will help with the content curation too. If you provide the content, we can help refine it and get it nice and pretty for the readers too. :)
16:25:36 <jflory7> I remember seeing the badges issued.
16:25:51 <pravins> decause: yes. Done done !!
16:25:53 <jflory7> I happened to look at badged.fp.o and saw the home page flooded with G11n vFAD badges issued :)
16:25:58 <decause> pravins: if you have, then we /could/ run the impact scripts
16:26:02 <pravins> #link https://badges.fedoraproject.org/badge/fedora-24-translation-sprint
16:26:05 <jflory7> decause: Ooh, for sure!
16:26:23 <jflory7> Very nice :)
16:26:31 <decause> lvoe it
16:26:33 <decause> love*
16:26:34 <decause> so
16:26:35 <jflory7> So... for this ticket, here's the proposal I think we can make:
16:26:39 <decause> what do we need to do for #29?
16:26:42 <linuxmodder> on the note of badges.fp jflory7   expect  PRs  on the  github  repo for ui
16:26:46 <decause> jflory7 is on it ;)
16:27:21 <linuxmodder> the asian kid that  came by  to talk android  came  late  sat to  chat about ui updates for badges
16:27:22 <jflory7> #proposed The vFAD was a success. Last action item for this ticket is a summary of the work done during the vFAD posted to the Fedora Magazine with a small pointer on the Community Blog. Once this is completed, the ticket can be closed.
16:27:24 <jflory7> Seem good?
16:27:33 <jflory7> +1
16:27:38 <pravins> +1
16:27:44 <GIANT_CRAB> +1
16:27:46 <decause> +1
16:27:47 <linuxmodder> +1
16:27:49 <GIANT_CRAB> jflory7++
16:27:50 <Dimuthu> +1
16:27:53 <pravins> On future note, we have to make it even bigger for Fedora 25.
16:28:11 <jflory7> pravins: I think now, the pathway is being paved to make it easier for this going forward :)
16:28:12 <jflory7> #agreed The vFAD was a success. Last action item for this ticket is a summary of the work done during the vFAD posted to the Fedora Magazine with a small pointer on the Community Blog. Once this is completed, the ticket can be closed.
16:28:16 <pravins> And that time, i definitely need more help from you all, specifically from rewards side.
16:28:17 <linuxmodder> that 6 +1s  i think we agree :)
16:28:18 <decause> pravins: this was just the first, we'll continue building this as a regular release schedule'd item
16:28:34 <decause> nice work making the first one a big success
16:28:36 <jflory7> pravins: Send along our congrats and thanks to the rest of the G11n team, you guys really kicked butt with this vFAD!
16:28:57 <jflory7> Okay, moving along to the next ticket:
16:28:58 <jflory7> #info === Ticket #34 ===
16:29:04 <jflory7> #info "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
16:29:05 <decause> pravins: this is a *great* example of new ways to do FADs that help us have widespread impact while stretching budget
16:29:09 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/34
16:29:14 <jflory7> Last meeting, we left off hoping to follow up with the Design and Badges sysadmins about if the badge proposals we made were feasible. We still need to do some follow-up. Outside of following up on existing requests, is there any other work to add on here?
16:29:36 <jflory7> This is mostly going to be my previous action item to follow up on the Design Team list with requests for feedback
16:29:45 <decause> jflory7: we're going to be doing a badges hacksesh soon, but ya, we just need to keep pluggin on the action items.
16:29:48 <jflory7> Is there anything else beyond this, though?
16:30:09 <jflory7> Right now, I think this week may just be a catch-up week on some of these other tickets
16:30:21 <decause> jflory7: agreed, I'm not ready fo ra badges hacksesh yet
16:30:54 <jflory7> Unless anyone objects, I say we just follow up on the previous action item to get feedback from Design Team list for the recent badge proposals. Then, once we have the feedback, we can go from there.
16:30:59 <decause> jflory7: perhaps we can just make "badges" a piece of our commops meeting, or start holding a "badges" meeting specifically... that is going to be a huge part of our work once we're past some of the budget things
16:31:03 <decause> we = decause
16:31:03 <decause> :P
16:31:12 <GIANT_CRAB> would be good to have badges for folks who write on commops, right? :P
16:31:18 <jflory7> Was pretty much about to suggest the same
16:31:24 <c0mrad3> decause+1 :P
16:31:28 <jflory7> I actually like the idea of a scheduled badges meeting
16:31:36 <GIANT_CRAB> decause+1
16:31:42 <jflory7> Doesn't even have to be a full hour, could be a 30 minute slot in the week
16:31:49 <trishnag> GIANT_CRAB, +1
16:32:04 <decause> jflory7: we'll do a whenisgood, starting with design team
16:32:05 <jflory7> GIANT_CRAB: Yes, absolutely! I think Bee submitted a ticket for that, actually
16:32:27 <jflory7> #action jflory7 Create a WhenIsGood poll for a badges hack session to share with CommOps and Design team
16:32:42 <decause> we've got enough badges requests and biz in the mix to wrangle on a weekly basis if we're going to make it through
16:32:49 <jflory7> So, finally proposal for this ticket:
16:32:55 <decause> there will also be an upcoming regular "onboarding" meeting too
16:33:09 <decause> where we check in with GSoC/Outreachy/RHT Interns
16:33:19 <decause> after they're hired, sometime in May
16:33:24 <c0mrad3> so commops will have 3 sub meetings :P
16:33:25 <decause> that is much later though ;)
16:33:42 <GIANT_CRAB> so much meetings
16:33:43 <GIANT_CRAB> wow
16:33:44 <jflory7> #proposed There are still incomplete action items for this ticket with following up on the badge proposals we made last week. We will follow up with the Design Team list for feedback. We also want to schedule a regular Badges hack session meeting where we can do design time on badges and work on strategy for them too.
16:33:46 <jflory7> +1
16:34:08 <decause> GIANT_CRAB: our meetings are all ticket driven, which means making sure that tickets are being opened AND closed
16:34:14 <decause> "doing meetings"
16:34:23 * decause waves to bee2502_
16:34:26 <bee2502_> .hello bee2502
16:34:29 <zodbot> bee2502_: bee2502 'Bhagyashree Padalkar' <bhagyashree.iitg@gmail.com>
16:34:30 <jflory7> #chair bee2502_
16:34:30 <zodbot> Current chairs: Dimuthu GIANT_CRAB bee2502_ c0mrad3 danofsatx decause elioqoshi jflory7 trishnag
16:34:32 <jflory7> Hey Bee!
16:34:48 <bee2502_> Hi !
16:34:57 <decause> jflory7: +1
16:35:15 <decause> jflory7: the proper meetbot sytax for that is actually "#idea" btw
16:35:22 <decause> just learned it, it will make fedmsgs ;)
16:35:54 <decause> also, timcheck, we're just past half-way
16:35:54 <jflory7> I kind of use #proposed as an arbitrary tag so we only log the final result in the minutes :)
16:36:00 <jflory7> Whoa, time flies!
16:36:00 <decause> jflory7: nod nod nod
16:36:13 <jflory7> Okay, any other votes on the above proposal for this ticket?
16:36:19 * jflory7 will repeat it really fast too
16:36:28 <linuxmodder> timecheck : halfway
16:36:29 <justharshal> +1
16:36:31 <jflory7> #proposed There are still incomplete action items for this ticket with following up on the badge proposals we made last week. We will follow up with the Design Team list for feedback and previous action items. We also want to schedule a regular Badges hack session meeting where we can do design time on badges and work on strategy for them too.
16:36:36 <decause> +1
16:36:38 <jflory7> +1
16:36:39 <justharshal> +1
16:36:43 <Dimuthu> +1
16:36:53 <c0mrad3> +1
16:36:54 <linuxmodder> +1
16:37:07 <jflory7> #agreed There are still incomplete action items for this ticket with following up on the badge proposals we made last week. We will follow up with the Design Team list for feedback and previous action items. We also want to schedule a regular Badges hack session meeting where we can do design time on badges and work on strategy for them too.
16:37:07 <linuxmodder> especially if we can  tag team the hack sessions
16:37:17 <jflory7> #info === Ticket #49 ===
16:37:21 <jflory7> #info "[Onboarding Series] Infrastructure"
16:37:27 <trishnag> jflory7++
16:37:35 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/49
16:37:40 <jflory7> We left off last meeting wanting to follow up on existing requests for Pagure-related badges. The technical specifications for the Pagure badges have all been +1'd.
16:37:56 <jflory7> I'm inclined to say we "merge" this week's work for this ticket with the previous action item / agreement
16:38:04 <jflory7> I think we've mainly just got follow-up to do on these right now
16:38:12 <decause> jflory7: nod nod nod
16:38:14 <decause> +1
16:38:27 <jflory7> +1 to using same agreement for this one too :P
16:38:54 <jflory7> #agreed There are still incomplete action items for this ticket with following up on the Pagure badge proposals. We will follow up with the Design Team list for feedback and previous action items.
16:39:01 <linuxmodder> +1 for a merge
16:39:08 <jflory7> #info === Ticket #68 ===
16:39:09 <jflory7> #info "Reconstructing the Campus Ambassadors program and campus outreach"
16:39:14 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/68
16:39:16 <decause> this is blocking on decause :(
16:39:18 <jflory7> Last meeting, we made an open call for university students, professors, faculty, and more to add themselves to the wiki page. decause was also going to work on migrating the raw notes from the Etherpad into the wiki. Is there any more planning or work we need to do here other than following up on previously determined actions? Do we want to post to the Ambassadors list yet?
16:39:36 <jflory7> decause: Anything we can do to distribute some work off from your plate?
16:39:40 * decause really needs to just post the raw dump somewhere as a start
16:39:55 <linuxmodder> etherpad ?
16:39:56 <decause> jflory7: yeah, lemme post what I got
16:40:12 <decause> #link http://etherpad.osuosl.org/fedora-EDU-refresh
16:41:12 <decause> objectives go back onto top prio slot after budget and gsoc are resolved
16:41:16 <c0mrad3> decause: we thought of deciding this thing at a FAD as I remember
16:41:36 <decause> c0mrad3: this is some new info, I haven't spread it far and wide yet, wanted to polish it more
16:41:50 <decause> I mentioned it during the council objectives meeting a couple of weeks ago
16:41:58 <decause> but had not polished
16:42:20 <decause> within these notes is mostly year 1 of a 3 year strategy
16:42:40 <decause> it's a bit longer looking than the simple 18 months of an objective
16:42:45 <decause> "simple"
16:42:47 <decause> :P
16:42:55 <decause> it needs polish, and explanation though
16:42:59 <decause> this is mostly an outline
16:43:13 <decause> tl;dr - We are going to hold an EDU FAD to develop materials
16:43:49 <c0mrad3> acknowledged
16:43:50 <decause> for ambassadors, and for some Super-set of an Ambassador-like group that gets specialized training on how to engage at EDUs
16:44:20 <jflory7> This sounds like a good item for a hackathon
16:44:25 <jflory7> s/hackathon/hack session
16:44:45 <decause> jflory7: this could be part of a Flock Workshop if I can't get the FAD onto the books before August
16:45:03 <jflory7> *That* would be cool too
16:45:06 <decause> we're going to have an actual FAD, but will try to keep the budget under, say, $500
16:45:14 * jflory7 nods
16:45:27 <decause> I know the budget right now, I can imagine how to make as much happen as possible
16:45:48 <decause> I mean, I know the combinations of 5 scenarios that play out for the budget, depending on which way we go
16:45:59 <decause> FADs are a bigger piece this year already than they ahve been in the past 3
16:46:15 <decause> and if we want to run more of them, I want to keep us well under the max funding
16:46:21 <decause> we've already got 3 before July
16:46:29 <decause> ok, 75% timecheck
16:46:32 <decause> should move on
16:46:46 <decause> #action decause post the etherpad link to the design-team ticket
16:46:55 <decause> #undo
16:46:55 <zodbot> Removing item from minutes: ACTION by decause at 16:46:46 : decause post the etherpad link to the design-team ticket
16:46:57 <c0mrad3> jflory7: next please
16:47:16 <decause> #action decause post the etherpad link to the design-team ticket, and update the University_Involvment Objective page
16:47:17 <jflory7> decause: We can follow up on this one at the next hack session and next week's meeting
16:47:30 <jflory7> This action item sounds good to me.
16:47:37 <jflory7> #topic Wiki Gardening
16:47:47 <jflory7> #nick NewMembers
16:47:48 <jflory7> #action NewMembers Add your timezone / interests on CommOps Wiki [ https://fedoraproject.org/wiki/CommOps ]
16:48:00 <jflory7> Any other wiki gardening to add in here?
16:48:14 * nils is missing his ticket, #69
16:48:20 <decause> jflory7: yes, we just need to give the modularization page a good hard look too
16:48:26 <jflory7> Oops, let's go back, didn't catch it.
16:48:28 <decause> nils: link to wiki page plz?
16:48:42 <nils> I filed it a quarter hoiur before the meeting, so it's my fault I think ;)
16:48:47 <nils> sec
16:48:48 <decause> nils: :)
16:49:03 <jflory7> nils: Oh!
16:49:06 <jflory7> This is an easy task for me
16:49:09 <jflory7> Will get this after the meeting
16:49:19 <decause> nils: link to ticket plz
16:49:30 <GIANT_CRAB> jjust applied for common ops
16:49:31 <jflory7> Wait, err, 69, not 61
16:49:39 <nils> https://fedorahosted.org/fedora-commops/ticket/69
16:49:47 <jflory7> #topic Tickets (con.)
16:49:51 <nils> the wiki pages are all linked in the ticket
16:49:53 <jflory7> #info === Ticket #69 ===
16:49:56 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/69
16:50:03 <jflory7> #info "Fedora Modularity onboarding"
16:50:08 * jflory7 reads
16:50:15 <decause> jflory7: it's a good one
16:50:39 <nils> I hope I can answer immediate questions, but I'm a noob in the m12n team myself...
16:50:51 <decause> I like that name
16:50:56 <decause> m12n++
16:51:00 <nils> haha
16:51:05 <jflory7> nils: This is an awesome ticket
16:51:18 <decause> jflory7: what we call "bread and butter" commops ticket
16:51:20 <nils> we're still not sure if it's "modularization" or "modularity" and kind of flip-flop between the two :o)
16:51:20 <jflory7> And this is definitely the kind of thing CommOps can and will help with :)
16:51:29 <nils> thanks!
16:51:31 <jflory7> decause++
16:51:37 <nils> yeah
16:51:40 <nils> decause++
16:51:40 <zodbot> nils: Karma for decause changed to 38 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:51:47 <decause> I like modularity (it's shorter, and reminiscent of 'singularity' ;P )
16:51:51 <jflory7> nils++ Thanks for filing this!
16:51:51 <zodbot> jflory7: Karma for nphilipp changed to 3 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:51:58 <jflory7> decause: Do we want to build this into our hack session tomorrow night?
16:52:07 <nils> jflory7: your welcome, and it's my jahb :)
16:52:28 <decause> jflory7: yeah, but this is also a *great* ticket for a newcomer to help tackle also, hopefully at the hacksesion maybe?
16:52:35 <jflory7> decause: I'm +1.
16:52:37 <decause> +1
16:52:43 <c0mrad3> nils++
16:52:45 <zodbot> c0mrad3: Karma for nphilipp changed to 4 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:52:50 <jflory7> Here, quick proposal for this one:
16:52:54 <c0mrad3> for the ticket :)
16:53:00 <nils> most of the work on the ticket was done by others, I suspect decause
16:53:09 <nils> I've just put in some tweaks and filed
16:53:15 <decause> #action commops join #fedora-modularization channel on freenode and help new contribs find their way around :)
16:53:32 <Dimuthu> decause++
16:53:37 <decause> 0:-)
16:53:45 <nils> do you have like an army of people watching channels or how does this work?
16:53:51 <decause> nils: we're working on it ;)
16:53:55 <jflory7> #proposed We will revisit this ticket fully tomorrow at the planned hack session. This is a great opportunity for a new member to get involved and help have an impact directly on the project. We need to to help brainstorm and create the welcome kit for modularization.
16:53:56 <jflory7> +1
16:54:04 <nils> awesome
16:54:05 <decause> +1
16:54:09 <nils> jflory7++
16:54:09 <zodbot> nils: Karma for jflory7 changed to 49 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:54:13 <c0mrad3> +1
16:54:17 <Dimuthu> +1
16:54:20 <GIANT_CRAB> +1
16:54:41 * jflory7 swings the gavel of agreement
16:54:41 <jflory7> #agreed We will revisit this ticket fully tomorrow at the planned hack session. This is a great opportunity for a new member to get involved and help have an impact directly on the project. We need to to help brainstorm and create the welcome kit for modularization.
16:54:50 <jflory7> Okay, five minutes left in the meeting...
16:54:56 <jflory7> Let's do a CommBlog blast!
16:55:01 <jflory7> #topic Community Blog
16:55:05 <nils> thanks folks
16:55:14 <jflory7> nils: Thank you for stopping by!
16:55:32 <jflory7> Okay, so as always, quick reminder: this section of the meeting is a lot of info all at once with some discussion at the end.
16:55:37 <jflory7> We have a lot new posts this week!!
16:55:38 <decause> nils: def hang out here if you're new, we're here to help
16:55:42 <jflory7> So hold on tight, here we go!
16:55:45 <jflory7> #info === This Week in CommBlog ===
16:55:51 <jflory7> #info (1) "Call for Nominations: Fedora Server Working Group"
16:55:55 <nils> decause: not new with Fedora, just m12n ;)
16:55:56 <jflory7> #link https://communityblog.fedoraproject.org/nominations-fedora-server-working-group/
16:56:01 <decause> nils++
16:56:02 <jflory7> #info Total Views (Apr. 6 - Apr. 12): 54
16:56:07 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1349
16:56:14 <jflory7> #info (2) "Call for Contributors: Fedora 24 Release Notes"
16:56:19 <jflory7> #link https://communityblog.fedoraproject.org/fedora-24-release-notes/
16:56:25 <jflory7> #info Total Views (Apr. 7 - Apr. 12): 164
16:56:30 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1335
16:56:38 <jflory7> #info (3) "Fedora and Mozilla Activity Days in Prishtina, Kosovo"
16:56:42 <jflory7> #link https://communityblog.fedoraproject.org/fedora-mozilla-activity-days-in-prishtina-kosovo/
16:56:47 <jflory7> #info Total Views (Apr. 8 - Apr. 12): 26
16:56:52 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1313
16:56:58 <jflory7> #info (4) "Fedora Stickers Sale: UnixStickers.com!"
16:57:02 <jflory7> #link https://communityblog.fedoraproject.org/fedora-stickers-sale/
16:57:07 <jflory7> #info Total Views (Apr. 8 - Apr. 12): 25
16:57:12 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1394
16:57:18 <jflory7> #info (5) "Document Freedom Day 2016: Singapore"
16:57:23 <jflory7> #link https://communityblog.fedoraproject.org/document-freedom-day-2016-singapore/
16:57:33 <jflory7> #info Total Views (Apr. 11 - Apr. 12): 8
16:57:34 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1320
16:57:37 <GIANT_CRAB> fml
16:57:37 <jflory7> Social media exposure?
16:57:52 <jflory7> GIANT_CRAB: I don't think we got this on social media, let's follow up in a bit
16:57:53 <jflory7> #info (6) "Fedora 24 Wallpapers: Vote now!"
16:57:56 <decause> GIANT_CRAB: we just posted it, but yeah
16:57:58 <jflory7> #link https://communityblog.fedoraproject.org/fedora-24-wallpapers-vote-now/
16:58:03 <jflory7> #info Total Views (Apr. 11 - Apr. 12): 623
16:58:07 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1369
16:58:08 <decause> nice!
16:58:13 <jflory7> #info (7) "BrickHack 2016 and Fedora: Event Report"
16:58:18 <justharshal> Significantly more
16:58:20 <jflory7> #link https://communityblog.fedoraproject.org/brickhack-2016-event-report/
16:58:24 <jflory7> #info Total Views (Apr. 12): 7
16:58:30 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1143
16:58:36 <jflory7> #info (8) "Time to test Fedora 24 internationalization"
16:58:41 <jflory7> #link https://communityblog.fedoraproject.org/time-test-fedora-24-internationalization/
16:58:46 <jflory7> #info Total Views (Apr. 12): 128
16:58:50 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1405
16:58:57 <jflory7> #info === Coming Up in CommBlog ===
16:59:01 <jflory7> #info (1) "DevConfCZ 2016: Event Report"
16:59:05 <jflory7> #link https://communityblog.fedoraproject.org/?p=1027&preview=1&_ppp=6b95d2c034
16:59:15 <jflory7> Okay, that's everything. A little commentary from my perspective:
16:59:34 <GIANT_CRAB> oh my goodness
17:00:01 <jflory7> We definitely had a *LOT* of content that went out this past week, which was awesome! But I'm a little bit afraid this was a little too much for our level of publishing, because we dropped eight things in the past week and have one article as a draft right now.
17:00:05 <c0mrad3> busy week for community blog :)
17:00:13 <jflory7> So, for future reference, I think we should avoid stacking up things like this when we can.
17:00:24 <jflory7> This will help make sure everything gets its time out on the front page and gets decent exposure
17:00:32 <GIANT_CRAB> ye
17:00:34 <decause> jflory7: yeah, but many of them were time sensitive, which can't be avoided
17:00:37 <jflory7> Right
17:00:45 <jflory7> So we have to anticipate having some of those things come in too
17:00:54 <decause> jflory7: we also just need to make sure we're auto-sending to social-media list
17:01:11 <jflory7> decause: Would be cool if we could auto-post new posts from the CommBlog to the social-media list
17:01:13 <decause> we got clearance for commblog to get posted to @fedora twitter channel, so we should hook that up
17:01:15 <jflory7> I know WP can do that too
17:01:19 <decause> jflory7: jinx!
17:01:23 <decause> wow
17:01:32 <jflory7> decause: Hmmm... what do you mean with @fedora and CommBlog posting?
17:01:36 <jflory7> Like auto-posting?
17:01:52 <decause> it's not 'auto' posting in that every single one goes there
17:01:57 <decause> you set it up on a per-post basis
17:01:59 <jflory7> Setting it up with Jetpack?
17:02:01 <jflory7> Peeeeerfect
17:02:05 <jflory7> That would be awesome.
17:02:16 <jflory7> I'm like 50% on the Jetpack integration for some reasons, though
17:02:20 <decause> I saw a checkbox for it
17:02:23 <jflory7> It's not good for posting to multiple platforms
17:02:30 <jflory7> e.g. Facebook + Google+ and then Twitter
17:02:39 <jflory7> Being that you can't use some things on some platforms and others
17:02:46 <decause> yeah, we should just subscribe social-media@ to the rss feed of commblog ;)
17:02:48 <jflory7> e.g. 140 chars on Twitter versus more space on FB / G+
17:02:50 <linuxmodder> cross-posting like my  blog posts do
17:02:50 <jflory7> Definitely
17:02:57 <c0mrad3> Jetpack works fine jflory7
17:03:00 <jflory7> I think we should follow up on this later.
17:03:16 <decause> #action decause / jflory7 explore how to subscribe social-media@ to the rss feed of commblog ;)
17:03:19 <jflory7> c0mrad3: It does work, but I think it would be better to do different messages for each platform as compared to the same message on all the platforms.
17:03:33 <jflory7> There's different strategies for each platform. :)
17:03:36 <linuxmodder> jflory7,  jetpack isnt  but the  default  share feature is
17:03:37 <jflory7> Anywho...
17:03:45 <jflory7> We're a little bit late in the meeting, anything else for CommBlog?
17:03:46 <c0mrad3> time check 5 min past our time
17:04:10 <jflory7> decause: Did we want to hit Release Schedule this meeting, or do you feel like we've got enough on the CommOps plate right now?
17:04:22 * jflory7 wasn't sure if we had new things to add here or if we should jump to Open Floor
17:04:32 * jflory7 also didn't add anything to the agenda like he wanted to
17:04:36 <linuxmodder> jflory7,  I'd say  channel and  hacksession for REL sched
17:04:52 <jflory7> Yeah, do want to get hack session planned and on the calendar for tomorrow
17:04:57 <jflory7> Will do at open floor
17:04:58 <c0mrad3> jflory7: if we want to do it different for each platform we need to do it manually
17:05:22 <jflory7> c0mrad3: Right - so I think auto-posting for some platforms is fine, but then we will still have to follow up with people that have the special powahs! ;)
17:05:54 <decause> yeah, dump the sched for release
17:05:58 <decause> just as an FYI
17:06:00 <decause> here
17:06:03 <decause> dump = post :P
17:06:07 <GIANT_CRAB> Hmmm
17:06:10 <jflory7> #topic Release Scheduling
17:06:18 <GIANT_CRAB> we have a common ops ticketing system?
17:06:31 <decause> GIANT_CRAB: we use fedorahosted, yeah
17:06:37 * jflory7 is digging for the special link
17:06:46 <jflory7> #link https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
17:07:07 <jflory7> #info Next CommOps release milestone is May 3rd for Beta Release
17:07:12 <GIANT_CRAB> Decause Hmmm, I'll post up the upcoming story-telling posts stuff (for events) I guess.
17:07:15 <jflory7> We already have an action item to follow up with mktg list.
17:07:17 <GIANT_CRAB> great
17:07:27 <GIANT_CRAB> Talking points?
17:07:44 * jflory7 is about to have to run - let's plan the hack session really fast so we can get it on the map
17:07:47 <jflory7> #topic Open Floor
17:07:55 <jflory7> GIANT_CRAB: Getting the talking points in for this is huge!
17:07:55 <decause> nod nod
17:07:58 <decause> jflory7++
17:07:58 <danofsatx> btw, it's CommOps, Community Operations. Not Common ops....we're pretty uncommon around these parts.
17:08:07 <decause> GIANT_CRAB: it's true, talking points is huge
17:08:11 <decause> :P
17:08:19 <jflory7> Okay, so tomorrow, what times are good?
17:08:23 * jflory7 checks his own calendar
17:08:39 <c0mrad3> what about the release notes that we took into commops
17:08:43 <decause> usual, 6-9pm (22:00-01:00UTC)
17:08:47 <jflory7> Could do right after the Marketing meeting tomorrow
17:08:49 <jflory7> decause: +1
17:08:59 <jflory7> If that sounds good, let's just put it on the map
17:09:05 <decause> nod nod nod
17:09:07 <jflory7> I wanted to do the poll to find a good time for others to jump in
17:09:11 <jflory7> Didn't get to it this past week
17:09:16 <jflory7> Will get this week for sure
17:09:16 <decause> jflory7: I'll be on campus a lil bit on Friday too, FYI
17:09:26 <jflory7> decause: Oh yeaaaaaaah, forgot about the 40th!
17:09:31 <jflory7> Keep me in the loop on the details :)
17:09:33 <decause> #info decause is travelling to ROC this weekend again
17:09:51 <decause> jflory7: we can do a possible hack session there too ;)
17:09:54 <jflory7> #agreed Hack session on Wednesday, 2016-04-13: 22:00 UTC - 1:00 UTC
17:09:59 <jflory7> decause: For sure.
17:10:12 <decause> ok
17:10:14 <jflory7> #action jflory7 Put the hack session on the calendar TONIGHT
17:10:15 <jflory7> :P
17:10:17 <decause> we're at 10 over
17:10:19 <jflory7> Okay, anything else for open floor?
17:10:21 <decause> anyone have other open biz?
17:10:23 <jflory7> I'm seconds from bouncing out.
17:10:26 <decause> kk
17:10:30 * decause is chaired, can end it
17:10:33 <c0mrad3> ! Release notes
17:10:43 * decause has parting thoughts too
17:10:46 <decause> c0mrad3: release notes?
17:10:49 <jflory7> decause: Okay, cool, going to begin packing up but will idle a bit longer
17:10:54 * jflory7 brbs
17:10:56 <c0mrad3> are we working on it ?
17:11:16 <decause> Beta Release notes? yeah, I think GIANT_CRAB is going to follow up with marketing team about hitting the list IIRC
17:11:32 <decause> GIANT_CRAB: is this true? if so, maybe assign an action item for it?
17:11:55 * GIANT_CRAB is confused
17:12:16 <GIANT_CRAB> is this about the "getting people excited about F24 release"?
17:12:17 <c0mrad3> #action GIANT_CRAB will follow up with marketing team about Beta Release Notes
17:12:28 <c0mrad3> #undo
17:12:28 <zodbot> Removing item from minutes: ACTION by c0mrad3 at 17:12:17 : GIANT_CRAB will follow up with marketing team about Beta Release Notes
17:12:36 <decause> ok, I'm confused now too :P
17:13:07 <GIANT_CRAB> "Article Idea: What do you look forward in F24?"
17:13:11 <c0mrad3> strong points about fedora 24
17:13:14 <GIANT_CRAB> okay, uh
17:13:25 <justharshal> GIANT_CRAB: +1
17:13:55 <GIANT_CRAB> I suggested that one on common ops last week and then followed that up with marketing
17:14:15 <GIANT_CRAB> but not sure what do you mean by beta release notes?
17:14:22 <decause> interesting, ok
17:14:41 <linuxmodder> timecheck +14 mins
17:14:48 <jflory7> I'm closing out now. If someone can get the meeting minutes for me, that would be awesome! See you all soon, all!
17:14:50 * jflory7 disconnects
17:14:50 <decause> GIANT_CRAB: we do the big "release notes" for what has happened in Fedora in each release
17:15:07 <decause> GIANT_CRAB: check for the alpha notes in the commblog
17:15:12 <GIANT_CRAB> sec
17:15:18 <decause> the beta will be similiar with more details
17:15:21 <linuxmodder> GIANT_CRAB,  each release even the beta has a need for  notes on  what's new , what's buggy  etc
17:15:29 <decause> the Final release notes are what go out when we ship a new release
17:15:45 <decause> it is a *big* deal in Fedora, usually our highest days of social media traffic
17:15:52 <decause> we help write those now, with the marketing team
17:16:02 <decause> GIANT_CRAB: release notes is a specific task commops helps with
17:16:08 <GIANT_CRAB> https://communityblog.fedoraproject.org/fedora-24-release-notes/
17:16:24 <decause> yes
17:16:33 <decause> we need to make the next version for beta, and then final
17:16:39 <decause> but we're wayyyy over
17:16:44 <decause> talk in #fedora-commops if you have more questions
17:16:45 <linuxmodder> I help with the  pre-release ones then  hold on tight when I join the release day  mirror  madness
17:17:03 <decause> any other open biz?
17:17:05 <decause> going once
17:17:06 <decause> going twice
17:17:07 <decause> going thrice
17:17:17 <decause> #topic Closing Thoughts
17:17:27 <linuxmodder> to the channel ..........?
17:17:45 <decause> the m12n request coming in is an excellent example of our message making it through the project
17:17:56 <decause> the types of support and contributions that our team can help with
17:18:13 <decause> the budget is what is going to consume the next week, almost 2 weeks for me personally
17:18:22 <decause> so I'm going to be pre-occupied a bit
17:18:30 <decause> if folks need more from me, keep pinging
17:18:47 <decause> once we get through GSoC and Budget, I'll be more available for closing loops
17:18:54 <decause> if folks need me, ping me more
17:19:03 <decause> otherwise, I"m very happy with the way everyone is supporting eachother
17:19:15 <decause> let's keep making commops a great place to work together :)
17:19:21 <decause> thanks all for your work
17:19:35 <decause> and see you at the hacksesh I hope tomo night, 22:00UTC
17:19:42 <decause> Thanks everyone for being here
17:19:45 <decause> thanks jflory7 for chairing
17:19:50 <decause> #endmeeting