WEBVTT 00:00.000 --> 00:11.880 So, we've had a long talk about some of the implications of the cyber-Isileans Act, 00:11.880 --> 00:15.520 but I can imagine that there are some developers in this room who are wondering how the hell 00:15.520 --> 00:17.920 am I going to implement all this. 00:17.920 --> 00:22.400 Now, luckily, there is a solution to that problem, and it is the standards which are currently 00:22.400 --> 00:27.000 under development for the CRA, and they cover a number of different verticals, so it can 00:27.000 --> 00:32.440 be anything from operating systems to system, event and information management. 00:32.440 --> 00:39.760 There is a really wide variety, and I was I, Simon myself and others, have been working 00:39.760 --> 00:44.840 on this for quite some time now, so we're heads to tell you about how you can get involved 00:44.840 --> 00:46.720 if you want to get involved. 00:46.720 --> 00:52.000 First, it would be extremely rude of me not to say thank you to a couple of people who 00:52.000 --> 00:54.240 are currently in the room. 00:54.240 --> 00:59.000 We have Alton and Law, both from Etsy, which is one of the European standardization 00:59.000 --> 01:03.080 organisations, who have been working with us to make sure that open source developers can 01:03.080 --> 01:05.120 participate in the standardization work. 01:05.120 --> 01:08.120 I know there are a few of us in the room, but I do think they deserve a round of applause for 01:08.120 --> 01:12.640 that, because it's the first time in history that open source developers can get directly 01:12.640 --> 01:16.680 involved in the standardization process, so I think they deserve a better than the 01:16.680 --> 01:20.360 applause for that. 01:20.360 --> 01:25.440 So we're getting quite late in the process now, but the goal of today really is to show 01:25.440 --> 01:28.880 you precisely how you can do just that. 01:28.880 --> 01:33.920 So first thing you need to know is that if you want to get involved and you're not sure 01:33.920 --> 01:39.760 where to start, you can contact Simon and all myself, and we will happily sort of get 01:39.760 --> 01:41.560 you involved, get you integrated. 01:41.560 --> 01:46.360 We can get you into the meetings at the standardization organisations as well, so please 01:46.440 --> 01:51.280 feel free to reach out to us, we're getting a little bit of feedback, but you can reach 01:51.280 --> 01:58.240 us at, so Jordan at open source.org and Simon at open source.org, just going to give you 01:58.240 --> 02:03.120 a little bit of a show of how you can participate as well more directly, which you like 02:03.120 --> 02:05.120 to take the mic and the rate. 02:05.120 --> 02:06.120 I can do that. 02:06.120 --> 02:07.120 Okay. 02:07.120 --> 02:08.120 For our views as well. 02:08.120 --> 02:09.120 Which have you done that? 02:09.120 --> 02:10.120 Yes. 02:10.120 --> 02:11.120 Okay. 02:12.040 --> 02:17.080 And we're playing slide karaoke here, because I've not seen his slides. 02:17.080 --> 02:18.080 It's not even slides. 02:18.080 --> 02:19.280 I'm going to go straight to the last. 02:19.280 --> 02:30.600 So at Etsy, the first of all clarified, the standardization work is in two broad 02:30.600 --> 02:32.080 parts. 02:32.080 --> 02:38.440 There are horizontal standards that standards that affect every kind of product, that are 02:38.440 --> 02:45.680 being developed at San Senlec, and those standards are punitively difficult for anyone 02:45.680 --> 02:52.360 from outside the standards machine to get even to read, let alone to get involved in. 02:52.360 --> 02:56.680 We do have a coming plan that will come to that later. 02:56.680 --> 03:02.240 And then all the vertical product standards are being, or most of the vertical products 03:02.240 --> 03:05.600 standards are being developed at Etsy. 03:05.600 --> 03:09.400 Etsy is one of three European standards or organizations. 03:09.400 --> 03:18.960 That's Senlec and Etsy, and they were designated as, by regulation, 1025, 2012. 03:18.960 --> 03:22.800 This is not really what they do for a living, either of them. 03:22.800 --> 03:28.120 Senlec tends to do standards about interoperable infrastructure, like making sure your 03:28.120 --> 03:32.800 pipes fit together and your roads have got the right rate of tarmac. 03:32.800 --> 03:38.360 And Etsy is dominated by the standardization of telecommunication standards, although it 03:38.360 --> 03:45.120 has, in the recent decade, diversified a great deal into many other areas. 03:45.120 --> 03:51.720 The vertical standards are being developed by a committee called EU Standards Request, within 03:51.720 --> 03:55.920 a larger technical committee called TC Cyber. 03:55.920 --> 04:00.480 I'm lucky enough to be the Vice Chair of the USR, and we're lucky enough to have law 04:00.480 --> 04:09.600 in the back row there as our Secretary and Administrator, and actually the person that makes 04:09.600 --> 04:12.600 everything work. 04:12.600 --> 04:18.080 Gainy access to these organizations has been challenging, but we're going to tell you 04:18.080 --> 04:22.920 in a minute about, again, a cunning trick that we have discovered that will allow anyone 04:22.920 --> 04:26.080 in the room to be involved if you would like to be. 04:26.080 --> 04:32.880 So if you go visit that, you're at the top there, you'll discover that many of the standards 04:32.880 --> 04:40.960 are on GitLab, and you can just look at the markdown of the improgress standard. 04:40.960 --> 04:49.840 And most of the time, you can also open issues that describe your comments, preferably polite, 04:49.840 --> 04:56.800 detailed accurate comments that can be actualized into changes in the spec. 04:56.800 --> 05:05.040 So far, Etsy is chosen not to allow poor requests or change requests to be submitted. 05:05.040 --> 05:11.920 Maybe next time, I don't know, but in your issue, if you have got a concrete change to the 05:11.920 --> 05:17.840 standard that you are reading, the rapporteurs do not mind at all if you give them text 05:17.840 --> 05:19.840 that they can quote from. 05:19.840 --> 05:25.840 Sorry, derive their own version from. 05:25.840 --> 05:32.040 So this shows you the one of the standards, this is the root of standard, so I'll 05:32.040 --> 05:34.360 operate in system standard. 05:34.360 --> 05:38.760 This is being maintained by somebody who holds the pen on behalf of the technical 05:38.760 --> 05:47.760 committee called the rapporteur, because these standards are typically rather unprofitable 05:47.760 --> 05:55.520 for Etsy's members, Etsy very wisely secured funding for paid rapporteurs to work on them. 05:55.520 --> 06:00.960 And so most of the standards have got somebody who is a professional rapporteur who is gathering 06:00.960 --> 06:05.320 the expert input of the technical committee and writing the text. 06:05.320 --> 06:11.760 At the moment, all of these standards are at the stage where they are all the sections 06:11.760 --> 06:17.720 are filled, they are viable, they are probably acceptable as a standard, and they 06:17.720 --> 06:21.440 have all just been reviewed by the European Commission. 06:21.440 --> 06:24.520 But you can still come comment. 06:24.520 --> 06:29.880 These specs are still accepting comments on a monthly rolling cycle. 06:29.880 --> 06:36.440 Your comments will all be considered, they will all be taken into the committee and reviewed 06:36.440 --> 06:43.160 in a meeting where your suggestions will be considered and either accepted or will work 06:43.200 --> 06:47.920 on something different or it will be lightly declined. 06:47.920 --> 06:53.360 We are not too prudous about this, we will politely decline if what you have submitted 06:53.360 --> 06:55.560 is not acceptable. 06:55.560 --> 06:59.760 For example, to give you an example, the FSFE have commented on quite a few of the things and 06:59.760 --> 07:05.240 so we will take the comments and work with them with people inside Etsy to try to get 07:05.240 --> 07:10.520 those comments passed through, especially when it comes to stuff like freedom to use certain 07:10.520 --> 07:15.240 stuff, where on say, routers or dealing with issues with security with bootloaders, stuff 07:15.240 --> 07:16.240 like that. 07:16.240 --> 07:22.000 So we are actually out of time already. 07:22.000 --> 07:26.000 The essential has been said, except for how to join in. 07:26.000 --> 07:27.000 So you have the slide on that? 07:27.000 --> 07:28.000 I don't. 07:28.000 --> 07:29.000 OK. 07:29.000 --> 07:36.560 So through the careful work of some senior people at Etsy, OSI has got the privilege of being 07:36.560 --> 07:44.320 able to ask genuine community members to be admitted as members of the ESR committee at 07:44.320 --> 07:45.320 Etsy. 07:45.320 --> 07:50.520 And if you work on a project which is effective by the CRA and you are willing to put 07:50.520 --> 07:55.280 in the hard work of attending the meetings of reading the specifications, you should get 07:55.280 --> 08:02.040 in touch with me or him or with law and we will work to have you admitted into the committee. 08:02.040 --> 08:08.160 We have had several excellent contributions, the Zen community is helping us a great deal, 08:08.160 --> 08:13.880 we are getting excellent contributions from the Debian community, but it may well be that you 08:13.880 --> 08:18.200 are the perfect person to join in with this standardisation activity. 08:18.200 --> 08:23.040 And then the other coming plan, Zen Senleck is almost impossible to make a contribution 08:23.040 --> 08:26.280 to, I'm sorry, it's true. 08:26.280 --> 08:33.080 And if you join the Etsy committee, again through the magic of administration, we can 08:33.080 --> 08:39.120 probably give you access to the Zen Senleck working groups that are working on the horizontal 08:39.120 --> 08:40.120 standards. 08:40.120 --> 08:44.400 And again, if that's what you really want to happen and you want to think about it very 08:44.400 --> 08:50.720 seriously before you say yes, come and talk to me and I will try and help you get involved 08:50.720 --> 08:52.640 in that activity. 08:52.720 --> 08:57.520 This is all revolutionary for me, I've been working on standards since 1988. 08:57.520 --> 09:03.520 This is the first time it's been possible for the ad hoc community of open source to 09:03.520 --> 09:08.000 actually be actively involved in the standards process without having to go through an 09:08.000 --> 09:14.800 employer or a national organisation to gain access both of which turn out to be quite tricky. 09:14.800 --> 09:20.200 So I'm really pleased by what has been achieved, particularly by Alton, who wrote the 09:20.240 --> 09:23.040 MOU that we're doing this all under. 09:23.040 --> 09:25.400 So that's everything we don't have time for questions. 09:25.400 --> 09:29.520 There are quite a few rappel tours around, there are even some in the room, like there's 09:29.520 --> 09:32.240 a couple of air back there. 09:32.240 --> 09:36.960 So again, ask these people and we will help you get involved, thanks. 09:36.960 --> 09:41.600 And do stick around because we have an amazing final session of the day with Toby Langel, 09:41.600 --> 09:45.720 who's going to talk to us a bit about his experience in standard setting in how we can do 09:45.720 --> 09:46.720 it better hopefully. 09:46.720 --> 09:48.880 Toby, I'm going to hand over to you.