 Let's start. Hi, my name is Edward Lucena. I usually can be found on IRC or social media like Streamboy. I'm going to talk about the Fedora i3 Spin, the new spin that was released right now in Fedora 34. Today we are going to talk about the i3 Widow Manager. But before starting to talk about the i3 Widow Manager, I'm going to tell you what is a i3 Widow Manager and what is specifically i3 Widow Manager. I'm going to talk about the Fedora i3-C, the special interest group that is working to create the Fedora i3 Spin. A little bit of the history of the group. What are the objectives? We're going to talk about the Fedora i3 Spin. We're going to have a little demo and at the end I'm going to share the contacts for you to join to the team or collaborate in any way you can help the team. So what is the i3 Widow Manager? A Widow Manager is the software that controls the Windows position in a graphical environment. Every desktop environment has a Windows Manager because it's a separate software that is in charge of putting the Windows in the position that it's going to be. In that regard, a Tilly Windows Manager is a Windows Manager that doesn't require any other extra software and it puts the Windows in order in the form of tiles. Or she gives the treatment to each window as a tile. So the windows are not overlapping one of each other but they are put aside or below them or above them. And specifically the i3 Widow Manager is a Tilly Windows Manager that is written to be easily used by users and to be easy to configure. How is that? Well, normally Windows Manager are the configuration of the Tilly Windows Manager is done in the programming language of the Tilly Windows Manager is written. In the cases i3, even when it's written in C, pretty sure that it's mostly C, the C language, it uses an RCA file to be configured or a config file that is not written in a programming language. So it's easier to write and you don't require any specific knowledge of programming language. So the Fedora i3c, a little bit of history. It was like five years ago, maybe a little more, when the first my share committee get together in a presence meeting. I was presented by Justine, the manager I was using at that time Cinnamon, because it was very low of resources. And it was easy to use for me, but because I have a modest machine, he showed me the i3 Widow Manager. He showed me how little resources it uses. And I start to testing and use it for myself and I get used to it. And right now I know I don't stop using it. It's really, really easy to use. My workflow adjusted to that metaphor of desktop really easily. And after that, I was starting to create the idea from several people that was using i3 to create something that get i3 directly into the distribution without any other desktop environment. So, who wanted to work with, who liked that idea. I start to give very, very good feedback. When I started to see the first one, one of the first ones to be in there is Dan Semela or Defolos as we know it. And it turns that Defolos is the maintainer of the i3 package on Fedora, so it was very, very helpful. It was very, very helpful to have him in the team because he knows exactly how the i3 Widow Manager is greeting and how to help. And I put together kind of team, a lot of people just say, hey, why not? We're going to do it. It's a great environment. I'm already using it. Also, I contacted Ben Cotton, that is the Fedora Program Manager. And tell me that, yes, why not? The SIG is something that is easily to use. You just need, I have a visitor here. I know two or three people that are using it in Red Hat and I'm going to put it in contact with them. We already have a document that was basically the base we used to create the iSpin having the things that they saw which should be included in the district, in the Spin. So we started to having some packages that we saw are vital to the Spin. And we started to discuss we should include this, people that use i3 normally use this. We create a Kickstarter file that was put together by Nasir and it was put for the distribution by Odilon. So we just start to create the district. We have the goal to make i3 Windows Manager more approachable and useful for Fedora users. And the idea is not only because i3 is normally used by power users, by seasoned men, but people that love the keyboard because it's a keyboard driven environment. But because of the little memory it used and the little resources it used, we think more people can use this environment. Once you get hard to configure it or it's not hard to get used, how people normally think about Windows Managers that are hard to use. It's not hard to adjust your workflow to that and we want people to know that it's not that hard to use. So we gather these design goals and we discuss it and put it into our documents because we think that these are the focus we have to create through the Spin we are using. So the first design goal is that simple is better than complex. We are not trying to create something very, very complex to use. People just can get used faster. Fast is better than furious. Even when we include of course the most important features that Fedora is. By word like BTRF compression like the system the OOM. Our goal is that it is fast and low resource uses. There should be one and preferably only one obvious way to do that. And this is because there are tons of packets that do the same thing in our district because people love different scenes to do this. The configuration and the word data, for example, there is like, I don't know, like 10, maybe 15 PDF readers in the district. So we are trying to create one. We discuss it. We maybe take two, three, four weeks discussing if something is going to be included or not. What are the advantages? Testing it. How many memory, how much memory consume, how much is used in the community, how feedback you can get, how is maintained upstream. And to have just only one way to do this stuff in your desktop. And now it's better than never. We're trying to, this is something that we came across because people keep up. They're telling us that why we choose i3 that is based on the X server and no using Suai that is based on Wayland where X server is supposed to be deprecated relatively soon. And you say, well, now it's better than never. You can start the project when you want and the idea is just to complete it. No, no habit and a specific moment of the time. So we're going to talk about this thing. People don't know that as being a community maintained version of Fedora that you specific environment there is a there is there is another approach that is there Fedora labs. There are distributions that are potentially targeting one specific topic like astronomy, like design, like gaming, like security. And that is the labs. The spins are normally just Fedora with a specific desktop environment. So spins for desktop environment and labs for timing targets and created a spring in federalize not that hard. Normally you start like Fedora remix. You can check the documentation how to do it is really is not that hard. And if you follow the documentation we have in in the i3 documentation on on the Fedora docs, you're going to find that you only need to know how to write a kickstart file that is not that hard. So the Fedora i3 is really, really small. We have just a few software in it. And most of the software we have is RCLI tools. At the moment we are not shipping for example something that I got asked a lot to we are not shipping office suite. People just can't get the office suite they want because you can install whatever thing you want to include in your environment. So normally we have just Firefox because browsing the network is really, really needed. We have a network manager applet to control the network manager to control the network to connect to Wi-Fi or control or related to your network. We have an MSI that is the CLI tools from the network manager to control the network. If you don't want to use the applet you can do it just by the network manager applet. We have RSVT because we need to include terminal emulator. We have a program to control the background that is called azote or I don't know how it's called in English. I just pronounce it in Spanish is azote. We have mousepad because we have a text editor. We have tuner that is our file manager or the file manager we are pushing. We have dunce that is the notification system. And a lot of tools that are included in i3 like the i3 status and i3 log that are software that put the bar under the desktop and i3 log is just to lock your screen. So how we build the federal i3 SPIN? Gathering meetings to discuss what software is going to be included or what decisions we have to make. One thing is pending to create the distribution and we use the pagur issue tracker to do all of this and they get forced to maintain our Kickstarter files. So this is the link of the issue tracker we are using for the district. We get together normally in IRC bridges to two matrix. That's the matrix URL using element that is basically the most common interface that is used to get matrix. And once we get all together we put our Kickstarter in the Fedora Kickstarter. We have a member that is called Aldi Lon that is the one that is controlling the Fedora Kickstarter part of the Fedora i3 SPIN. He is doing amazing work contacting the relaying and all the engineers that run the infrastructure in Fedora to get our Kickstarter, pull it off with the parameters how it should be built. Even when it's easier to create the Kickstarter file to include it in Fedora you need to follow several, I'm not going to say rules but at least parameters to make it right. So he's controlling this and is working beautiful. So now I'm going to show you demo. I don't know how to stop this. I assume I should stop this and this again. So now this is the starting part of normally the Fedora ISO running. So you say just start. I'm going to show you this fast because the intallation process is long. I just want to show you something that I also get asked too much. People that is not familiar with Windows. You need to know the modification key or the modifier key that it will be the center of your workflow. After that, almost all of the windows, the modifier key plus enter to open a terminal and from there you start to work. This is the first configuration screen when i3 is asking you if you want to create the configuration or you want to use the default. And I use the so-called window screen. For a scale screen, you use X-Render or Render. This screen is not going to be the screen. This is just the installation screen. So when you enter the terminal, like I say, modifier plus enter, you're going to be showing a message that say type life to start the installer. You can say use life inst. And it's going to show you a super scary splitted screen that people get scared very easily. I think we are going to put the modifier w to expand the window. And from here you follow normally the normal installation flow in Anaconda. So I'm going to restart this machine. I already have an installation. Now this is your XBT. People keep telling that this is not the best terminal emulator, but it's very small and it's basically the one that i3 use by default. But from here you can install whatever you want to install. And now I'm going to show you more the features of the window manager, not only installation of software. So we have the configuration file that is something that people need to know is in .config. Slash i3 slash config. You do 3. Sorry. And this is the installation file. Don't worry about the text that you cannot read because it's green. You can just read the black text. And this is the standard i3 configuration. We are not touching the configuration file yet. We want to put some stuff, but right now we are using just the standard. And we just add the NMA template, the never-managed template. As you can see here, you use mod return to open a terminal. You close or kill the windows. This is the way to close the software using mod chief queue. And with mod D, you put D menu. D menu is the software that is used to run software to start your programs. Now, the way the tilling window manager works, and I'm going to show you a little of my magic here, is that as you can see, windows never get one on top of each other. They are always put in form of tiles. And we can start just walking around. So you can create an arrangement. I'm going to put it a little smaller. So you can see in the position you want. And you have until 10 work spaces, work spaces. So you can have one, two. If you see, then you cannot see because it's super small. You can one, two, three, four, five, six, seven, eight, nine, and zero. That is the 10 one. And you can move windows from one space to another. And you can see there is an inactive workspace because there is a window there. I put it there. I can move it to the 10 workspace. See, now the idea of 5.3 is that you can have a tree of Boolean tree of own managers in a different way. But you can also put it in form of tabs or a tablet layout. When you can say here in the upper part, there are tabs with the application and they are all full screen. I think with the tilling window manager that normally get people mad as the normally applications room full, not always applications are made to room full screen. For example, the calculator is not intended to be used full screen because it's a small application. But you can make your window floating. It's not the idea because you are using a tilling window manager why to create a tilling use a floating window, but you can do it with window chief space. You can move your windows around with it again. And other thing is that you can resize your, your windows. So I think this is very adaptable to every application I normally use as a CSAT mean now a DevOps engineer. So this type of configuration works for me very well. Everything that you can install in Fedora is installable in our Spring, of course, everything that is in our repos. And we have used a few number of programs. I normally recommend people to use to switch the menu for the menu desktop. And I'm going to show you the difference. I'm sorry, I'm used to beam. Oh, how do you get out of nano? Yeah, I know the screen is too small. I just want to show you this up here. You can see there is like the name of comments, no programs. So if you can find. But if you use the other configuration. Fresh. Why is this not working? Yeah. Something is wrong with my screen. Just give me a second. This is a friend. I didn't know what happened. Let me stop this a little bit. And now I'm going to share the entire screen. This is my I3 desktop environment, my complete desktop. So if you can see up here. There is our desktop files. That is the difference between them. Okay. This is the difference between the D menu and the I3 D menu desktop that it runs with desktop files and not with comments. And because I'm running out of time, I'm going to put the next slide to give you a little moment of question to get involved. You can just get yourself into a meeting in the IRC pound fedora.i3 or in the matrix. It was shared in the chat. You can test the image we built. You can help packaging. You can help testing. You can help documenting. Into a meeting or into a room and just chat with us. Our communication channels, like I say in IRC is pound fedora.i3 in matrix pound fedora.i3 column matrix.org. In telegram we have the ad fedora.i3 or our mailing list that i3wm at least dot fedora.project.org. Just write to us and start working with us. If you have questions, the QAA tab, sure. I always forgot that. GTK application, for example, takes more than a minute to load. Usually just a way window to a sensor load. Any recommendation to fix that? Well, I never get this problem. Maybe you need to check how much CPU are you using or if there is a problem reading your disk. But no, not specifically with the environment. I don't have any idea of what can happen or why this is happening. Will there be a test day for this as this seems to be something gaining popularity? Yes. We tried very hard to have a test day before the fedora.i3.i4 release. But it got hard to get involved because I was doing tons of stuff and life happens. But yes, we want to include a test day. We're moving our ticket for the testing or the issue. We are using our issue tracker from fedora.i3.4 for fedora.i3.5. But yes, we want to create a test day with you. Is there a key to run a program that is not a terminal? You can set that. Normally, there is not set it. For example, I have in my configuration, I have a mode chief F to run Firefox. And mode chief V to run Vim or VIM. How do you get the batch for the release party that you have to ask the moderators? Also, I'm not sure how. Maybe we can have the answer in the chat. But yes, Luna, you can create any key combination to run a program specifically. Terminal is one that is set by default because it's the start of everything. But you can set any program you want or you like. I used to have Genome screenshot. That is a screenshot tool that I'm using. Firefox Vim. I think that's brave because I use the brave browser in my work. Set it specifically to a key you want. So you can create any combination of key you want to launch any program you want to launch. Also, I modify my menu. I'm not using the menu. But yes, you can create any combination you want in your .config. It's the .i3.config. If there is no other question, I think I'm past my time for two minutes. So, yes, I'm over time. Thank you for coming and see you in other rooms of the place. Thank you for coming. Bye.