16:55:28 <jflory7> #startmeeting Fedora CommOps (2016-02-16)
16:55:29 <zodbot> Meeting started Tue Feb 16 16:55:28 2016 UTC.  The chair is jflory7. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:55:29 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:55:29 <zodbot> The meeting name has been set to 'fedora_commops_(2016-02-16)'
16:55:31 <jflory7> #meetingname CommOps
16:55:31 <zodbot> The meeting name has been set to 'commops'
16:55:40 <jflory7> #chair decause jflory7 bee2502 cprofitt mailga danofsatx
16:55:40 <zodbot> Current chairs: bee2502 cprofitt danofsatx decause jflory7 mailga
16:55:44 <nb> .hello nb
16:55:44 <jflory7> #chair bee2502_
16:55:44 <zodbot> Current chairs: bee2502 bee2502_ cprofitt danofsatx decause jflory7 mailga
16:55:44 <zodbot> nb: nb 'Nick Bebout' <nick@bebout.net>
16:55:47 <jflory7> #chair nb
16:55:47 <zodbot> Current chairs: bee2502 bee2502_ cprofitt danofsatx decause jflory7 mailga nb
16:55:52 <jflory7> #topic Agenda
16:56:06 <jflory7> #link https://fedoraproject.org/wiki/Meeting:CommOps_2016-02-16
16:56:11 <jflory7> #info 1. Roll Call
16:56:15 <jflory7> #info 2. Announcements
16:56:20 <jflory7> #info 3. Action items from last meeting
16:56:25 <jflory7> #info 4. Tickets
16:56:30 <jflory7> #info 5. Wiki Gardening
16:56:34 <jflory7> #info 6. Community Blog
16:56:38 <jflory7> #info 7. Open Floor
16:56:42 <jflory7> #topic Roll Call
16:56:46 <jflory7> #info Name; Timezone; Subprojects/Interest Areas
16:56:49 <jflory7> .hello jflory7
16:56:50 <zodbot> jflory7: jflory7 'Justin W. Flory' <me@justinwflory.com>
16:57:04 <jflory7> #info Justin W. Flory; UTC-5; CommOps, Marketing (Magazine), Ambassadors, Join, and more
16:57:09 <jflory7> We'll let roll call sit for a bit :)
16:57:42 <decause> .hello decause
16:57:44 <zodbot> decause: decause 'Remy DeCausemaker' <decause@redhat.com>
16:58:37 <linuxmodder> .hello corey84
16:58:38 <zodbot> linuxmodder: corey84 'Corey Sheldon' <sheldon.corey@gmail.com>
16:58:59 <linuxmodder> cydrobolt,  ??
16:59:05 <jflory7> danofsatx said he may be joining us late, he is in the commute right now.
16:59:21 <keekri> .hello keekri
16:59:22 <zodbot> keekri: keekri 'Keerthana Krishnan' <contactkeerthana@gmail.com>
16:59:27 * decause waves to keekri
16:59:32 <keekri> Hey guys!
16:59:54 <jflory7> Hello all :)
17:00:06 <keekri> decause: Hope you had fun on your trip!
17:00:14 <jflory7> Today is looking like another packed meeting... if you haven't read it yet, here's today's agenda: https://fedoraproject.org/wiki/Meeting:CommOps_2016-02-16
17:02:03 <nb> .hello nb
17:02:04 <zodbot> nb: nb 'Nick Bebout' <nick@bebout.net>
17:02:21 <decause> keekri: indeed I did. Super busy, and super good.
17:02:26 <jflory7> Hi Nick :)
17:02:33 <decause> nb: welcome
17:02:41 <jflory7> Shall we proceed into announcements and let any stragglers roll in as we go?
17:02:49 <decause> nod nod nod
17:02:52 <jflory7> #topic Announcements
17:02:55 <keekri> jflory7: nb: Hey guys!
17:03:02 <jflory7> #info === Ticket #5 - https://fedorahosted.org/fedora-commops/ticket/5 ===
17:03:06 <jflory7> keekri: how's it going? :)
17:03:13 <jflory7> #info * "Write a beginner's guide to using Trac for Community Blog"
17:03:16 <fale> .hello fale
17:03:18 <zodbot> fale: fale 'Fabio Alessandro Locati' <fabio@locati.cc>
17:03:19 <jflory7> #info No additional progress to report on this ticket at this time; jflory7 is still planning to have an early draft prepared by the end of the month
17:03:25 <keekri> :)
17:03:31 <jflory7> #action jflory7 Start draft on Trac 101 article in Community Blog
17:03:33 <jflory7> fale: Hiya!
17:03:41 <jflory7> #info === Ticket #41 - https://fedorahosted.org/fedora-commops/ticket/41 ===
17:03:53 <jflory7> #info * CommOps Trac now has email notifications for tickets you have replied to or are copied on
17:04:00 <jflory7> #info === New tickets in our Trac this week ===
17:04:02 <keekri> Hey fale! I remember seeing your mail in the list, welcome!
17:04:05 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/42
17:04:12 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/43
17:04:15 <decause> fale: welcome :)
17:04:16 <linuxmodder> expierencing some lag at this location sorry for delays taht may occur
17:04:18 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/44
17:04:18 <decause> MarkDude: welcome
17:04:24 <MarkDude> Hello
17:04:27 <jflory7> #link https://fedorahosted.org/fedora-commops/ticket/45
17:04:31 <jflory7> MarkDude: o/
17:04:36 <linuxmodder> nice showing today
17:04:39 <jflory7> That's all the announcements I have listed right now.
17:04:41 <jflory7> linuxmodder: Agreed!
17:04:50 <keekri> MarkDude: linuxmodder: Hiya!
17:04:59 <jflory7> As for the new tickets, I think it will be best to include them in future agendas -- this meeting will probably be pretty tight to fit them in here
17:05:07 <jflory7> But I recommend that you all check them out to see what's ahead :)
17:05:10 <linuxmodder> keekri,  0/
17:05:12 <decause> jflory7: nod nod, keep it rolling
17:05:20 <jflory7> #topic Action items from last meeting
17:05:31 <MarkDude> Hello all, a bit under the weather
17:05:38 <jflory7> Quick info on this: if it's [Completed], we just keep rolling, if not, a quick one-line check-in by whoever it is actioned to
17:05:40 <linuxmodder> MarkDude,  welcome
17:05:45 <jflory7> #link https://meetbot.fedoraproject.org/fedora-meeting-2/2016-02-09/commops.2016-02-09-16.56.html
17:05:51 <jflory7> #info * commops create a ticket to start the EDU Inventory list, possible repo in pagure
17:06:02 <jflory7> decause: Was this partially completed in your tickets?
17:06:11 <decause> jflory7: yes, there is a ticket ont he commops trac now
17:06:18 <linuxmodder> seemed that way to me
17:06:34 <linuxmodder> that is onboarding  inventory right ?
17:06:40 <decause> linuxmodder: not quite
17:06:51 <jflory7> Okay, cool, so we will defer that to ticket discussion
17:06:56 <decause> EDU inventory is a list of what folks we have near/at various universities
17:07:05 * decause keeps rolling
17:07:07 <jflory7> #info ^ [Completed] More information about this can be found in tickets
17:07:16 <jflory7> #info * commops create an individual ticket for Fedora Infra Onboarding badge
17:07:21 <jflory7> As far as I know, this is not completed yet
17:07:27 <decause> jflory7: not yet
17:07:42 <jflory7> decause: Want to take that one on with the info you picked up from Config Management Camp?
17:07:51 <decause> #action decause create an onboarding series ticket on commops trac for Fedora Infra, based on cfgmgmtcamp slide deck
17:07:55 <jflory7> decause++
17:07:56 <decause> jflory7: on it
17:07:56 <linuxmodder> decause, ah ok
17:08:02 <jflory7> #info * [In Progress] decause post Grand Unified Year In Review article to Announce List when we have a link
17:08:10 <jflory7> This is an ongoing task, dependent on getting more YiRs
17:08:15 <jflory7> We need to talk about that today too
17:08:20 <decause> #link https://github.com/decause/decks/blob/master/cfgmgmtcamp-fedoraopeninfra.pdf
17:08:20 <jflory7> But a little bit later on
17:08:31 <jflory7> #info * [Complete] commops review WiTNY draft to publish this week
17:08:36 <jflory7> #info * [Complete] decause close commops proposal ticket on trac for flock
17:08:45 <jflory7> #info * [Complete] jflory7/decause ping tatica with an email and see how she is doing (info in Ticket #17)
17:08:50 <keekri> there's a commops join page thing from the last time but we could take it up during the wiki gardening.
17:08:56 <jflory7> #info * decause dig up link for g11n devconf talk
17:09:04 <decause> keekri: agreed
17:09:06 <decause> wiki gardening
17:09:11 <jflory7> keekri++ Yes, that is an excellent topic for wiki gardening! I want to hit on that too
17:09:21 <jflory7> decause: Do you want to find that and link to it on the ticket?
17:09:33 <jflory7> This ticket is also on today's agenda
17:10:22 <nb> wikis can always use gardening :)
17:10:26 <decause> #link https://www.youtube.com/watch?v=xEHa0nDjJvg
17:10:31 <decause> #info g11n talk
17:10:33 <nb> do we need more people able to prune old pages?
17:10:37 <jflory7> nb++ :)
17:11:09 <jflory7> nb: As for pruning old pages, I think that's part of a larger task we want to complete in F24 cycle or so.
17:11:15 <jflory7> Or at least an initiative of sorts to get going
17:11:22 <jflory7> I'll link you to the ticket in a bit :)
17:11:24 <decause> nb: I think there will be a wiki vFAD at some point in the future
17:11:26 <jflory7> Moving ahead with action items:
17:11:28 <jflory7> #info * [Complete] jflory7 Update Ticket #29 with DevConfCZ discussion info
17:11:33 <jflory7> #info * [Complete] jflory7 File a new ticket for Google Summer of Code internship planning
17:11:37 <jflory7> #info * [Complete] decause close ticket #36
17:11:38 <keekri> nb++
17:11:38 <zodbot> keekri: Karma for nb changed to 16 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:11:41 <jflory7> #info * [Complete] jflory7 Create ticket for CommOps Workshop agenda planning
17:11:46 <jflory7> #info * decause follow-up on brickhack sponsorship after Ruth gets back from PTO due:2/19
17:11:51 <jflory7> decause: Want to hit on this today? ^
17:11:57 <decause> jflory7: she's not back yet
17:12:15 <decause> jflory7: we'll talk more at hackfest
17:12:18 <jflory7> Oh, right -- we can maybe talk about some of the strategic planning anyways?
17:12:21 <jflory7> Sounds good to me +1
17:12:26 <decause> I pinged all the sponsorship loops yessterday with spot
17:12:33 <jflory7> #action jflory7 / decause Discuss BrickHack details later today
17:12:43 <jflory7> #info * [Complete] jflory7 Share preliminary thoughts on CommOps Join process with the mailing list to get some discussion going, cc: bee2502, keekri, and decause
17:12:50 <jflory7> #info * decause draft for FOSDEM event report due:2/19
17:12:54 <jflory7> #info * decause draft for DevConf event report due:2/19
17:12:59 <jflory7> #info * decause draft for FedoraOpenInfra (cfgmgmtcamp) due:2/19
17:13:17 <jflory7> decause: Some other reports for the upcoming week?
17:13:27 <jflory7> I don't see a need to have all three done by Friday but one this week would be nice
17:13:28 <decause> ummm... those *four* will likely be eenough ;)
17:13:37 <linuxmodder> Workshop being  centered on ?
17:13:41 <decause> drafts first, publish sched later
17:13:46 <linuxmodder> sorry also in the server retooling  mtg
17:13:59 <decause> jflory7: I have a mandate to release event reports earlier
17:14:17 <jflory7> decause: Ahhh, I see. Want to re-action them to your deadline(s)?
17:14:34 <decause> linuxmodder: the workshop will be a place where we can powow with other teams at Flock who want to interface with commops.
17:14:39 <decause> this could take any number of forms
17:14:43 <jflory7> linuxmodder: The Flock Workshop?
17:14:44 <decause> we'll know more as we get closer
17:14:58 <jflory7> decause: Gotcha. We can revisit as necessary then
17:15:01 <decause> don't want to set it in stone now
17:15:02 <linuxmodder> jflory7,  +1 for that and  hacking on that later
17:15:04 <jflory7> #info * [Complete, thanks cprofitt!] jflory7 Create a ticket to have a full discussion about our on-boarding process and looking ahead to gaining new contributors while being mindful of different factors that might raise the contributing barrier
17:15:05 * mailga still busy but taking a glance...
17:15:10 <jflory7> #info * [Complete] danofsatx Shoot an email to the mailing list about CommOps shirts (!!!)
17:15:21 <jflory7> That's all leftover action items. Now onto tickets
17:15:26 <jflory7> #topic Tickets
17:15:30 <jflory7> #link https://fedorahosted.org/fedora-commops/report/9
17:15:33 <decause> TIMECHECK: we're about 25% of the way through the hour
17:15:38 <jflory7> #info === Ticket #17 - https://fedorahosted.org/fedora-commops/ticket/17 ===
17:15:44 <jflory7> #info * "Interview Fedora's Diversity and Inclusion Advisor, tatica"
17:15:51 <jflory7> Can we finish this today or tomorrow?
17:15:57 <decause> jflory7: tatica will be back on the grid starting next week
17:16:01 <decause> I just talked with her today
17:16:09 <jflory7> linuxmodder: Sounds good to me. There is also a ticket for the Flock workshop in our Trac. :)
17:16:21 <jflory7> mailga: Welcome! We're just getting into tickets, so you're not too late :)
17:16:29 <decause> mailga: welcome back
17:16:40 <jflory7> decause: Acknowledged. We'll aim tentatively for next week.
17:16:51 <bee2502> Hi
17:16:55 <decause> bee2502: welcome welcome
17:17:02 <decause> .hello bee2502
17:17:03 <zodbot> decause: bee2502 'Bhagyashree Padalkar' <bhagyashree.iitg@gmail.com>
17:17:09 <bee2502> I hope i am not too late
17:17:14 <keekri> bee2502: Hey!
17:17:15 <decause> you're here for tickets
17:17:15 <bee2502> *I
17:17:25 <jflory7> #agreed tatica will be fully back next week, so decause will ship the email announcing tatica's position to the announce mailing list sometime next week
17:17:30 <bee2502> Hii keekri
17:17:31 <jflory7> bee2502++ You're in good time! :)
17:17:39 <jflory7> #info === Ticket #29 - https://fedorahosted.org/fedora-commops/ticket/29 ===
17:17:43 <jflory7> #info * "G11n - proposal for the group revitalization"
17:17:48 <jflory7> Did we want to have any follow-up on this ticket?
17:18:00 <jflory7> We mentioned we wanted to a quick check-in this week for any new details
17:18:10 <jflory7> ETA for this ticket is March 22nd
17:18:10 <decause> jflory7: yes. fale and pravins likely have some screenshots from our deconf session
17:18:22 <decause> of the whiteboard
17:18:27 <decause> screenshot = pics
17:18:44 <jflory7> Awesome.
17:18:54 <jflory7> Going to link that video here too, for relevancy
17:18:56 <jflory7> #link https://www.youtube.com/watch?v=xEHa0nDjJvg
17:19:00 <decause> nod nod nod
17:19:05 <decause> pravin's talk was really good
17:19:14 <decause> great intro to the various moving parts
17:19:45 <decause> next
17:19:48 <jflory7> So I guess our current status on this is to continue collecting artifacts for the article and addressing on-boarding process, e.g. talks, pictures, videos, etc.? And on track is to be published by March 22nd?
17:20:17 <decause> jflory7: we'll set an actual organizing meeting for next week (2/22 will be one month out)
17:20:23 <decause> let's set an action item for that
17:20:47 <decause> #action decause/fale/pravins schedule a g11n vFAD organizing meeting for 2/22 or nearby
17:21:00 <jflory7> #agreed We will begin organizing this process at our next meeting, Feb. 23 -- more details next week
17:21:08 <jflory7> #info === Ticket #37 - https://fedorahosted.org/fedora-commops/ticket/37 ===
17:21:13 <jflory7> #info * "Making a "Join" series on the wiki"
17:21:18 <jflory7> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/BEIBVIIFGUOH3L32YSHFEDMO7IDGQOB5/
17:21:22 <jflory7> Take a look at the 6-step process proposed in the ticket. Any proposed modifications, additions, or deletions in the process? Is it good to ship?
17:21:35 <jflory7> For clarification, this is about our *own* Join process :)
17:21:44 <bee2502> Jflory7 awesome work on join process
17:21:50 <jflory7> There was some discussion about this on the mailing list, and that thread is linked above
17:21:53 <keekri> I have some points on that
17:21:54 <bee2502> jflory7++
17:22:00 <keekri> jflory7++
17:22:06 <decause> jflory7: I would add a 7) Acquire the Onboarding Badges series?
17:22:13 <jflory7> bee2502: Thanks, feel free to add any thoughts you have too :)
17:22:19 <jflory7> keekri: Sure, what do you think?
17:22:25 <keekri> True. decause++
17:22:32 <jflory7> decause: Hmmm, do we want that now or later? Or do we just want to link to the Trac ticket?
17:22:34 <decause> gotta check deeply and see what overlaps there are with the badges and the steps
17:22:48 <jflory7> It would be awesome to get this badge approved, it seems like badges are a little bit behind
17:22:53 <decause> jflory7: we need to make it "official" and get the badge approved
17:23:11 <decause> jflory7: I have a 'mockup' and a concept, but I'm not sure if it will pass muster
17:23:13 <keekri> Well, when I started working on this, I had checked out the main join page and there's no peep of commops there.
17:23:17 <jflory7> decause: Any idea on how we could raise the priority of that badge?
17:23:37 <jflory7> keekri: We definitely need to get ourselves on the global Join page too.
17:24:08 <decause> #link http://imgur.com/xaLivtn
17:24:16 <bee2502> jflory7 decause can we add CommBlog in CommOps join process somehow ?
17:24:35 <jflory7> heheh, I like it
17:24:39 <decause> bee2502: maybe. I think that raises the barrier to entry a lil bit higher
17:24:47 <keekri> So I'd like to bring issue to the forefront too. In fact, I felt that the intro pages of multiple fedora subsections needed to be updated.
17:24:52 <jflory7> bee2502: Maybe just registering on the CommBlog and adding info to your bio?
17:24:58 <decause> not going to get into the badge concept now
17:25:15 <decause> bee2502: the planet addition piece counts for that mostly
17:25:27 <keekri> Like, the design team still has 'artwork' as their title in the join page.
17:25:53 <decause> keekri: yeah, updating other team's join pages would be a great thing for wiki gardening tasks
17:26:03 <decause> keekri: perhaps we can open another ticket on commops trac?
17:26:09 <bee2502> decause I see
17:26:12 <jflory7> keekri: We could probably look at adding clean-up of Join pages to a ticket too. I saw in the video mattdm linked last night / this morning that the QA team also issued a call for #help on their Wiki
17:26:17 <jflory7> * on their wiki Join page
17:26:27 <keekri> Exactly, that's why I had gone for wiki gardening earlier.
17:26:37 <decause> jflory7: whenever we see #help like that, we can def add a ticket
17:26:59 <decause> keekri: you wanna take an action item to open a ticket for that?
17:27:24 <nb> jflory7, decause i added you two to pruners on the wiki
17:27:33 <decause> TIMECHECK: we're almost half-way through meeting block
17:27:38 <keekri> jflory7: How would that ticket look like ?
17:27:39 <jflory7> In regards to this current ticket, I do like the idea of maybe adding registering on the CommBlog as a requirement to be approved to the FAS group
17:27:50 <keekri> What's the scope of that ?
17:27:54 <decause> keekri: we can help you after the meeting :)
17:27:57 <jflory7> keekri: If you want, I can help guide you through that after the meeting in #fedora-commops? :)
17:28:12 <decause> something like "Update Join pages for other subprojects" woudl be the title, with a bullet list to links for other join pages
17:28:13 <keekri> Cool. That would be great, thanks!
17:28:16 * mailga still thinks that without a "go" from other groups we can't do anything. We shall come back to the fed-join SIG idea for merge join pages of each group.
17:28:26 <jflory7> nb: Awesome -- you'll have to explain the context of that to me after the meeting. :)
17:28:36 <keekri> mailga++
17:28:36 <zodbot> keekri: Karma for mailga changed to 9 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:28:58 <decause> mailga: we would *absolutely* want to include the subproject in a request for feedback, but the beauty of the wiki is that rollbacks are easy
17:29:07 <jflory7> For Ticket #37: 6-step process + registering on the CommBlog + link to the on-boarding badge Trac ticket (?)
17:29:23 <jflory7> Why don't we do a +1 / -1 vote on that, actually? Let me make a #proposed
17:29:30 <nb> jflory7, it gives you permission to delete pages on wiki
17:30:02 <keekri> #action keekri open a ticket for updating join/intro pages in the wiki
17:30:02 <decause> kk
17:30:05 <jflory7> #proposed For our Join process, we will use the 6-step process described in the email thread, add registering on the CommBlog, and link to the on-boarding badge Trac ticket
17:30:08 <jflory7> +1
17:30:26 <jflory7> nb: Okay, cool, I see -- thanks! nb++
17:30:33 <keekri> Is that ok?
17:30:38 <jflory7> keekri: Perfect :)
17:30:45 <decause> +1
17:30:47 <bee2502> +1
17:31:10 <jflory7> Going once--
17:31:15 <jflory7> Going twice--
17:31:25 <jflory7> Going thrice--
17:31:32 <jflory7> #agreed For our Join process, we will use the 6-step process described in the email thread, add registering on the CommBlog, and link to the on-boarding badge Trac ticket
17:31:32 <keekri> sold! :D
17:31:35 <jflory7> Next ticket
17:31:42 <jflory7> #info === Ticket #38 - https://fedorahosted.org/fedora-commops/ticket/38 ===
17:31:47 <jflory7> #info * "Onboarding Process Discussion"
17:31:50 <jflory7> Discussed briefly last week during Open Floor - please look at the proposed solutions in the ticket. Should we consider pursuing any of these? Any other new ideas?
17:32:02 <decause> #action decause update onboarding (bootstrapping) ticket on fedora-badges trac. add concept proposal...
17:32:24 <MarkDude> Making Fedora-Join a thing, and not just a link to wiki, used to be shinier :)
17:32:34 <jflory7> The proposed solutions are: CommOps mentors, bulking down our meetings, having major decisions being voted on in tickets.
17:33:29 <decause> I'm def +1 on ticket votes
17:33:30 <linuxmodder> mtg attendance is surely a  lax thing atm I'd personally  like to see us  get a bit tighter on that group wide
17:33:43 <linuxmodder> ticket votes are great idea
17:33:48 <decause> folks made a good point about not everyone being able to make the meetings
17:33:56 <jflory7> I'm +1 on ticket votes too. Whenever we need to make a decision, the ticket link should be sent out to the list and given maybe a 48 hour window for being voted on?
17:33:59 <decause> this is how we do it in council land
17:34:00 <linuxmodder> also makes it  more streamlined with other subs
17:34:18 <decause> we do "lazy consensus" in council land as well
17:34:23 <decause> which is kinda nice
17:34:26 <bee2502> Ticket votes +1 but not sure about cutting down on meetings
17:34:29 <jflory7> decause: Can you elaborate a bit there?
17:34:33 <decause> sure
17:34:45 <decause> folks can vote +1, or +0 or -1
17:34:59 <decause> if no one votes -1, it is assumed that everyone agrees
17:35:03 <linuxmodder> the meetings part i was getting at is  at least 50% mtgs / month  to stay active status
17:35:07 <decause> it avoids the need for quorum, which is helpful
17:35:18 <keekri> agree with the tickets
17:35:26 <decause> if someone votes -1, discussion ensues
17:35:32 <jflory7> linuxmodder: My concern with that is if someone has a hard time conflict with a meeting time
17:35:33 <linuxmodder> jflory7,  same way we do in famNA
17:35:36 <mailga> IMHO ticketing approval in ML has to be the last chance. Tickets must be approved in meetings. If someone has interest in a ticket he should attend.
17:36:05 <linuxmodder> jflory7,  valid  but you generally know of those in time to alert the team no?
17:36:19 <jflory7> decause, mailga: So when we come to a point where we need to make a decision, how about lazy consensus with a 24 or 48 hour window?
17:36:23 <linuxmodder> mailga,  +!
17:36:33 <decause> 48 is a good window, max 72
17:36:45 <jflory7> Okay, let's make a #proposed here
17:36:48 <keekri> 48 is ok.
17:36:49 <jflory7> Oh, wait--
17:36:49 <linuxmodder> 72 is a bit long for most imo 48 is nice
17:36:58 <jflory7> What are the thoughts on mentors?
17:37:04 <mailga> 48 is good for me.
17:37:06 <jflory7> Maybe a bit too soon for that, I think?
17:37:10 <linuxmodder> who are current mentors ?
17:37:13 <jflory7> I don't see us at a size where having mentors is super effective
17:37:17 <jflory7> linuxmodder: None, it was just an idea
17:37:23 <decause> right now, pretty much everyone is a mentor
17:37:26 <decause> :)
17:37:26 <jflory7> yeah ^
17:37:28 <keekri> mentors might be difficult to implement
17:37:37 <keekri> true dat :)
17:37:42 <linuxmodder> jflory7,  setup the plugs now easier later to scale
17:37:48 <jflory7> Okay, so now let me form a #proposed:
17:38:32 <jflory7> #proposed To help make on-boarding into CommOps easier, for making key decisions, we will use lazy consensus votes in our Trac tickets, with a 48 hour deadline after notifying the mailing list about the vote
17:38:35 <jflory7> +1
17:38:44 <decause> +1
17:38:59 <bee2502> +1
17:39:06 <keekri> +1
17:39:15 <jflory7> Going once--
17:39:20 <jflory7> Going twice--
17:39:28 <jflory7> Going thrice--
17:39:31 <linuxmodder> +1
17:39:35 <jflory7> #agreed To help make on-boarding into CommOps easier, for making key decisions, we will use lazy consensus votes in our Trac tickets, with a 48 hour deadline after notifying the mailing list about the vote
17:39:39 <jflory7> Next ticket
17:39:44 <jflory7> #info === Ticket #39 - https://fedorahosted.org/fedora-commops/ticket/39 ===
17:39:48 <jflory7> #info * "CommOps and Google Summer of Code"
17:39:51 <jflory7> Approaching deadline alert! What needs to happen ASAP?
17:39:56 <jflory7> Proposal deadline is this Friday!
17:40:17 <linuxmodder> and coding starts in mid may iirc
17:40:22 <keekri> Wow, who's doing that? Do you need some help?
17:40:22 <jflory7> Right.
17:40:35 <jflory7> In order for us to get in on this, Fedora has to have proposed projects in by Friday
17:40:35 <linuxmodder> do we have a solid  structure for a gsoc project tho?
17:40:39 <jflory7> Not sure if decause has more info on this
17:40:49 <jflory7> linuxmodder: We were planning on rewording Outreachy projects a bit
17:40:53 * decause has updates yes
17:40:57 <jflory7> linuxmodder: They needed to be reworded to be more code-oriented
17:41:04 <jflory7> decause: Sure!
17:41:04 <decause> we have until 2/19 to get our organization applied for
17:41:15 <decause> I've been working with OSAS to identify GSoC admins and mentors
17:41:23 * danofsatx is here
17:41:24 <decause> we need at least 3, and we think we have them
17:41:32 <jflory7> danofsatx++ welcome :)
17:41:34 <decause> this is an item for tonight's hacksesh
17:41:56 <jflory7> Cool. So I see us finalizing the proposed CommOps slot for GSoC tonight then?
17:41:57 <linuxmodder> what hard params do we have for admins | mentors?
17:42:03 <jflory7> As a hard deadline?
17:42:10 <decause> jflory7: yes, among other slots too if we can find them
17:42:38 <decause> the kernel slot will not be a GSoC proposal though (I don't think)
17:42:41 <jflory7> Cool. Works for me.
17:42:46 <linuxmodder> I'm down for mentoring on the outreachy stuff as is (and assumed mods to be  code oriented)
17:42:49 <jflory7> Yeah, it was approved for Outreachy
17:42:53 <jflory7> Makes sense for no kernel slot
17:42:56 <bee2502> What slot is going to open for gsoc ? CommOps ?
17:43:01 <jflory7> I think CommOps + Hubs
17:43:07 <decause> bee2502: that is the plan for now, but we gotta rework it a bit
17:43:15 <jflory7> Lemme find the link
17:43:15 <decause> and Hubs, yes, but that also needs to be reworked
17:43:36 <jflory7> #link https://fedoraproject.org/wiki/Outreachy/2015#Project_List
17:43:37 <linuxmodder> what about hubs need swork?
17:43:37 <decause> threebean will likely not be able to mentor for hubs this summer
17:43:51 <bee2502> Adding Hubs and badges would be great
17:43:51 <decause> linuxmodder: there is a proposed projects for outreachy link in the wiki
17:44:07 <decause> bee2502: badges is a design-oriented projet, and would not fit hubs :/
17:44:12 <decause> err, fit GSoC
17:44:34 <jflory7> Actually, scratch that earlier link
17:44:35 <jflory7> #undo
17:44:35 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0xb900950>
17:44:38 <jflory7> #link https://fedoraproject.org/wiki/Outreachy/2016_potential_projects
17:44:44 <decause> jflory7: that's the one, yeah
17:44:44 <jflory7> There's the most recent copy of the slots
17:44:46 <decause> jflory7++
17:44:53 <keekri> Actually, outreachy allows design projects...
17:44:59 <decause> and, there have been some updates to the Hubs slot now too as of today
17:45:07 <jflory7> keekri: Outreachy does, but not GSoC to my understanding :(
17:45:23 <bee2502> decause -  I meant something like metrics or what badge to get next ? Etcv
17:45:27 <keekri> Yup, just Outreachy.
17:45:39 <decause> bee2502: that would be part of the GSoC slot I reckon, yeah
17:45:49 <jflory7> 15 time warning (this is our last ticket worth noting)
17:45:56 <jflory7> * 15 minute
17:45:57 <MarkDude> ALL of these thing- or at least most are being done by ITG in Philippines.
17:45:58 <decause> bee2502: we're going to be drawing heavily upon the outreachy plan of work
17:46:04 <keekri> jflory7: Need any help with the description rewriting ?
17:46:09 <MarkDude> On 2016 outreach, they've done so for years
17:46:16 <decause> MarkDude: ITG? things?
17:46:30 <jflory7> I think decause has a few plans that will be hashed out tonight.
17:46:37 <MarkDude> The group in PH that has potential more Fedorans, and does Outreach
17:46:38 <jflory7> In the interest of time, I'm going to make a proposal:
17:46:44 <decause> keekri: yeah, we're going to do a session later tonight 4pm-7pm EST with hangouts to work on lots of tickets/things
17:47:07 <decause> keekri: i realize that is probably a bit late for you and bee2502 though :/
17:47:08 * MarkDude will have mic for then, and some links :) eof
17:47:16 <decause> we'll have to pick an earlier slot later this week maybe
17:47:16 <keekri> jflory7: 4pm? Oh noes..
17:47:20 <linuxmodder> decause,  scratch b/j  I'll use chrome if needed tonight
17:47:34 <linuxmodder> keekri, conflict?
17:47:44 <decause> linuxmodder: it'll be quite late for her ;)
17:47:46 <keekri> With my sleep, yeah...
17:47:51 <decause> keekri++
17:47:51 <jflory7> #proposed GSoC deadline is Friday, Feb. 19th; tonight, from 21:00 - 23:00 UTC, there will be a Hangout session to collaborate on wrapping up on the slots and other things. GSoC slots need to be finished ASAP.
17:47:57 <keekri> :D
17:48:04 <decause> +1
17:48:04 <linuxmodder> +!
17:48:08 <jflory7> +1
17:48:14 <keekri> +1
17:48:16 <bee2502> +1
17:48:22 <jflory7> (Of course, updates post-session will be shared with the list)
17:48:26 * MarkDude is willing to proxy anything bee2502 needs. We agree on a fair amount. You can be their with your words (via me)
17:48:26 <bee2502> Time though :(
17:48:34 <jflory7> Going once--
17:48:36 <MarkDude> +1
17:48:38 <linuxmodder> I may be a bit late ---430ish
17:48:42 <jflory7> Going twice--
17:48:46 <jflory7> Going thrice--
17:48:51 <decause> no worries, we'll have plenty to do
17:48:51 <jflory7> #agreed GSoC deadline is Friday, Feb. 19th; tonight, from 21:00 - 23:00 UTC, there will be a Hangout session to collaborate on wrapping up on the slots and other things. GSoC slots need to be finished ASAP.
17:48:52 <MarkDude> sp their/ there
17:49:01 <bee2502> MarkDude++
17:49:01 <zodbot> bee2502: Karma for markdude changed to 3 (for the f23 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
17:49:01 <jflory7> #topic Wiki Gardening
17:49:10 <jflory7> #nick NewMembers
17:49:11 <jflory7> #action NewMembers Add your timezone / interests on CommOps Wiki [ https://fedoraproject.org/wiki/CommOps ]
17:49:17 <jflory7> #help The Fedora QA team asked for help in improving their Join page to highlight the ways a non-code contributor can help with QA
17:49:37 <jflory7> keekri already has an #action filed for this ^
17:49:48 <linuxmodder> jflory7,  I can stab at the QA bit this week
17:49:51 <jflory7> Any other wiki gardening topics?
17:50:00 <jflory7> linuxmodder: Awesome! We'll get you CC'd on the ticket for sure :)
17:50:04 <keekri> Yup, although, that's general, I didn't specify QA
17:50:16 <jflory7> keekri: Right.
17:50:20 <jflory7> Wiki gardening, going once--
17:50:24 <decause> keekri: yeah, we need a ticket for *all* the join pages
17:50:25 <jflory7> Going twice--
17:50:35 <jflory7> Going thrice--
17:50:36 <decause> jflory7: will work it out with you after this meeting
17:50:42 <keekri> Sure.
17:50:48 <jflory7> #topic Community Blog
17:50:55 <jflory7> decause: acknowledged
17:51:03 <jflory7> Okay, here comes a few stats really fast, hold on tight :)
17:51:08 <jflory7> #info === This Week in CommBlog ===
17:51:11 <jflory7> #info * "Fedora Infrastructure - Year in Review"
17:51:16 <jflory7> #link https://communityblog.fedoraproject.org/infrastructure-year-in-review/
17:51:20 <jflory7> #info Total Views (Feb. 09 - Feb. 16): 58
17:51:24 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=990
17:51:28 <jflory7> #info * "WiTNY 2016: Event Report"
17:51:32 <jflory7> #link https://communityblog.fedoraproject.org/witny-2016-event-report/
17:51:37 <jflory7> #info Total Views (Feb. 15 - Feb. 16): 35
17:51:41 <jflory7> #link https://communityblog.fedoraproject.org/wp-admin/admin.php?page=stats&view=post&post=983
17:51:49 <jflory7> sorry again about this one decause :P
17:51:50 <jflory7> #info === Coming Up in CommBlog ===
17:51:54 <jflory7> #info * "Campus Ambassadors Initiative"
17:51:59 <jflory7> #link https://communityblog.fedoraproject.org/?p=759&preview=1&_ppp=335b600284
17:52:05 <jflory7> #info * In drafts: "I contributed ! 2015 Fedora Contributions Video using Gource(fedmsg2gource?)", "Fedora Server Working Group discusses minimal installs"
17:52:16 <jflory7> And that's all for CommBlog on the agenda.
17:52:28 <jflory7> Anything else to add here?
17:52:35 <jflory7> Bulking up our publishing schedule would be nice
17:52:46 <jflory7> decause: If we could ship one event report this week, that would be nice
17:52:54 <jflory7> And actually, we need to do some follow-up on YiRs...
17:52:55 <decause> jflory7: agreed
17:53:03 <jflory7> Not nearly as many as I hoped would be in yet :(
17:53:06 <linuxmodder> Server was planning to have some guides ready  for highlight on blog  iirc  next week ?
17:53:24 <jflory7> I know FPC, FESCo, Docs, and I think one or two others I pinged about it, so they might have something started
17:53:27 <linuxmodder> Server YiR among those  docs  /guides
17:53:34 <jflory7> linuxmodder: That would be so awesome to have
17:53:50 <jflory7> I think we need to do some follow up on FPC and FESCo
17:53:59 <linuxmodder> today was all retooling demo stuff but  was mentioned in yesterdays mtg
17:54:01 * decause should probably do something for council also
17:54:06 <jflory7> Docs YiR was assigned to bexelbie but he wasn't at the meeting where it was assigned to him
17:54:15 <jflory7> At this point, though, we really need to expedite these
17:54:19 <linuxmodder> I'll  probe again in server if it goes cold
17:54:24 <decause> bex has been *quite* busy with Europe too
17:54:28 <jflory7> I think we're pushing relevancy if we wait around much longer
17:54:43 <decause> agreed
17:54:43 <jflory7> decause: Understandably so -- maybe we could see if he could get something drafted late this week or early next
17:54:58 <decause> I think we just need to get some sync responses in the form of bullet points, and fill in our own
17:55:11 <jflory7> Hmmm?
17:55:30 <jflory7> Oh, you mean we write them with information provided?
17:55:31 <decause> I think asking in IRC channels for answers, and writing them down in real-time is the fastest way to get this answered
17:55:37 <jflory7> Yeah, me too
17:55:42 <decause> having truly "bare bones" YiR posts
17:55:49 <linuxmodder> I'd say past next friday let it drop off due to relevance
17:55:51 <jflory7> Want to discuss this in the hack-session or in the channel after meeting?
17:56:02 <linuxmodder> sure
17:56:04 <decause> 3 highlights, one goal, one intro paragraph about what team does (based on wiki description)
17:56:05 <jflory7> linuxmodder: Past Feb. 29th, I say no more too
17:56:13 <jflory7> Minus our final "2015 in Review" one
17:56:25 <decause> GUYIR should be posted on 2/29
17:56:30 <jflory7> decause: +1
17:56:35 <jflory7> In interest of time, here's a quick proposal:
17:56:48 <linuxmodder> that's  60 days to reflect  none of our subs are that busy or undeerstaffed to be unable to do it in that time
17:56:51 <linuxmodder> imo at least
17:57:03 <decause> seems reasonable to me too
17:57:13 <decause> we're at 3 mins
17:57:16 <jflory7> #proposed Come up with a quick action plan for finalizing on YiR articles this week or early early next week. ETA for the "2015 in Review" article is Feb. 29th.
17:57:17 <jflory7> +1
17:57:27 <linuxmodder> +!
17:57:31 <decause> +1 (at hack session tonight)
17:57:37 <jflory7> Whoops, right, will append
17:57:39 <linuxmodder> earlier  preferred but  NLT 2/29
17:58:00 <jflory7> Going once--
17:58:03 <MarkDude> Short videos to point to blog/posts/magazine seems to make sense- this video will point to my interview with Magazine. Under 2 minutes is a thing these kids under 35 want I hear https://www.youtube.com/watch?v=NZzJUyc6wtI
17:58:05 <jflory7> Going twice--
17:58:15 <jflory7> Going thrice--
17:58:20 <jflory7> #agreed Come up with a quick action plan for finalizing on YiR articles this week or early early next week during tonight's hack session. ETA for the "2015 in Review" article is Feb. 29th.
17:58:24 <linuxmodder> under 30 more like it
17:58:26 <jflory7> And open floor
17:58:28 <jflory7> One topic here
17:58:29 <jflory7> #topic Open Floor
17:58:33 <jflory7> #info === commopsbot ===
17:58:37 <jflory7> #link https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/YD2ZBB3YJTVWNYJD7U4UMS3J2R7K6RBJ/
17:58:50 <decause> #info Hangout'n'hack session tonight from 4pm-7pm EST
17:58:51 <jflory7> There was a lot of discussion in this thread about making two CommOps IRC channels
17:59:10 <jflory7> #info ^ 21:00 - 23:00 UTC for others :)
17:59:42 <jflory7> I personally am +1 to separating the fedmsg notifications in #fedora-commops into a second channel, e.g. #fedora-commops{watch,bot}
17:59:49 * decause is -1 on an additional channel
18:00:03 <jflory7> I think it might be better to reduce the chatter in the main channel then
18:00:06 <decause> we can turn down the volume on the bot, but having another channel defeats the purpose of the notifications
18:00:14 <mailga> two channels are a bit confusing.
18:00:34 <decause> it's already hard with #outreachy and #join and #ambassadors and #mktg all being separate
18:00:50 <decause> nb: we can turn down the notifications though
18:00:57 <bee2502> We should prolly turn down the added to cla groups
18:00:58 <jflory7> I think the fedmsg notifications are useful, but in their current form, they can be counter-productive to conversation. I anticipate this will be more noticeable as we continue to grow
18:01:22 <jflory7> bee2502: Yeah... that's related to another issue. Lots of spambots in the past 48 hours. puiter wijk and the Infra team are fighting them off right now.
18:01:33 <decause> bee2502: the cla_groups is our "growth" metric. perhaps we can get a "tally" at the end of the day, or something?
18:01:50 <decause> ouch...
18:01:51 <jflory7> bee2502: A tally in a static location sounds good to me, but that metric might be skewed for the unforeseen future
18:02:02 <decause> we can turn it down for now
18:02:07 <jflory7> Yeah
18:02:08 <decause> I *really* liked it when I was at FOSDEM for example
18:02:14 <bee2502> Hmm - yes I agree on the tally
18:02:23 <decause> I could see when someone logged into badges for the first time, based on event tabling
18:02:30 <jflory7> I think turning off Planet posts might be a good idea too... I like having them personally but they can be noisy and it fills up the scrollback
18:02:40 <jflory7> If we want to see what's new, we can check the Planet
18:02:41 <decause> it was helpful for me to say to ambassadors "hey I counted 27 people who signed up for FAS"
18:02:45 <decause> but that is noisey, yes
18:03:07 <decause> ok, I can deal with planet posts going elsewhere also
18:03:09 <jflory7> Maybe we pick up on the mailing list with a list of hooks to disable and discuss from there?
18:03:27 <jflory7> And do a vote in a ticket as per the voting method described earlier?
18:03:30 <decause> jflory7: yeah, let's take it back to the list
18:03:51 <jflory7> #action jflory7 Add information about the voting process discussed in today's meeting to the wiki and share with the list for posterity's purpose
18:03:52 <decause> we're 3 over now
18:03:54 <decause> anything else?
18:04:01 <jflory7> Nothing from me personally.
18:04:19 <decause> kk
18:04:28 <decause> I'll see some ofyou folks later for hacksessoin
18:04:30 <decause> session*
18:04:33 <decause> jflory7++
18:04:36 <linuxmodder> dropped a wordfence  blog post in -commops
18:04:40 <decause> thanks for chairing
18:04:52 <linuxmodder> about  pass attacks (brute forces)
18:05:03 <decause> linuxmodder: nod nod
18:05:05 <jflory7> my pleasure, good to have you back (officially) now, decause :)
18:05:08 <decause> :)
18:05:13 <decause> gavel us out?
18:05:16 <jflory7> #endmeeting