18:00:18 #startmeeting Council (2021-03-04) 18:00:18 Meeting started Thu Mar 4 18:00:18 2021 UTC. 18:00:18 This meeting is logged and archived in a public location. 18:00:18 The chair is bcotton_. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:18 The meeting name has been set to 'council_(2021-03-04)' 18:00:19 #meetingname council 18:00:19 The meeting name has been set to 'council' 18:00:21 #chair bookwar dcantrell jwf riecatnor spot mattdm bcotton asamalik x3mboy sumantrom marianab 18:00:21 Current chairs: bcotton_ bookwar dcantrell jwf riecatnor spot mattdm bcotton asamalik x3mboy marianab sumantrom 18:00:22 #topic Introductions, Welcomes 18:00:26 .hello2 18:00:27 dcantrell: dcantrell 'David Cantrell' 18:00:31 .hello2 18:00:32 mattdm: mattdm 'Matthew Miller' 18:00:41 hi everyone! 18:00:51 hello 18:00:58 .hi 18:00:59 x3mboy: x3mboy 'Eduard Lucena' 18:01:07 * jwf|m waves 18:01:24 marie is on vacation this week, so she should not be showing up :) 18:01:25 .hello jflory7 18:01:26 jwf|m: jflory7 'Justin W. Flory' 18:01:36 .hello2 sumantrom 18:01:39 sumantro: sumantro 'Sumantro Mukherjee' 18:02:24 .hello2 18:02:25 bookwar: bookwar 'Aleksandra Fedorova' 18:03:24 .hello2 18:03:25 spot: spot 'Tom Callaway' 18:03:43 #topic Today's agenda 18:03:44 #info Add the Fedora goal of having complete integrated system 18:03:45 #info Trademark Approval Request: Shells.com 18:03:47 #info Your topics here! 18:03:56 upcoming virtual face to face. 18:03:57 #topic Add the Fedora goal of having complete integrated system 18:03:58 #link https://pagure.io/Fedora-Council/tickets/issue/280 18:04:00 #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:04:01 #info previously: “We'll come back to this with exponential backoff” 18:04:04 mattdm: ack 18:04:10 bookwar: anything? :) 18:04:29 no, only the guilt 18:04:33 same! :) 18:04:39 yay guilt! 18:04:47 bcotton_: remind us again in two meetings? :) 18:05:01 #info we will come back to this two meetings from now 18:05:08 #topic Trademark Approval Request: Shells.com 18:05:10 #link https://pagure.io/Fedora-Council/tickets/issue/349 18:05:27 so a few of us met with the shells.com folks earlier today 18:06:01 there are some exciting possibilities for getting Fedora Linux on that platform with non-x86_64 arches and whatnot 18:06:21 the main technical blocker right now is we want them to use the Fedora kernel 18:06:37 also, we're going to start a team to maintain Shells images as spins 18:06:47 mattdm, dcantrell anything you want add? 18:06:48 .hello marianab 18:06:53 and the reason they aren't doing that is that they are using a custom initrd which grows the filesystem 18:07:01 we need to really make sure the SIG works for shells.com 18:07:12 where we left in the meeting it sort of felt like that was left entirely on us 18:07:19 we have tech to do that, but they aren't familiar with it, so I suggest that as a first start for the SIG 18:07:32 for it to work we do need to make sure we have some initial recruiting done for people to keep it going 18:07:39 dcantrell yeah I'm going to ping back with the person from their side tagged with it and offer some handholding 18:07:51 mattdm: +1 18:07:53 Too many exciting SIG and WG and too few time to devote to all 18:08:12 the custom initrd and resizing to me sounded like they just need some help on using the fedora tools to do that 18:08:21 we definitely need to attract some people with enginineering experience around those tools 18:08:22 I really don't think there's anything special going on with their setup 18:08:57 promoting the non-x86_64 arches should be highlighted in the announcement(s) 18:09:17 for me the idea of getting a Fedora system on power pickle or arrrrrrrrrrrrrm quickly is appealing 18:09:18 those will be running under emulation, rought? 18:09:26 yeah, it's all under emulation 18:10:06 also the Shells.com indicated that they're willing to give comp accounts to people in the SIG, so there's some carrot here too 18:10:15 I'm going to hypothesize that debugging on aarch64 in shells.com will be faster than fighting with something like a raspberry pi 18:10:30 probably! 18:10:31 dcantrell++ 18:10:31 spot: Karma for dcantrel changed to 6 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 18:10:36 mattdm: yes, that's very important to promote because no one is going to want to do this work or contribute in the blind 18:11:00 dcantrell++ 18:11:21 and not just blind, but without getting anything personally back, to be blunt. 18:11:31 yeah, pretty much 18:11:42 handing out an account does not really cost them a whole lot for what they will gain 18:12:44 I mean, it's cool to have Fedora in more places, and this is nifty, but I don't think it's going to be market-shattering, so it's a little different from the "we must work with the 90%-of-the-market-cloud-provider" in terms of _general_ benefit. So the specific benefits for contributors are really important. 18:13:03 And then if it really does take off, we will be in a good place. 18:13:23 I agree. They also seem interested in helping Fedora too. The idea of a shells.com sponsored test day is interesting. 18:13:24 This might be a little bit "quiet part out loud", but it's honest :) 18:14:01 Yeah worth noting that they're some of the people behind the PIA vpn and who have sponsored Freenode for years. 18:14:12 So they've already been helping us out in other ways :) 18:14:15 Nice 18:14:47 i am not sure SIG is the right format though 18:15:02 it doesn't look like they are going to be community-driven in their decisions 18:15:23 they were open to the idea of the fedora community owning the Fedora images for shells.com 18:15:24 they want to be 18:15:32 bookwar: our suggestion was a SIG around a spin or spins tailored for their environment. They actually _do_ want that to be community driven 18:16:06 but how do you define the goal? "Spin for shell.com" ? sounds not right to me 18:16:20 "Spin for aarch64 with ... features" ? 18:16:33 Why not? For a while the Cloud SIG goal was "make the best possible AWS image" 18:17:00 It's a specific-case spin, but... that's a thing spins can be. 18:17:05 ok, maybe i am out of touch there 18:17:19 I was thinking of Cloud to be a more generic think 18:17:22 thing* 18:17:57 I will avoid long disgression into history. Save for another time. :) 18:18:09 Anyway, i do agree providing the space for this work is nice. So I am just nitpicking on the choice of wording, but we can skip that. 18:18:20 :) 18:18:30 anything else on this topic? 18:18:34 I think that's all 18:18:39 I was testing the image and how it's now and it works pretty well 18:18:49 So, I'm +1 to work with them in the SIG 18:19:03 #topic Upcoming virtual face-to-face 18:19:16 all yours, mattdm 18:20:50 Uh, yeah :) 18:21:10 So, this is scheduled for next week! 18:21:25 Show of hands for anyone who remembered this :) 18:21:29 o/ 18:21:34 when next week? 18:21:54 It is 2-5pm US/Eastern 18:22:03 days? 18:22:08 thursday only 18:22:17 o/ 18:22:23 o/ 18:22:24 This is to replace the meetup we weould normally have at DevConf 18:22:33 okay, excellent remembering y'all :) 18:22:46 Generally, the November meeting is the big multi-day thing and this is a quicker check-in 18:22:53 * spot remembers nothing! muahahaha 18:23:00 thanks to Ben for setting up the calendar invite ) 18:23:31 To be perfectly candid, I do not have a defined goal going into this right now, but I promise a meaningful and useful agenda by early next week. 18:23:47 let discuss the survey again? 18:24:12 I think we'll mostly focus on existing issues that need to be tackled, a little socializing, and some future brainstorming 18:24:22 yes, survey is a good example of existing issues 18:24:38 Nothing super big and strategy-shaking. We'll save that for November :) 18:24:52 OMG I hope we can actually have that be an in-person meeting. 18:25:28 If anyone has suggestions for more things we should put on the agenda, let me know 18:25:32 now or in the next few days 18:26:13 I think everyone _should_ have that calendar invite. 18:26:52 I do 18:27:07 and looking at my other calendar I actually have it in there already 18:27:07 I do too 18:27:23 cool 18:27:42 I'm not focusing here 18:27:48 How many topics are left? 18:28:02 open floor :) 18:28:07 Cool 18:28:18 I really have to focus, so I will go out 18:28:23 See you next week 18:28:24 o/ 18:28:47 anything else on this one? 18:29:04 #info If you have agenda ideas, let mattdm know 18:29:07 see you x3mboy! 18:30:05 i have an open floor item I guess 18:30:10 #topic Next meeting 18:30:12 #info The next Fedora Council video meeting is Thursday 11 March featuring Máirín Duffy talking about the logo refresh 18:30:13 #info The Q1 Council virtual face-to-face is Thursday 11 March 18:30:15 #info The next regular business meeting is Thursday 18 March 18:30:27 #topic Do we have anything to announce? 18:30:29 #info This is a regular check to make sure we're communicating to the contributor (via CommBlog) and user (via Magazine) communities 18:30:34 i'm not aware of any pending announcements 18:31:37 I could maybe count my open floor item as an announcement even though it's not really new 18:31:49 and is in fact something we're communicating through the commblog 18:32:18 ben ghost-wrote me a post about my "call it Fedora Linux" crusade and that's going out ... tomorrow(?) 18:32:41 and I submitted this change: https://fedoraproject.org/wiki/Changes/Fedora_Linux_in_os-release 18:32:46 Tuesday 18:32:51 Tuesday is the new tomorrow. 18:32:59 #info Tuesday is the new tomorrow 18:33:00 I knew it was one of those "T" days. 18:33:48 Febturday 18:34:10 So anyway, please do your best to support me in using "Fedora Linux" instead of plain "Fedora" when referring to the OS or distribution or package collection 18:34:43 I will try but it's going to take a while to untrain myself 18:34:54 #info please do your best to use "Fedora Linux" instead of plain "Fedora" when referring to the OS or distribution or package collection 18:34:55 You don't (bcotton_!) need to "interject" to correct anyone, just start using it differently 18:34:56 we already went one way on the name, now we're adding things back to the name 18:35:09 dcantrell: yeah, me too. 18:35:13 dcantrell: it is very awkward the first 100 or so times 18:35:25 i will try 18:35:31 I'm going to go ahead and skip this rename and just go back to calling it Fedora Core 18:35:48 dcantrell: that joke is permitted. the one about Fedora GNU/Linux is not. :) 18:35:54 #jokepolice 18:36:00 dcantrell++ 18:36:01 wait, what really? 18:36:02 Southern_Gentlem++ 18:36:05 dcantrell, no Fedora Community 18:36:35 dcantrell: (no actual joke police) 18:36:51 mattdm, i will edit my blog post to say Fedora Linux updated iso 18:37:00 Southern_Gentlem awesome, thanks! 18:37:04 Southern_Gentlem++ 18:37:40 Basically, this helps us focus on the project as a community not just some bits, and _also_ makes it easier to talk about things we do that aren't those specific bits. 18:37:46 mattdm: are we renaming editions? Fedora Linux Workstation? Fedora Linux Server? 18:38:13 dcantrell: no, those can stay, because they're already "Fedora __________" 18:38:40 the blog post answers that question, but matthew is very excited 18:38:51 bcotton_ :) 18:38:57 I will hold my questions until the blog post is live 18:39:11 I also look forward to LWN's write up on the name 18:39:17 it's good to hear the questions :) 18:40:01 anything else? 18:41:28 I guess not :) 18:42:41 bcotton_ you still with us? :) 18:42:42 #topic Open floor 18:42:42 Maybe a November topic, but it will be after I am off Council. But the recent uptick of interest in SIGs would be nice to formalize. Or make a strategy about how Fedora SIGs work. Or can work. 18:43:16 jwf|m: thanks that's a good idea and builds on the stuff from our Minnesota meeting 18:43:38 Looking forward to CommBlog post 🌠 18:44:39 last call! 18:44:52 Southern_Gentlem++ 18:45:44 18:46:16 alrighty, thanks everyone! 18:46:19 #endmeeting