Thank you, everyone, for coming, especially a big thank you to the organizers.
This is a great event, and I'm really honored to be here.
It's my first time at Fozdem, and this is an incredible community, incredible event
that I've wanted to come for years.
I'm representing today the KDE Ecoinitiative.
This is a community project involving several people.
Some of them are here.
Some who were here earlier in the Railway open source dev room in this room earlier
today, and some presented earlier today in the online event of the Energy Dev Room.
I'm going to talk today about combating software-driven environmental harm with free software.
I'm not going to be as technical as some of the other talks.
I'm going to focus more on some of the softer sides of free software and how that's good
for the environment.
There's a lot of links in the slides.
If you want to download them, you can either go to our lab repository, or you can scan
the QR code.
I'll come back to this at the end.
To get started, to get an idea of what the problem is.
This is some data from a report from the Association for Computing and Machinery.
It's the oldest association of its type since 1947.
They estimated how much energy consumption the entire ICT sector, sorry, the greenhouse
gas emissions of the entire ICT sector is.
In their estimates, they find that it's within 1.8 to 3.9% of global greenhouse gas emissions.
This is roughly equivalent to the airline industry, which is estimated at 2.5%.
This data includes everything from production to transportation to end-of-life treatment,
bitcoin, training, machine learning models, and things like this.
As they say at the very beginning of the report, computing can help mitigate climate change,
but it must first cease contributing to it.
In their projections, they estimate that by 2050, the ICT sector will contribute about
30% of global greenhouse gas emissions.
Can I ask, we're going to knit zero by 2050, where are they?
So this data is assuming nothing changes from today.
And some of the major contributors to this are training machine learning models that
has increased 300,000 times between 2012 and 2018 and is currently doubling every few months
in terms of energy consumption.
That's one of the main contributors, a short lifespan of digital devices is another.
Digital devices, they estimate to be at, by 2025, 75 billion devices in the world.
That's about 10 per person.
If everyone, if that's distributed evenly, of course it's not.
And in their report, they claim at one point towards the end, efficiencies must be coupled
with slash demand, so conservation, to reduce the ICT sector carbon emissions.
And those are going to be two of the main points I'm going to talk about today, efficiencies
and conservation.
This is from another report, this does not include such a vast data set as the ACM report.
This is from the SHIFT project, it's a project, a nonprofit from France.
This is from 2019, and this is looking at usage and production and how that is distributed
in terms of energy consumption.
This does not include things like Bitcoin, it doesn't include transportation.
So there are several things that are not in this data set.
But they estimate, and this is just a good idea to think about what I'm going to talk
about today, they estimate that usage, which is on the left side, including terminals,
that's all the end user devices.
Networks and data centers contributes about 55% of energy consumption, whereas production
is 45%.
And again, this is not including an entire, the full data set.
For today, I'm going to talk a little bit about all of these things, I'm going to talk
about production in sort of a broad strokes, not going into any of the individual devices,
and focus mostly on the terminals, so the end user devices, but it does have some relevance
in terms of network and data center usage.
So as I said, I'm going to talk about efficiency and conservation, what do I mean by efficiency?
I mean same task, achieving the same result, but using fewer hardware demands.
This is going to be focused on desktop software, KDE is a desktop software development nonprofit,
and conservation that is reducing waste driven by software, and that will become clear in
just a second.
This is some data looking at the energy consumption of two word processors.
This is from a report from the German Environment Agency, in which they compared various software
products doing the exact same thing.
This is called a standard usage scenario, this is usage scenario measurements, so basically
they're running the exact same script to generate the same task from the software, and then
looking at how much energy it consumes by using an external power meter.
And what they find is that word processor one, which they only identify as an open source
word processor, is consuming four times less the energy compared to word processor two,
which they only identify as a proprietary software product.
Now you might look at this and say, okay, for one individual user, this is maybe not
that significant, but you have to think of it at scale.
For word processors, every university, every office, every government institution is using
word processors.
When you multiply this up by millions, possibly billions of users, that really adds up.
And I'm going to give an example of how that adds up.
This is directly taken from an online course on sustainable software design from Detloff
Thoms.
In this example, he imagines a scenario where you just have a one CPU second reduction in
your software.
And that one CPU second reduction is about the equivalent of 10 watt second savings.
When you multiply that by 1.5 million users, who are having perhaps in this, that savings
is interacted with 20 times a day, 230 times a year in your working day, that adds up to
19 megawatt hours of savings.
What does that mean to make a comparison if you take a modern electric vehicle and drive
it?
That would be the energy needed to drive from Paris to Beijing and back six times.
This is just from one CPU second reduction.
If I can convince 500 people to do 10 of those reductions with those exact same numbers,
you end up with 95,000 megawatt hour savings.
That's the equivalent to the energy consumption of a 30,000 two-person households in one year.
This adds up once you start looking at it at scale.
Going back to those two word processors, this is from that same report comparing word processor
proprietary and open source, looking at the energy consumption over time and what you
see here is, so I'm not going to focus on what's happening before this blue line.
I'm just going to look at what happens here.
This is the point in that usage scenario script when the script saves the document and then
goes idle.
This lower plot is the open source application.
What you see is that the document is saved and in fact it goes idle.
By comparison, looking at the proprietary software product, it continues doing things.
What is it doing?
I don't know.
It's maybe telemetry, a phoning home, doing some sort of analytics.
Can the user opt out of this?
Probably not.
This is probably outside of the user control.
Is it necessary for the functionality of that software?
Probably not.
I don't know that speculation, but when you look at what's happening over time, you can
see a significant difference here.
That's it for efficiency.
I'm going to come back to some of this in the second half of the talk.
I'm going to look at conservation now, reducing waste driven by software.
This is an infographic and I'm going to go through it now.
This is from a report-based UN data, I believe, which sort of from 2016, there's a reference
to a tsunami of e-waste.
This is actually increasing.
The data that they report is that it would be the equivalent to the materials used to
build 4,500 Eiffel Towers in one year that's e-waste.
That would be, just I thought about what if you stacked all those Eiffel Towers up, that
would be 17 times higher than Mount Everest.
This is in one year and it's increasing.
Less than 20% of our e-waste gets recycled.
In our landfills, e-waste accounts for about 2% of the waste in it, but it's 70% of the
toxic waste in landfills.
This is really damaging to the environment.
What does software have to do with this?
That's a hardware issue.
Well, software determines how long we can use our hardware.
You have things, problems like abandonware or planned obsolescence, where your device
is no longer supported.
My parents got this on one of their machines and I convinced them to switch to Linux because
of it, because to update would have required buying new hardware.
You have bloat and feature creep, where your device no longer meets minimum system requirements.
The result is that you have new devices produced and shipped, and functioning devices are discarded
as e-waste.
This is data from Apple.
I got it from a book called Smart Green World.
This is particularly scandalous that functioning devices end up as e-waste when you consider
that this is from Apple's own data, 78% of the greenhouse gas emissions comes just in
the production.
This is completely useless waste and contribution to the climate crisis.
I said I talk about free software.
I'm going to first focus on KDE's vision.
My main point here is that what's good for the user is good for the environment.
KDE has the vision.
This is from about five years ago the community came up with, what do they want to see long
term for KDE?
What they want is a world in which everyone has control over their digital life and enjoys
freedom and privacy.
Each word is broken down at the website if you go to the link.
I'm going to focus on a couple of them, so a world, so everyone in which everyone has
control over the digital life.
How do they want to do that?
They want to hand control over to the user.
They want to put you in the driver's seat, and the way they do that is by making free
and open source software.
To enjoy freedom and privacy, without the freedom to make changes and share them, users
are entirely reliant on the vendor's benevolence for apparent control.
Transparency and user autonomy aren't features.
They're inherent to free and open source software.
Those same values are what make free and open source software already more sustainable than
non-free software.
It's not just me saying this.
This is also the German Environment Agency, which released the award criteria for the
Blue Angel Eco-certification for software for desktop software in 2020, in which they
recognize that transparency in energy consumption and user autonomy in letting users decide
how they use their software actually is more sustainable.
There are three main categories to the award criteria, resource and energy efficiency,
potential hardware operating life, and user autonomy.
In other talks, I go through what I'm calling the three steps to eco-certification, measure,
analyze and certify, measuring by running usage scenarios, measuring energy consumption,
using that data using a tool like Oscar, the open source software consumption analysis
in R, and then collecting the data.
I'm not going to talk about the measurement and analysis today.
I'm going to actually focus more on those softer qualities, the user autonomy ones.
And a bit more detail, this is what the criteria require.
So resource and energy efficiency, it means that you are transparent about how much energy
your software consumes when it's used by an average user.
What an average user is, is not defined.
You have to decide what you think your software is used by most users.
Most importantly, you have to publish it.
You have to make it transparent about what your assumptions are.
And then with that, then you measure the energy consumption and publish it.
The potential hardware operating life, the requirement is that it runs in hardware that's
five years old.
Now this to me is far too low.
I mean, most people, and I have an example later, are using free software, can use devices
up to at least 10 years old.
Five years is not very much.
It's 2018 at this point.
And then the user autonomy criteria.
And this is where a free and open source software really has an advantage.
Connecting features or, sorry, qualities like uninstallability and modularity that you
can only install what you need, not more, not less.
We have support that the software can be supported beyond the original developer's intentions.
Offline capability and freedom from advertising that you can use the software without it having
connect to a server or run processes to feed you ads.
Documentation of your use of open standards, how you can uninstall and things like this,
and transparency.
Now, I would say that most people in the free and open source software community take these
for granted.
We don't think of these things as being sustainable.
And so I'm going to pick just three of them and talk a little bit about them now.
And I think then I'll have plenty of time for questions.
So uninstallability and modularity, right, this is not exciting news, right?
We can uninstall things completely when using a free and open source software.
A lot of proprietary software products you can't, right?
By leaving things, so by running things that you don't want, right, you're creating inefficiencies
when using that software.
It's going to take longer to load and start, it's going to take longer to shut down.
Those software components that you're not using might be adding CPU seconds to add up
once you start thinking about it, scaling it up to millions, possibly billions of users.
Modularity, if there are things that are being installed with a software product that you
don't want, right, that's again creating inefficiencies.
Free software gives users the control to decide what they install or uninstall.
And that creates a more efficient software product.
Continuity of support.
This is actually a picture I asked around in the KDE community, which hardware people
are running KDE Plasma on that they know is no longer supported by the vendors.
And one person responded, this is from, I don't know if this is the exact model, but
a 2009 MacBook that had their end of life in 2019 with Apple's 10.10 Mac OS.
And they are now running it with an up-to-date operating system Kabuntu with Plasma, long-term
support without any problems.
You can do this because the support for free software doesn't have these arbitrary or planned
end of life moments.
The Blue Angel, in their criteria, you don't have to be free and open-source software to
get the award, but you do have to have a plan for long-term continuous support after you
stop as a company developing that software product.
And if you don't, you have to make it free and open-source software to get the eco-label.
Offline capability and freedom from advertising, just to put some numbers to this, right?
So at KDE, and like many other free software products, there's no forced opt-in telemetry.
In fact, KDE does have a telemetry policy, but it's opt-in at all times.
Users aren't automatically giving data to KDE.
Most other software is not also requiring that.
What does that mean in terms of energy savings?
So this is a graph from a report for the EU, Carbon Footprint of Unwanted Data Use by Smartphones.
And what I like is it makes a very clear connection between the network and the data centers in
terms of power consumption, right?
So every time your smartphone or computer is going through the network, of course it's
consuming energy.
They in this report say that 60% of EU citizens, when asked, would opt out of advertising if
they could on their smartphones.
They estimate that that savings, if those 60% of the people could opt out, would be at
its worst 3 to 8 million metric tons of CO2 a year.
That would be equal to 370,950,000 EU citizens annual energy consumption, right?
For something that many users probably don't want.
So yeah, these things add up by making software that respects users, that gives users choice.
We are actually making more sustainable software.
There's many more topics to talk about.
If you're interested in the topic, you guys get a sneak peek to our handbook about measuring
energy consumption of software.
It actually will be officially announced next week.
But it's online now if you want to go to our website, eco.kd.org, in which we cover
sort of three main parts.
Why does this matter is the first part.
What is the Blue Angel?
It's focused on the criteria as a benchmark for what a sustainable digital society could
look like.
And the part three is then how do you measure your energy consumption and how do you fulfill
the user autonomy requirements if you're interested in eco-certifying your software.
KDE has been interested in eco-certifying their software.
We are proud to announce that we're the first to have a eco-certified computer program in
the global eco-labeling network with Ocular.
This is from April last year.
There are other initiatives that I just wanted to point out before my time is up that I think
are really important.
This is from the Free Software Foundation in Europe.
It's an open letter to demand that the right to repair must include software.
It goes, software determines how long we can use devices and if we have a right to repair
them, we should have the right to repair, to put any software we want on those devices.
You can keep devices in use as, again, a Free Software Foundation Europe initiative that's
really great upcycling your phone.
Just look into it.
I just wanted to point it out because I think they're doing great things.
If you're interested in, as a software developer, measuring software, we set up a lab in KDAB.
This is Arna who gave a talk earlier today in the online energy dev room.
Chris has helped out, set it up.
Several other people who are involved in the KDEco initiative have helped set this up.
We have a lab that's going to set up so that you can measure the energy consumption with
an external power meter.
We're in progress right now of trying to make an online portal so that you can upload your
usage scenario script, get a report back.
You can either use it for data-driven decisions about your own software design or applying
for something like the Blue Angel Eco label or similar.
I just wanted to, as a final note, KDE is voted in October to make sustainable software,
one of their goals, one of their three goals for the next couple of years.
In KDE, we're trying to align various initiatives within the community, doing things similar
to actually what was talked about earlier, trying to think of ways to give users information
similar to that light bulb that Kai was talking about earlier that gives you an indication
of what's consuming energy, and we're thinking of how we can implement those things into
like an eco-widget so that users can get information about what maybe the grid intensity, what
the power grid mix looks like at that moment so they can decide if they want to do an update
when there's more green energy, things like this.
Various other initiatives if you're interested.
This is a community project.
You're welcome to get involved.
Various channels to get in touch with us, email, mastodon.
We have a big blue button online meetup every second Wednesday, that's next Wednesday,
I want you to talk about various things, and then mailing lists in Matrix Room.
Thank you.
I just have to note that this is a project, so I'm working in the Blower Angle for Foss
project, which is a government funded project from the German government.
Thank you very much, and I look forward to your questions.
Actually, I'm going to do one thing.
We have online questions as well.
I feel like online folks always get ignored first, so I'm going to just try.
Is there any online questions that we could?
None so far.
Okay.
Then I'm going to bring it to the room.
If you're in contact with the German government, can you vouch that they tell to the hardware
producers to open source their drivers?
I can certainly mention it next time I'm at an event, and I have someone's ear, which
is not often.
So the question was, sorry I have to repeat it, if I can, next time I'm in contact with
someone from the German government, if they can open source drivers, they can force hardware
vendors to open source drivers, is that, yeah.
And I would be happy to try to drop that comment if I can.
I saw a hand over here before.
I think it was yours, yeah.
So the question is, so what is the Blue Angel?
Where do you find out information about the Blue Angel as a consumer?
And the Blue Angel, so I actually can, I'll ask, I think there probably are some German
speakers in this room, or people who are in German speaking countries, who here knows
the Blue Angel and what do you know it for?
And what is it known for?
Paper.
Most people say paper.
So it's really unknown for paper products, and toilet paper in particular, and I've started
some talks making the joke, what software and toilet paper have in common.
They can be certified.
So Blue Angel certifies a lot more than that.
There's hundreds of products, cleaning, detergents, construction materials, things like this.
In the IT sector, they certify servers, or server providers, and now software.
And that's it.
They want to extend this, just to put this out, they want to extend the equal label to
not just desktop software, but also mobile apps, and distributed software systems, or
client server type things, that's in progress right now.
The desktop software, how you can find out about it is if you go to the Blue Angel website,
there they have a list of all the products.
I don't remember the link off the top of my head, but it might be, no.
It's on our website, if you're buying a product, and it's on the packaging.
So that's the kind of thing that, and what it says, so it's maybe just an important point,
they're a type one equal label, which means that it looks at the entire lifespan of the
product, and it requires a third party evaluation of compliance.
Whereas other equal labels, not like type two or type three, I think are the others,
don't require third party evaluation.
So it has a bit more of a stringent process in the evaluation.
Is there time for more questions, or we have to switch over.
I'm happy to talk in the hallway, or in online, or after the event, so thank you.