14:00:03 #startmeeting Fedora Council - Wed, 19 July 2023 14:00:03 Meeting started Wed Jul 19 14:00:03 2023 UTC. 14:00:03 This meeting is logged and archived in a public location. 14:00:03 The chair is mattdm. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 14:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:03 The meeting name has been set to 'fedora_council_-_wed,_19_july_2023' 14:00:09 #meetingname council 14:00:09 The meeting name has been set to 'council' 14:00:15 #chair jflory7, mattdm, sumantrom, bt0dotninja, bookwar, siddharthvipul1, dcantrell 14:00:15 Current chairs: bookwar bt0dotninja dcantrell jflory7 mattdm siddharthvipul1 sumantrom 14:00:24 .hello2 14:00:25 #topic Welcomes and Hellos and Stuff 14:00:25 dcantrell: dcantrell 'David Cantrell' 14:00:45 oh good dcantrell, I can see you 14:00:51 .hello jflory7 14:00:52 jwf: jflory7 'Justin W. Flory' 14:01:03 I've been having a problem where I don't get messages from the IRC side 14:01:06 so I just now was able to log in to the matrix thing 14:01:23 I have missed numerous meetings because I never see them happening in irc 14:01:26 Are my messages coming to IRC though? 14:01:31 Zodbot is not replying to me… 14:01:36 yes, I am seeing these messages 14:01:43 I got zodbot 14:01:46 .hello2 14:01:47 mattdm: mattdm 'Matthew Miller' 14:01:52 but i didn't see a reply to you 14:01:53 .hello jflory7 14:01:54 jwf: jflory7 'Justin W. Flory' 14:01:58 Oh, okay 14:02:19 I just remember a meeting where David must have thought some of us were talking to ourselves, because the relay was busted :D 14:02:30 I guess I'll poke Element again -- they haven't responded yet 14:02:31 yeah, that's more often than not 14:02:38 Or are all on IRC and haven't seen me :) 14:02:48 Anyway, who else do we have here? 14:03:04 I know Vipul is traveling right now 14:03:04 whenever I log in to matrix, assuming it lets me log in, it insists that I verify myself on another device. which makes no sense. or enter a security key, which I don't have 14:03:56 Matrix asks you to set an encryption passphrase, which is separate from the login password (or in our case, FAS integration). You have to remember it and save it on account initialization I think, though 😬 14:04:07 Not intuitive and not obvious 14:04:09 dcantrell: It's got some sort of chain-of-identity thing which it uses to pass encryption keys around. 14:04:14 if I did, I promptly forgot that 14:04:31 it also aggressively logs you out, which I find annoying 14:04:42 We might need a Matrix venting session at Flock 😀 14:04:49 or we could just stop using it 14:04:50 If you don't have another device, there is an option somewhere to reset. This will lose old encrypted messages, but then you can set a phrase. 14:05:02 Which I suggest just saving in a password manager 14:05:10 mattdm: I have tried that a few times and it never works, though is does succeed at removing all past messages 14:05:28 dcantrell: The fragmentation story continues :D 14:05:33 Oh, BTW 14:05:42 If I have not told both of you yet, I have rooms confirmed for both of you 14:05:45 Once you have the passphrase saved though it should be fine. 14:05:56 Is it just the three of us? 14:06:06 jwf: good, I hope so since I booked it and all and have the receipt 14:06:45 #topic Agenda 14:07:14 Let's do: 14:07:14 1. Flock stuff 14:07:14 2. Tickets that could use attention 14:07:14 3. Done! 14:07:26 I have some Flock questions 14:07:35 #topic Flock 14:07:50 questions, then! 14:08:23 dcantrell: OK, great, yes I see you on the self-pay list :) 14:08:29 Well, with the hotel I mean 14:08:37 Versus payment via PO 14:08:39 so I'm concerned that Rocky Linux will be aggressive and/or antagonistic towards RH associates. I think we should have some guidance on behavior, etc 14:08:50 their recent posts online in various walled gardens concerns me 14:09:12 Yeah, that was Not Cool. 14:09:13 Well, it was not just in walled gardens. :) But yes, I absolutely hear you on that. 14:09:24 yeah, they are not being quiet 14:10:31 as a developer, I really have no interest in participating in those sorts of mud slinging conversations or pretending to work with a group that is clearly not being a good community member 14:10:38 So, there is open communication between me and the Rocky folks related to that incident. You might have seen that posts were removed yesterday – which was also not something that was demanded/asked for either. 14:10:55 Ugh, talking about this would be a lot easier over an A/V call instead of text. 14:10:55 it doesn't matter if they were removed 14:11:12 I can do a call 14:11:19 There are a lot of moving pieces to this specific topic and not all of them are things I feel comfortable sharing in a public forum just yet. 14:11:53 But I agree on behavior guidance and leading with the best foot forward, but I think this is a Red Hat topic and it is something we are addressing on the Red Hat end of things. 14:12:02 I am not sure this is a Fedora community topic but I could be convinced otherwise 14:12:12 I actually think it's both 14:12:23 Red Hat needs to address this with Red Hat associates headed to Flock 14:12:42 Fedora needs to address the CoC to the community and remind everyone of what is expected of everyone 14:12:43 One of the key things that I am underlining to everyone regardless of employment is that Flock is a community conference. It is a community of people, not companies and products. 14:13:01 yes, and that needs to be communicated wearing a Fedora logo 14:13:02 dcantrell: Yes, this is planned. 14:13:28 dcantrell: Do you mean a message now, or at Flock, or? 14:13:29 The CoC would be underlined with or without the tension that is there. 14:13:47 a message now to those going as well as at the "Welcome to Flock" opening session 14:13:58 I don't think this is unreasonable given the tone in the community at the moment 14:14:09 we are Fedora, but we cannot pretend the Rocky incident doesn't impact us 14:14:58 It does. We have some dialogue in the Fedora Marketing dialogue on this as well, about how we position our brand and online presence leading up to Flock 14:15:03 is it true that we're getting Rocky Linux badge lanyards? 14:15:07 s/dialogue/channel/ 14:15:17 dcantrell: Yes, together with Red Hat, Fedora, and CentOS 14:15:29 That was in the sponsorship prospectus. 14:15:34 yeah, ok, so if I'm showing up and see that, I'm going to be annoyed 14:15:42 and I know I won't be the only one 14:15:56 I saw some discussion about this in the flock volunteers channel. This isn't a great moment to say "don't say bad things about corporations". 14:16:04 no, it's not 14:16:18 Yes. The pre-event comms would be in the next week or so for Red Hatters. 14:16:33 privately, no fewer than 3 people have mentioned to me that they are considering not going specifically because of Rocky Linux's behavior 14:17:08 But, "be respectful to each other" still applies 14:17:09 One lanyard with all. 14:17:09 justin, is this a "pick your lanyard" thing, or one lanyard style with all names? 14:17:20 * mattdm has worn Oracle lanyards before, and at RH Summit they were... Deloitte, I think? 14:17:38 dcantrell -- ouch 14:18:05 I know the summit has done different things, but on the Fedora side of the house we're supposed to be seperate from all the corporate and business bullshit 14:18:25 Rocky is dragging that in and seeing it at Flock will leave a sour taste for some 14:18:30 yeah, we've never had a controversial sponsor before 14:18:43 There is a lot of "can't win" here 14:18:48 I know 14:18:50 Yes 14:18:55 I have been trying to play out some what if scenarios 14:19:04 Red Hat has worked with controversial sponsors before like Docker. But also, Fedora is not Red Hat. 14:19:05 my plan is to not engage, but I am envisioning the worst from them 14:19:46 in a way, Flock is supposed to be a venue where we all work together on the same stuff, regardless of employer. I feel like Rocky is turning this in to college football rivalries 14:19:52 which I have nearly zero patience for 14:20:01 That's well said. 14:20:02 (seriously, who tf cares about that?) 14:20:32 and yeah, I am annoyed about this because this is the FIRST in person event since the sweat lodge that was Budapest 14:20:35 In fairness, I mentioned that there is dialogue happening between Rocky and Flock staff since that specific social media event. The people whom I have engaged with have approached this in good faith and underlined that they also want to build a constructive conversation in the upstream. 14:20:36 I *want* an in person event 14:20:54 I think it is fair that I can say that their social media coordination does not seem to be coordinated. 14:21:11 I don't think kicking Rocky out would help things. 14:21:20 Does that reflect what the people coming to Flock will be like? I don't know. But I have not gotten that feeling and I have been very cognizant that it is an element. 14:21:22 David, do you have a suggestion of something we (or I) could do that might help? 14:22:35 the best I can think of is a general communication from you, mattdm, to the community about Flock and why we do it. don't call out Rocky's behavior but remind people of how we work together to make things and collaborate. I guess try to set the tone before we're all there and jetlagged 14:22:58 This is 100% a conversation that would be easier over a call than text 14:23:03 I like that suggestion 14:23:05 and separately from that, RH needs to send guidance to associates going to Flock and remind us all that we are going as community members, we don' 14:23:10 t represent RH, etc 14:23:14 I am ok with a call 14:23:18 send me a google meat invite 14:23:19 And even without the controversy, we have not done Flock in so long, that might be warranted anyways 14:23:26 jwf: true 14:23:32 I can write something. 14:23:37 google meat lol 14:23:46 Fedora Magazine, then echoed out to social media? 14:23:54 I know the Marketing team can help with messaging 14:24:12 * mattdm misses his ghost-writer :) 14:24:13 that works for me. I'd like it to go to everyone, regardless of whether they are attending Flock 14:24:13 s/messaging/outreach/ 14:24:33 👍️ 14:25:07 jwf: I trust what you said about RH planning something, but, like....now would be good :) 14:25:13 #action mattdm to work on that today 14:25:27 mattdm: ghost writing for you is not strictly in the category of "things Red Hat paid me to do", so it's still an option, but the lead time may be longer these days 14:25:58 Ben Cotton (he/him): I _will_ take you up on that! ❤️ 14:26:20 1. Did you have an alert set to pop up in case I ever mentioned ghost writing? 14:26:52 2. Do you want to take a stab at this one? Probably aiming at a publish date of Monday. 14:28:44 But don't #action yourself on that one. I actually have ideas already. 14:29:04 Anyway we said half hour. I want to mention the other things quickly -- any more on flock? 14:29:32 Just my bucketful of pending actions :) 14:29:47 okay then 14:29:52 Schedule is due today… all final notifications will go out to pending speakers 14:30:18 #info flock schedule will be published today, and final notifications to speakers 14:30:28 #topic A few tickets of note 14:30:33 https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-461-approve-fedora-logo-usage-for-laptop-special-editions/85814 14:31:28 Tuxedo Computers has a nice Fedora edition. However, they have some not-in-Fedora tools. What to do with trademark request and that. 14:31:54 actually that's the only one that seems really "address-before-flock" urgent. 14:32:31 * jwf clicks 14:32:45 are the not-in-Fedora tools they include open source? 14:32:47 dcantrell, please leave thoughts when you get a chance. 14:33:01 they are open source, but there is an non-upstream kernel module 14:33:36 and with that, I'll go draft a message for the magazine and justin can get back to work :) 14:33:42 thanks everyone! 14:33:43 #endmeeting