 So it's five o'clock, so I'm going to go ahead and get started as I have a lot that I want to cover today. But first, following up on the presentation right before mine. My name is Joseph and I got involved with a new Linux, maybe about 10 years ago and have been very enthusiastic about free software since then. I was first introduced during my studies in experimental linguistics using Linux for corpus linguistics and analyzing language in that way. But today I'm going to talk about something very different. I'm going to talk about energy consumption in software and how to eco certify your software. This is part of a project called Katie eco, which is comprised of two separate projects, which I'll talk about during the talk. Before we get started, there will be a lot of links and references in the talk. If you would like, you're welcome to download the slides at our GitLab repository. It's invent.kde.org slash teams slash eco slash be for false. And there you will get links to many of the sources that I'm referencing today. Just so you know, similar to the talk this morning from Matthew Miller Miller, I'm very distracted by chat and other kinds of things happening in the screen. So I'm going to close the chat for now and hopefully we'll have time and I'll open them back up at the end so I can answer any questions and engage with the fedora community. So some background before we get started. There's a report from the Association Association for Computing Machinery in October 2021, which estimates that the ICT sector contributes about 1.8 to 2.8% of the global greenhouse gas emissions. This number includes everything from desktop software to internet services and servers to data centers and blockchain proof of work systems and things like this. To put that into perspective, the global aviation industry is estimated to contribute about 2.5%. So we're more or less in the same general area. What's contributing to this? So many people think about digitization as being a way to reduce CO2, right, instead of traveling by airplane to a conference where we can all get together. Now we are meeting online and therefore saving a lot of greenhouse gas emissions. But in the past 10 years, there's been an explosion in the ICT sector. For example, the area of artificial intelligence increased by 300,000 times the energy consumption between 2012 and 2018, and now is doubling every few months according to the report. And the number of internet connected devices is predicted to increase 5-fold between 2015 and 2025, where there will be over 75 billion internet connected devices. And on the trend that we're on now, if this continues, the report estimates by 2050, the ICT sector will contribute about 1.3 of all global greenhouse gas emissions. Let's take a look at the distribution of what's contributing to the energy consumption in the ICT sector. So this is a graph. This doesn't include certain things. This is from the SHIFT project, which is a French nonprofit, which is looking to move away from fossil fuels. This does not include blockchain technology. It does not include transportation energy consumption. It also doesn't include end-of-life treatment. The graph is sort of broken up into two parts. On the top right, you see the energy consumption for production. And on the bottom left, you see the energy consumption for usage. And the production accounts, according to this data, this is from 2017, so it may be a little different today, but it gives the general idea. Accounts for 45% of the energy consumption in digital technology and usage accounts for 55%. Now, in my talk today, I'm going to talk about things that are relevant for the production energy consumption, as well as the usage, what the referential is, terminals, so any of the devices that we use. I have nothing to say about data centers. I have nothing to say about networks. I might reference something, but it's not the point of the talk. And I have nothing to say about blockchain technology to put some boundaries on what we're going to talk about today. And the main takeaway message that I have today is that the two pillars of free and open-source software that is transparency and user autonomy already put free and open-source software at the forefront of sustainable software design. And it's not me, just me, that's saying that the Blue Angel eco-label, which is the official eco-label of the German government, also recognizes the values of transparency and user autonomy as being crucial for a sustainable digital future. I'm going to talk first about energy in a few different ways in terms of energy efficiency, energy conservation, and energy sources. And then I'm going to talk at the end of the talk today about the Blue Angel eco-label and how to eco-certify your software. So first energy, different aspects of energy consumption that I'll talk about. So energy efficiency. By efficiency I'm referring to doing the same task, but requiring less from the hardware that you're doing it on. So the result is the same, but the energy consumed is decreased. Energy conservation is about eliminating unnecessary processes which are going to drive up energy consumption and energy sources. I'm going to specifically talk about maximizing renewable energy sources. So let's look at energy efficiency. This is from a report from the German Environment Agency, which is comparing different computer programs doing the exact same thing. I'm going to focus today on the two far left bar plots. This is a comparison of word processors. So word processor one in light green and word processor two in dark blue. Again, doing the exact same thing, word processor one consumes four times the energy compared to word processor two. So this might not make a big difference for one individual user, but you have to think about it at scale. And to illustrate that, I'm going to take a back of the envelope calculation from an online course, a sustainable programming at SAP from Detloff-Thoms to look at how the numbers quickly add up. So let's imagine what the yearly savings would be for one worker when eliminating just one CPU second from a process. One CPU second is about 10 watt seconds in energy consumption and reducing by one CPU second means you reduce each transaction by about 10 watt seconds. If there are 20 such transactions a day over a working year of 230 days, that adds up to a 46,000 watt second savings. Now that in itself is not much. That's roughly the equivalent of a 50 watt light bulb, which is on for 15 minutes. But now let's multiply that out, for example, to the EU. The EU has about 500 million people in it. If 2% of that 500 million use GNU Linux, which is roughly the market share of Linux and one fourth of that 2% uses, for example, the PDF reader ocular. We're talking about 2.5 million users and that one CPU second reduction will result in 32 megawatt hour savings in the EU. To put that into perspective, that's roughly the equivalent of driving 180,000 kilometers in a modern electric vehicle. That would be the equivalent as driving from Paris to Beijing 11 times back and forth. So these are non-trillion numbers. Now, if we can think about, if I can convince 300 Fedora developers and other free software communities to achieve just 10 of those optimizations. We're talking about 96,000 megawatt hour savings. That's roughly the equivalent of the power consumption in a year of 30,000 two-person households. So the numbers add up very quickly. Now let's think about energy conservation and the processes that are running when we're using a computer program. So again, this is from the German environment agency comparing two text editors, the same two text editors from before. But now we're including the information over time of how much energy is being consumed at which point in time. I'm going to focus now on everything after that red line. That red line is the point when both text editors, again, they're doing the exact same thing, save the document that they're working on and then go idle. You can see in the bottom plot that the text editor in fact goes idle. In the upper plot, the text editor continues to do various tasks. The question is what is happening here? Is it telemetry? Is it phoning home? Is it necessary for the functionality of a text editor? Can users disable these extra processes that are happening? That's the first part of energy conservation I'm going to talk about. The second one is software-driven hardware obsolescence. So some of you may have friends or family that have seen the warning that this device doesn't meet minimum system requirements or this device is no longer supported, even though they may have bought the hardware just five years ago. The result of these software-driven hardware obsolescence is that you have new devices that are produced and shipped unnecessarily. And functioning devices end up in landfills as you waste. To put this in terms of numbers about energy consumption, this is from Apple's environmental report on the iPhone 7. This graph is taken from a book Smart Green World. And you can see that the iPhone 7 in its lifetime will contribute about 56 kilograms of CO2. And 78% of that comes from production, 1% comes from the end-of-life treatment, and 3% comes from transport. Only 18% is in the use. So software-driven hardware obsolescence is a huge waste when it comes to energy consumption and greenhouse gas emissions. And some of you may know the statue in England, the waste electrical and electronic equipment statue. This is a statue that is seven meters tall and weighs about 3.3 tons. It's representative of the electronic equipment thrown away by the average UK citizen in their lifetime. And the last area I want to talk about is energy sources. This is a abstraction of energy supply in terms of renewable energy. On the y-axis you have how much renewable energy is available and on the x-axis you have the time of day. And what you can see here is there's a base level of energy supplied to the power grid from renewable energy. But at certain times of day you have an increase where you have more renewable energy that's feeding the grid. So now let's get to what does it have to do with free and open source software. So free and open source software is inherently socially oriented. So Matthew Miller today at one of the first talks described Fedora as wanting to make a better world for everybody. Free software empowers users and communities to do so. How does it do that? Well the open development process means that both users and developers have an influence and users can become developers and contribute to that process. Users can contribute bug reports or feature requests so that developers can develop what society wants and needs, not just what companies want. And this empowerment means that we are empowered to find new and creative ways to improve software sustainability for this and future generations. So let's go back to the three different areas I want to talk about today. First looking at the bar plots for the text editors in terms of how much energy they consumed when doing the exact same thing. So measuring the energy consumption and making it transparent is the first step towards making our software more sustainable. At the minimum it means users can make informed choices about which software they want to use. And a better outcome is when developers are aware of what is contributing to the energy consumption of their software. They can then drive the energy consumption down making their software more efficient. Now, you know, growing up we had the saying think global act local well with software you can act local and act global right so this back of the envelope calculation to get from one CPU second to the annual power consumption of 30,000 two person households. If you if you think about that at a global scale right that was just for the EU, if we multiply that by 16 times, we're talking about roughly the power annual power consumption of a city like Liverpool. Right and by making the energy consumption transparent, we can push other software developers and other companies to do the same. Just to reference what we're doing at KDE, we've started labeling merge requests and bugs in terms of the efficiency tag. Here you see a screenshot it's quite difficult to see on the screen, but this is a screenshot from bug reports, labeled efficiency and this includes things like high CPU usage. When software is freeze or hang when things slow down, all this contributing to a higher energy consumption and our first merger quest at KDE labeled efficiency was in November 2021. We've had 120 efficiency merger quest since then, and hopefully many more in the future and want to encourage other free software communities to do something similar. Looking at energy conservation. So again, these are the two text editors over time and the focus is on everything after the red line. The question is, once we know that the software is contributing to these extra tasks when it should go idle with free and open source software, we can take a look at the code and see what it's doing. Prioritary software, you don't have that option, right? And we can design our software so that users have the option to opt out. Let's imagine this is telemetry, which can be useful as some of the discussion earlier was about, you know, it's helpful to have statistics and numbers about what's what our users are doing with the software. But if we should give users the option of being able to say they want to turn it off also for ecological reasons. So they're consuming less energy. And if we turn it off by default, it's not only good for privacy reasons, but it also means that you're not going to have a millions of users contributing to higher energy consumption. So yeah, we are empowered to make these choices so that we can make our software more efficient. In terms of energy conservation, FOSS gives users a real choice to continue using their software. Again, this was already talked about earlier today about support for older hardware. I don't know about you, but I know I use hardware and I have used hardware for much of the past 10 years that is no longer supported by the producers. I've introduced the Linux to family and friends because they wanted to continue using up to date operating systems, but they were no longer able to using the software they're using previously. And as a result, what this means is that function devices remain in use and new devices are not produced and shipped unnecessarily. And this can have a huge impact on the energy consumption over the lifetime of that device. Again, thinking back to the iPhone over 80% was just in the production, transportation and end of life treatment. And we can demand more, right? This is for the EU, but this can be a global push that the right to repair must include software. The Free Software Foundation Europe has an open letter to legislators in the EU published in April, demanding that users have the right to freely choose operating systems and software running on their devices. And we can do more. Again, this is from a Free Software Foundation Europe initiative called Upcycling Android in which they're trying to keep smartphones up to date with Free Software so that the device doesn't end up as e-waste. Of course, there's a long tradition of install events for GNU Linux. We can keep devices in use so they don't end up as e-waste. And by doing so, we can shrink this wee statue. Sorry, my graphic design skills are not very good. I just made it much smaller. And we can conserve the shared resources that we have in our society. And the final point is regarding renewable energy sources. Again, looking at the plot of at what times of day is there more renewable energy supply? If we can shift tasks that are shiftable. So, for example, updates, two times a day when it's maximizing renewable sources, we are contributing less to the greenhouse gas emissions of the technology. This is a project actually that just very recently, together with the Green Web Foundation and KDEco, we're looking at how to get information from the grid. This is the Green Web Foundation has been looking at this. Packaging something that can then check what the power supply mix looks like at a certain time of day and then recommend doing updates or other shiftable tasks at those times. If you're interested in the topic, we want to write a proposal to get funding to develop this for Free Software distributions. So please be in touch. My email will be at the end of the presentation. So now let's get to the end of the talk. The Blue Angel Award Criteria for Desktop Software, which was released in 2020. They recognize in the award criteria that transparency and user autonomy are crucial to sustainability. We'll look at the three main categories in just a second. The award criteria were the main motivation for the KDEco projects, the Free and Open Source Energy Efficiency Project and the Blaua Engelford FOS for which I'm the project and community manager. So the ABCs are the award criteria. So the Blue Angel is the official equal label of the German government. It's the oldest equal label in the world since 1978. And it's an equal label that looks at the entire life cycle of a product. The ABCs, the three main categories are potential hardware operating life. That is, does the software and this is specific for desktop software run on hardware that's at least five years old. And do users have choices about how the software runs in order to influence the energy consumption? That is, can they install or uninstall software? Can they only install what they need? Is there transparency about in the APIs? And are they able to then choose different software products with the data formats that are used? Is there continuous support? Can they use the software offline and without advertising? These are the criteria that Free and Open Source is already fulfilling in most cases. This is what I'm calling the false advantage. You don't need to be free and open source software to fulfill these criteria, but we take it as given that users have autonomy in their software usage. What we need to do in the Free Software community to be eco-certified with the Blue Angel is to make our consumption demands transparent. And that's going to be the last couple of minutes of my talk. So there are three steps to eco-certification. Measure your software, analyze the results, and then certify. How do you measure? This is an example of the lab setup. Here you have a computer on the far left of the graph system under test. This is the hardware that you use to test the application you want to look at the energy consumption of. That's connected to a power meter. And you're collecting then the data on a separate computer that you then do the analysis with. We are currently setting up a lab in Berlin at KDAB Berlin, who have been very generous to offer space in their offices. We've had two sprints. This is the first one from the 21st of May. And this is the second one from just a couple of weeks ago. It's still a work in progress, although we do have the setup there. We're working on the tooling so that we can automate the process as much as possible. What do you measure when you measure the software? You measure the baseline consumption, the idle mode consumption standard usage scenario. The baseline is just the operating system went on. Idle mode is when the software is running, but nothing is happening. And the standard usage scenario is when you represent what a typical usage of that software would be in order to get an idea of how much energy it consumes. All this has to be transparent and published. Once you have the data, you can take the results and use a tool like Oscar, the open source software consumption analysis and R tool, which is developed by the campus beer confed or the environmental campus beer confed. And this requires three things, the log file of the actions taken in your standard usage scenario and idle mode, your energy consumption data, as well as your hardware performance results such as CPU usage, RAM usage, et cetera, which you can collect using a tool, a free software tool called collect all. Once you feed that into the program, you get a report back. It looks something like this. This is for K mail email client from KDE. Here you have, you see 31 repetitions of the standard usage scenario. And you can see there are spikes in the energy consumption at certain points in time. That's for example, when sending an email with an attachment, right, which is going to require more processes. For certification, you need documentation of the categories hardware operating life and user autonomy. And then you need to publish and submit your consumption demands in resource and energy efficiency. I'm going to wrap up now in the next 20 seconds. I just wanted to say KDE is very proud that we are the first ever the first. We have the first ever eco certified computer program with ocular. We were eco certified by the Blue Angel in February. And this is a very exciting thing for us. We would love. So this is under the KDE umbrella, but the free and open source energy efficiency project in the Blau Angle for Foss are for all free software communities. This topic is much bigger than any one distribution in any one community. Will you join us? The conversation has already been started in Fedora. I know that there are other initiatives for environmental justice, but Andy Arts has started discussion at the discourse link here. And if you would like to get in touch with us, the easiest way is to go to our website, eco.kde.org. And you will then see a button get involved and has all the information that you see here. And again, the slides are available. I'll return to this in just a second and I want to just add that the project Blau Angle Foss is funded by the German Environment Agency and the Federal Ministry for the Environment, Nature, Conservation, Nuclear Safety and Consumer Protection. So thank you very much. I'm going to open the chat now and I hope that I can answer some questions in the remaining time. Unfortunately, I will have to leave punctually at 6.30 German time since I have a train to catch. So thank you very much. If there are questions so I'm looking at the chat. And I'll start. So thank you for the positive responses and we would love this really is a topic that this this is for all of us and it's for for future generations. So if you're interested, please get in touch with us. Start your own projects in Fedora and your own communities. Let's collaborate. Let's join forces to make this make free software really the most sustainable software. So I'm browse. I'm going through the chat now to see if there are any questions. So there's a comment here about browsers getting faster and websites getting more complex. There's a term for this. This is the rebound effect. It's a real issue that once you have efficiency gains, often then usage will then erase any of the gains that you get. And this is a social issue, not a technological issue. And this is also part of what Katie Eco wants to develop as a culture around sustainability. It's not just a technological issue. So there's a question about if including crypto mining. The first two plots that I had, which I can return to now one did the numbers did include crypto mining that was the association for computing machinery. This 1.8 2.8% includes crypto mining. The second plot here does not this only this does not include transportation production as well as things like proof of work. I would love to continue the conversation with anyone who is watching. Please be in touch. Please. Join the conversation within fedora and and let's let's collaborate and make make this a reality. All right, then I think if there are no more questions. We'll return to the. The link to the slides. You're welcome to download and please be in touch. All right. Thank you very much everyone. Thanks everyone for this great conference and enjoy the next few days.