15:00:02 #startmeeting Council (2020-02-19) 15:00:02 Meeting started Wed Feb 19 15:00:02 2020 UTC. 15:00:02 This meeting is logged and archived in a public location. 15:00:02 The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:02 The meeting name has been set to 'council_(2020-02-19)' 15:00:03 #meetingname council 15:00:03 The meeting name has been set to 'council' 15:00:14 #chair jonatoni riecatnor contyk dgilmore mattdm sumantrom tyll bcotton pbrobinson asamalik 15:00:14 Current chairs: asamalik bcotton contyk dgilmore jonatoni mattdm pbrobinson riecatnor sumantrom tyll 15:00:16 #topic Introductions, Welcomes 15:00:22 .hello psabata 15:00:23 contyk: psabata 'Petr Ĺ abata' 15:00:36 .hello riecatnor 15:00:41 riecatnor: riecatnor 'None' 15:01:17 .hello till 15:01:18 tyll: till 'Till Maas' 15:04:29 not much of a party today 15:04:37 i guess i'll have to eat all of the donuts myself 15:04:45 #topic Today's agenda 15:04:55 there's not a lot on the list that we can do much about 15:05:06 #link https://pagure.io/Fedora-Council/tickets/issues 15:05:17 anyone have anything in particular we should go over? 15:06:33 Nothing from me really to discuss, just hard at work on stuff we've already agreed on :P 15:06:41 that makes one of us! ;-) 15:07:14 okay, i have a couple of things i can run through real quick, so the minutes have something in them 15:07:25 #topic 251 - Fedora Project & Nitrokey 15:07:27 #link https://pagure.io/Fedora-Council/tickets/issue/251 15:07:53 tyll: you were going to follow up on this. is this something we're still working on or should we drop it? 15:08:28 i know you've been a bit ...distracted... for a while :-) 15:09:08 we also agreed that we'd wait for the new logo to get hardware, but it seems like there's some work that could be done in advance of that 15:09:24 update on the logo is Mizmo has it pretty darn close to done. Going to present that to the legal team and a reminder to pick it back up with the start of the new FY 15:09:30 bcotton: yes, I am still following up on this. Actually puiterwijk is not in the infra team anymore and since CPE still seems to be reorganizing their priorities, I did not reach out to them again 15:09:53 understood 15:10:10 bcotton: there are enough different Nitrokey options that there should be one device that will support whatever Fedora is going to use, I think 15:10:31 once you have an idea of the scope of work needed, we should put together an epic brief to get that on their radar 15:11:28 #link https://teams.fedoraproject.org/project/fedora-council-infrastructure-priorities/us/6?kanban-status=439 15:11:41 now there's a card on our epic brief kanban board :-) 15:11:44 bcotton: I think it is more a question about what kind of authentication will be supported in the future not necessarily an requirement from our side 15:12:08 if it is still SSH, it would be a different device than if it would be only FIDO U2F 15:13:02 tyll: okay. we'll still want to figure out our requirements for them though (i'm thinking mostly from a policy perspective). maybe it should wait until after the AAA project is done? 15:13:05 I will reach out to CPE to see if I can get an answer and a new point of contact 15:13:07 or relatively done 15:13:16 tyll++ 15:13:59 bcotton: what do you mean with policy? I guess the policy of who gets something would be our decision 15:14:20 tyll: ACTION: @till to develop a proposal that includes: 1. who will get the key and 2. how we will enforce it (including what infra work, if any, would be required) 15:14:35 we should tell CPE how we want it enforced 15:15:01 e.g. do we want to require that it be used for everyone who has it? is it optional for people who have it? are there certain systems where it shoudl be required and the rest optional, etc 15:15:16 ah, I see 15:15:18 the who gets it is entirely our decision 15:15:50 but the enforcement, i think, we'd want to have a say in and let CPE implement our requirements as they see fit 15:16:40 anything else on this topic? 15:18:39 not from me 15:18:44 #topic 249 - Logo adoption timeline 15:18:47 #lnik https://pagure.io/Fedora-Council/tickets/issue/249 15:19:04 riecatnor: since you brought it up, i'll put it in the record 15:19:24 #info Mizmo has a new new logo pretty darn close to done. Going to present that to the legal team and a reminder to pick it back up with the start of the new FY 15:19:34 riecatnor: is there a design ticket for this? 15:22:23 erm, it was closed bc reasons 15:23:09 https://pagure.io/design/issue/620 15:23:32 #link https://pagure.io/design/issue/620 15:24:24 i'd suggest a new ticket open with the work being done in there 15:26:16 are there any fedora-official places where this is being discussed? i've only seen it on twitter 15:26:47 I can see if Mizmo thinks that is wise. I believe the logo is just getting small changes and iterations at this point 15:27:21 in fact I am sending the most current one to legal saying here is an update and where do things stand? 15:27:37 theres no need for a new ticket it's just refinements now 15:27:43 the ticket is closed because the council approved it 15:27:54 welcome, mizmo! 15:28:43 o/ 15:29:00 i'd disagree that the council approved it if you're making changes, but maybe it depends on the scope of the refinements 15:29:45 bcotton: font kerning and minor tweaks to letter paths is really not worth going thru another approval 15:31:14 i have some suggestions that would change it pretty markedly but in experimenting with them i dont think they will work out 15:31:52 mizmo: i'm inclined to agree in that case, but it's hard to know since it's not been community-visible (at least that i'm aware of, i do miss a lot of things) 15:32:18 @bcotton i've been on maternity leave for 4 months and only back now 2-3 weeks, nothing has been done in secret 15:32:41 mizmo: i didn't mean to imply that 15:32:50 not saying you did just want to be direct 15:33:04 the ticket got pretty toxic :-( 15:33:05 i'd expect nothing less from you, my friend :-) 15:33:18 this appears to be logged so i dont want any confusion 15:34:36 I sent off an email on the logo, and requesting at least a time frame so we know what to do with swag/event stuff 15:34:59 okay so to recap: riecatnor is checking with legal to make sure it's in their budget for CY2020 and to check on next steps. mizmo is making a few final tweaks. so at this point we're waiting on input from legal in order to proceed 15:35:02 is that a good summary? 15:35:22 yep 15:35:27 yeh. do you want me to do a new ticket for the final final version or should i put it on the existing council ticket? 15:35:39 and if the former what queue should the ticket be in do you think 15:35:59 i dont want to blog post it or anything like that bc most assuredly it'd get comments like 'cant you change this one thing' and it's not really open anymore 15:36:14 (by open i mean, open for business and major restructuring) 15:36:15 I think adding it to the council ticket is good 15:36:33 kk 15:36:35 mizmo: i'd say the final final version can be a reopen of the approved council ticket and we can wait a few days to see if any council members demand a new vote 15:37:06 #info riecatnor is checking with legal to make sure it's in their budget for CY2020 and to check on next steps. mizmo is making a few final tweaks. so at this point we're waiting on input from legal in order to proceed 15:37:11 @bcotton that seems fair 15:37:19 thanks dude :) 15:37:38 #action mizmo will reopen the approved Council ticket when the final final version is ready 15:38:09 mizmo: thanks for all your work (and suffering slings & arrows) 15:38:17 anything else logo-related before we move on? 15:39:19 #topic 284, 288 - Publish readouts from {November, January} Face-to-Face 15:39:20 thats it from me 15:39:39 #info Two of four November readouts are published on the Community Blog 15:39:50 #link https://communityblog.fedoraproject.org/lets-write-a-new-vision-statement-for-fedora/ 15:39:57 #link https://communityblog.fedoraproject.org/fedora-council-november-2019-meeting-councily-business/ 15:40:06 #info The remaining two are scheduled for later this month 15:40:43 #info mattdm is drafting a January readout. We'll probably publish a vision statement follow-up before the rest of the January readout 15:41:15 my goal is to have all of the face-to-face readouts published before our next on (which is in August, so that's an achievable goal) 15:41:33 this was mostly for zodbot's benefit, but any questions or comments here? 15:42:38 sounds good to me 15:42:53 #topic 276 - Status of CI objective 15:43:02 It's done. 15:43:07 #action bcotton to remind dperpeet to write the closeout post for CI Objective 15:43:30 #topic Next meeting 15:43:38 #info The next Fedora Council meeting is 4 March 15:43:49 #topic Do we have anything to announce? 15:43:51 #info This is a regular check to make sure we're communicating to the contributor (via CommBlog) and user (via Magazine) communities 15:45:11 I am working on a blog post for commblog. Part event report/part outline for rise campaign. I would like to have that done by next week 15:45:22 riecatnor++ 15:46:11 #topic Open floor 15:46:19 anything else in the last few minutes? 15:46:53 sorry for missing today I was in a call :( 15:47:00 I'm just coming up with a devel@ email announcing the Modularity team changes as the DNF team keeps urging me to do so. 15:47:24 So that will go out shortly. 15:47:31 Not sure what the status of the new objective is. 15:47:44 contyk: great. if you want another set of eyes, let me know 15:47:54 * contyk nods 15:48:04 contyk: happy to have a look at that, too, if you want! 15:48:05 the status of the new objective is "dmach or his designate should submit a new proposal to the council" 15:51:12 last call! 15:52:39 okay, thanks everyone! have a good wednesday 15:52:44 #endmeeting