WEBVTT 1 00:00:00.279 --> 00:00:03.029 (exciting music) 2 00:00:05.640 --> 00:00:08.070 So, what do we do at the Green Software Foundation? 3 00:00:08.070 --> 00:00:10.617 So, a lot of what we do is, is standards, 4 00:00:10.617 --> 00:00:12.630 and I think we've heard about the SCI today 5 00:00:12.630 --> 00:00:15.210 is one of the standards that we work on. 6 00:00:15.210 --> 00:00:16.260 This is it. 7 00:00:16.260 --> 00:00:17.938 Everybody thinks of the SCI, 8 00:00:17.938 --> 00:00:20.663 and, I remember I had a friend who said 9 00:00:20.663 --> 00:00:25.320 she freed up a whole evening 10 00:00:25.320 --> 00:00:28.650 to sit down and read the SCI specification, 11 00:00:28.650 --> 00:00:30.120 and was finished in about 10 minutes, 12 00:00:30.120 --> 00:00:31.020 because it's actually not very long. 13 00:00:31.020 --> 00:00:32.700 It's about four pages long. 14 00:00:32.700 --> 00:00:34.800 But what the, the magic of the SCI is we managed 15 00:00:34.800 --> 00:00:37.770 to get 68 organizations together to agree 16 00:00:37.770 --> 00:00:40.482 on a kind of basic concepts, 17 00:00:40.482 --> 00:00:44.040 and that's kind of why it's important to have standards, 18 00:00:44.040 --> 00:00:47.961 just so we can agree on these basic things. So that's the 19 00:00:47.961 --> 00:00:50.973 SCI, there's an, an entire specification, which goes into 20 00:00:50.973 --> 00:00:54.665 a bit more detail to how to compute different parts 21 00:00:54.665 --> 00:00:57.690 of this equation, but it doesn't really stop there. 22 00:00:57.690 --> 00:00:58.590 Kind of what's next? 23 00:00:58.590 --> 00:01:01.920 How do we, oh, and what we did was we developed the SCI 24 00:01:01.920 --> 00:01:03.780 in collaboration with all those organizations, 25 00:01:03.780 --> 00:01:05.190 then we moved it into ISO, 26 00:01:05.190 --> 00:01:07.050 then we became an ISO standard. 27 00:01:07.050 --> 00:01:10.650 That's really where the power of a lot of the work 28 00:01:10.650 --> 00:01:12.870 that we do is through that collaborative effort. 29 00:01:12.870 --> 00:01:17.010 You don't get something into ISO after the fact. 30 00:01:17.010 --> 00:01:19.147 You have to start from day one, saying, 31 00:01:19.147 --> 00:01:21.150 "We want to do this thing collaboratively. 32 00:01:21.150 --> 00:01:22.920 We need to demonstrate that BCG, 33 00:01:22.920 --> 00:01:25.980 that all these other organizations got involved together 34 00:01:25.980 --> 00:01:26.813 to create this standard." 35 00:01:26.813 --> 00:01:28.410 That's how it gets adopted. 36 00:01:28.410 --> 00:01:29.700 And once it gets into ISO, 37 00:01:29.700 --> 00:01:33.810 that's when policy makers pay a lot more attention. 38 00:01:33.810 --> 00:01:36.205 So a lot more attention being given to SCI 39 00:01:36.205 --> 00:01:39.395 since its ISO submission from policymakers. A lot more 40 00:01:39.395 --> 00:01:42.300 interest from that perspective. What's next? 41 00:01:42.300 --> 00:01:44.250 I'm literally just on the train over, 42 00:01:44.250 --> 00:01:47.970 was communicating with people 43 00:01:47.970 --> 00:01:50.970 from the Standards Working Group on SCI for AI. 44 00:01:50.970 --> 00:01:54.900 How do we explore and expand this space even further? 45 00:01:54.900 --> 00:01:56.250 There's also a lot of interest. 46 00:01:56.250 --> 00:01:58.260 Blockchain has not disappeared, remember blockchain? 47 00:01:58.260 --> 00:01:59.093 Do you remember it? (audience chuckling) 48 00:01:59.093 --> 00:02:00.540 It was a hot topic before AI. 49 00:02:00.540 --> 00:02:01.710 It hasn't gone away. 50 00:02:01.710 --> 00:02:04.620 In fact, I think, looking even at today's emissions, 51 00:02:04.620 --> 00:02:07.350 blockchain is still higher than AI. 52 00:02:07.350 --> 00:02:09.600 And even when we go forward a couple of years, 53 00:02:09.600 --> 00:02:12.450 AI will surpass, but blockchain is still there. 54 00:02:12.450 --> 00:02:13.283 It's still out there, 55 00:02:13.283 --> 00:02:15.480 it's still a significant cause of emissions, 56 00:02:15.480 --> 00:02:16.680 but that there's a lot more interest, 57 00:02:16.680 --> 00:02:18.030 as interest in SCI for finance. 58 00:02:18.030 --> 00:02:19.230 What does that look like? 59 00:02:19.230 --> 00:02:23.220 So, this is kind of what's being explored next. 60 00:02:23.220 --> 00:02:26.430 A lot of the focus for next year is going to be giving 61 00:02:26.430 --> 00:02:30.000 lots more concrete advice, concrete specifications, 62 00:02:30.000 --> 00:02:33.930 pushing them into ISO, getting more policy makers, 63 00:02:33.930 --> 00:02:35.910 giving more advice for policymakers, 64 00:02:35.910 --> 00:02:38.760 so, when they do develop policies, 65 00:02:38.760 --> 00:02:42.540 it will be aligned and a lot of us will have our input 66 00:02:42.540 --> 00:02:44.400 into that process. 67 00:02:44.400 --> 00:02:46.440 So yeah, I just have this join us for a few seconds. 68 00:02:46.440 --> 00:02:47.760 If there's anybody who's interested 69 00:02:47.760 --> 00:02:50.220 in joining the foundation, you can reach out. 70 00:02:50.220 --> 00:02:52.520 I'm happy to have a conversation with anybody. 71 00:02:53.640 --> 00:02:55.320 So this talk originally was, 72 00:02:55.320 --> 00:02:57.300 I think I had the title, "Doing for Sustainability 73 00:02:57.300 --> 00:02:59.910 What Open Source Did for Software." 74 00:02:59.910 --> 00:03:03.690 That's a 45-minute talk, that's not a 20-minute talk. 75 00:03:03.690 --> 00:03:05.880 A 20-minute talk is "Impact Framework: 76 00:03:05.880 --> 00:03:07.860 The Solution to Opaque Carbon Reporting," 77 00:03:07.860 --> 00:03:10.380 so there's, like, a subset of that talk, 78 00:03:10.380 --> 00:03:13.351 unfortunately without all the jokes. 79 00:03:13.351 --> 00:03:14.184 (audience chuckling) So this is gonna be 80 00:03:14.184 --> 00:03:15.120 a very serious talk. 81 00:03:15.120 --> 00:03:17.103 I couldn't get most of my jokes in. 82 00:03:19.380 --> 00:03:20.790 So, Impact Framework is something 83 00:03:20.790 --> 00:03:22.770 that we've been developing inside the foundation. 84 00:03:22.770 --> 00:03:24.930 It's actually started to develop when, like, 85 00:03:24.930 --> 00:03:26.970 the SCI came out, 86 00:03:26.970 --> 00:03:29.310 and we developed, delivered it, everybody got together. 87 00:03:29.310 --> 00:03:32.220 It was like years of discussions on calls, 88 00:03:32.220 --> 00:03:35.370 so many conversations, and we delivered it. 89 00:03:35.370 --> 00:03:38.367 Then I was like, "Right, everybody, go calculate it" 90 00:03:40.980 --> 00:03:44.120 ... and it was very hard to actually compute the SCI score. 91 00:03:44.120 --> 00:03:45.360 It still is quite hard. 92 00:03:45.360 --> 00:03:47.580 Like, even though we've actually all agreed 93 00:03:47.580 --> 00:03:48.780 on the equation, 94 00:03:48.780 --> 00:03:52.020 actually computing that value is still quite significant. 95 00:03:52.020 --> 00:03:54.210 So there's a bunch of projects that started 96 00:03:54.210 --> 00:03:55.110 inside the foundation, 97 00:03:55.110 --> 00:03:57.780 and they all evolved eventually into what we now call 98 00:03:57.780 --> 00:03:59.400 the Impact Framework. 99 00:03:59.400 --> 00:04:00.233 So what is it? 100 00:04:00.233 --> 00:04:01.830 It's a couple of different things. 101 00:04:01.830 --> 00:04:05.100 It started off as what we call a custom calculator. 102 00:04:05.100 --> 00:04:09.030 How you actually calculate an impact an SCI score, 103 00:04:09.030 --> 00:04:11.100 or other scores, as GHG. 104 00:04:11.100 --> 00:04:12.960 How do you actually calculate that? 105 00:04:12.960 --> 00:04:14.460 But where it has evolved into, 106 00:04:14.460 --> 00:04:16.680 and where I think it's even more interesting, 107 00:04:16.680 --> 00:04:19.050 is it's turning into a file format 108 00:04:19.050 --> 00:04:21.780 for communicating environmental impacts. 109 00:04:21.780 --> 00:04:23.100 This is why I get very excited, 110 00:04:23.100 --> 00:04:23.933 but the audience is like, 111 00:04:23.933 --> 00:04:25.200 "I don't really know what you're talking about." 112 00:04:25.200 --> 00:04:27.180 I'm very, very excited about this. 113 00:04:27.180 --> 00:04:29.670 Like, we need a future where, when somebody... 114 00:04:29.670 --> 00:04:33.965 I get sent constantly PDFs, blog articles, 115 00:04:33.965 --> 00:04:36.851 this, that, the other, like, "This is our computation," 116 00:04:36.851 --> 00:04:39.610 and it's very hard for me to make that judgment, 117 00:04:39.610 --> 00:04:40.710 make that criteria. 118 00:04:40.710 --> 00:04:43.200 We need a common way of communicating. 119 00:04:43.200 --> 00:04:45.690 I'm a standards body, so that's obviously what I believe in, 120 00:04:45.690 --> 00:04:48.180 but remember the world where we didn't 121 00:04:48.180 --> 00:04:50.550 just use USB-C for everything? 122 00:04:50.550 --> 00:04:51.930 That's the world we're creating, 123 00:04:51.930 --> 00:04:54.780 is we all can all communicate climate impacts 124 00:04:54.780 --> 00:04:56.100 exactly the same way. 125 00:04:56.100 --> 00:04:59.320 Trust me, that will grow this ecosystem 126 00:05:00.360 --> 00:05:02.100 incredibly fast. 127 00:05:02.100 --> 00:05:04.410 So I just need once to explain a couple of concepts 128 00:05:04.410 --> 00:05:07.770 for Impact Framework so we can understand how it works. 129 00:05:07.770 --> 00:05:10.830 So one of the things we noticed a lot of organizations doing 130 00:05:10.830 --> 00:05:15.120 is this is carbon, this is water, this is electricity. 131 00:05:15.120 --> 00:05:17.790 Like, we don't actually get these numbers directly 132 00:05:17.790 --> 00:05:19.140 from a lot of organizations. 133 00:05:19.140 --> 00:05:21.300 We need to compute them ourselves. 134 00:05:21.300 --> 00:05:23.190 And what we noticed the community starting to do 135 00:05:23.190 --> 00:05:24.300 a couple of years ago was, like, 136 00:05:24.300 --> 00:05:27.030 well, we don't have carbon figures, 137 00:05:27.030 --> 00:05:29.801 but I know much, how many CPUs are being used, 138 00:05:29.801 --> 00:05:31.320 and I know what the utilization is, 139 00:05:31.320 --> 00:05:33.510 we know how many downloads they have, 140 00:05:33.510 --> 00:05:35.520 we know all this other information. 141 00:05:35.520 --> 00:05:38.130 Is there a way of turning this into carbon? 142 00:05:38.130 --> 00:05:40.590 And so, this is what we call an observation, 143 00:05:40.590 --> 00:05:42.360 and that's what we call an impact, 144 00:05:42.360 --> 00:05:43.800 and that's what Impact Framework does. 145 00:05:43.800 --> 00:05:47.430 It helps take observations and turn them into impacts. 146 00:05:47.430 --> 00:05:50.010 This is a beautiful animation, oh my word. 147 00:05:50.010 --> 00:05:54.810 So what this did, we do it with a bunch of models, 148 00:05:54.810 --> 00:05:56.550 and one of the things we realized, 149 00:05:56.550 --> 00:05:59.310 everybody historically was trying to create, like, 150 00:05:59.310 --> 00:06:02.880 this one model that worked for every single use case, 151 00:06:02.880 --> 00:06:04.770 whether you're... whatever cloud provider, 152 00:06:04.770 --> 00:06:07.560 whatever you are doing, this one model would work. 153 00:06:07.560 --> 00:06:08.910 And what the community realized, 154 00:06:08.910 --> 00:06:09.960 actually, that doesn't work for us. 155 00:06:09.960 --> 00:06:11.790 We need to break this out into smaller models. 156 00:06:11.790 --> 00:06:14.040 If you're used to the Linux environment, 157 00:06:14.040 --> 00:06:15.540 kind of like breaking things up 158 00:06:15.540 --> 00:06:16.950 into a lot of smaller chunks, 159 00:06:16.950 --> 00:06:19.860 and then you can cherry-pick the models that you want to do, 160 00:06:19.860 --> 00:06:23.580 what you need to do to compute your environmental impact. 161 00:06:23.580 --> 00:06:25.080 And that's really the feedback we were getting 162 00:06:25.080 --> 00:06:27.727 was from a lot of organizations, a lot of people, 163 00:06:27.727 --> 00:06:30.870 "We can't use this generic method. 164 00:06:30.870 --> 00:06:35.870 My company uses a very unique stack of software 165 00:06:35.970 --> 00:06:37.470 that it doesn't work for me." 166 00:06:37.470 --> 00:06:40.620 It needs every single computation for every single company, 167 00:06:40.620 --> 00:06:41.880 for every single software product. 168 00:06:41.880 --> 00:06:44.370 It's gonna be a bespoke computation. 169 00:06:44.370 --> 00:06:48.120 This is going to be a hard problem to solve. 170 00:06:48.120 --> 00:06:50.610 This is not an easy problem to solve. 171 00:06:50.610 --> 00:06:52.020 This is the hard... 172 00:06:52.020 --> 00:06:54.750 sustainability, climate change is the hardest problem 173 00:06:54.750 --> 00:06:55.860 humanity's ever faced. 174 00:06:55.860 --> 00:06:58.530 We are not gonna have any easy solutions here. 175 00:06:58.530 --> 00:07:00.990 So that's what they were really working towards. 176 00:07:00.990 --> 00:07:02.973 We want bespoke solutions. 177 00:07:04.710 --> 00:07:06.363 This is where I go into a demo, 178 00:07:07.800 --> 00:07:10.500 and this is where I lose most of you, 179 00:07:10.500 --> 00:07:12.570 because I'm about to show you, 180 00:07:12.570 --> 00:07:14.310 although I did give this talk in Brighton, 181 00:07:14.310 --> 00:07:16.023 and there is a little bit more, 182 00:07:17.130 --> 00:07:19.950 little bit more to it than there was at that point. 183 00:07:19.950 --> 00:07:23.610 So, how it works, 184 00:07:23.610 --> 00:07:27.270 so this is where I... 185 00:07:27.270 --> 00:07:28.323 Trust me, it's okay. 186 00:07:29.408 --> 00:07:31.680 (audience laughing) It's okay, okay? 187 00:07:31.680 --> 00:07:32.940 I've given this talk before, 188 00:07:32.940 --> 00:07:34.950 so I won't show you much of this, 189 00:07:34.950 --> 00:07:38.460 but this is what we call an Impact Framework manifest file. 190 00:07:38.460 --> 00:07:41.823 We actually call an IMP file, a .IMP file. 191 00:07:42.660 --> 00:07:46.020 You will be sharing .IMP files. 192 00:07:46.020 --> 00:07:49.380 You won't be sharing to me your carbon emissions number, 193 00:07:49.380 --> 00:07:51.633 you'll be sharing a .IMP file, 194 00:07:52.770 --> 00:07:54.960 and this file contains within it 195 00:07:54.960 --> 00:07:58.110 not only the carbon emissions calculation of our website, 196 00:07:58.110 --> 00:08:00.900 but everything, all the data that was used 197 00:08:00.900 --> 00:08:02.220 in that calculation, 198 00:08:02.220 --> 00:08:04.830 all the methodologies, all the coefficients 199 00:08:04.830 --> 00:08:07.050 all baked into this one file, 200 00:08:07.050 --> 00:08:08.580 and it's actually reexecutable, 201 00:08:08.580 --> 00:08:10.987 so you can then take this file and go, 202 00:08:10.987 --> 00:08:14.460 "Oh, I don't agree with how the GSF has computed this. 203 00:08:14.460 --> 00:08:16.140 We actually have a different methodology, 204 00:08:16.140 --> 00:08:18.970 and we're gonna recompute and give our 205 00:08:18.970 --> 00:08:22.530 methodology." We don't take sides in the GSF. 206 00:08:22.530 --> 00:08:24.750 Use whatever methodology you use. 207 00:08:24.750 --> 00:08:26.430 We just want to standardize ways for you 208 00:08:26.430 --> 00:08:29.370 to compute that and communicate that. 209 00:08:29.370 --> 00:08:32.970 So this is, I won't go into too much detail. 210 00:08:32.970 --> 00:08:35.220 There's quite a lot of data inside here. 211 00:08:35.220 --> 00:08:37.890 We know, I gave this talk in Brighton last year, 212 00:08:37.890 --> 00:08:39.660 where all I had was this YAML file 213 00:08:39.660 --> 00:08:41.490 and it was very hard to give the talk, 214 00:08:41.490 --> 00:08:43.830 but so one of the things that we've been building recently 215 00:08:43.830 --> 00:08:45.600 is we know this is very hard for people to understand. 216 00:08:45.600 --> 00:08:47.760 I can read this, a lot of other people can't read this, 217 00:08:47.760 --> 00:08:49.770 so we built a visualizer. 218 00:08:49.770 --> 00:08:51.360 So this is the visualizer, and again, 219 00:08:51.360 --> 00:08:53.640 this is not a dashboard per se, 220 00:08:53.640 --> 00:08:58.080 this is just a visual representation of that .IMP file, 221 00:08:58.080 --> 00:08:59.730 this file that we will be computing 222 00:08:59.730 --> 00:09:03.030 and sending to everybody else in the future. 223 00:09:03.030 --> 00:09:06.510 So this is the total carbon emissions of the GSF website. 224 00:09:06.510 --> 00:09:09.180 The data is from August 1st to August 31st. 225 00:09:09.180 --> 00:09:10.470 That's the dataset. 226 00:09:10.470 --> 00:09:14.940 Our total emissions was 2.4 kilos for our website, 227 00:09:14.940 --> 00:09:19.940 and our SCI score is 0.13 grams per visit. 228 00:09:20.580 --> 00:09:23.583 That's how an SCI score works, it's carbon per something. 229 00:09:25.500 --> 00:09:28.890 But we also know that these headline numbers, they're not... 230 00:09:28.890 --> 00:09:30.630 If you want to get to action, 231 00:09:30.630 --> 00:09:33.090 if you wanna get to advice to take, 232 00:09:33.090 --> 00:09:34.410 you need to get granular. 233 00:09:34.410 --> 00:09:36.090 That's one of the things we really advocate for, 234 00:09:36.090 --> 00:09:38.640 is to get as granular data as possible. 235 00:09:38.640 --> 00:09:40.110 Temporily granular, 236 00:09:40.110 --> 00:09:42.120 and what days was the carbon emissions that high? 237 00:09:42.120 --> 00:09:43.350 How does that... 238 00:09:43.350 --> 00:09:46.260 What information can you decide from that? 239 00:09:46.260 --> 00:09:49.380 But also, where? 240 00:09:49.380 --> 00:09:51.750 A website is a complicated process. 241 00:09:51.750 --> 00:09:53.457 The processes that we build in, 242 00:09:53.457 --> 00:09:56.220 our website is quite simple in comparison. 243 00:09:56.220 --> 00:09:58.680 A lot of our organizations have tens of thousands 244 00:09:58.680 --> 00:10:00.600 of servers running very, very complex, 245 00:10:00.600 --> 00:10:03.180 but you need to know where those emissions are coming from 246 00:10:03.180 --> 00:10:05.640 to find the actions that you need to take. 247 00:10:05.640 --> 00:10:08.490 So that manifest file that you saw 248 00:10:08.490 --> 00:10:11.670 actually has a tree inside it with all the emissions numbers 249 00:10:11.670 --> 00:10:13.620 for everything inside it. 250 00:10:13.620 --> 00:10:16.740 So this is all of it, and it was broken down. 251 00:10:16.740 --> 00:10:21.740 I know, on this day, the carbon emissions were 81 grams, 252 00:10:21.763 --> 00:10:23.970 and I can see what drove it. 253 00:10:23.970 --> 00:10:26.820 Most of it was the users, on the website. 254 00:10:26.820 --> 00:10:27.653 Makes sense, right? 255 00:10:27.653 --> 00:10:28.710 The browsers. 256 00:10:28.710 --> 00:10:30.990 Even when the browser, you can dive into kind of how 257 00:10:30.990 --> 00:10:33.300 did we compute and calculate that? 258 00:10:33.300 --> 00:10:35.190 You can dive even deeper. 259 00:10:35.190 --> 00:10:36.780 We believe it's all here, 260 00:10:36.780 --> 00:10:40.050 all the data that was used in that calculation is there. 261 00:10:40.050 --> 00:10:42.540 All the methodology that was used in that calculation, 262 00:10:42.540 --> 00:10:46.140 it's all here, it's all transparent. 263 00:10:46.140 --> 00:10:48.993 You can take this file, 264 00:10:50.514 --> 00:10:51.870 you can take this file, 265 00:10:51.870 --> 00:10:52.860 I'll send this, 266 00:10:52.860 --> 00:10:54.660 I can send this to people, 267 00:10:54.660 --> 00:10:59.190 and, you can say, "Hey, I don't agree with you. 268 00:10:59.190 --> 00:11:00.600 That's interesting, how did you make that? 269 00:11:00.600 --> 00:11:01.560 How did you calculate that?" 270 00:11:01.560 --> 00:11:02.643 I can download it. 271 00:11:04.170 --> 00:11:08.582 I can then open it up myself in my own editor, 272 00:11:08.582 --> 00:11:11.760 or however I want to look at it. 273 00:11:11.760 --> 00:11:14.280 I can see all of the information I've had. 274 00:11:14.280 --> 00:11:15.180 I can go, "Do you know what? 275 00:11:15.180 --> 00:11:17.422 I don't agree with this." 276 00:11:17.422 --> 00:11:19.825 This is... you won't, you won't know what this is. 277 00:11:19.825 --> 00:11:21.600 This is what we call a power curve. 278 00:11:21.600 --> 00:11:23.790 You can go, "I don't agree with your estimate there. 279 00:11:23.790 --> 00:11:26.670 I think it should be 100.2." 280 00:11:26.670 --> 00:11:28.410 You can save that. 281 00:11:28.410 --> 00:11:30.690 You can then go into a terminal. 282 00:11:30.690 --> 00:11:33.120 There's lots of tooling here that you can build, 283 00:11:33.120 --> 00:11:34.360 and you can recompute 284 00:11:36.120 --> 00:11:38.400 "My Website's Emissions." 285 00:11:38.400 --> 00:11:42.450 You have the power to recompute 286 00:11:42.450 --> 00:11:46.560 our emissions with your coefficients, 287 00:11:46.560 --> 00:11:49.380 your models, your methodologies, 288 00:11:49.380 --> 00:11:51.900 and republish it back to us. 289 00:11:51.900 --> 00:11:53.463 We don't know if this is right. 290 00:11:54.300 --> 00:11:57.300 Joseph, head of R&D, he's been a climate scientist 291 00:11:57.300 --> 00:11:58.290 for 12 years. 292 00:11:58.290 --> 00:12:00.690 He's been in the Arctic and Antarctic, 293 00:12:00.690 --> 00:12:04.200 measurin, ice sheets, 294 00:12:04.200 --> 00:12:05.700 which I thought was cooler than what it was. 295 00:12:05.700 --> 00:12:08.360 It turns out you don't get, you don't actually get a, ah... a, uh... 296 00:12:11.139 --> 00:12:12.630 I always imagine the Antarctic, 297 00:12:12.630 --> 00:12:14.370 all these scientists are in these kind of buildings. 298 00:12:14.370 --> 00:12:15.930 It's a bit cold, but you know, they have... 299 00:12:15.930 --> 00:12:17.910 It's a tent, it's a tent. 300 00:12:17.910 --> 00:12:20.100 You sit in a tent for a month. 301 00:12:20.100 --> 00:12:22.743 So he computed all of this, 302 00:12:24.306 --> 00:12:25.433 but we don't know whether we're right or wrong. 303 00:12:25.433 --> 00:12:27.600 This is our best guess. 304 00:12:27.600 --> 00:12:28.740 This is our best guess. 305 00:12:28.740 --> 00:12:29.793 We think we're right. 306 00:12:31.396 --> 00:12:33.521 You can challenge us. 307 00:12:33.521 --> 00:12:34.830 That's really the future that we want. 308 00:12:34.830 --> 00:12:37.410 We want a future of transparency, 309 00:12:37.410 --> 00:12:39.720 where we are being fully transparent 310 00:12:39.720 --> 00:12:41.573 with all of our data, all of our emissions. 311 00:12:41.573 --> 00:12:43.620 We want everybody to be this way 312 00:12:43.620 --> 00:12:46.080 so that then you can be challenged. 313 00:12:46.080 --> 00:12:48.270 That's the future I want, is you can be challenged. 314 00:12:48.270 --> 00:12:49.500 You can be, 315 00:12:49.500 --> 00:12:51.120 because we're only gonna learn 316 00:12:51.120 --> 00:12:54.060 through people challenging each other, 317 00:12:54.060 --> 00:12:56.220 questioning each other's solutions, 318 00:12:56.220 --> 00:12:58.080 and proposing a better solution. 319 00:12:58.080 --> 00:13:00.420 So if you think it's wrong, do you know what you can do? 320 00:13:00.420 --> 00:13:03.150 You can download this, you can change it, 321 00:13:03.150 --> 00:13:05.340 you can check it back into our repository. 322 00:13:05.340 --> 00:13:06.340 You can then create a pull request, 323 00:13:06.340 --> 00:13:07.440 and, "I think you're wrong, 324 00:13:07.440 --> 00:13:09.300 this is why I think you're wrong." 325 00:13:09.300 --> 00:13:10.900 This is the future that we want. 326 00:13:15.540 --> 00:13:17.440 Let me make sure I covered everything... 327 00:13:19.860 --> 00:13:23.190 Yeah, we also have, we ran a hackathon last year 328 00:13:23.190 --> 00:13:27.840 for the Impact Framework, 329 00:13:27.840 --> 00:13:30.480 and we had quite a few plugins. 330 00:13:30.480 --> 00:13:31.500 These are methodologies. 331 00:13:31.500 --> 00:13:32.430 These are plugins for the Impact Framework 332 00:13:32.430 --> 00:13:33.843 that can be built. 333 00:13:35.160 --> 00:13:37.680 We had over 50 submissions, 334 00:13:37.680 --> 00:13:40.110 and they're all now available on this website. 335 00:13:40.110 --> 00:13:41.253 One of my favorite... 336 00:13:43.533 --> 00:13:44.366 one of my favorite is... 337 00:13:48.549 --> 00:13:49.382 ... is Death. 338 00:13:51.090 --> 00:13:52.890 Yeah, one of my favorite is Death. 339 00:13:52.890 --> 00:13:54.210 This is a plugin that you can add 340 00:13:54.210 --> 00:13:57.000 that will then take from your numbers, 341 00:13:57.000 --> 00:13:59.910 and you add it to your pipeline of plugins, 342 00:13:59.910 --> 00:14:01.230 and as well as carbon, 343 00:14:01.230 --> 00:14:03.930 it will compute the number of premature deaths 344 00:14:03.930 --> 00:14:06.060 that are gonna be caused by your product. 345 00:14:06.060 --> 00:14:10.390 It also will compute how many people will be displaced 346 00:14:11.610 --> 00:14:12.960 by your software products. 347 00:14:12.960 --> 00:14:15.120 I know it's a challenging conversation, 348 00:14:15.120 --> 00:14:17.220 but this is why we're here. 349 00:14:17.220 --> 00:14:19.860 Let's not forget this, this is why we're here. 350 00:14:19.860 --> 00:14:23.370 So, um... yeah... 351 00:14:23.370 --> 00:14:25.920 let's get back to the talk. 352 00:14:26.880 --> 00:14:28.140 There are a lot more jokes 353 00:14:28.140 --> 00:14:29.370 in the 45-minute one, (audience laughing) 354 00:14:29.370 --> 00:14:30.203 seriously. 355 00:14:30.203 --> 00:14:32.430 It was hilarious, I had the whole room crying, 356 00:14:32.430 --> 00:14:33.263 but, um, ah... so yeah. 357 00:14:36.803 --> 00:14:39.120 So what's the plans for this? 358 00:14:39.120 --> 00:14:44.010 So we had that file that you saw, that .IMP file. 359 00:14:44.010 --> 00:14:44.850 Like, it's very early, 360 00:14:44.850 --> 00:14:47.280 we haven't really started this process yet fully, 361 00:14:47.280 --> 00:14:50.640 but the discussions now are to then publish this, 362 00:14:50.640 --> 00:14:51.750 get it as a proper standard. 363 00:14:51.750 --> 00:14:55.170 We should get consensus on and publish it to ISO. 364 00:14:55.170 --> 00:14:56.970 My dream, every product in this world 365 00:14:56.970 --> 00:14:59.280 that is computing an environmental impact, 366 00:14:59.280 --> 00:15:02.310 you can right-click, download an .IMP file, 367 00:15:02.310 --> 00:15:06.570 and then you can then compare that impact to something else. 368 00:15:06.570 --> 00:15:09.180 You can then start really communicating. 369 00:15:09.180 --> 00:15:12.390 I want the USB-C for sustainability 370 00:15:12.390 --> 00:15:15.630 so we can all connect together and all start communicating. 371 00:15:15.630 --> 00:15:17.013 That's what we need. 372 00:15:19.050 --> 00:15:23.130 This is me, this is not the foundation, this is my dream, 373 00:15:23.130 --> 00:15:24.750 and there are things in the foundation 374 00:15:24.750 --> 00:15:26.340 which are forming into this dream. 375 00:15:26.340 --> 00:15:27.723 This is my personal dream. 376 00:15:28.710 --> 00:15:31.380 You will not be able to sell a software product 377 00:15:31.380 --> 00:15:35.170 in this world in the future unless it has a SCI score 378 00:15:36.270 --> 00:15:40.680 with evidence backed by a IMP file. 379 00:15:40.680 --> 00:15:42.150 That is the future that I want. 380 00:15:42.150 --> 00:15:43.500 If this future existed, 381 00:15:43.500 --> 00:15:46.650 everything else would snap into place. 382 00:15:46.650 --> 00:15:48.450 If you have to sell a product, 383 00:15:48.450 --> 00:15:50.220 you have to publish a SCI score, 384 00:15:50.220 --> 00:15:51.770 that's the future that we want, 385 00:15:54.120 --> 00:15:56.070 and that's the future I'm dreaming of, 386 00:15:56.070 --> 00:15:58.533 and that's the future I want to help build, 387 00:16:00.443 --> 00:16:02.550 and I'm gonna build it through standards. 388 00:16:02.550 --> 00:16:03.830 I know we're gonna be... 389 00:16:05.250 --> 00:16:06.240 This is a saying that I have. 390 00:16:06.240 --> 00:16:07.680 "If you're fully transparent, 391 00:16:07.680 --> 00:16:09.300 you can't be accused of greenwashing. 392 00:16:09.300 --> 00:16:11.500 You can only even be accused of being wrong." 393 00:16:12.600 --> 00:16:15.120 In my fuller talk about open source 394 00:16:15.120 --> 00:16:17.460 and how we kinda wrap it all together, 395 00:16:17.460 --> 00:16:18.600 this was the punchline, 396 00:16:18.600 --> 00:16:21.240 'cause open source is about transparency. 397 00:16:21.240 --> 00:16:24.390 It's abou, bringing it all together. 398 00:16:24.390 --> 00:16:26.138 So I think if you're fully transparent, 399 00:16:26.138 --> 00:16:26.971 you can't be accused of greenwashing. 400 00:16:26.971 --> 00:16:27.804 You can only be accused of being wrong, 401 00:16:27.804 --> 00:16:29.250 and that's the future that I want. 402 00:16:29.250 --> 00:16:31.800 I want the future where, when somebody publishes 403 00:16:31.800 --> 00:16:33.090 a sustainability report, 404 00:16:33.090 --> 00:16:34.500 there are no claims of greenwashing, 405 00:16:34.500 --> 00:16:37.773 there's just, "Oh, interesting approach. 406 00:16:38.610 --> 00:16:40.710 I would do it this way. 407 00:16:40.710 --> 00:16:42.840 Here's my computation." 408 00:16:42.840 --> 00:16:44.290 That's the world that I want. 409 00:16:46.920 --> 00:16:47.753 That's it. 410 00:16:49.200 --> 00:16:50.572 Thank you very much for your time. 411 00:16:50.572 --> 00:16:53.739 (audience applauding)