18:00:41 #startmeeting Council (2017-01-16) 18:00:41 Meeting started Mon Jan 16 18:00:41 2017 UTC. The chair is mattdm. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:41 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:41 The meeting name has been set to 'council_(2017-01-16)' 18:00:43 #meetingname council 18:00:43 The meeting name has been set to 'council' 18:00:45 #chair mattdm jkurik jwb langdon robyduck tatica bexelbie 18:00:45 Current chairs: bexelbie jkurik jwb langdon mattdm robyduck tatica 18:00:47 #topic Introductions, Welcomes 18:00:55 .hello bex 18:00:56 bexelbie: bex 'Brian (bex) Exelbierd' 18:01:06 good $TIMEOFDAY, everyone! 18:01:19 .hello jkurik 18:01:19 jkurik: jkurik 'Jan Kurik' 18:02:01 i'm about to hop on a call. definitely won't be attending today unfortunately. maybe you could discuss shifting the time an hour later or something 18:02:22 jwb: Yeah, plan is to reschedule meeting entirely after today's election concludes 18:02:51 .hello langdon 18:02:52 langdon: langdon 'Langdon White' 18:03:00 jwb: can you check the logs and vote in ticket after? 18:03:27 * mattdm waits a few minutes to see if robyduck is around 18:04:07 .hello robyduck 18:04:08 robyduck: robyduck 'Robert Mayr' 18:04:54 excellent 18:05:00 #topic Agenda 18:05:08 I've picked out these tickets: 18:05:12 1. Trademark approval for LXQt spin 18:05:14 2. Budget Reallocation (FADs and FUDCons) 18:05:16 3. Reimbursement issues 18:05:18 4. PRDs and overall strategy 18:05:54 2 and 3 will be fast 18:06:45 does anyone have anyhting else to add? 18:07:03 nope 18:07:18 ok let's go :) 18:07:20 umm 18:07:23 one, maybe 18:07:30 langdon? 18:07:40 "council get together in brno" if we have greater than 3-4 people? 18:07:55 robyduck, will you be there? 18:08:19 mattdm: that depends if I will be still Council member or not 18:08:38 robyduck: oh yeah, good point. :) 18:08:45 ;) 18:08:54 So, depending on election outcome, we will have more than 4 18:09:04 okay I'll put this as agenda item #5. 18:09:12 #topic Trademark approval for LXQt spin 18:09:14 #link https://pagure.io/Fedora-Council/tickets/issue/84 18:09:53 This has several plus ones in ticket. It seems non-controversial. 18:10:05 I'm going to call for a 3-day lazy consensus. Sound good? 18:10:12 I am +1 (for the record) 18:10:50 +1 the lazy conensus 18:11:24 +1 for me too, but this will involve many other teams too, once we have the trademark approval 18:11:56 robyduck: yeah, this is just the trademark approval part. 18:11:59 okay next topic :) 18:12:04 #topic Budget Reallocation (FADs and FUDCons) 18:12:05 #link https://pagure.io/Fedora-Council/tickets/issue/83 18:12:07 bex go :) 18:12:29 I haven't made a huge amount of progress - mechanical budget work has taken longer than hoped 18:12:39 I have the data collected for analysis on the policy 18:12:42 just need to have time 18:12:47 btw.. mattdm don't you have 3 +1s on the spin ticket? 18:13:06 langdon: yeah but needs to be no -1s and jwb still could come along and nix it 18:13:11 or tomorrow's new council member 18:13:11 on the alternative methods, I have been testing them and so far no troubles 18:13:22 mattdm, ohh.. right.. totally.. language was just a little confusing 18:13:25 Again, just needs policy work 18:13:31 langdon: sorry 18:14:08 bexelbie: wait, I think you're ahead of the agenda 18:14:20 this is the "move fad money around" thing 18:14:21 mattdm, i think i was just behind :) 18:14:22 you said go 18:14:23 I went :) 18:14:25 sorry 18:14:35 yeah .. so #3 is done 18:14:38 go _on this topic_ :) 18:14:38 now for #2 :P 18:14:44 ermagerd 18:14:53 going and going on a specific topic 18:14:56 so totally different 18:15:06 so the ticket is pretty complete 18:15:19 we have unspent money in FUDCons that I'd like to move to FADs 18:15:27 ticket 83, that is :) 18:15:27 I'll balance out Flock later once the regions are done 18:15:33 do we have any comments from APAC? 18:15:55 what comment you want 18:15:58 like they didn't underspend by design? 18:16:06 s/they/you ;) 18:16:06 I was not on the council when the money was allocated, but based on the way the additional budget for LATAM was approved, this is council money to move, not regional money, aiui 18:16:17 langdon, this is not related to their regional budget 18:16:20 bexelbie: this is *just* moving council-level FUDCon/FAD allocation money, right? 18:16:26 mattdm, that is correct 18:16:27 oh you just answered that :) 18:16:30 no regional funds are being adjusted 18:16:31 gotcha .. ok 18:17:03 then i guess im +1 .. i can't see how this isnt pretty much perfunctory 18:17:10 In that case, I think this is just accounting blah blah blah and doesn't require much more than a rubber stamp 18:17:23 mattdm++ for stamps! 18:17:23 langdon: Karma for mattdm changed to 7 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:17:29 mattdm, that rubber stamp is a +1 from the council :) 18:17:35 bexelbie: yep :) 18:17:46 but.. my w/c sounded smahtah 18:17:48 This is reallocating funds and increasing our FADs budget so I feel it has importance 18:18:43 On a related note, I don't think we will have any more of these for this FY 18:18:49 i assume the q for what to do with the 1k is the matter of another ticket? 18:19:04 langdon, actually we already allocated it :) 18:19:11 that is why I am closing the loop 18:19:19 bexelbie, not per the ticket 18:19:21 The diversity FAD is pushing the FADs negative 18:19:27 diversity FAD was approved a while back 18:19:32 says some for diversity.. and some for "other stuff" 18:19:34 when we didn't realize how much had already been spent in FADs 18:19:38 i meant the "other stuff" 18:20:03 $1132.19 to FADs to cover parts of the Diversity FAD which is already approved and to leave a balance toward additional FADs or prepayment for next year's FADs (possibly the Council FAD) 18:20:51 bexelbie, i think we are just talking past each other here.. i read that as open ended, i think you read it as closed 18:21:05 but i am fine reading it with your interpretation 18:21:25 langdon, ok .. I am not actually sure we are even talking about the same thing 18:21:33 let me know when you guys are unconfused 18:21:38 as I read it this is covering the shortfall in the Diversity FAD allocation 18:21:48 and leaving a balance which could be allocated by the council at a later date 18:22:01 with the suggestion that it might be used to prepay Council FAD expenses in FY18 18:22:09 but not allocating it as such 18:22:15 "additional FADs or prepayment for next year's FADs" < this reads to me as "some fads to be decided on later" .. and i was commenting "we will have new tickets when those fads are proposed, right?" 18:22:37 langdon, yes, we would 18:22:44 so we are good 18:22:49 I didn't read your "other stuff" comment that way 18:22:54 which is what I was trying to understand 18:23:08 yep, we are good 18:23:21 bexelbie, yep.. hence why i thought we were talking past each other ;) 18:23:27 "words are hard" 18:24:42 * mattdm didn't think he was confused before but is now 18:25:06 mattdm, just nod and smile.. we are good 18:25:09 "Confused? You won't be after this episode of Fedora Council." 18:25:10 next topic :) 18:25:29 * mattdm nods 18:25:31 * mattdm smiles 18:25:39 #topic Reimbursement issues 18:25:41 #link https://pagure.io/Fedora-Council/tickets/issue/76 18:25:43 #link https://pagure.io/Fedora-Council/tickets/issue/77 18:25:45 ok bexelbie NOW this stuff 18:25:55 Both of these are still in progress. 18:26:06 do you want the tickets still open? 18:26:08 data has been collected for working on a reimbursement policy 18:26:18 experimentation going on for alternative payment methods 18:26:29 I think it can't hurt, but if we need them closed I am ok with closing them too 18:26:46 I'd like tickets to either have activity/updates or be closed 18:26:46 I see the tickets are representing ongoing work 18:26:54 works forme 18:26:57 for me too 18:27:15 mattdm: +1 18:27:21 Shall I add activity or close them? 18:27:29 Yes. 18:27:32 Yes you should. :) 18:27:33 * langdon notes mattdm thinks like a maintenance programmer/sys admin ;) 18:27:56 I'll take that as a complement :) 18:28:03 tickets MUST BE CLOSED.. glen gary glen ross quote 18:28:10 always be closing! 18:28:21 always be reopening 18:28:23 use onlly 1 ticket 18:28:26 no matter what 18:28:40 * langdon notes bexelbie and langdon think like architects.. where everything is kinda squishy 18:28:45 I mean, it's fine if there's a backlog somewhere. But we can have only so many things on our plate. 18:28:53 Limit WiP, yall 18:29:26 should we have a backlog tag? 18:29:29 * langdon is giggling over here seeing these discreet examples of psych profiles ;) 18:29:36 to indicate important but not on deck? 18:29:48 bexelbie, you should close them.. or matt is gonna not be able to sleep and come to your house 18:29:56 open a new ticket when next action is available 18:30:03 lol 18:30:03 works for me 18:30:06 track ongoing work as a separate matter 18:30:17 there's a bazillion things which are important but not on deck 18:30:23 labeling them will just make us sad. 18:30:32 -1 for sadness.. 18:30:40 exactly! 18:30:52 * langdon goes to open an anti-sadness ticket 18:30:59 so speaking of which... 18:31:06 #topic PRDs and overall strategy 18:31:08 #link https://pagure.io/Fedora-Council/tickets/issue/63 18:31:22 The top two things on *my* todo list right now are: 18:31:34 1. Rework Fedora objectives page, rethink mission with council 18:31:50 2. Remind WGs of importance of PRDs and refresh of strategy 18:31:56 #2 is actually first. 18:32:14 But, I think it'd be *better* to do #1 first. 18:32:22 Brian and I have been talking about this a little bit 18:32:32 and it's one of the main purposes fo the planned council fad 18:32:38 #1 feels like a blocker on a lot of processes 18:32:48 but Council FAD 18:33:06 are there any ideas of rethinking the mission? 18:33:10 yeah. So what I'm doing here is saying that I had an action item to do #2, but I'm bumping it to the backlog 18:33:24 robyduck: you mean, specific ones? 18:33:29 yes 18:33:47 So, here's my basic thoughts... 18:33:48 I mean, if there are some the Council could work them out 18:33:57 Our mission is: to lead the advancement of Free and open source software and content as a collaborative community. 18:34:03 at least, that's the current statement. 18:34:10 yup 18:34:32 But, in 2017, if we sat down and started from scratch to do that, *what sane person would say "the best way is to build a linux distro!" 18:34:53 At the same time, I think we *do* want to build a linux distro AND have good reasons to do so 18:34:59 But that's not articulated in our mission. 18:35:15 I think we should move some of the more grand statements to our vision statement 18:35:31 aha, gotcha 18:35:36 and connect our stated mission a little more closely with what we're here to do 18:35:40 Does that make sense? 18:35:59 now it makes sense even to me :) 18:36:04 +100 18:36:06 jkurik: nice :) 18:36:18 yes, time has changed since our actual mission statement, we *could* really work out something more artuclated 18:36:24 articulated even 18:37:14 Yeah, that's the other thing — I think the current one is from 2009/2010, and it's good to take a critical look every... decade or so :) 18:37:19 and I think having an updated mission would also give us some marketing plus outside. which is always a good thing 18:37:46 yeah, good point 18:38:44 and could help us with our own marketing and community/user growth 18:38:55 I hope we can have something where we can draw a logic model for the project overall, and have all of the parts work 18:39:25 I'm still drafting my "hopes for 2017" FPL message... Do you think I should put this as part of it, or should I start a separate discussion? 18:39:38 I think you should tease it 18:39:44 and then make it separate 18:39:50 *nod* good suggestion 18:39:52 and that should go to comm blog 18:39:55 the 2017 18:39:58 with the tease I mean 18:40:06 also good suggestion 18:40:14 definitely separate.. and arguably.. not the 2nd part at all 18:40:16 we want some level of organic discussion 18:40:22 commblog should also have the accomplishments stuff 18:40:26 this message is #3 on my list 18:40:38 langdon: the 2016 in review stuff I already posted? 18:40:53 mattdm, on commblog? i saw the email.. not the blog post 18:41:12 It didn't get, like, any response on the council list, so putting it on the comm blog is probably a good way for it to get a little more attention 18:41:34 arguably.. that is one for magazine .. 18:41:40 as it is about "users" .. sorta 18:41:47 it's mixed 18:41:50 I can easily see this on magazine 18:42:03 bexelbie: the 2017 part, the 2016 review, or the mission? 18:42:06 * bexelbie is working on the next installment of FCAIC news - will let mag and commblog decide where it runs 18:42:20 I'd tease mission in 2017 18:42:28 then put it where you want the discussion to be 18:42:35 and tell them where it will be in the teaser 18:42:42 I *definitely* want the discussion to be on the council list 18:42:42 so if you want to do it in blog comments, put it there 18:42:47 then put it there first 18:42:49 I do not want to do it in blog comments 18:42:57 after it gets somewhat baked you can move it to a bigger crowd 18:43:02 I think 18:43:10 yeah. 18:43:44 okay, so, do we want to have a separate #topic for "possible meeting in brno"? 18:43:48 it's what I'd like to do with the events conversations 18:43:55 bexelbie++ 18:44:06 once they gel (that's the word) 18:44:42 I can get us a non-devconf overlapping space if we know when people will be in Brno 18:44:51 or can work to get us an overlapping one if we'd prefer 18:45:20 #topic possible meeting in brno 18:45:30 I will not be in Brno during DevConf this year (some personal/family issues), having a meeting a day before/after the devconf helps me 18:45:44 Sorry dropped hook for a min there 18:46:39 I will be there from late on the 24th (but jetlagged) and leave monday the 30th 18:46:43 Would the Monday after work? 18:46:46 I'm there for basically the two weeks around DevConf 18:46:46 so no 18:47:16 Why not a dinner like we did some other time? 18:47:24 25th dinner? 18:47:44 +1 for the 25th dinner 18:47:55 DOW? 18:48:01 25th dinner sounds good. I'm already booked for dinner and *breakfast* on the 26th 18:48:05 Wed 18:48:24 I think that works 18:48:36 Anyone else in Brno (pending mystery council person in a few days) 18:48:38 ? 18:49:02 I think jwb will be there 18:49:07 bexelbie: s/days/hours/ 18:49:33 jkurik, microseconds please :P 18:49:47 :) 18:49:50 it is sounding like 25 dinner or during devconf 18:50:00 barring a lunch on 25 (/me is probably booked on 26 already) 18:50:36 jkurik, do you think we'd need a reservation - I would hope we could walk in to most places (barring food challenges 18:51:12 bexelbie: I am typically making reservations as you never know .... 18:51:15 * langdon is a food challenge 18:51:27 * mattdm votes for Annapurna 18:51:35 langdon, will that work for you? 18:51:39 jkurik, ^^? 18:51:44 Not as bad as mattdm though 18:51:53 Yeah 18:51:55 bexelbie: you mean Annapurna ? 18:52:02 it works for me 18:52:04 jkurik, yes 18:52:05 ok 18:52:21 what time do people want to eat? 18:52:47 I will still be jetlagged so time is no object 18:53:12 Well we want to meet a it too? Or just social? 18:53:25 "a bit" 18:53:48 I am ok with meeting too 18:53:56 they don't have a private room, iirc 18:53:57 Maybe like 5.. And order slowly.. 18:54:10 bexelbie: I am flexible with my eating habbits :) 18:54:10 we should meet and do some concrete stuff whch is faster to do face to face 18:54:11 if we're obnoxious enough, any room will be a private room 18:54:13 I don't think we need that.. But wifi would be nice 18:54:26 I recall them having wifi 18:54:42 worst case I can make you all sit on my uncomfortable chairs 18:54:43 :P 18:54:54 I can stand. 18:55:15 okay, so I actually have one interesting other nonrelated thing 18:55:27 #topic note on fedora stats kaiju 18:55:34 5m! go! 18:55:47 smooge has been looking at the automated fedora stats 18:56:20 one big concern I had was an apparent big drop in numbers in 2016 (which we're back up over, but i liked to see continuous growth) 18:56:45 * langdon thinks council should have a badge for when people do stuff for the council 18:56:47 it seems like this is at least in some significant part to two new proxy servers being added -- but their logs not captured 18:57:00 langdon++ yes good idea 18:57:28 so, i386 drop may still be a thing, but overall, that big kaiju bite (too big to be a dinosaur, see) may be explained 18:57:38 Lol 18:58:13 #topic One Minute for Open Floor 18:58:16 go! 18:59:02 me! 18:59:06 robyduck: go! :) 18:59:38 just wanted to tank you all for the nice experience here, and hopeful to see you next week too, otherwise at next FLOCK!!! 18:59:48 thanks robyduck! 19:00:00 thanks for all your hard work on everything! 19:00:05 Robyduck++ 19:00:10 ;) 19:00:34 robyduck++ 19:00:34 bexelbie: Karma for robyduck changed to 8 (for the f25 release cycle): https://badges.fedoraproject.org/tags/cookie/any 19:00:57 * langdon wonders if case matters 19:01:04 mmmh cookies 19:01:10 robyduck++ 19:01:16 nice. and thanks everyone else too 19:01:23 langdon: one cookie per cycle :) 19:01:23 cheers 19:01:27 #endmeeting