 All right, good morning everyone. Thank you for coming. I will talk about depth sources and the new features We have implemented since last year so I made a talk at depth conf last year and we made a lot of changes since then Better so I will first introduce depth sources quite shortly because I guess a lot of people here know it already It's roasted at sources.debian.net. You can try it out while I do the talk Then the new stable features that were announced last year now work the patch tracker and copyright tracker And what we are currently doing is a mobile version of depth sources So that's sources.debian.net Basically, it allows you to bruise all the source code of all Debian package ever. They are all archived And you can bruise through a web interface You can also search the source code if you have code search.debian.net that will redirect you back to depth sources They also provide some statistics about source code that they will present you in a minute So that's the basic interface. You can view co-say The syntax highlighted code source and for instance the number of Source lines of code in package. So on the left you see for the Linux kernel All the C code all the XML C++ extra code number of lines and we also provide some suit statistics So you can see the evolution of the millions of lines of code So for unstable there is a lot Way more than stretch. That's because we have many versions of Chromium kernel extra that add up So last year at Debian. We were developing a patch tracker and a copyright tracker Well now everything works fine. Thanks to our previous GSOc student, Ernestis. I represent this You can treat out sources.debian.net slash patches which replaces the old patch tracker That is a P&M It looks like this for any package. You can bruise the patches that are applied You can see all the difference on the on which files they are applied and you can bruise the With the patch syntax colorized to Second feature the copyright tracker. So for copyright passable files Represent all the licenses and all the files on which felt they they are applied So it looks like this Basically, you can you can bruise all the other files and see the license So that's for Firefox. You can see Modilla Public License or GPL2-3 And you can scroll to actually read the licenses that are applied Restrictions we need machine machine passable data for this So it only works currently with the 3.0 quilt version of patches and we need machine passable debian slash copyright So if If it's not possible for your package, please add it. We need it Now go mobile So I found a lot of people got this kind of devices nowadays, so we really need to go mobile You can you can have the source code in your pocket Raise your hands if you're bored in the in the middle We'll have to get a fancier design with Use the bootstrap framework. So it's quite nice, but still links compatible. Don't worry And we will add new features So we had a problem previously it looked like this. It's not really handy. It looks like nothing and it was a bit annoying to Well scroll scroll zoom in zoom out on your on your package. So That's work in progress and it will look like this It actually already does but not for that part not for every page In bruiser edition of files. So last year Raphael geysers implemented a Chromium and Firefox plugin to allow the edition of files directly in your In your browser so I can show you Demonstration of this So that's a random file and you you get an edit button So you can change this deep edit And you can email a patch directly So you can edit any file in any deviant package and email the patch to the maintainer It's very useful to correct typos quite fast But currently it requires a plug-in. We wanted integrated natively in depth sources for desktop and mobile So you can actually you will be able to patch deviant from your phone from anywhere I've grown that is it's work in progress. We have a gsoc student who is working on this I run the LNA If you want to help that she's always welcome, of course Well, that's all it was a bit short, but we have time for questions and discussion. Thank you What is the plan for sources to be an org? There is a discussion about this with the DSA I'm not in the email loop Stefan was a key release taking taking care of this I think it should appear. I don't really know. I hope so Work in progress Thank you So the edit in place that uses report pack as a backend and it requires the user to set up a local mayor server and configure it To edit the files. Yes. No, you just need a browser and you can edit files in your browser Then you generate a diff that you can download and email yourself or just click the email button Yeah, but but the email functionality you require so locally set up No, it will just open your email client. I can do I can do it if we have time Or do you see I miss the beginning of the talk so maybe you address this but Or do you see this fitting with code search on one side and snap shut them your nog on the other side? Shouldn't this all be a single big service? Yes, it should be possible But we don't have the same database as cultures. That's really I don't know how it works, but they have a big database of all the c tags in unstable That we don't do but I guess it could be manageable with the snapshot. I don't know. I don't know how it works That's a good idea Did you had trouble with accessibility and sources dot devian.net? Or do you know whether it's fully accessible because I recently got the book reports that some Bootstrap features are not For tracker and we never got any any bug reports for this. So we try to make some nice html 5 accessible I know I'd like some reports of people But with the new mobile version And the new mobile slash desktop version. It should be cleaner So more accessible. Thank you Thank you for the speaker