15:58:53 <jflory7> #startmeeting Fedora CommOps (2016-06-14)
15:58:53 <zodbot> Meeting started Tue Jun 14 15:58:53 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:58:53 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:58:53 <zodbot> The meeting name has been set to 'fedora_commops_(2016-06-14)'
15:58:59 <jflory7> #meetingname commops
15:59:00 <zodbot> The meeting name has been set to 'commops'
15:59:05 <jflory7> #nick commops
15:59:10 <jflory7> #topic Agenda
15:59:15 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-06-14
15:59:19 <jflory7> #info (1) Roll Call / Q&A
15:59:32 <jflory7> #info (2) Announcements
15:59:38 <jflory7> #info (3) Action items from last meeting
15:59:43 <jflory7> #info (4) Tickets
15:59:48 <jflory7> #info (5) Wiki Gardening
15:59:53 <jflory7> #info (6) Community Blog
15:59:59 <jflory7> #info (7) Release Schedule
16:00:00 <linuxmodder> .fas linuxmodder
16:00:00 <zodbot> linuxmodder: linuxmodder 'Corey W Sheldon' <sheldon.corey@openmailbox.org>
16:00:02 * danofsatx isn't here today. Family activities take precedence.
16:00:04 <jflory7> #info (8) Open Floor
16:00:17 <jflory7> #topic Roll Call / Q&A
16:00:21 <skamath> .hellomynameis skamath
16:00:22 <jflory7> #info Name; Timezone; Sub-projects/Interest Areas
16:00:22 <zodbot> skamath: skamath 'Sachin S Kamath ' <sskamath96@gmail.com>
16:00:24 <decause> .hello decause
16:00:25 <jflory7> If this is your first time at a CommOps meeting, feel free to introduce yourself to everyone and say hello! If anyone has any questions before we get started with the rest of the agenda, now is also a good time to ask.
16:00:25 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
16:00:31 <skamath> jflory7: o/
16:00:36 <c0mrad3> .hello dhanvi
16:00:36 <jflory7> danofsatx: Acknowledged, enjoy your time with family :)
16:00:37 * linuxmodder is semi here multi tasking including an HR call myself  soon
16:00:37 <decause> #info decause; UTC-4; CommOps, GSoC, Budget, Council, *
16:00:37 <zodbot> c0mrad3: dhanvi 'Tummala Dhanvi' <dhanvicse@gmail.com>
16:00:39 <danofsatx> Employment activites, also. Things are looking up, I should be getting a second (third?) inteview request from Red Hat this week ;)
16:00:52 <jflory7> #chair linuxmodder skamath c0mrad3 decause
16:00:52 <zodbot> Current chairs: c0mrad3 decause jflory7 linuxmodder skamath
16:00:58 <jflory7> danofsatx: Best of luck with the interviews!!
16:01:32 <c0mrad3> #info Tummala Dhanvi (c0mrad3); UTC+5:30; CommOps, Security, Docs, GSoC, *
16:01:33 <jflory7> #info Justin W. Flory; UTC-4; CommOps, Marketing / Magazine, Ambassadors, Infrastructure-fi, Join, Diversity, etc.
16:01:42 <linuxmodder> #info Corey Sheldon (linuxmodder) utc -4 / GPG D2264944 /  Ambassadors, join,security,docs,commops,diversity,mktg,GSoC
16:02:09 <skamath> #info Sachin S. Kamath; UTC +5.30; CommOps, GSoC, Metrics, Badges etc
16:02:37 <jflory7> We'll wait a few more minutes for some others to show up :)
16:03:31 <linuxmodder> skamath,  about the vps convo in -commops  let  danofsatx / sahilsho (in #ovaha)  know if you have any issues
16:03:43 <skamath> linuxmodder: Sure, thanks :)
16:03:53 <linuxmodder> aren't you also a fellow  mozillian tho?
16:04:05 <skamath> linuxmodder: No, c0mrad3is.
16:04:09 <linuxmodder> ah
16:04:21 <sayan> .hello sayanchowdhury
16:04:22 <zodbot> sayan: sayanchowdhury 'Sayan Chowdhury' <sayan.chowdhury2012@gmail.com>
16:04:28 <skamath> sayan: o/
16:05:02 <sayan> #info Sayan Chowdhury;UTC+5:30; Infrastructure, Cloud, CommOps, Marketing, Ambassadors etc.
16:05:16 <jflory7> #chair sayan
16:05:16 <zodbot> Current chairs: c0mrad3 decause jflory7 linuxmodder sayan skamath
16:05:18 <jflory7> Hi sayan!
16:05:23 <sayan> skamath: hey
16:05:29 <sayan> jflory7: Hi :)
16:05:40 <GIANT_CRAB> hi
16:05:42 <GIANT_CRAB> testing
16:05:57 <skamath> GIANT_CRAB: Test pass :)
16:06:09 <c0mrad3> GIANT_CRAB: working fine :)
16:06:16 <GIANT_CRAB> #info Huiren Woo; UTC+0800; Ambassador, CommonOps, Marketing
16:06:17 * c0mrad3 waves to linuxmodder
16:06:20 <nb> .hello nb
16:06:21 <zodbot> nb: nb 'Nick Bebout' <nb@nb.zone>
16:06:23 <linuxmodder> c0mrad3,  mornign
16:06:38 <jflory7> GIANT_CRAB: Hey Huiren, glad you could make it out!
16:06:40 <linuxmodder> how was the talk besides full nb
16:06:44 <jflory7> Hiya nb!
16:06:47 <c0mrad3> well linuxmodder it night 9 for me :)
16:06:47 <jflory7> #chair GIANT_CRAB nb
16:06:47 <zodbot> Current chairs: GIANT_CRAB c0mrad3 decause jflory7 linuxmodder nb sayan skamath
16:07:00 <skamath> Hah, timezones :p
16:07:06 <linuxmodder> its morning somewhere ALL day  :)
16:07:15 <jflory7> Alrighty.
16:07:16 <GIANT_CRAB> hello jflory7! good to see you
16:07:20 <jflory7> Let's go ahead and get started!
16:07:27 <jflory7> #topic Announcements
16:07:33 <jflory7> #info === Last week: Fedora 24 no-go, delayed to June 21 ===
16:07:39 <jflory7> #link https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/CCPEFDBYMHBNLTNG2CC57KUBBQOO67RD/
16:07:44 <jflory7> #info Due to a remaining blocker bug in F24, the release has been delayed by one week to June 21st, 2016. If all goes well, we should be back again here next week with a new Fedora release on our hands.
16:07:49 <jflory7> #info === Events coming soon: Red Hat Summit, Flock ===
16:07:53 <jflory7> #link https://www.redhat.com/en/summit
16:07:58 <jflory7> #link https://flocktofedora.org/
16:08:03 <jflory7> #info Two upcoming events on the Fedora calendar are Red Hat Summit (June 27-29) and Flock, Fedora's annual contributor conference (August 2-5).
16:08:09 <jflory7> #info === "Fedora Council Meeting 2016-06-13: Report on CommOps " ===
16:08:15 <jflory7> #link https://youtu.be/AQWybn1QVKc
16:08:22 <jflory7> #info Yesterday at the Fedora Council meeting, decause gave a report on the status, work, and accomplishments of the CommOps sub-project. Thanks to everyone who helped pull together information and the presentation yesterday! decause++ bee2502++ skamath++ meskarune++ commops++ It's worth a watch if you haven't checked it out already.
16:08:24 <jflory7> eof from me
16:08:28 <jflory7> Anyone else have anything to add in?
16:08:43 <decause> the council report went really well
16:08:51 <meskarune> .hello
16:08:51 <zodbot> meskarune: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
16:08:57 <meskarune> .hello meskarune
16:08:58 <zodbot> meskarune: meskarune 'Dolores Portalatin' <meskarune@archwomen.org>
16:09:00 <jflory7> Hi meskarune! :)
16:09:03 <jflory7> #chair meskarune
16:09:03 <zodbot> Current chairs: GIANT_CRAB c0mrad3 decause jflory7 linuxmodder meskarune nb sayan skamath
16:09:03 <decause> thanks bee2502 and skamath for picking up the slack to get metrics generated
16:09:04 <skamath> decause++ Was watching it a while ago :)
16:09:16 <jflory7> Really regret not being around for that yesterday :(
16:09:21 <meskarune> howdy
16:09:22 <decause> jflory7: it happens
16:09:23 <jflory7> Ended up being poor timing for me.
16:09:28 <decause> meskarune++
16:09:53 <skamath> decause: np :)
16:10:03 <decause> EOF
16:10:13 <jflory7> Alrighty! Announcements, going once...
16:10:18 <jflory7> Going twice...
16:10:23 <skamath> jflory7:  ex-provider--
16:10:28 <jflory7> Going thrice...
16:10:39 <jflory7> skamath: Heh, yeah. Finally have cable and not DSL any more :P
16:10:45 <jflory7> #topic Action items from last meeting
16:10:51 <jflory7> #link https://meetbot.fedoraproject.org/fedora-meeting/2016-06-07/commops.2016-06-07-15.58.html
16:10:56 <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:11:02 <jflory7> #info === decause Follow up with tatica and diversity team about LimeSurvey availability ===
16:11:14 <jflory7> Anything here?
16:12:39 <decause> we started digging for the survey questions
16:12:51 <decause> you were part of that thread
16:13:13 <decause> I think I'm just going to give the credentials to others so they can log in an create stuff
16:13:15 <jflory7> decause: ping :)
16:13:15 <zodbot> jflory7: Ping with data, please: https://fedoraproject.org/wiki/No_naked_pings
16:13:55 <jflory7> We'll come back to decause's actions in a bit
16:13:56 <decause> jflory7: I'll prolly do a voice call with you and transfer them
16:14:00 <jflory7> #info === [COMPLETE] skamath File a ticket in the Fedora Badges Trac for a CommOps on-boarding badge that is dependent on other badges and/or hooks to be awarded; ask in #fedora-commops if assistance is needed ===
16:14:09 <jflory7> #link https://fedorahosted.org/fedora-badges/ticket/464
16:14:10 <jflory7> skamath++
16:14:11 <jflory7> #info === [COMPLETE] jflory7 Write a first draft of objectives / goals for the vFAD on wiki page, share with commops, get feedback, look at finding open dates (cc: decause) ===
16:14:16 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/10#comment:5
16:14:21 <jflory7> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/GSZLMED2YQ3HNQVJDH6ETCJCWXZTRCIE/
16:14:29 <GIANT_CRAB> Any planning on the dates?
16:14:31 <jflory7> #info === [COMPLETE] jflory7 Post to the CommOps mailing list about Ticket #71 about creating the Ambassador guidelines for artwork assets based on mizmo's feedback ===
16:14:32 <GIANT_CRAB> progress*
16:14:45 <jflory7> Oh, whoops, I just got a flood of messages
16:15:15 <jflory7> decause: Okay, that sounds good to me.
16:15:25 <jflory7> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/L7VXDJD47JSB5O7UUQNUDTGZTSSTA7LB/
16:15:38 <jflory7> #info === decause Follow up with tatica and diversity team about LimeSurvey availability ===
16:15:47 <decause> #action decause review the vFAD goals/objectives/etc
16:16:07 <jflory7> #info In-progress; working on getting data back for the survey questions, will work on transferring credentials soon
16:16:13 <jflory7> #info === decause Work with jzb to organize the release party in Raleigh, NC area ===
16:16:43 <decause> jflory7: I'm going to look into this during our 1x1 on Thursday most likely
16:16:46 * jflory7 nods
16:16:50 <jflory7> Will re-action
16:16:55 <jflory7> #action decause Work with jzb to organize the release party in Raleigh, NC area
16:17:01 <jflory7> #info === decause nail down Flock arrangements, add them to Fedocal ===
16:17:18 <decause> #action decause nail down Flock arrangements and add to fedocal
16:17:22 <decause> next
16:17:30 <jflory7> #info === decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available) ===
16:17:39 <decause> for...?
16:17:43 <decause> the FAD, right
16:17:45 <jflory7> I believe the EDU FAD
16:17:47 <jflory7> Yeah.
16:17:55 <decause> re-action plz
16:17:59 <jflory7> GIANT_CRAB: We'll get to the date discussion for the CommOps vFAD in a bit, it's our first ticket for today. :)
16:18:07 <jflory7> #action decause / spot look into booking conference rooms in the Tower (Fedora on 9 if it is available)
16:18:09 <GIANT_CRAB> okay
16:18:15 <jflory7> #info === decause ship "final" version for review by EoB thursday of F24 GA Release Announcement ===
16:18:31 <jflory7> Guess we got an extra week on this one anyways :)
16:19:26 * linuxmodder reads back
16:20:44 <decause> jflory7: yeah, we'll revisit after go/no-go thursday
16:20:48 * jflory7 nods
16:20:56 <decause> bkp is part of this loop bigtime
16:21:21 <jflory7> #action decause Finish "final" version of F24 GA Release Announcement for review after go/no-go meeting on Thursday
16:21:27 <jflory7> #info === [COMPLETE] jflory7 Create a Fedocal event for the hack session, 2016-06-08 22:00 UTC ===
16:21:30 <jflory7> #link https://apps.fedoraproject.org/calendar/meeting/4145/
16:21:37 <jflory7> omiday++
16:21:58 <jflory7> Okay, that's all action items! I think my message flood got the rest of them, I hope...
16:22:06 <jflory7> #topic Tickets
16:22:12 <jflory7> #link https://fedorahosted.org/fedora-commops/report/9
16:22:17 <jflory7> #info === Ticket #10 ===
16:22:22 <jflory7> #info "CommOps vFAD 2016"
16:22:27 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/10
16:22:31 <jflory7> #link https://fedoraproject.org/wiki/FAD_CommOps_2016
16:22:35 <jflory7> In the ticket, there is a summary of the changes made to the wiki page for the vFAD, mostly focusing on our purposes for a vFAD, the impact we'd like to have by organizing this, and the objectives we would wish to accomplish. A vote was put out last week, and as according to our voting policy, the ticket "passed". The next steps should be trying to pick out a date for when we could organize our vFAD and reach the most people. Also deciding how
16:22:35 <jflory7> long we want to run our vFAD?
16:22:38 <GIANT_CRAB> When would be a good date?
16:22:51 <jflory7> I know the end of June and probably end of July are not good times.
16:22:58 <jflory7> I'd like to organize it before Flock
16:23:08 <GIANT_CRAB> Uh, I guess 9 to 10 hours?
16:23:10 <jflory7> July 15-17 should also be out because of Fedora Women Day.
16:23:16 <GIANT_CRAB> Would we be using any video conference?
16:23:22 <jflory7> GIANT_CRAB: I wasn't sure if we wanted to do a one-day sort of FAD or like a weekend one.
16:23:26 <GIANT_CRAB> I know Red Hat has this Bluejeans thing
16:23:51 <GIANT_CRAB> sec, let me re-review the vFAD
16:23:51 <jflory7> GIANT_CRAB: We probably would be since it's all remote. We've used Jitsi and Hangouts in the past, but maybe Bluejeans would work best since it seems to have many ways for people to participate
16:23:59 <jflory7> That would require a Red Hatter to set up, I believe, though.
16:24:02 <c0mrad3> GIANT_CRAB: I think video should not be a problem
16:24:19 <c0mrad3> GIANT_CRAB: I was don't easily for Docs FAD
16:24:56 <jflory7> #info BAD TIMES: June 26-30 (Red Hat Summit), July 15-17 (Fedora Women Day / weekend), end of July (Design FAD / Flock right around corner)
16:25:03 <decause> weekend before EDU FAD maybe?
16:25:10 <jflory7> Did we set a date for the EDU FAD?
16:25:21 <decause> yeah, it's like the 27th-ish maybe?
16:25:25 * decause checks
16:25:45 <jflory7> Oh, I didn't know we had a date! So like this weekend or the next...?
16:25:50 <decause> 22-23rd
16:25:55 <decause> of July
16:25:59 <jflory7> Ohhhhh, okay
16:26:02 <decause> is the proposed EDU FAD Slot
16:26:04 <jflory7> Not June :)
16:26:17 <jflory7> decause: The weekend before that is Fedora Women Day.
16:26:17 <GIANT_CRAB> 16/17 July seems fine
16:26:20 <decause> that weekend before is Women's day then
16:26:26 <decause> ?
16:26:29 <jflory7> Yeah.
16:26:34 <GIANT_CRAB> oh wait
16:26:35 <GIANT_CRAB> ya
16:26:47 <GIANT_CRAB> lol these dates are so terrible
16:26:49 <decause> jflory7: what if we made it during the commops workshop?
16:26:54 <jflory7> July 2-3 is technically open, although that is right before a holiday in the US too.
16:26:54 <decause> at Flock?
16:27:02 <jflory7> decause: Hmmmm... I'm not opposed :)
16:27:11 <decause> the workshop is technically only 2 hours
16:27:26 <GIANT_CRAB> There's a APAC FAD on 2-3 July, but I don't think it will affect much.
16:27:28 <jflory7> Would be hard to get all the things we have in the agenda in that time slot though
16:27:32 <decause> well, we should def enable remote participants for workshop either way
16:27:42 <jflory7> Yeah.
16:27:45 * decause was thinking of workshops in the past being all day
16:27:47 <meskarune> so I think maybe we should just take a little from the FLOSS survey: http://flossproject.merit.unu.edu/floss1/stats.html (sorry I shoudl have posted eariler)
16:28:02 <jflory7> Also, one concern at Flock would be bandwidth too for A/V.
16:28:04 * jflory7 opens
16:28:32 <GIANT_CRAB> apologies, APAC FAD is on 9 July
16:28:46 <GIANT_CRAB> #link https://fedoraproject.org/wiki/FAD_KualaLumpur_2016
16:28:53 * decause queues up that link from meskarune for later
16:29:10 <jflory7> meskarune: Ooh. That would definitely be a useful resource for the Diversity survey. Can revisit this one for sure! I think tatica would find it useful too.
16:29:29 <jflory7> So, tentative dates for the CommOps vFAD might be...
16:29:45 <jflory7> #idea Proposed Dates: June 25-26 (little soon)
16:29:47 <decause> jflory7: have we discussed the possibility of doing the vFAD after Flock at some point?
16:29:54 <jflory7> #idea Proposed Dates: July 2-3
16:30:08 <GIANT_CRAB> 25/26 RH Summit?
16:30:08 * decause will be returning from RHT Summit that day :/
16:30:12 <jflory7> #idea Proposed Dates: July 30-31
16:30:21 <jflory7> Oh, wait, we ruled out the first June dates, right...
16:30:24 * decause will likely be travelling to FLOCK
16:30:30 <GIANT_CRAB> #agree with July 2-3
16:30:36 <jflory7> decause: I don't think we had discussed it.
16:30:44 <decause> I'm not the only one that should have schedule considerations though
16:30:49 <jflory7> Although it might be nice prepwork for Flock to try knocking out some of our tickets and the on-boarding discussions
16:31:00 <jflory7> So far, July 2-3 is seeming like one of the better choices
16:31:01 <decause> if the 2-3 or 30-31 work for everyone else, we should do it
16:31:17 <jflory7> decause: Were you blocked for July 2-3?
16:31:24 <skamath> 2-3 +1
16:31:35 <sayan> July 2-3 wfm
16:31:41 <jflory7> Works for me as well.
16:31:53 <GIANT_CRAB> 2-3 +1
16:32:20 <decause> my flight is 7/2
16:32:20 <GIANT_CRAB> ah crap, I think I've got something on that date, June 30-31 +1
16:32:37 <jflory7> decause: Oh, back from Summit?
16:32:41 <decause> jflory7: we should do a whenisgood
16:32:45 <decause> for those two dates
16:32:48 <decause> to the mailing list
16:32:51 <jflory7> Yeah, that would be good for people who are also not here too
16:32:52 <decause> have it closed by next meeting?
16:32:55 <c0mrad3> for me any date is okay but I may not be available all the day
16:33:02 <sayan> decause++
16:33:08 <GIANT_CRAB> decause++
16:33:23 <decause> those dates seem reasonable though
16:33:27 <skamath> c0mrad3: Your builds passed?
16:33:44 <jflory7> #action jflory7 Create a WhenIsGood and share with CommOps mailing list to decide on vFAD dates of July 2-3 or June 25-26
16:33:49 <jflory7> ^ sound right?
16:33:54 <skamath> jflory7++
16:33:58 <decause> jflory7: yes, skamath can help with that too
16:34:01 * jflory7 nods
16:34:07 <jflory7> Will keep skamath in the loop on this one :)
16:34:14 <jflory7> Alrighty. I think this should be good for this ticket for now!
16:34:18 <decause> nod nod
16:34:20 * skamath nods as well
16:34:25 <decause> timecheck: 50%
16:34:26 <decause> no
16:34:32 <decause> timecheck: 30%
16:34:33 <decause> :)
16:34:45 <jflory7> #agreed We decided on two "best case" dates for vFAD, will throw out to list with a WhenIsGood to get more input
16:34:52 <jflory7> #info === Tickets #34, 49, 69 ===
16:34:55 <GIANT_CRAB> Alright, you guys have fun, gotta get off and sleep
16:34:57 <c0mrad3> skamath: yes it a clean build everything passed :) https://copr.fedorainfracloud.org/coprs/dhanvi/pintail-asciidoc/
16:34:58 <jflory7> #info #39: "[Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series"
16:35:03 <jflory7> #info #49: "[Onboarding Series] CommOps!"
16:35:05 <skamath> c0mrad3++
16:35:08 <jflory7> #info #69: "Fedora Modularity onboarding"
16:35:13 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/34
16:35:17 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/57
16:35:21 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/69
16:35:28 <jflory7> #info CommOps Team Onboarding Steps > Badges Team Missing Badges > Hubs Team Badges Tracks and Widgets
16:35:30 <jflory7> skamath filed a ticket for the CommOps on-boarding badge series on the Badges Team Trac. In the ticket, we have the basic criteria, some name ideas, a badge description, discussion on how to automate the badge, and some initial artwork concept ideas.
16:35:33 <jflory7> Best place to start for now... how do we want to handle automation of this badge? Should it be dependent on whether a user already has certain badges? Questions to ask: Is this an expensive operation? Will we be able to hit everything we need?
16:35:36 <jflory7> Alternatively, would it be better to make sponsorship in the FAS group the best way to automate this? This will ensure a human is verifying the person has performed the needed responsibilities and tasks to become "bootstrapped" in CommOps. The FAS group memberships have to be manually approved already, so this is a factor to consider too.
16:35:47 * jflory7 gives time for everyone to read
16:36:04 <skamath> jflory7: We don't have the description and artwork idea yet.
16:36:21 <skamath> We should discuss about it and make suitable edits
16:36:32 <jflory7> skamath: I added name + description + artwork concept idea in the ticket earlier for a base to work off of. :)
16:36:33 <c0mrad3> !
16:36:36 <jflory7> c0mrad3: Go for it!
16:36:49 <skamath> jflory7: Oh, rad. jflory7++
16:36:57 <jflory7> skamath: We can discuss my suggestions here though.
16:37:00 * skamath should have checked
16:37:06 <jflory7> Oh, and this link:
16:37:08 <jflory7> #link https://fedorahosted.org/fedora-badges/ticket/464
16:37:50 <decause> jflory7: I like basing it off of the FAS memebership because it implies a human has reviewed things
16:37:55 <c0mrad3> IMHO automation of badges doesn't really help as everyone will be just in hurry to just do the task and get badges but not concentrate in joining the team
16:38:13 <decause> but, I think making it easy for a human to review is important too
16:38:20 <meskarune> idk, I have not been using badages as a reason to do things
16:38:27 <decause> so like, applicant filing a ticket with links to all the criteria, or something
16:38:28 <meskarune> but they are nice to see what you have accomplished
16:38:38 <linuxmodder> c0mrad3,  I agree
16:38:39 <jflory7> decause: Plus that is also an inexpensive operation since many badges also use FAS group sponsorships already
16:38:50 <decause> meskarune: some folks use them to find work, but we want to also use them as a way to rolemodel
16:38:59 <skamath> jflory7++ That is definitely an awesome idea!
16:38:59 <jflory7> Well, in this case, the human factor would be something that would be in play
16:39:03 <meskarune> yeah, that makes sense
16:39:07 <jflory7> The automation would be the sponsorship into commops FAS group
16:39:08 <linuxmodder> meskarune,  me niether but its the incentivize the millenials  idea
16:39:28 <decause> it's 50/50 for sure
16:39:57 <linuxmodder> jflory7,  I think commops should be  cla +3  or  demonstrated efforts in a  commops  controlled  venture
16:39:57 <jflory7> In either case...
16:40:01 <linuxmodder> but that is me
16:40:14 <jflory7> linuxmodder: This is going off of our Join steps we defined a few months ago.
16:40:22 <jflory7> CLA+3 seems like a high barrier to entry to me, though...
16:40:27 <linuxmodder> at the point you are  cla +3  you are  active enough you need to consider commops ml anyway
16:40:54 <jflory7> If I were getting started at the time, I don't know if I would have considered CommOps because it would seemed like you'd have to be involved with the project for some time before you would be helpful / useful to the sub-project
16:41:05 <jflory7> I don't think that's necessarily the case
16:41:09 <linuxmodder> cla +1 is  min for people space  how is asking  for demonstrated  efforts in at least  2  groups  too high
16:41:12 <jflory7> for reference:
16:41:13 <jflory7> #link https://fedoraproject.org/wiki/CommOps/Join
16:41:19 <skamath> linuxmodder: You can't neglect the new-comers who are interested in just writings, can you?
16:41:37 <linuxmodder> that would be  cla +2 as is
16:41:57 <linuxmodder> cla +1 would be  docs and  to edit  would be  +2  commops  beign the 3rd
16:42:21 <jflory7> Well, this topic would be more about reconsidering our Join process as it is.
16:42:32 <linuxmodder> or have a  ML trigger  using  pingyou's fedora-active-user py script
16:42:33 <skamath> linuxmodder: nod nod
16:42:37 <skamath> that makes sense
16:43:01 <linuxmodder> I personally am getting tired of  drive by  members in ALL sub projects
16:43:02 <jflory7> If there's holes in our Join process, that would be probably be better raised as its own independent discussion
16:43:05 <skamath> cla +2 is a good idea. I personally think cla+3 is high for onboarding
16:43:23 <c0mrad3> jflory7: why reconsidering our steps are fine but we just have to add badges to them
16:43:39 <linuxmodder> or make cla +2 default and  full commops  actions  cla +3
16:43:45 <jflory7> I feel like our Join process on the wiki is enough to determine whether someone receives sponsorship into the team. https://fedoraproject.org/wiki/CommOps/Join
16:43:47 * skamath is only cla+3
16:44:01 <linuxmodder> skamath,  for less than 6 months that is  not bad
16:44:14 <linuxmodder> and you unlike some newcomers are active
16:44:35 <jflory7> Time check, 50%
16:44:59 <skamath> nod nod
16:45:02 <jflory7> So we still want to consider the human approval for the FAS group at the least, it seems.
16:45:11 <linuxmodder> heck yes
16:45:13 <jflory7> I think that's the best for CommOps as well
16:45:34 <jflory7> #action jflory7 Write YAML file for CommOps on-boarding badge based on FAS group sponsorship
16:45:45 <linuxmodder> I think ALL groups  should start  locking down on ML and  overall activity  metrics for badges and access tbh
16:45:46 * skamath will help
16:45:49 <meskarune> it seems like there are more people signed up for commops than actively contributing
16:46:02 <linuxmodder> ^^
16:46:15 <meskarune> in arch people are removed from teams for inactivity
16:46:22 <skamath> meskarune: Exactly! That is why I suggested a cleanup in the last meeting
16:46:22 <meskarune> but I realize that isn't practical for everyone
16:46:27 <linuxmodder> #idea instuite a  monthly  mailing like infra has for  weeding out inactive members
16:46:56 <meskarune> it makes it easier to make sure information is going to the right people
16:47:01 <linuxmodder> any user that is not responsive in the usual 7 days like infra does is removed  and has to re-apply
16:47:04 <c0mrad3> linuxmodder: fas takes care of the inactive members
16:47:07 <skamath> meskarune: Last meeting, we were planning to do the same with CommOps as well. A monthly check-in will be super useful
16:47:24 <skamath> c0mrad3: They are not kicked out of groups though
16:47:34 <meskarune> I think like 2 months or 3 inactive is reasonable
16:47:51 <meskarune> some people may be on school vacation and not have internet access or whatever
16:47:55 <jflory7> One thing to consider too is that a lot of the people on our wiki page added themselves there before we actually had a Join page (or were sponsored into the FAS group before that time). So not everyone who is in the group now may have followed those steps that we created a little bit after we got started. I think an initial go-through of the members of the FAS group to verify if they have completed the steps is a good idea. But having some kind
16:47:55 <jflory7> of check-in on a regular basis seems alright to me.
16:48:15 <jflory7> Yeah, for Infrastructure, I think a month makes more sense, but for us, I think quarterly might be a good way to go about it
16:48:32 <skamath> jflory7: nod nod
16:48:54 * c0mrad3 nods for monthly checkins and about 3/4 months inactivity
16:49:36 <jflory7> #action jflory7 Open a ticket to look into drafting an (automated?) check-in email with members of CommOps to determine activity
16:49:45 <decause> +1
16:49:50 <jflory7> Alrighty. I think we've covered this ticket pretty well, then.
16:49:57 <skamath> jflory7++
16:50:22 <jflory7> There's one last ticket on the agenda, and I think it's a pretty interesting one too based on the new information that we got last week.
16:50:28 <jflory7> #info === Ticket #71 ===
16:50:33 <jflory7> #info "Centralizing Ambassadors / Events resources and utilities"
16:50:38 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/71
16:50:42 <jflory7> Based on feedback given by the Design Team, there are already efforts and repositories in place to bring together Design resources. However, the Design Team has a strong preference for having Ambassadors or others request assets or design work for the printing press in the Design Team Trac to ensure that guidelines are met and the Fedora brand is well-represented. The suggestion I had was better communicating this process to the Ambassadors.
16:50:42 <jflory7> Take a minute to review the ticket and let us know what your thoughts are.
16:50:47 <jflory7> #link https://pagure.io/designassets/tree/master
16:50:57 <linuxmodder> c0mrad3,  nope it doesn't as is  sdaly
16:50:59 <linuxmodder> off the list with first unresponsive  out of  group with 3  consective sounds logical
16:51:01 <linuxmodder> if on vacation they are  exempt from that
16:51:03 <linuxmodder> only during the vactaion term
16:51:22 <jflory7> I thought this was particularly interesting as it seems to me that there is a disconnect between the Ambassadors and the Design Team
16:51:54 <jflory7> I think it shows there's a need for improved communication between the two teams on the proper process of getting design work done for regional events
16:53:02 <decause> mleonova said she was working on a repo just like this, so I'd like to see if her work closes this ticket
16:53:10 <jflory7> decause: Well, technically, yes.
16:53:14 <decause> well, from a "artifact" standpoint
16:53:15 <jflory7> The repo linked above is that
16:53:26 <jflory7> The artifact exists, but it's not the solution the Design Team wants for this ticket :)
16:53:31 <decause> the larger issue, there isn't enough communication between the teams
16:53:34 * jflory7 nods
16:53:36 <decause> that isn't going to be about a repo
16:53:51 <decause> that is going to take some kind of regular cross-pollination
16:53:58 <decause> this is what FOSCO is meant to address
16:54:32 <decause> we (FAMSCO/Council) have talked a lot about WHAT FOSCO is, but I think this is a great example of a WHY
16:55:03 <meskarune> is there a place to look to see the things various teams have done?
16:55:05 <decause> we should point to this ticket/discussion in the FOSCO ticket as a way to help give that group context
16:55:31 <meskarune> Like, you guys just recently had a list of all your accomplishments, and having a regular list like that, maybe monthy would help others to keep up with the news here
16:55:42 <meskarune> and same for other subprojects
16:56:11 <jflory7> decause: Is there increased traction on the formation of FOSCo? I just wonder if it would be better to defer this to whenever FOSCo happens (which may or may not be this year), or if it would be better if we did a wiki page about the process for Ambassadors and properly socialized it, and then passed it on to FOSCo for future maintaining.
16:56:17 <meskarune> so at a glance you would know what people in ambassadors are working on
16:56:27 <jflory7> meskarune: As for that, I don't know if there's anything quite like that. In a future world, that might be Fedora Hubs.
16:56:36 <meskarune> oh I see
16:56:38 <jflory7> It would be super useful to have as a resource, especially for something like this
16:57:08 <meskarune> maybe there could be subproject news pages with a simple over view of things that are happening
16:57:22 <decause> meskarune: we talked about this in the council meeting yesterday
16:57:23 <jflory7> So I guess like the Community Blog in a sense, but more static?
16:57:34 * jflory7 imagines a place to see the recent news from each category in the CommBlog
16:57:40 <decause> the process used to be searcing on the "Events:2016" category in the wiki
16:57:42 <meskarune> decause: oh nice :)
16:57:46 <decause> as a proxy for activity
16:58:03 <decause> but, folks are not as vigilant about doing the wiki pages these days according to cwickert
16:58:18 <decause> I think jflory7 is right about Hubs being the new place
16:58:23 <meskarune> https://wiki.archlinux.org/index.php/ArchWiki:News
16:58:32 <meskarune> so the arch wiki team has a news page where they place updates
16:58:42 <meskarune> the devs post updates on the mailing list
16:58:46 <decause> interesting
16:58:56 <meskarune> but arch is very small, and there isn't a ton of news lol
16:59:07 <meskarune> fedora has lots of stuff going on
16:59:10 <decause> I suppose commblog serves this purpose, though not as much in a pointed way connected directly to devel
16:59:49 <decause> meskarune: the devel list, or announce list, is where that type of content lives typically in fedoraland
16:59:59 <jflory7> I wonder if there would be a smarter way to query each category on the CommBlog and have a place to quickly display little summaries of the most recent article in each category
17:00:01 <decause> but there is no "web view" of that (outside of hyperkitty)
17:00:08 <jflory7> All the categories on the Community Blog are only sub-projects
17:00:23 <meskarune> decause: yeah, I am just wondering about having a quick overview rather than people who aren't in commops needing to dig through discussions to figure things out
17:00:36 <decause> meskarune: nod nod nod
17:00:44 <decause> a think a "news" hub would be cool for that
17:00:52 <decause> maybe we can file a ticket on the hubs tracker
17:00:58 <decause> but that doesn't help us for a few more months
17:01:00 <meskarune> that sounds like a great idea
17:01:05 <decause> it's a good idea though meskarune
17:01:16 <meskarune> and people can keep up with what is happening in other projects in general
17:01:17 <jflory7> A News hub would be super cool.
17:01:29 <decause> solid
17:01:43 <jflory7> #idea Create a "News" dashboard / widget in Fedora Hubs for at-a-glance news about what's good in the Fedora Project
17:01:53 <decause> and for "activities" an Events Hub would be good too likely
17:02:01 <decause> maybe that is part of news?
17:02:10 <jflory7> #idea Taking advantage of categories on the Community Blog to aggregate news about each sub-project
17:02:15 <decause> tickets though, conversation and consensus will figure it out
17:02:47 <jflory7> We can leave an open action for filing an issue on the Hubs ticket tracker about a News widget.
17:02:59 <jflory7> Unless someone thinks that's an action item they'd want to take on!
17:03:02 <decause> I'm +1 to both ideas
17:03:21 <skamath> +1 ; +1
17:03:43 <c0mrad3> +1 to news on community blog not sure about the hubs
17:04:10 <jflory7> #action commops File a ticket on the Pagure repository for Fedora Hubs about creating a News widget that aggregates different sources of information and puts it together for easy consumption by a reader
17:04:32 <jflory7> #link https://pagure.io/fedora-hubs/issues
17:04:54 <jflory7> What did you all think about the earlier proposal about who handles this issue in the short-term?
17:05:07 <jflory7> Do we want to try tackling a wiki page to communicate the process and hand it off to FOSCo in the future?
17:05:16 <jflory7> Or do we want to defer it as a task for the future FOSCo to handle?
17:06:14 <decause> I think we should update the existing ticket with the "WHY" part of FOSCo
17:06:25 <decause> because right now, the conversation is all about the WHAT
17:06:46 <decause> this will help give some concrete examples for HOW FOSCO will solve what kinds of problems
17:07:00 * jflory7 nods
17:07:14 <jflory7> I can get that perspective into the ticket.
17:07:53 <jflory7> #action jflory7 Update Ticket #71 with the "WHY" perspective in relation to FOSCo
17:08:02 <jflory7> Sound good for now?
17:08:21 <decause> sgtm
17:08:31 <decause> we should file a news hub ticket though
17:08:45 * jflory7 nods
17:08:57 <decause> with a link to the arch news wiki, and maybe other news feeds/tools from distros if we have exmaples?
17:09:11 <jflory7> We assigned that as an open action item earlier; if I have the time, I'll try to file one.
17:09:15 <jflory7> The news page from Arch is a good one
17:09:24 <jflory7> I'm not as familiar with any other tools other distros are using.
17:10:11 <meskarune> decause: I can search around :)
17:10:23 <meskarune> I swear I have seen something similar in ubuntu
17:10:25 <decause> meskarune++
17:10:30 <jflory7> meskarune++
17:10:32 <jflory7> That would be awesome :)
17:10:42 * jflory7 notes the time
17:10:48 <jflory7> Do we want to go ahead and move on from tickets?
17:10:56 <jflory7> I think we covered the angles on this one today too.
17:11:04 <skamath> I need to go for dinner. I'll catch up with you folks later :)
17:11:16 <meskarune> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue469?action=show&redirect=UbuntuWeeklyNewsletter/Current
17:11:21 <meskarune> I found their weekly news letter
17:11:25 * skamath fades out
17:11:32 <jflory7> skamath: Adios!
17:11:46 <jflory7> meskarune: Perfect! That should make it into the meeting minutes now :)
17:12:16 * jflory7 wonders if it's automated or a person writing that all up
17:12:33 <sayan> Automated most probably
17:12:48 <jflory7> Heh, I would hope :)
17:12:49 <sayan> most of the news letters are
17:13:08 <jflory7> Looks like it would be a lot of work to do manually.
17:13:10 <decause> timecheck: 75%
17:13:13 <c0mrad3> meskarune++
17:13:20 <jflory7> Anyways, we're down to the last 15 minutes. I think we're good on tickets for today. :)
17:13:34 <jflory7> Let's move on...
17:13:34 <jflory7> #topic Wiki Gardening
17:13:38 <jflory7> #action commops New members, make sure you add your timezone / interests on CommOps wiki [ https://fedoraproject.org/wiki/CommOps ]
17:13:45 <jflory7> Any wiki gardening to point out today?
17:13:49 <decause> https://fedoraproject.org/wiki/Red_Hat_Summit_2016#Fedora_Booth_Staffing
17:14:37 <jflory7> decause: Do we have a list of anyone who might be attending in part with fedora?
17:14:48 <decause> mattdm, maxamillion, decause
17:14:53 <decause> those are the ones I know
17:15:14 <jflory7> Is there a mailing list we could ping?
17:15:23 <jflory7> We probably need to get the word out to the folks attending to add their info there
17:15:27 <decause> it'd be good to post to the devel list maybe, and ask anyone who is already going to Summit to add their name to the wiki, and sign up for booth time
17:15:45 <decause> announce list maybe
17:15:54 <decause> devel list is prolly best
17:15:56 * c0mrad3 agrees
17:16:08 <jflory7> +1 for devel list.
17:16:14 <jflory7> Want to drop a ping there, decause?
17:17:52 <decause> ok, yeah
17:17:56 <decause> put it on my plate
17:18:12 <jflory7> #action decause Drop a line to the devel list to have anyone going to Red Hat Summit add their info to the wiki page
17:18:14 * jflory7 nods
17:18:18 <jflory7> Anything else for wiki gardening?
17:18:20 <jflory7> Going once...
17:18:30 <jflory7> Going twice...
17:18:35 <jflory7> Going thrice...
17:18:45 <jflory7> #topic Community Blog
17:18:54 <jflory7> #info How This Works: There is a quick blast of information about what was published in the past week with some metrics, followed by posts that are being drafted. After the information blast, the floor is opened for any Community Blog-related discussion. Here we go!
17:19:00 <jflory7> #info === This Week in CommBlog ===
17:19:02 <decause> popcorn
17:19:06 <jflory7> #info (1) "Getting started with Fedora QA (Part 1)"
17:19:12 <jflory7> #link https://communityblog.fedoraproject.org/getting-started-fedora-qa-part-1/
17:19:17 <jflory7> #info Total Views (June 9 - June 14): 510
17:19:34 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=1608
17:19:40 <jflory7> #info === Coming Up in CommBlog ===
17:19:46 <jflory7> #info (1) "Cloud Working Group FAD"
17:19:50 <jflory7> #link https://public.etherpad-mozilla.org/p/fad-summary-2016-june
17:19:56 <jflory7> #info Written by jzb, looking at publishing this week.
17:20:02 <jflory7> #info (2) "Event Report: PyCon 2016"
17:20:06 <jflory7> #link https://communityblog.fedoraproject.org/?p=1602&preview=1&_ppp=d3705befb7
17:20:10 <jflory7> #info (3) "Getting started with 'update-testing' Fedora QA part 2"
17:20:14 <jflory7> #link https://communityblog.fedoraproject.org/?p=1609&preview=1&_ppp=8a0d20416e
17:20:20 <jflory7> #info (4) "Getting started with Fedora QA part 3"
17:20:24 <jflory7> #link https://communityblog.fedoraproject.org/?p=1610&preview=1&_ppp=676163dcfd
17:20:25 <jflory7> eof
17:20:36 <jflory7> Any other Community Blog news / discussion?
17:21:11 * sayan needs to leave for dinner, will catch up with the logs
17:21:14 * sayan &
17:21:17 <jflory7> sayan: Sounds good, see ya!
17:21:21 <jflory7> CommBlog, going once...
17:21:26 <jflory7> Going twice...
17:21:36 <jflory7> Going thrice...
17:21:45 <jflory7> #topic Release Schedule
17:21:49 <jflory7> #link https://fedorapeople.org/groups/schedule/f-24/f-24-key-tasks.html
17:22:06 <jflory7> #info Final Release Public Availability (GA) 	Tue 2016-06-21
17:22:15 <jflory7> #info Fedora 22 EOL auto closure 	Tue 2016-07-19
17:23:28 <jflory7> If all goes well, in one more week, we'll have F24 by the time we meet :)
17:23:54 <jflory7> #topic Open Floor
17:24:02 <jflory7> Anything we want to bring up here at open floor?
17:24:37 * c0mrad3 nothing in my mind
17:24:40 <nirik> I had a quick item...
17:24:43 <jflory7> nirik: Sure!
17:25:05 <nirik> you all are using fedorahosted trac tickets for tracking things, right?
17:25:10 <jflory7> nirik: Yes!
17:25:25 <nirik> would you be willing to look into moving to pagure? see if there's things you need that pagure doesn't do yet?
17:25:38 <jflory7> nirik: It's something I've thought about a little bit personally
17:26:07 <nirik> ok. we are trying to gather feedback from vaious projects about moving over.
17:26:11 <jflory7> One big "desireable" item for me is being able to CC FAS users directly from tickets to get a notification in an inbox.
17:26:16 <nirik> if someone has time to investigate for your needs that would be great
17:26:22 <jflory7> We use components pretty heavily, but I think that could become tags
17:26:40 <nirik> is the ticket cc thing filed yet?
17:26:43 <jflory7> Milestones is something that would be easy to convert.
17:26:53 <jflory7> Hmmm, not sure. I can look at filing a ticket for it if it doesn't exist.
17:27:13 <jflory7> #action jflory7 Look into filing a ticket on Pagure for CCing users / lists from a Pagure issue
17:27:14 <nirik> https://pagure.io/pagure/issue/746
17:27:19 <jflory7> Ah!
17:27:31 <nirik> but might be good to add your specific use case there
17:27:38 <jflory7> Yeah, I can add that in there
17:27:48 <jflory7> I'll give it some more thought and see if I can come up with some more specifics
17:27:56 <jflory7> That's just the first thing that comes to mind. :)
17:28:17 <jflory7> But I'd be happy to add some feedback to Pagure for making it easier for ticket-oriented teams to look at migrating.
17:28:20 <nirik> I'm sure there may be others... thats just the kind of data we are looking for. ;)
17:28:30 <jflory7> nirik: One you may want to especially consider is the Badges Team. Their Trac is heavily customized
17:28:40 <jflory7> I don't know if threebean or someone else set that one up.
17:29:01 <nirik> jflory7: yeah, I mailed the badges list about it.
17:29:11 <nirik> adamw actually set all that up I think.
17:29:18 * jflory7 nods
17:29:23 <jflory7> Sounds good.
17:29:23 <adamw> that was me
17:29:53 <nirik> I am sure pagure can't do the same workflow as it is, but perhaps we could do many of the easy things to get it closer...
17:30:07 <jflory7> nirik: Thanks for bringing this up in our meeting!
17:30:08 <nirik> or figure out another workflow
17:30:21 <nirik> no problem.
17:30:34 <jflory7> Alrighty, we're right at time... anything else anyone wants to bring up?
17:30:42 <jflory7> Otherwise, we'll close out and head back to #fedora-commops :)
17:30:58 <decause> parting thoughts, quick?
17:31:04 <jflory7> decause: Go for it :)
17:31:12 * jflory7 passes the baton
17:31:15 <decause> #topic Parting Thoughts
17:31:33 <decause> This past 2 weeks have been extremely busy with on-the-ground events that we all had a hand in preparing for
17:31:56 <decause> PyCon went very very well, and the Fedora <3's Python branding was a *huge* hit
17:32:12 <decause> thanks to all of you, commops, mktg, design, ambassadors, who had input during that process
17:32:34 <jflory7> pycon++
17:32:35 <decause> lots of plotting and planning went into that
17:32:43 <decause> as well as Google Summer of Code
17:32:48 <decause> we're in a "doing stuff" mode right now
17:32:55 <decause> preparing for RHT summit
17:32:58 <decause> preparing for Flock
17:33:04 <decause> executing on our GSoC plans
17:33:16 <decause> thank you all for your continued work to bridge the subprojects and get stuff done
17:33:28 <decause> if you get a chance, def watch the council update
17:33:51 <decause> I think it was a good overview of all the great work happening in our team, and specifically thanks many of the busy folks making it happen
17:33:58 <decause> I cannot thank you all enough for your support and hard work
17:34:05 <jflory7> decause++ commops++ :)
17:34:10 <decause> as I always say, the Friends Foundation is the strongest in Fedora
17:34:20 <decause> and you folks make that stronger each day
17:34:24 <decause> let's keep up the good work
17:34:43 <decause> Happy Hacking All :)
17:34:58 <jflory7> Happy hacking, decause :)
17:34:59 * decause is good now
17:35:20 <jflory7> +1 to close out and head back to home base!
17:35:29 <decause> +1
17:35:46 <jflory7> Alright, see you all in channel. :)
17:35:47 <meskarune> +1
17:35:52 <jflory7> #endmeeting