 It's just above. So I have not really preferred slides. I will sit down. I will relax. I will show you the red lines where I was traveling around the world for DVMid and similar things. So if you want to have a kind of travel, just join us. It's fun. So what about the buff? Well, I just want to show you who is in the team. And maybe we start. What's your interest? Why are you sitting in this buff? Are you working in the field of medicine or biology? Just start. Take the microphone or so. Or you are just looking for some chair in the shadow, right? Some entertainment or so. Looks like I will just talk now. I mean, I don't work in this field. I study medical computer science and therefore I have some interest in this area. I mean, the moment I don't do that much in this area, but I have quite an interest because I mean, otherwise I wouldn't have started studying it. I think it's also nice. So I think it's interesting for me to see what's going on and maybe help to be able for people working in this area that they are able to use free software, maybe use Debian. I mean, so yeah, that's my interest here. Yeah. Okay. Somebody else who wants to explain why he's here? No. Just curious. Okay. And that's nice that you are coming. He is interested in Davychem team. Well, basically, Davychem is doing similar things like Debian Made. Debian Made is packaging medical and biology software and they are packaging chemistry software. And if we are not aware what Debian Made is all about, then I possibly should start differently. But to stick to my slides, we have some people who have some interest for various reasons to build packages from biology and medical packages. Biology is included because it's microbiology is quite used in medicine. And actually, there is some free software to manage a medical practice or manage a hospital. There's also software, but not that much. And we have to fight hard to get this. And in biology, the targets are mostly easier to tackle. And these people who are in the team, we are even more, but these are the top 10 people who are, for instance, uploading packages. Started in 2002, there are some packages even uploaded in 2001, which are by chance in Debian. And you see there is some kind of five years, not so much happen. And then something happened. We met, we met in, I just said this in the other talk. We met together face to face and people are joining the team because they think it's interesting to meet to do some common things. The same effect is on the mailing list here. The interesting thing is that we have also very active upstream. For instance, a third frequent poster on our mailing list is a doctor, medical doctor who is working on a GNU made package. It's a practice management program. And his brother is also quite active. So these people are working on some software. So this Debian made user list is the connection between users and developers. And Debian made is all about connecting users and developers. We try to make the missing link between both because I had the impression that users are taking Debian usually as a full-grown product, which can't be changed. Download DVD or whatever or download the packages from internet and use it. And no, it's not really that way. Free Software is all about doing something, enhancing it. And so this team, Debian mid team, is trying to help people working in medical care and biology research. So this is on our mailing list. And we have a developer mailing list, which is for the development of packages, not so much about the users, to not scare away the users with technical stuff. We have also some statistics about who is hunting bugs in Debian mid. You also see some active people. Also, since we met in 2011, we had some increase. And this is about the commits in the version control system using Git and S4n. So we have also some people who are regularly posting here. And here you see some overview about so-called tasks. Any blend is divided in task or organized in task. We have here packages which are working for biology research. You see about 120 to 140 packages all to solve problems in biology research. I think that is kind of a lot. I don't know any distribution which has more than we have. And we have also a section to develop biological applications. This is also some interesting thing. We have some support for epidemiologists. There are quite a few of packages. We have also a lot of packages for medical imaging. So if you know something about these dichom images and solve this is a keyboard. And you can, we have some dichom fuel, something to analyze the software. And we have also software to develop medical imaging applications. And medical practice, we have some packages. So actually, if people hear the term debian made, they assume, well, this is some software to run my practice. Well, no, it's not. It contains some software to run your practice and besides a lot of other stuff. We have also, or what I also want to say, if you are new to debian made, I do not have the opinion that a medical doctor should just fetch the debian distribution, install, for instance, GNU made and run his practice on this. This is technically possible. But I do not really want to make the doctor fix his computer, but he should fix me. And so he should not be distracted by his computer. But the way I see debian made is to give some as best as possible preparation for some service company. So they could install on the doctor's computer and they are responsible. They get money for it. They get really money. And we are providing all the stuff they need. We would be happy if they would send some money back to debian. This would be okay. But otherwise we are doing free software. Yes, the question? Not that I'm aware of. I would like to, but I'm not aware of free to start a company. Yeah. Yeah, it's, it's there. Okay. Then there is something in cytology. We have some, some team in debian, which is a small team, but very efficient team. It's called neuro debian. They have their own website. And so in principle, you could also call neuro debian a blend. And we, I'm working on it to, to take them over to, to use our framework. And so, because it's quite easy to apply this. And they could organize way better and have a lot of profits. And we have some tools, I say, for health care use. There are some, some software like quit count, if you want to stop smoking or so. And something, yeah, work, work rave. If you work too much on your computer, it pops up every 45 minutes to say, no, you make a break and do some exercises also. Something which is, yes, also something connected to health. But yeah, and we all do this categorizing. It is not necessary that, that we all maintain the packages. For instance, in, in biology, there's a lot of stuff which is cross connected to the chemist. And we just organize the packages. So we are not a packaging team. We are just categorizing stuff. And we also package, but this is not the main points. The main point is that we try to enable the user to easily pick the software he is seeking for. This is basically, well, this is just, these are just my slides. And I can show you what we have for packages, because this is kind of good overview. I had this just in the other talk. We have, well, this is a German locale. I can change my browser to, to the French, but I just want to show you that it's localized. You do not need to understand the description. We have just, as I show you in the graph, biology, biology development, imaging and so on. And we could go, for instance, into, into imaging. And you see, there are some, some packages with their package descriptions with screenshots. You can mouse over the screenshot and you see it. And the, the description is translated. You have the information. How many users are using it? You see there's a new upstream version. So there's some work to do. And actually, this is what, what I wanted to do also with you in the workshop. How can I find tasks to do in our team? We really want you to do something. It's not just about hearing. Well, this is German fix the translation. If you see the translation is wrong, you could fix it and just click on it. But unfortunately, this server is currently not running. We just talked about this. So the idea is users who are visiting this page are most probably experts in medical imaging. I don't understand this. I can't really translate it correctly on the, the other specific field. But people who are visiting this page have a good chance to, to really are good translators. Or if there's missing a screenshot missing, you can click on it and you can upload it. And it's, it, it goes all into the official service of Debian screenshots.debian.net. You go there and you find the place to upload the screenshot. And we are also quite happy that we have these citations. We have frequently packages which are done by scientists and scientists are happy if they are quoted. And so they see, oh, if I get my package into Debian, I get another hit for my quotation. That's nice. So I try to get my package into Debian until we are doing it. That's why the way we, we are trying to build the bridge between users, upstream developers, and this is an important point. So here you can translate. This is not just translated. Just you can translate. So this is the way we organize our work. And we have also something which is not yet ready. We have some preparation in Git, right, or in SVN or whatever. What I'm doing is I'm checking the version control system of different teams. Not only Debian Meet, also Debian Jam, whatever. And trying to get all the machine readable information. So we have information here which is not even in Debian, but it's there. And so if somebody comes and says, well, what can I do? This is your work you can do. This is your to-do list. And this is available for all blends. It is for Debian, Debian, Edu, Debian games. And so you can use it. I'm frequently asked about DevTex because DevTex is another way inside Debian to categorize packages. This is a good technique. And we are trying to use it inside this framework. The problem is DevTex works only on existing packages. And these packages do not yet exist. So we can do some more. We are not competing with DevTex, but we try to integrate and add some additional features. So I think either you have questions or we just start finding a target and start packaging it if you want me to do this. And then you see how to work with this framework. But I would love to see some more questions from you or people who are becoming late. What's your interest in showing up here? Any questions? I have tried experimentally to find the packages related to Debian Med, to Debian Cam, and to NeuroDebian. Because you mentioned that there should be tasks for each of these. Actually there should be for each blend and also for NeuroDebian probably there should be more than one task. And I could find the Debian Cam and I could find those for NeuroDebian. Actually those for NeuroDebian are within science, Debian science or something. But I couldn't find those for Debian Med. Can I have a look what you mean? Because I'm not really sure. So what I do is going to package search and search by keyword. Debian Cam works, Neuro something works, but Debian Med doesn't work. There is a source package I can show you. There is a Debian Med source package. There is a source package which is divided into several, I shouldn't make it larger, right? The source package Debian Med is divided and Med package is made bio, made bio-dev. This is a development part. Med data, Med dental, Med pharmacy and so on. This is what you get. I think the Debian, the Debian packages are also the binary packages are starting with Debian and the Debian Med are just the prefix made, well, okay, maybe. This is actually not really the way we should advertise it, but you are right. This might be different. In Debian Edu has education prefix and Debian Science has a science prefix. I'm a friend of not so much typing, so Debian is under the beginning and so Med seems to me, well, okay. This is answering the question. Another question. What do we want to do? We could do, this is actually not really a Debian Med package. It is not teammate, but we can check on the, go on top here. What common packages we have in Debian Med and Debian. This is easy. It's only in the biology task. Yes, it's me again. Okay. I didn't see how you found, how you find the list of to-dos and also how do you find the list of to-dos for Debian and for other plans? There is no common to-do list. I just want to show, I come back to your finding to-do list. I'm just seeking here for Debian and you see the packages are maintained. This is Gamgee, General Atomistic Modeling Graphic Interface. Some packages which we are listing on our biology section are maintained by the Debian Med team. There is no conflict in different packaging teams because one package might be very interesting for biologists and for chemists as well with a different perspective. You have several things there. You have statistics packages which are relevant for several sciences, but also for our target user group. Here you can see the common things, but this is finally not so interesting for the user. Regarding the to-do list, everything what is marked in yellow, right? On this page you have a lot of yellow things. Upload screenshot. Upload screenshot. I've done a lot of work at Debian and to Debian conference. We had some several new version available problems here. They are gone since I'm here. Here we have a new upstream and we can look. This is package, right? You can see upstream has version 1.28 and there's new upstream version. This is by clicking on the yellow button you find the work to do. Then we can go download the source. This is most probably pretty easy. I'm just uploaded. I recently uploaded this package and just some simple uploads. We have also done a lot of stuff. Before I went to Debian conference, a lot of yellow stuff. Go tagging. You can go to DevTags and I also made it here in Enrigo's talk and made the DevTags. Oops, not found. Didn't it found? Go tagging. You see in this DevTags interface, this is just tagged. The reason why it's yellow on the web page is that DevTags are manual processed. I put this DevTags on Monday also and it's not just processed. This is only not true for all the things. If you want to do some DevTagging, you find your work here. Uploading screenshots is always possible. Sometimes these applications are commander and applications. It's hard to find a reason with screenshot, but other times not. Then we have here a new upstream version, new upstream for DSP package. This is some internal knowledge because Laszlo Kajan is upstream and I will not touch his upstream version. He will do it himself. This is no work I will do now. This is some interesting thing. Ambos is a large beast and we are lagging two minor versions behind. We are lagging one version behind because there was a Debian release when we did not touch it. Now it's time to tackle this one. I'm not really the main Ambos package, but the other person, Charles Plessy, has some kind of time constraints now. It's probably my thing and I hope to get it done at DevConf maybe in the weeks later. This is the usual QA work you can do, and then we have on the left side, it's a little bit hard to distinguish this color. This is green. Here we have Debian packages in experimental. Here we have Debian packages in new. I'm also checking the new queue. These packages are uploaded to new. There's not anything needed to be done because it's just waiting. The next section is we have some inofficial packages or we have something in VCS. Wait a moment. This small screen is not that comfortable. The information is obtained automatically from the version control system because I'm checking the team, the version control system from the relevant teams, from Debian Edo, Debian Giz, and so on. All the information is read into ultimate Debian database. Now we can display this information and if you see something which you are interested in, just find the relevant code and finalize the package. There can be different reasons why the package is not yet finished. There are also examples where there are inofficial Debian packages. Maybe I find one. To do this, it's quite long. Here's one from Ensembler. There is an inofficial package. You can click on it and find on the upstream page the package which you can install with varying, yes, user experience, I don't know. But if you want to package it, it might be a good start to look at what these upstream developers did and perhaps enhance it, fix it, or just upload it if it's okay. Some more questions? The description for uploaded packages come from the packages file or it's a separate database. No, okay. Yes, we are using all the information which is automatically available. So a person contributing to Debian that met also improved the translation for all the users. Yes, we are always using the Debian infrastructure and nothing in between or in parallel. This would be crazy. We started with, in 2002, when I started with Debian Meet, I started with manually written web pages on www.debian.org. And this definitely does not scale. And then some people got the idea to put it on the wiki because the wiki is always up to date, at least in theory. But if only one person cares for one wiki page, it isn't. And so I came up with this automatic update mechanism. It is basically on the very same information as you are creating the meta packages. The meta packages are created from so-called task files. It says depends package one, package two, package three, full bar. And then you get the meta package rendered and also these web pages from the very same information. So what you are doing to create meta packages, these web pages, or I can also show you the bug pages. You have also pages about bugs. What you are doing is just to fill in this very, very simple control file, similar shaped file, and then you get all the information. So the idea behind the bugs page is also easy. If I'm biologist or whatever chemist, I want to fix some bug. I go to the package where all what I'm interested in is assembled, and this is actually here. And this is also from the same, very same database, which is carrying the information about the task. Some color scheme is applied here. So we should fix the red ones first and then the yellow ones and so on. Any other questions? We have just 12 minutes left, I think. Is there a view about the translator? Following the countries says there is how many translators for this country? Can you say it again? I have not understood. Is there a view to follow how many translators there is by country? Well, we had this view, and this view is possibly a good way to make some competition between countries to push people to translate. But this view is not working anymore. I would like to get it again, but it's currently not existing, and it's not so high on my priority list, but I think we should get it again to say, well, French people are the best, or so like this. Yeah, it's competition is something you need some motivation for people working for free software, right? And this kind of competition could provide a little bit to competition, right? I think the Italians were quite good and Germans also good. Yeah. But and there are some fields where the Portuguese translators from Brazil put some effort in, but I'm not really informed, and we had this list of packages with tick marks and the flex and so but it's, I put it a little bit higher on my to-do list because you ask, okay? So some other questions? Yeah, I'd be happy about questions. Sure. Come on. Okay. I'm very confused. There is Alliot. Yes. Alliot looks like a collaboration platform based on FusionForge. Devian Med has a page on Alliot and they became two, but then from that, call it Alliot homepage, there is a link to the homepage of the project. For they became the link to the homepage of the project points to nothing. Yes. For Devian Med, it points to a wiki page. I don't see how I get to the actual project page that you have been showing us. Okay. And I wonder if there is one such for they became because I haven't found it. Yes. Well, if you Google for Devian Med, you get to the official www.devian.org site and yeah. Well, this is what you get when you the first hit when you Google for it, right? And there is a link to the task page. It is in full text. Every enhancement everybody's here in the room who tries to see can he thinks you can do it better. Please do it, right? And the second link is Devian Med wiki. It is possibly also on this homepage. We do not even have an official logo. This is a kind of suggestions. We are lacking of manpower. Please make better. We are very happy. And it seems I don't I don't can't speak for the devian devicam team that the devicam team is lacking even more of manpower. And this is an effect you will have seen that some wiki page the documentation always sucks. We really need people who help us the documentation right. So this also on this wiki page, you find your way to the task pages. They are there. Right. Yes. This is definitely some point. I'm always working with these task pages because it answers the question if my mother asking me what are you doing. Look, this is a lot of stuff. Or if my colleagues are asking me, I'm working on a medical institute and I'm using some of this software we have, but they don't realize because they are users of this different operating system where every software is installed by some magic and whatever. And when my colleagues say, well, this package or this program does not work under my operating system, I say, well, I had a suggestion for you, just use this one. But it takes some time until this is approached. Actually, my motivation to run devian meet was once my institute might decide to use free software, I want to be able to present a ready system. And I think from my point of view, I'm there. We have something which is really, really usable in my environment, but they did not yet decided to use it. We have some more years left to become even better. More questions, more criticism points we could do better. If you're interested, just subscribe to the mailing list. I hope we have interesting topics for you. We have also some training program, how you can learn packaging, which I just was talking when I came here, this mentoring of the months. So if you want to learn packaging, pick an example from our task page, which is not yet done or find a bug or something like this. And I will teach you for one month how to do packaging. This is your chance. Maybe if you are connected to the David Shem team, well, you don't need to be an official student of this mentoring of months, things to get some help on our mailing list, right? If you have a problem, we try to solve it for you. And just don't be shy and ask what you want to know. But this is kind of a formalism we put on it. I would have loved to see some more real members of the team, which are what means members of the team, people who are just uploading or working together, but they are not here at Debian Conference. Actually, the Debian Made Project is a very small leaf project inside the Debian Universe because there is a small common set between medicine and free software. And we are just trying to cover this one. So we have a very branch or leaf project. And we only can survive because Debian exists and we only can survive because we are caring for a lot of people in our team and because we are caring for the technique, which is used also by others. So this is the main strategy. So if you think what the hell makes medicine inside Debian, because Debian is a general operating system, where Debian is a universal operating system. So it should also cover medicine, biology, and other fields. It's lacking a little bit on this last part, the other fields, because they are not that much provided. Chemistry is quite good. We have a Debian science, which is kind of an umbrella over mathematics, physics, electronics, astronomics. And so these could be all covered a little bit better. So if you are just stumbling by and coming from a different field, maybe Debian science is something for you. And maybe we could make also more focus on some certain sciences, which is quite interesting, but it's also work. If you are afraid of work, then it's not really for you. So three or four minutes left. Other questions. I can also stop talking if I'm boring you. It's fine. By the way, I just asked about the translation server. It's not yet running. He just wanted to do some translation for us and was stumbling about the fact that it's this effect I will show you. Just manage correct or fix the translation. We try to do it and the network is weak, but it's not working anyway. It's because some server in Spain is shut off and nobody is starting shutting it on. And this sucks because, well, I will not blame the Spanish people because they provided the server for several years. But we are losing translators. It's not normal. It's somebody who had contact five weeks ago or so. And he is patient waiting, coming to DevCon, trying to learn something, but other people just will go away. If I try three times to translate something and it doesn't work, I will never try again. This is kind of stupid. Well, I think we should stop here. It's okay. Thank you.