18:00:02 #startmeeting Council (2021-01-21) 18:00:02 Meeting started Thu Jan 21 18:00:02 2021 UTC. 18:00:02 This meeting is logged and archived in a public location. 18:00:02 The chair is bcotton_. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:02 The meeting name has been set to 'council_(2021-01-21)' 18:00:04 #meetingname council 18:00:04 The meeting name has been set to 'council' 18:00:05 #chair bookwar dcantrell jwf riecatnor spot mattdm bcotton asamalik x3mboy 18:00:05 Current chairs: bcotton_ bookwar dcantrell jwf riecatnor spot mattdm bcotton asamalik x3mboy 18:00:07 #topic Introductions, Welcomes 18:00:27 helloooo everyone 18:00:27 * jwf waves 18:00:40 * spot wakes up 18:00:47 hello Ben Cotton Underscore! 18:01:00 .hello2 18:01:02 x3mboy: x3mboy 'Eduard Lucena' 18:01:15 * King_InuYasha waves 18:01:18 .hello ngompa 18:01:19 King_InuYasha: ngompa 'Neal Gompa' 18:01:39 .hello jflory7 18:01:40 jwf: jflory7 'Justin W. Flory' 18:02:24 .hello2 18:02:25 mattdm: mattdm 'Matthew Miller' 18:02:31 .hello riecatnor 18:02:33 riecatnor: riecatnor 'Marie Nordin' 18:02:39 .hello2 18:02:40 bookwar: bookwar 'Aleksandra Fedorova' 18:02:58 that's almost everyone, so let's get started 18:03:14 #topic Today's agenda 18:03:16 #info Logo adoption timeline 18:03:17 #info Fedora annual survey 18:03:19 #info Add the Fedora goal of having complete integrated system 18:03:20 #info Your topics here! 18:03:29 * bcotton_ remembered to replace #topic with #info when copypasta-ing this time 18:03:33 bcotton++ ;-) 18:03:40 #topic Logo adoption timeline 18:03:42 #link https://pagure.io/Fedora-Council/tickets/issue/249 18:03:51 So, good news! 18:04:10 We have legal clearance to move forward with the new logo as designed by mizmo 18:04:21 #info We have legal clearance to move forward with the new logo as designed by mizmo 18:04:27 .hello2 18:04:28 dcantrell: dcantrell 'David Cantrell' 18:04:28 We are waiting for RH Legal to file a thing 18:04:38 "A thing" is not the technical term. 18:04:58 I'm just being vague because I'm not sure how much we should say before that is actually filed. 18:04:58 maybe a trademark registration? 18:05:04 are we going to be ready by devconf? ) 18:05:21 bookwar: definitly by *a* devconf 18:05:27 definitely, too 18:05:34 We were told that that would take about a week, about a week ago 18:05:41 So bcotton_ is following up. 18:05:44 so, 2024. 18:05:46 cool. 18:06:04 bcotton_ won't let that happen :) 18:06:16 i wonder if get more flame than centos got 18:06:24 * bcotton_ is a pro at sending pestering emails 18:06:35 Well, we do have a very long, very public track record on our logo 18:06:41 mizmo++ 18:06:41 jwf: Karma for duffy changed to 3 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:06:52 woohoo! 18:06:53 We also need a roll-out plan. Ben, Marie, Mo, and I are working on figuring that out. 18:06:57 mizmo++ 18:06:58 Conan_Kudo: Karma for duffy changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:07:22 duffy++ 18:07:28 There are a lot of things that need to be changed -- not just the logos but the guidelines and stuff 18:07:29 FINE ZODBOT 18:07:48 duffy++ 18:07:48 bcotton: Karma for duffy changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:07:49 jwf: sure, but i would brace for impact anyway. There will be a news wave. 18:07:54 mattdm: I wonder if a docs.fp.o reboot from the wiki would be in order… 18:07:57 are we getting new generic branding for this? 18:08:29 And, we've also been asked to _keep_ using the "classic" logo in place. 18:08:37 King_InuYasha: you mean the remix secondary mark? 18:08:38 or fedora-remix branding? 18:08:44 bookwar: Inevitably. I am skeptically optimistic that it won't be received terribly. Given that we still get the Facebook comments, even in 2020 18:08:45 mattdm: yes 18:08:59 I don't think that's currently in scope. 18:09:08 One thing at a time. :) 18:09:18 It might make sense to update the typeface to match 18:09:21 yeah 18:09:36 mattdm: then i guess let's not make any announcement until we have the plan figured 18:09:46 mattdm, which typeface? 18:10:03 I think in some part, continuing to use the current logo is just going to happen in practice because we won't be able to have a big changeover day 18:10:27 riecatnor: https://fedoraproject.org/wiki/Legal:Secondary_trademark_usage_guidelines 18:10:45 mattdm, gotcha thanks 18:10:51 But it would be nice to also have some areas where we are specifically using the Classic mark intentionally 18:11:09 you can see where the rpi branding design was inspired from :) 18:11:11 We don't need to solve that here but would like your ideas as you have them 18:11:34 mattdm: why not use the main logo for Project activities? 18:12:06 King_InuYasha: We discussed that. The problem is a lot of the reasons we wanted a new logo apply to those uses 18:12:11 :/ 18:12:12 Like, maybe 95% of them. 18:12:26 I mean, they also apply to the Fedora software use cases. 18:12:31 then this is going to be difficult 18:12:49 King_InuYasha: that is correct 18:12:51 we don't exactly have any good boundaries we could neatly apply them 18:12:52 I am one-tenth-seriously thinking of making a Fedora Classic spin. With fvwm. 18:13:03 mattdm: it'd better have fvwm95 :) 18:13:11 sure :) 18:13:21 (that was my first window manager :) ) 18:14:05 It will be difficult, but we'll get it done :) Once we have a green light to go public, I think we can revisit then. But good to know there is real traction here 18:14:15 mattdm: the problem there is to come up with the common definition is "classic", which is impossible 18:14:20 But anyway, I think the question for the council is: do we want to try and land this for the F34 launch? 18:14:26 It might be a good casual note in bcotton's FPgM weekly reports 18:14:35 mattdm: That seems ambitiously ambitious 18:14:37 FSVO "land" 18:14:40 mattdm: yes please, it would align well with branding refresh in Plasma 18:14:47 bcotton_: right. 18:14:58 we're in the process of redoing basically the entire visual look of Plasma in Fedora 18:15:05 I think we need to understand the scope of landing it for F34 launch is 18:15:14 what the scope* 18:15:20 riecatnor++ 18:15:37 I think it would basically be: We use the new logo for: 18:15:43 1) at least the Editions 18:15:47 2) Fedora Magazine 18:15:53 3) Fedora Docs 18:16:21 all by 34 release day 18:16:28 4) Fedora KDE :P 18:16:36 but yeah, that makes sense 18:16:53 King_InuYasha that falls under 'at least' rather than 'must' to me but sure since you want to do it anyway 18:17:08 and then we would start rolling it out to other places as time and effort permit 18:17:15 so we have until mid April 18:18:01 Yeah. My feeling is that if we can't do at least 1-3 above, we should delay until two weeks after the F34 launch (when the buzz of that dies down) and then start changing things for F35 18:18:18 assuming the design team can make updated assets in that time frame, #2 and 3 shoudl be easy to implement 18:18:20 (That is, if we can't do 1-3, explicitly do none.) 18:18:36 so, we will need Mo to make the files for all of these I am guessing. so that is the first piece, Mo's capacity. Tho I think she is excited for this 18:18:42 i do like the all-or-nothing approach 18:18:52 Other early targets would be hyperkitty, discourse, matrix, and the wiki 18:19:13 most of those things don't actually _use_ the Fedora logo 18:19:25 unless we've changed the fedora-bootstrap visual style too? 18:19:58 mattdm: I think you forgot social media, Discourse, and Matrix ;) 18:20:20 Oh, yes, social media probably should be part of the launch. 18:20:34 what are the places to keep the old one then? 18:20:35 Twitter and Facebook at least, because that's our biggest audiences. 18:20:59 bookwar: right, no idea. :) 18:21:12 but it is _everywhere_ in places like https://koji.fedoraproject.org/koji/ 18:21:19 https://koji.fedoraproject.org/koji-static/images/koji.png 18:21:31 There is also LinkedIn (stickster?), Reddit, Discord, Telegram, YouTube, Instagram… etc 18:21:46 anyway, this is getting into details. all of this will need to go into the plan. 18:21:52 +1 18:22:02 ooh logo talk? 18:22:07 so it sounds like we have general agreement that we want to give this a try 18:22:08 mizmo: yes :) 18:22:09 Well, +1 to putting it in a plan 18:22:22 should it be in a ticket? Or in a doc? 18:22:25 I am somewhere between -1 and +0 for targeting new logo for F34 18:22:26 just going to say "I think we need to wait for mizmo to make the decision I want to make" 18:22:43 mattdm: what decision? 18:22:44 so i'm going to suggest we #action mattdm to coordinate a plan for the logo rollout and come back to council with a proposal 18:22:58 mizmo: starting rollout of new logo in f34 18:23:00 I feel like we should spend more time scoping it than just one meeting before taking a vote on something that comes with a lot of new work 18:23:03 i have an initial cut of a plan riecatnor and i worked on way back but its very high level branding 18:23:08 oh thats my decision? o_O 18:23:13 mizmo: yes 18:23:13 bookwar: I think mizmo riecatnor and I will come up with a proposal 18:23:41 mizmo: well, it's a decision where you have a lot of the weight since we expect you'll do most of the work :) 18:23:48 oh i just sort of assumed it was happening and scheduled myself accordingly 18:23:56 well, that makes that easy 18:23:58 bcotton_: go ahead and action me that :) 18:24:13 i mean i would have a happier less stressful life if it could wait, but also... excitement to get it going so 18:24:30 #action mattdm to coordinate a plan for the logo rollout and come back to the Council with a proposal 18:24:47 does having the plan approved by council be a prereq to getting into f34 bc time is tight for beta 18:24:50 I will feel more confident voting on something more concrete :) We could make it for F34, but we need to take a proper inventory of what that will require first 18:25:13 or say could there be an f34 plan, then the full rest of everything plan after beta deadlines are made 18:25:22 mizmo: that's fine 18:25:26 mizmo: yes, that 18:25:26 and I think what we're aiming for 18:25:36 +1 18:25:36 mizmo: yes, that was my suggestion. scroll up a bit to where I made a numbered list 18:25:51 okay, so let's move on to the next topic then 18:25:53 ok cool what i have been working on is putting together a table in the pagure ticket on the design team pagure of all the spots it needs to be updated 18:26:09 ok. I'll try to get a proposal for F34 ready before next week 18:26:12 #topic Fedora annual survey 18:26:14 #link https://pagure.io/Fedora-Council/tickets/issue/327 18:26:15 #info Previously, bookwar said she'd draft a proposal for this 18:26:16 even if it will not have all the details 18:26:40 bcotton and i said it will be in november :( 18:26:52 bookwar: i left that part out :-) 18:27:32 and i do still want to make it 18:27:35 it's november somewhere! 18:27:51 but i am really afraid to say anything about the time now 18:28:31 bookwar: no problem. it's not the most pressing issue. we can keep checking in on it from time to time (or if you want to hand it off to someone else, we can ask for volunteers) 18:29:16 if anyone wants to volunteer, i'll gladly accept that, but let's keep it for now 18:29:16 I wonder if Mindshare has bandwidth and capacity for this, either to lead or just to assist. Given their success in running previous surveys 18:29:40 I can also check back in with the NPS people I was talking to pre-covid 18:29:48 x3mboy and riecatnor could call that one better than me^^ 18:29:56 Those discussions fell apart solely because of pandemic fatigue. 18:30:01 I did what? 18:30:30 x3mboy: Mindshare Committee bandwidth to assisting with a community-wide survey about Fedora 18:30:51 x3mboy: This one -- https://pagure.io/Fedora-Council/tickets/issue/327 18:30:55 I think there is some BW 18:31:01 there is a process in which to request a survey through mindshare 18:31:03 But not sure how much 18:31:14 let's do that then so bookwar can stop feeling guilty 18:31:21 Well, the copy needs to be written 18:31:29 it is only someone taking that and putting it into lime survey 18:31:55 Would Mindshare be interested in co-authoring the copy? 18:32:09 I think mindshare is a bit cut off from the engineering side of Fedora, as engineering side is from mindshare. this should be with the council imo 18:32:21 oh! i just wanted to throw this out there - by some chance i own the fedora.limequery.com / fedora@limesurvey account, if somebody wants the reins happy to give for this 18:32:22 Fair 18:32:40 * mattdm has to step away from keyboard for a few minutes. don't wait for me :) 18:32:42 +1 to riecatnor 18:32:46 the initial question list is there in the etherpad 18:33:09 do you thinl we can find some small unibiased audience where we can make a test run for them? 18:33:09 I think ensuring the reps from mindshare and fesco review it makes sense tho. 18:33:26 riecatnor: yes, definitely 18:34:11 riecatnor: so i need to bring it to mindshare and fesco and council as a ticket, right? 18:34:16 what we have already is a pretty good start 18:34:44 I guess it mainly needs some refinement? 18:35:00 i would not bring it to mindshare and fesco as tickets. i'd say bring it to the council as a ticket and let the mindshare/fesco reps handle their respective groups 18:35:16 bcotton: ok, good point 18:35:25 this is definitely something we can discuss at the next mindshare meeting 18:36:06 so how about I'll take the content from the etherpad, reread it, and then repost it into that ticket as a proposal? 18:36:18 +1 18:37:17 is this survey thing something we can use in various WGs? 18:37:36 WGs/SIGs/etc.? 18:38:00 I think the idea is that it is community wide? 18:38:22 #action bookwar to review the content from the survey etherpad and repost into the ticket as a proposal 18:38:31 anything else on this topic? 18:38:40 not from me 18:39:08 #topic Add the Fedora goal of having complete integrated system 18:39:09 #link https://pagure.io/Fedora-Council/tickets/issue/280 18:39:11 #info From vF2F: mattdm and bookwar to find a place to fit “upstream first” and then add in the contents of https://fedoraproject.org/w/index.php?title=Objectives&oldid=2124 18:39:50 mizmo, for the limesurvey account, the person would be siddharthvipul :) 18:40:09 mattdm, bookwar any progress on this one? 18:40:22 riecatnor - his accoutn is fedoraproject.limequery, i have the fedora.* one 18:40:39 bcotton_: nope! kick that to next meeting plesae :) 18:40:56 #info We'll come back to this next time 18:41:02 speaking of next time... 18:41:11 King_InuYasha: btw, my original idea on survey was because the nano vs vim debate and i started to think if we want a "classic spin" as mattdm mentioned. And then i realized i have no idea what can be counted as classic in the community, and i want to know what community is actually doing 18:41:26 #topic Next meeting 18:41:28 #info The next regular business meeting is Thursday 4 Feburary 18:41:31 well, "classic" is overratted 18:41:37 call it "retro" :) 18:41:37 #topic Do we have anything to announce? 18:41:39 #info This is a regular check to make sure we're communicating to the contributor (via CommBlog) and user (via Magazine) communities 18:43:40 #link https://communityblog.fedoraproject.org/community-outreach-revamp-objective/ 18:44:03 follow up, please vote or comment here :) 18:44:05 #link https://discussion.fedoraproject.org/t/fedora-objective-proposal-community-outreach-revamp/25928/4 18:44:40 any other announcements? 18:45:22 not from me 18:45:29 yes 18:45:37 * bcotton_ waits 18:45:50 #link https://pagure.io/mindshare/issue/248 18:45:58 #info Mindshare committee is organizing a presence at fosdem 2021 18:46:33 we are attempting to organize a swag raffle contest for that! 18:46:41 that is all :) 18:46:52 #topic Dashboard check 18:46:54 #link https://docs.fedoraproject.org/en-US/project/dashboard/ 18:47:32 so not today because i haven't had time to organize my thoughts, but be prepared for a proposal from me that we give up on this :-) 18:47:44 yeah :/ 18:48:22 but there are no recent updates that require the Council's help, so that's nice 18:48:31 #topic Open floor 18:48:41 anything for open floor? 18:48:45 * King_InuYasha shrugs 18:48:54 Fedora 34 doesn't look like it'll beat Fedora 33 on changeset 18:48:59 changeset numbers that is 18:49:11 it got close though 18:49:57 There were some new docs tickets opened as an FYI 18:50:12 #link https://pagure.io/Fedora-Council/council-docs/issue/102 18:50:21 #link https://pagure.io/Fedora-Council/council-docs/issue/103 18:50:31 the D&I team is organizing a virtual meetup 18:50:36 #link https://pagure.io/fedora-diversity/issue/189 18:51:43 the community outreach/ambassador survey closed and the co-leads & folks from the TTF have begun to analyze the data 18:52:10 Excited to see that :) 18:52:31 nice 18:52:38 Under: What do you see other organizations doing that you think works well? 18:52:38 "SuSE has the lizard suit girl mascot. Bring back Spot in a penguin suit." 18:52:55 +1 18:53:32 🤣🤣 18:53:45 ha 18:54:01 In all seriousness, there are some very interesting insights to gather 18:54:42 Looking forward to sharing that in a digestible format :) 18:54:54 uhhh 18:55:10 lol 18:56:02 last piece of news, potentially the most important.. I have adopted two kittens! and named them Ruby & Sapphire 18:56:07 that is all :) 18:56:14 <3 18:56:59 In a positive note, we are getting attention in the media for several stuff, not only technical 18:57:15 #action riecatnor to post pictures of cats to matthew's pet thread on discussion.fp.o 18:57:16 Like phoronix mentioning the amby's revamp 18:57:18 Oh? 18:57:24 nice! 18:57:38 #link https://www.phoronix.com/scan.php?page=news_item&px=Fedora-Community-Outreach-21 18:57:49 OTHER CAT PICS ALSO WELCOME 18:58:12 https://discussion.fedoraproject.org/t/pets-of-fedora/25180 18:58:41 And several podcasts shows (DLN and Linux Unplugged) choosing Fedora 33 as beste desktop of 2020 18:59:51 rad :) 19:00:16 well on that positive note, that seems like a good time to 19:00:19 #endmeeting