 still not recording. He's preparing to record. Now he's on. Well, this is the Fluorite 3C meeting. We have the agenda. I'm going to put the agenda in the chat here just to have it. I think everybody took some time to read today's agenda. Let's see. If you want to present yourself or we'll proceed directly to topics as you went. Come on. Don't talk to everybody at the same time. Okay. Let's see. And the topics we have to discuss today, we have the final chance proposal review that was in charge with Justin. Okay. I call to introduce yourself and nobody talks. That's why I jumped to the topics. But that's okay for those that could. I'm sorry. I can introduce myself. I was paying attention to another email. So I talked to you guys at the issue for the package group. My name is Odulan. I'm from Brazil. I'm using Fedora Wifi 3 for the last five or six years. I lost account. And when I saw you guys doing the work to create a new spin, I was interested on that. So I do work for Red Hat, but I do not work at Fedora. So that's, there's that. Welcome to the group. I love to see people interested. And this is kind of my little baby with the guys we founded the i3 sync. Because basically, because we want a way to have i3 without any other, don't have any other desktop stuff. Just i3 directly. And because I'm constructed the address. A good environment with the i3 window manager from scratch, just from the basic installation is quite difficult. So we want to make this more approachable for end users. And that's why we are trying to make an ISO that come directly with i3. And my name is Egor Lozena. I go as a stream voice in almost everywhere. When you can find me as a stream voice, I'm streaming Linux. For example, in Twitch, I'm streaming Linux, not stream boy. But, well, I'm from Venezuela. I live in Chile. I work in several parts of the Fedora project. I don't know what more to say. Dan, how about you go next? Yeah, hi. I'm Dan. I'm the current package maintainer of i3, which I kind of inherited and then jumped on that because, hey, I don't do that much about it. Anyway, so that's more or less my part of the story. And since due to my day job, I've had a bit of experience with OpenQA. I've started, I've currently started porting the OpenQA tests also support to also run on the i3 ISO so that we don't have to do every single part manually every time. So yeah, that's more or less what I've done so far. Come on, Naseer. That's your turn. So my name is Naseer Hussain. I go by the name of Naseer HM in the Fedora community. That goes from an IRC matrix everywhere. I'm Naseer HM, including my FAS ID. I am currently working on the kickstart part of things to get into, to get everything that we discuss in two code and like collaborate with the respin stick to create a respin for the kickstart. So that's something that I'm currently working on along with some documentation and all that. So I think Justin's about to join as well. I think he'll be, he says that he'll be a few minutes late. So I think for the first topic that's about change proposal final review is Justin's topic somehow. So Justin or the one who was working on it. Yes, just let's move to the next one and we will for Justin to talk about the proposal. We have from the next topic. Can we throw in another topic? Yeah. And so that's concerning if we want to have some sort of autos, some sort of desktop update notification service running or not. That's essentially we have a notification demon that's danced, not enabled by default, but it's there. At least I think that's the plan. But we have, so the open QA tests of Fedora include also a, also tests for desktop update notifications. And the question is, do we want to have that as well, which is more or less a matter of opinion? Well, to be honest, we discussed this in the IRC. My problem is not that we can show the message because I have those in the installation I had. But my problem is that those notifications usually are kind of a little late. I don't know if the update takes a package from package kit or from the DNF database or something like that. But normally when they show up that you have some updates, I already updated like five minutes ago. So I don't know why that happens, but it happens in every desktop I tried, in Cinnamon and in LXQT, and it also happens with Dunst in entry. So I think, to be honest, I don't like the idea to enable the, we do have updates notification, but for sure we actually have notifications system. So I think there are two different topics there. Once they have notifications and then include the notifications. Yeah, so I actually don't care about update notifications. I haven't used them ever. I don't even have a notification demon. I think it's distracting and annoying. So I'm from the same group as Dan. I don't use that update manager as well. It's always DNF update on Fedora machines. So let's not include that. Great. We are doing great. And what about the current notification demon? Like do we want to enable it by default in the live and in installation? Or do we want to... I think we don't need it in the live. I think it's okay for the installation. Okay, so we want to enable it after installation. Is that what we are thinking about? Yes. I don't know if Dan have other view point of view. I mean, normally we are going to use the installation just to launch Anaconda. There will be just a few people that is going to use it to test and they can enable it manually, I think, if they need it. I mean, if we are putting it into the install, we might as well enable it on live. I'm not sure if that will make a huge difference. Then can you just ensure one thing that if the notification demon is... that if when sent a notification, Dan's just working or not, because I could remember the last time that I worked on this pen, it was actually displaying the notification. So I'm not sure if Dan's needs to be enabled or it gets enabled when we install the package. I don't think that it gets enabled by default. I think if you install it, it's just there and you have to actually start the thing. Once you start it, it hooks somewhere via I don't know, D-Bus or something like that. I think that you use NotifySend to talk to D-Bus. I don't know if Dan's was NotifySend. Let me check. Dan listens to NotifySend. That's what the current open QA test is doing. It's actually just a start Dan's. Do a NotifySend foo. Take a look if there's a notification called foo and if it disappears and that's it. So it doesn't do anything more. Yes. Do you don't need to have a demon running? Oh, so it'll like actually listen to the send Notify in case we don't have the Dan's demon running. That's what you're saying. Like Notify listen actually sends that to a Unix socket or something and then Dan's like it goes via D-Bus. Yes, it goes through D-Bus. Through D-Bus. Sorry. Thanks for the info. So is that a plus one from all of us for Dan's? Yeah, I thought we agreed on Dan's. The thing is it's, Dan's will listen to D-Bus, but you have to launch it first. So just installing is not enough. If you want to have notification, you have to launch it once, which would be actually my preferred state of this since otherwise people who don't like it have to somehow kill it, which has been surprisingly difficult. It's easier to opt out than to opt in is what I'm hearing. It's easier to opt out than to opt in. No, it's actually easier to opt in than opt out. Yeah, opt in is just launched once and opt out is find out how to disable the Dan things. Okay, so, hi, Justin. But don't worry, that's okay. Well, I'm okay either way we choose. I do think it's necessary if we are going to include it, we should launch it by default. It doesn't make any sense to have it there without being launched. Okay, that's correct. Okay, so like we have agreed on enabling Dan's for the installation as well as with the live. So it should just enable itself or oneself once and then you can send the notify send to it to D-Bus. Okay, cool. So have you updated the MD pack, Edward regarding it? Okay, that's great. Thanks for everything. Yes, I viewed a new section called Agreedments, so we can just put what we discussed here. So I think as we agreed on the Dan's part of things, the first topic for today's meeting is about the change proposal, a review that Justin was actually working on. So Justin, would you like to provide some information regarding it? Yeah, let me share my screen really quick. Okay, can you see my screen? So this came up in the mailing list earlier and maybe you've had a chance to read through it already, but this is just the current draft for the Fedora change proposal, what we're targeting probably for Fedora 34. The only things I had wanted feedback on before, oh yeah, and I added this section of what Twitter had to say about our change proposal, but the only things that I was looking for final feedback on and I saw that DeFolos expanded on the how to test section with some notes there. Was that section getting a review on this section, how to test, and then the scope section, just getting a quick pass, not on this stuff, these are things that, well maybe some of these, but I don't think these, I'm just getting more a look over on the overall process of the scope, making sure that makes sense. There's no surprises in there or that we're not missing anything huge. And then all we have to do is just rename this wiki page to the right namespace and change the category from change page incomplete to change page pending and then Ben will just post it to the development list for us. It will all happen automatically, as I'm told. So that's all I have on that. So really it was just making sure that the scope makes sense and if we're happy with the test cases that we have written there. If we are, then we're good to submit. I have one question. The relaying issue number is also done by Ben with his auto magic with Audrey. Yeah, so either someone in Fesco or Ben will open a Fesco ticket tracker for the change. I actually haven't gone through that. No, go ahead. Sorry. If we include like a telegram feedback, we are going to have 3000 pages of people wanting the I3c to release this. No kidding. We could even make it just a dedicated wiki page just for that. Cool. Well, if there's any questions or things we want to talk about with the change proposal, we can now. But really I thought it was just going to be getting a quick plus one or just reviewing it, leaving a comment in the ticket with your plus one if it looks good or any feedback you have. And then we'll get this started. We'll make it official and we'll submit the change to Fesco. So I never find the ticket number in Pagger for the proposal. I've been lazy enough to don't look for it. So if you can tell me what the number of the issue is. I'll drop a link in the chat here in Jitsi and in the IRC channel actually. Dan, were you going to add something there? Yeah. So I recall that a while ago some of you guys faced some GTK race condition thingy. So in case that I don't know if it's been already resolved or what, but in case that was a relatively common thing, add that to the how to test that it's not that people do those steps that you use to reproduce it. So just to ensure that it doesn't occur again, since I never saw this GTK race condition on open QA. I think that's something related to the hardware side of things. And I think Edward will be able to provide a better insight on this one because I think he faced something similar on KVM team of 12 creating a virtual machine. And like, I'm not sure that's like solved yet, but that's similar for S sugar on S610 as well as IP. So it's something that affects both of us. Yeah, I think it's not related to itery. So if it's going to be solved, it isn't going to be solved by us, we can just document it. But it happened specifically with my hardware, because in virtual machine that doesn't happen. And it happens when I was launching the Anaconda command from the command line. I wasn't using Dminion in the live inst command. I was using Anaconda dash dash graphic, I think I don't remember if graphic or GUI instead of using the live inst command. And at the end, I finished my installation with the text interface of Anaconda. It was kind of hard, but it was fun for what it is worth. And it proved that it's not an issue related or itery or even with the installation process. It's something specifically with the GUI live inst. And I think nobody else faces that. I don't know if anybody tried the ISO in very metal and not in virtual machine. But I don't know what further we can go from that. Maybe we can include a test case from some hardware and prevent people? I don't know. I think if we tell people just install it, then they should hit the bug if it's still a thing. And if not, then all is fine. Since that was just essentially does the install or launch or doesn't it launch? So I was thinking about adding something in our documentation about it that if in case it could be in our frequently asked questions that if you face something like this, you can follow the text live instead of the live inst. So we can, what do you think about that? Also, the matching with that, when I do that, when I raise that condition, it's still pretty much empty. So I can reinstall any time we need to test. And when we have a new fresh ISO, that is the next topic. Because the last ISO is kind of old. And we have included still the mouse pad change from with G edit. Oh, sorry. But yes, I can try it again in documented. I think, I don't know how we can treat that with a chamber proposal. It's going to be like a blocker for some reason to launch the spin to face this, because I think I remember. Well, if you can't launch the installer, that's kind of big blocker. So but I think we don't, I think it wasn't the only one that faced that. I think lxqt also. I don't remember who say it. Say that in the chat. But I'm pretty sure somebody say Yeah, I was just wondering, did we think about posting to the spins mailing list? I know it's not very active, but there's a good chance that if someone else has run into this before they'd be on that mailing list. It should that's a great idea. I can dig up a link on the mailing list if someone wants to take an action to just drop a drop a note there and ask about the race condition issue. Yeah, please. I can try. I can drop the mail later. If nobody take on that, I can take it. For the current evaluation of the ISO, that's actually some of my part that what we are currently having. So let's just quickly go through what we can what we last added in the in the kickstart file for the ISO. So as far as I could remember, the packages were working fine in the last respin build. But there was an issue that that caused the wallpaper to not working fine in the live side of things. So on the live, I've actually created the way we've added a pay package to set wallpaper. There would be a more minimal package that we can search for and use that instead. Or like, if you any of you have any recommendations like something really really like that could that's just used to set the wallpaper. Or like we can use that and that's what I've fixed in the past days. So it's the current year of status that we have live and installation where you can find the packages we have installed by being tested automated tested by the dense deflows. And that's what we have worked on the last I just love it. I don't know if there's anything lighter than fear. But say so light. It feels the lightest like I was thinking about something the lightest thing available just just out of curiosity and wonder that if we could go something more lighter than fear but I hope you've got maybe a good with fear because it's working fine. If there's something more lighter than my good. Maybe we can start for like the initial launch over the spin to use fest and that's what we have and we know it works. And while it's still maybe not the most it does a lot of things I might not be the best tool for the job. It's the most convenient one to us now. It would be cool I think to probably make a ticket to actually look at how the wallpaper gets read on the system and maybe see if there's a way that we can do that in an I3 native way because we have the package for Fedora with the wallpapers but that would be a nice to have. But I have a question just for the live session we really need like the M to be launched. I think we can just start X in the I3 with a live in common running. I don't know just wondering. I'm pretty sure we needed to when after three kind of expects nowadays to be launched by a display by an actual display manager. So you can do it by a start X but if stuff breaks you are on your own. So I've run into issues with Nvidia graphics cards and start X and upstream told me essentially please use light DM and with light DM it works. So they don't they it's essentially start X is effectively broken. No that's okay. I was just wondering just trying to to look another maybe another solution but if it doesn't work it doesn't work. It works most of the time. It just breaks sometimes. Yeah we need to avoid that sometimes especially because we are going to have a lot of people that want to have minimal resources with their Nvidia card to power of maybe data gaming. There was actually what most people talked to me about the I3. They want something really really minimal more minimal than than anything to leave every other resources. So nice. And to be honest the Steam package was really smooth with I3 in the background. I was playing Contrastrite Global Offensive and it was awesome. I was using it DXVK with I3 and there's no wreckage trap. So it was amazing. So Nessir so what's the final situation that the current situation from DAISO? So we can talk with the with the respawning people with the third gentleman to to produce a new ISO right now. We have to see some certificates. I would like to add just one thing there for collaborating with the respins. I think it would be better to wait a day or two because I would have to rewrite the kickstart actually removing some of the XFC stuff that we have there along with splitting our changes into specific into different files because you would actually have to include the Fedora repose file because that's where all the Fedora level changes happen. So in case a system change lands so we wouldn't be able to modify the flatten kickstart but if it would be modified so if it would be modularized then it would be much easier to do that. So it I'll most probably get it done in a day or two so if someone could assign an action item to me to split the kickstart and and collaborate with the respins to build it so it'll most probably take a day or two for me. Do you want to put that as a follow-up for the next I3 SIG meeting? Yep. Yeah that'll be a good idea so I could demonstrate the new kickstart and show how clean it is then how clean it is and how messy it is now. Super. So we'll go and why don't we set that as the follow-up for the next I3 SIG meeting. I'll put that into the IRC chat. Sure. You are managing the IRC meeting with Subbot? Just more like collecting the links and the actions. Yeah sure because I wasn't paying attention to IRC. No yeah I'm just like dropping like just notes and stuff in there not not anything like chat. No we are because Nasir and I we are working on on the happening so we are putting everything there. We forgot totally about IRC. Oh got it. I wasn't looking now I see it. So I think let's move with the next topic. What do we have as the next? The next topic is the is weird part talk about it and several points but we are talking about the QA. So in this case our guy is done so he can help us to to understand a little bit more of the open QA test cases. What do we need from that part? What do we have to do? How we can help you to move this forward? In a nutshell unless you want to spend a few weeks reading up stuff you can't. It's not intended as an insult but the open QA is not easy to grok so it essentially comes down to I'll eventually submit submit my changes to the test repo and that's probably have and figured out with Adam Williamson how how they're going to like it and tweak it until until they're happy with with everything. So I mean the the one thing which is relatively easily possible is that everyone thinks about possible stuff that they want to test. So for instance in I in I3 should I don't know I want tiling tabbing etc pp to work and I don't know in mouse pad sync text highlighting should work or comparable stuff like that but besides that I'm afraid there's not too much that can be easily done. Well basically I think I was trying to look at other tests from other distant environments but they have too many stuff that they want to be able to do that we don't want to be to have for example they have test cases to library office to open a document but we are not including library office because that we are going to let people to choose if they want library office or or kde office or the genome office suite that I never remember how it's called or they are going to install each application separately that's why I have problems. I think I was the last thing I was thinking about was to include cops or some print management but I think also for I'm kind of torn because for power users it's okay to don't have it because it's super easy just to install and configure but for final users maybe they just want to plug the printer and just launch system config printer and roll with it. For that uh so I have a point about for people trying to learn open qa so dancer mac deflos actually has some really awesome rich live streams where he have demonstrated the open qa 101 and how can anyone get started with pearl and open qa and some basic testing stuff so go check that out and learn open qa in a year where that's open suce specific open qa is a lot about convention and adam tweaked open qa a lot quite a lot so it's his instance is quite different but the basics are the same but adding a completely new uh a completely new test suit is a little bit involved but I mean I can um I mean I'm not I'm not discouraging anyone from getting started I'm just saying it's going it takes a while to get into the system and open qa is something in itself that's great uh Justin you would like to add something yeah I was just going to come back to Edward's question about the printer um I I think there's a a way that we can I think there's a compromise there because I think what we can do is ship something that's like a simple printer configuration utility just like you'd have with GNOME settings or kde settings if you have that desktop or you can go and manage your printers if we could find like whatever the xfce equivalent is or some other desktop environment that's a little more modular we could put that in there and leave it to the user to go beyond that um because like my experience as with printer drivers um first it's a gamble of whether they have them for linux or not and that they do then you're usually running like all kinds of crazy shell scripts is root and downloading from there there's you know printer drivers are a mess so I think just leaving it simple with just like here's a tool to help you do that stuff that's okay but we don't have to go to the extent of trying to make i3 the perfect printing environment for linux people are still trying to do that after well decades but my printer is using a 10 years old driver that is never updated from the factory that I have to install with the 32 bits package because it doesn't have a 64 bits package so I understand what you're saying yep so I think that's that's my feel on on the printing side of it we can just do like a simple app yeah and is here go ahead uh so uh as we have like have some I think there would be some research needed on the printer side of things other than that uh I think uh the third topic was that we would like most probably thinking about organizing a test day or test week where people can test our ISO and like defaults is automating all these testing stuff so I think it would be great currently to start documenting all of them because one thing that I've seen with test days like I've I started with participating in some of them with Fedora so I did find that those tests were actually very well documented that you can follow them step by step and perform the operation and test if we required the expected outcome is coming or not so that's what I'm thinking about that if we should start documenting those test cases in our docs to be used in the test day or test week so what's everyone's thought on that because like collaborating with open with the qa team would most rapidly need that I think we agreed some time ago that we are going to include uh volume icon and this will manage your outlet from the installation starting it's okay or I'm okay or I'm hallucinating I thought we wanted to collaborate with qa for test days yes because uh I have we have this document that probably a few of us read a read at the beginning it was from some guys from friend had that was thinking about the an i3 spin or or cd dial with i3 and one of the biggest comment I always all the time I read this the the comment of the good network manager is one that hits me because configuring the network from the cli is not straightforward if you don't know the nmcli it's painful to be really really honest we get used to because we did it a lot of time probably but but it's not easy and nobody's going to be familiar with in in the user line from the power user line is different because we tend to do everything with the command line but I think we need to is for me it's like we need it we really need a network manager graphically and in the in the first installation when it's recently and network manager outlet to the work pretty smoothly and from the volume there is no easy way to use pulse audio either so I think the volume icon is also a plus one for me it's what I use in here so I have nothing against and power control as well I could not live with a lot of headphones without power control so so for me I have like copied Justin's i3 config so that's how I actually started with i3 so I have got that volume stuff covered so if we have any package I'm not sure what package do we use for that so is that power control just in that view icon that we both are currently using in your configs power control so I can just do a quick screen share here it's just the pulse audio volume control application so you'll see here you have all of my sound these are all my sound to put some of these are going to be the audio and stuff from the call but if I was had Spotify here I'd see Spotify volume oops but let's not raise the volume so it's that thing that opens when you say open mix open mixer see yes okay right yes you can control your input and output devices and do different audio profile configurations so I was actually using the command line all the time without knowing that we have some GUI so there's been something really changing for me so I was still it's a plus one from like we shouldn't we can't expect the end user to be using the command line as I am doing so I think it'll be a plus one to figure out yep so we agreed to include these three things network manager applet a volume icon and problem control and then we we there is a QA test cases for that or we should include it or what for sound for sound and network management uh there might be one for network there's I think there's none for sound let me take a look well then if you can look at that I would like to ask what icon are we like thinking about adding in that's been like uh it doesn't even have any demonstration for the volume icon because with network manager straight forward but I'm not sure about volume so do we have that package or what package is it for that so please like can someone tell me about the package or so not sure if I understood the question about the package names like the package would we be using for the volume icon that's the question the package is called volume icon like that's the name just like I put it in the in the having the this volume icon that doesn't have any other name and it's just a little icon that has volume control and you can just uh oh he goes but that you can just roll your mouse wheel over it and put more or less volume and from there you can launch the the power control it's just a little icon from with the volume thing okay if it's volume control then I think we've added that and uh okay so uh Justin created and agreed so yep thanks Justin uh now I'm gonna add that so doesn't know there's definitely no sound tests on open qa that should be possible to include but I mean I know open qa can test sound but I've never done that but it would be interesting to take a look at that but I wouldn't I would maybe defer that for later and networking is essentially the same thing although that might be even a bit harder to pull off but checking whether the something like network manager applet or stuff like that shows up that's relatively easy to do so you can do that I have a question uh SORC takes care of the hotkeys from volume control and brightness and everything else right from the keyboard when you put the you have a button a media button to volume up volume down mute I don't know because uh I was reading again this ideas.nd and it says that they want something to take care about it and I think that's managed directly by by SORC by x11 by the x server you don't have to configure anything I never configured anything to have volume up and down with the with the hotkeys I think I always configured them manually so I've never heard of this package maybe we should include it then since that sounds pretty convenient but I think it's part of the x suite because it's working right now with the current uh i3 I just uh when you when I launch my i3 configs I just call the key with their with their x name it's like x free something that's true I never look at how they are working so maybe something with the firmware from the keyboard I don't know so what I'm also the hotkey for for play is called xf86 audio play fx adc audio pause fx adc audio next but I never configured that names from the key hotkeys they are configured by the x server I think at least I think those keys are actually configured by default and in the i3 config file you actually bind those keys to fax tl is that what you are referring to at work yes so I'm using the same thing and just since most probably using the same thing as well no that's okay I was just uh taking it because it's uh in the in my list of of things that people ask it was about this uh hotkeys management from from volume and stuff like related to what I think what in my time was what's called a multimedia keywords when they have the play and pause and volume up and volume down that's great so I think like that actually happens by default so we wouldn't have to work on that I think we have another package that I actually created an issue for a ticket fund that's uh dex auto start so I think I would give just a quick introduction what the package is all about it's about uh with the different desktop environments like gnom kde or xfce lx cutie what it does is it actually reads the uh dot desktop files in a specific directory and when you when you install a program like skype or zoom or something like that it actually creates a dot desktop file in some directory where your desktop environment reads this form and whenever you start your laptop it actually uh starts those programs in the background so it actually is helpful for programs like skype and stuff but we don't have that in i3 so there's a package called dex auto start what it does is that it actually reads through the the directory and finds the dot desktop files and starts them on once the session started so I think would that be a plus one from all of us or does anyone have any I'm still zero on that because I don't use those desktop files and would neither need for a for a program to start some application for me which I have installed previously it could be a zero from my side but what about you guys I don't know my my a tree starts things for me when I launch the session without we start or as I start I think really it'll be a thing that's interesting for people who are migrating over rather than people who are new installs so if you're coming from another desktop environment and you're uh if you're installing the i3 core group really this would be more of that use case and it would be for the spin that should make it pretty easy to adapt so at least all your applications you already expected to launch it open we'll still do that in i3 but we will need to make a documentation for that right because people will not expect to launch how it will auto start so we will need to teach people how to use that actually one thing I wanted to just bring up before the end of the meeting we were talking about some of the test cases this kind of reminded me of that um was we're talking about test cases and maybe getting an idea of what software other folks in the community might want to put in there I was going to suggest what if I um worked with the poll with the cpe team to do a line survey poll about some of our like how would you want to test the you know what do you what's your use case for fedora i3 like what are the things you do in i3 and maybe we can try to design test cases around some of that feedback but um I'd be willing to do some of I've been meaning to look at line survey for a while already so it'd be give me an excuse to finally go ahead and try that out if that would be helpful to get some feedback yeah sounds good sounds good to me too also I think uh there was a guy at my mind is way too easy I have a fish memory but there was a guy that offers to help us to customize the look and feel but because I think um I was looking at the beginning of this journey I was looking for the major right to the community edition and with the regular linux that came started with i3 and I was looking at instant os that is an another window manager but company started in the with that uh linux flavor and everyone tends to put um something that helps people to know the the most useless hotkeys and I don't know if that uh maybe was a thing for us maybe I don't know I don't want to include it in a wallpaper or put a conky over our desktop because I don't like conky at all but at least we can link a document or put a firefox bookmark with the i3 documentation for people to look at the first key when they are going they are just starting with i3 to help them I don't know what do you think about that yeah I think we could probably publish that in our our docs like kind of like a getting started kind of a section of our docs for people who are just starting to use the spin or that package group yeah because normally I another thing that people use a lot is to use i3 gaps but to be honest I don't like it and I don't use it also it's a patch that is not official anywhere so it's supposed to look better but well I think as we are running out of time we have another uh uh topic that's about package groups and we have Odi Odi how am I pronouncing your name right so Odi how okay the way that it wants so uh like uh so if uh Odi have you have any questions regarding where to get started with or my main question is what packages are we looking for to include at the first group i3 core like are we going to include i3 um let me get the from the kickstart we have i3 i3 lock i3 status danced fe and bright light only these five packages for the i3 core or I will like we will include something because I will start to work on the the proposal for the guys to include that on Fedora 34 science hits or target release I think Nassir this is the poll request you'll be making by the next meeting right with those changes that we've been kind of working on in discussion or do I have it misunderstood so for the next year that I am actually targeting is about breaking and splitting the pitch start along with the cleaning most of the I accept the packages and just keeping the I3 one so that will be a good starting point for Odi out to go through them and like we can in our next meeting we can discuss which we want in the I3 core and with something I think okay works for me also I don't know how to build or create package groups if I think that part of your experience or Aria you want to contribute with us yes that there's a doc that I link it on the issue it's let me paste on the on the chat we do have our repository that is called Fedora comps and each release will have the IXML file with the packages it's just a group of packages that we call so KDE has one comps Gnom has other so it's really simple from what I could get we just need to introduce ourselves to the guys at the development and explain why we need this at least from what I could get super yeah now that you link that it I remember that that's that's how those come together in the distribution so I think that would definitely be the right direction to go as soon as we have basically I think we just need to get the package list in the kickstart and then we can just use that as a reference point for when we go to the develop list can make a even make a pull request to the Fedora 34 comps list so I guess then maybe maybe then as part of that pull request for the kickstart just to make sure that we keep progress moving can do you think that we can get the full list of the packages to date that we've talked about adding in discussion in the past meetings to the the the kickstart file in the pago repo sure and it'll most probably take a day or two because I'll be breaking that split it kickstart into pieces and using include statements and build it on viewer this awesome cool so I think we have a plan for open floor from go ahead for one minute and for open floor I have the the calendar we have a problem with the calendar it shows like three meetings in one day at the same time so I don't know why this is happening and actually I don't know what calendar is the current one to see what ones which one we call delete and leave only one or even who have admin privilege in the six calendar to to remove this so we should ask we need the polls help he was the creator of all three of the events so he's the only one that can create them unless we ping maybe it's kevin nirik someone from come on character should take care of that no in that case it's either it's either the poll or we have to go to like the highest level of admin and fedo cow which is probably going to be like five people I get one of them to clean it up so it'll be easier we can get the poll to just go in there and fix it for us yeah let's go to the an action just to remind me that I need to talk to people to do this uh let's close because I want to eat it's lunch time here sure I'll put an action in the IRC for the follow-up on that and we can wrap there sure thanks for cheering thanks for coming bye guys