OpenSUSE Education
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 70 | |
| Author | ||
| License | CC Attribution 2.0 Belgium: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/39536 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
FOSDEM 20096 / 70
3
4
6
16
17
18
19
20
21
22
23
24
25
26
27
29
30
31
32
33
35
40
41
44
46
47
48
50
51
54
55
57
58
59
60
62
65
67
68
69
70
00:00
Goodness of fitFreewareSoftwareMultiplication signTouchscreenComputer animationLecture/Conference
01:26
Goodness of fitProjective planeEmailNormal (geometry)Repository (publishing)System administratorWeb pageProcess (computing)Right angleOpen setCountingLecture/Conference
02:25
Cartesian coordinate systemINTEGRALSoftware developerEndliche ModelltheorieTask (computing)Distribution (mathematics)Repository (publishing)State of matterPoint (geometry)Office suiteProduct (business)Arithmetic progressionExecution unitDirectory serviceQueue (abstract data type)Client (computing)Server (computing)Process (computing)Substitute goodIntegrated development environmentOnline helpSoftwareGoodness of fitRight angleLecture/Conference
06:07
SoftwareService (economics)BuildingRevision controlPoint (geometry)Software testingCache (computing)Process (computing)Repository (publishing)Multiplication signComputer fileSoftware developerMedical imagingEducational softwareInternetworkingRight angleWeb pageGreatest elementWikiOpen sourceDescriptive statisticsGame controllerSynchronizationInformationMathematicsKey (cryptography)Server (computing)Sign (mathematics)Fitness functionBand matrixStandard deviationTranslation (relic)BitConnected spaceProjective planeMetadataMoment (mathematics)NumberEigenvalues and eigenvectorsPhysical lawArithmetic meanQuicksortCasting (performing arts)Complete metric spaceCellular automatonHome pageUniform resource locatorDisk read-and-write headInheritance (object-oriented programming)Execution unitForcing (mathematics)Polar coordinate systemEnterprise architectureBeat (acoustics)BootingState of matterCuboidReading (process)Lecture/Conference
13:52
Computer-generated imageryRepository (publishing)Group actionMetadataMathematicsInformationHypermediaProjective planeSynchronizationServer (computing)Patch (Unix)Repository (publishing)Service (economics)Traffic reportingBuildingOpen sourceSoftware bugKey (cryptography)Computer fileCore dumpWikiOpen setElectronic mailing listMoment (mathematics)EmailDefault (computer science)Internet forumSoftware testingCartesian coordinate systemSoftware developerSoftwareDistribution (mathematics)Predicate (grammar)Universe (mathematics)Software development kitSummierbarkeitPosterior probabilityMultiplication signMedical imagingWeb pageTube (container)Data miningSlide ruleNetwork topologyCuboidGraph coloringCASE <Informatik>Revision controlPolar coordinate systemComputer configurationLecture/Conference
21:36
Projective planeOpen sourceFreewareServer (computing)SoftwareNumbering schemeHypermediaCartesian coordinate systemRevision controlOpen setPlanningRadical (chemistry)BootingRepository (publishing)Software bugMedical imagingSoftware developerOffice suiteVideoconferencingBand matrixHard disk driveSoftware repositoryINTEGRALEducational softwareMehrplatzsystemBuildingDebuggerWeb 2.0ModemOperating systemIP addressDecision theoryComputer hardwareDirectory serviceClient (computing)Key (cryptography)Configuration spaceDistribution (mathematics)Descriptive statisticsPolar coordinate systemDomain nameFormal languageTouch typingFunctional (mathematics)MereologyMultiplication signCoprocessorMoment (mathematics)ResultantData storage deviceGraphical user interfaceWave packetInternetworkingGeneric programmingNeuroinformatikService (economics)Computer configurationData structurePatch (Unix)NP-hardMaxima and minimaInstallation artScripting languageRange (statistics)Software testingPattern languageEndliche ModelltheorieInformationMobile appWindowFeedbackComputer programmingLocal ringStudent's t-testVideo gameLoginAbsolute valueProcess (computing)Term (mathematics)Physical systemRight angleStability theoryDatabaseFront and back endsCybersexWordSelf-organizationState of matterComputer fileLevel (video gaming)BitMoment <Mathematik>Content (media)Heat transferForcing (mathematics)Inheritance (object-oriented programming)Inverse elementSystem administratorMusical ensembleOrder (biology)NumberCapillary actionData miningIdentity managementSquare numberDigitizingQuery languageGravitationCellular automatonCuboidOctavePersonal computerNatural numberType theorySound effectTravelling salesman problemConnected spaceCondition numberDirected graphStress (mechanics)Figurate numberAtomic numberPoint cloudLecture/Conference
Transcript: English(auto-generated)
00:26
Okay, ladies and gentlemen, welcome, good morning, nice to see all of you there at this early time on Sunday. Well, we're just starting with this screen. The comment you see here is from a teacher in America saying, hey guys, what you're doing
00:50
is absolutely illegal. It can't be true that software is free and that's why we do this one.
01:02
Just to tell you, we are doing free software and yes, we want to tell children about it. We want the children uses free software and something, somebody told me it's good to use
01:21
free software and to free your mind. My fault, sorry, okay, sorry, good morning, I'm Andrea Florio, also known as Anubis G1
01:49
also known as Anubis G1 by the OpenSUSE community and here my mail. I am a pack gun packager since 2007 and I'm proud to join the open education project
02:05
last year. I started as a normal packager but later, thanks to Lars, I became one of the four administrators. Right now, I maintain several packages in our repository.
02:21
I lost the count really and my job is the technology teacher in the QSI International School, that is a school international where sons of a United Nation employees go on several states.
02:40
He is Lars Vogt and he can talk. Okay, welcome, my name is Lars Vogt, I'm formerly known as Lars Vogt and my nickname is Kleiner Eisbähr. It's a special name for the Germans under us and currently I'm working for the
03:00
alter build or distribution team for SUSE and joined the education team around 2006. Before, I worked on a special product called SUSE School Server and therefore, I have some knowledge about the education thing. I'm currently maintaining around 250 packages in the education repository and as you might
03:27
see, that's far too much and I hope I can give away some of those packages to the upstream developers in the near future. Okay, so that's our goals.
03:47
The main goal is wherewith do you teach tomorrow? The first goal and currently the main goal is to get OpenSUSE in schools and to support
04:02
those schools using OpenSUSE and help them to get it spread around all pupils. Of course, we want to provide the best integration between OpenSUSE and our application for both server and desktop. That's why for us, clients are important like servers because without them, we can't
04:27
provide a good environment in schools. You know lots of schools work using Active Directory and we think that we can't completely substitute Active Directory with OpenSUSE education.
04:41
That's why we provide both. We also try to contribute to improve OpenSUSE. That's why Lars told that hopefully we can send upstream our packages. What else? You can see here two goals, half green and half blue.
05:02
Those goals are still a kind of work in progress. In fact, we will try to build a cross-distribution education community but it's not really easy right now. The same thing is to work together with developers even if we have some examples
05:23
like Salome developers and took Spine once and lots of others. What else? Last point, support home users means if anybody of you has a kid, perhaps you might know what's the critical aspects letting kids working alone on your PC.
05:44
That's one other task we have. One is to work for schools and get educational applications in schools. Another one is to help home users with their kids so they can even use the same applications. It's really simple.
06:01
Or even get something like filter software for Firefox and so on. What does we have right now? We have a very, very big project and it's growing day by day. We have something like 800 packages for both. It's 32 and 74 bits.
06:22
We released the 1.0 add-on for OpenSUSE 10.2, 10.3, 11.0 and 11.1 and also for SUSE Linux Enterprise 10. We provide on our wiki description for not all the software right now,
06:42
but we are working to do that for lots of them anyway. We have our bugzilla and we have to say thanks to Noel for providing us that. We have a necessary repository, a developer wiki and our own page. You can see some URL on the bottom of the page.
07:02
We have also maybe the most important things, two repositories. The developer one and the frozen one. There are two. Why? Simply because one is intended for end user, the other one of course not. Let's see why.
07:20
The build service repository we wrote as developer one is not for end user. We can't add a license dialogue. We can write everything on that license dialogue, but we can't add into the build service repository. Not just features. We can't add control files.
07:41
We can't add package translations and everything else. We tried to install all the education software using the standard control file provided by the OpenSUSE DVD and simply doesn't fit. So using the build server repository, we can't work with it. It's not available without an internet access
08:01
because a single package sometimes triggers several packages to rebuild. So you need an internet access to download anytime the latest package. To enhance the third point, it's not available with all internet access.
08:22
Access means at least if you have schools with 50, 60, 100 PCs, you don't want each PC to connect directly to the internet to get all the packages. That's one point why we release an add-on ISO image so people can just burn it on the DVD and use this DVD
08:45
instead of connecting each PC to the internet. Okay, next point. Zipper add repository is non-refresh. Well, yes, it's simple. Just use the command line tool Zipper
09:02
and add the OpenSUSE build service education repository. You will notice that Zipper adds this repository with a marking non-refresh. So what can happen? You try to install one package one or two hours later and in this time the build service rebuilds the whole repository.
09:26
The package Zipper has in the cache is version 1.0 and release 35. No, the build service has rebuilt the complete repository. Zipper has the cached repository and says,
09:40
hey, I want release 35, but the build service has 36. And that's when Zipper tells you, sorry, this package is not available. Refresh means download at least the metadata. Even if you have an internet connection to refresh all the time, you have to download at least four megas.
10:02
So it's a waste of time, it's a waste of internet bandwidth and everything. No end-user information. Why packages as an aggregate version or release number? This is maybe one of the most important points. In fact, using a build service repository,
10:20
we can't provide information before installing a package. You can have information only after you install that reading the package changelog. That is not a good thing. You want to know what change we made before installing a new version.
10:45
Packages can be broken during testing. You know, that's a development repository. We update changes, we update patches, and sometimes packages are broken. And even if a test is always welcome, an end-user doesn't care about a broken repository.
11:03
Otherwise, it wants only a stable one. Wait, wait. So, no. One sec, please. Okay. That's our reasons for using the build service for developers and for testers. That's our reasons at the moment why we can't use the build service for end-users.
11:26
And hopefully, in the next future of the build service releases, all these topics will be gone. But until then, we stay with these seven points to tell people,
11:40
if you want stable packages, if you want packages that just work, please use our frozen repositories. So, this is a short overview of how we work at the moment. May I have this one?
12:02
So, on this side, you see what we as developers do. It's just simply the same process every developer knows. We get the sources, put them in the build service, the build service builds the package, hopefully, and afterwards, we can test the package.
12:23
We have additional testers around the world testing packages from the build service repository and add bugseller entries to our bugseller. Afterwards, we can just restart the process, fixing the packages, rebuilding them, testing them again, and so on and so on.
12:42
So, at the moment, once a time when we decide that we are in a stable enough state, we say, okay, now it's the time to create a frozen repository ready to use for end-users. That's when we begin to sync the build service repository outside.
13:04
We start just putting down the packages on a separate server and re-sign them with our own GPG key to make it clear that this package has nothing to do with the original build service.
13:21
It just has another GPG key, it has another signing. If you test such a package in the frozen repository, you will notice that these packages are already signed with the GPG key from the open source education team and not with the build service one. Another one is, building this repository enables us to use all the JAST features.
13:45
So, if you add this repository, you get a license dialog that tells you how you can reach us, how you can talk to us, how you can add bugseller entries, and so on. If you enable this repository, you have patterned files, which means a group of packages which are useful for small kids,
14:03
for bigger kids, for really universities, and so on, and even for servers. That's why we use this step to sync the packages outside of the build service repository. And, well, so-called shh-beep happens,
14:24
and sometimes all these packages in this frozen repository are broken. Well, the same is for every distribution, I think. And for this case, we have also a frozen, let's call it frozen,
14:41
it's just outside of the build service update repository. So, if we detect a broken package in this frozen repository, we already have enabled and installed an update repository in your zipper. If you install the frozen repository and look at the zipper,
15:04
you will get an additional update repository which is, per default, disabled. Because if you have a school with 60 or more PCs, you don't want even to search for updates in this repository. That's the reason why it is disabled, per default.
15:21
But if you enable it, you can get updates for these packages in the frozen repository. And these updates are coming, for example, with patch infos, so you can see, before you install a package, what has changed. And, of course, we don't have to forget our community.
15:41
In fact, using mailing lists, ears, and the bugzilla wiki request, we can have all the information we need to provide new packages to fix the bugs we can find. And everything works with our bugzilla. Everything will be moved there.
16:00
Without it, our work is very, very difficult. So, our community is maybe the core of our work, of our team. Without it, we can't work. Well, we've talked here, mailing lists, org, forums, and so on, all your possibilities where you can talk to people outside,
16:24
talk to the community, and often the community tells us, hey, I want this package, or this package could be a better package, or so on. And to not get lost, this information, we currently just use bugzilla, so we have, for example, an own wish list in our bugzilla,
16:43
so people can just add new package wishes. Going on? Okay. We talked about that yet, but we can't review again. So, we have update and frozen repository, but what are benefits?
17:04
Using a frozen repository, you don't need to refresh it. It's frozen. We follow the same policy as open SUSE repository. We have a frozen one and an updated one. The first one is not need to be refreshed. It's well tested and the packages are stable.
17:23
We have one GPG key that can fully control everything and is an add-on media. We provide an ISO and everything starts automatically. It's easy and easier to document. We, in fact, usually provide documentation about the most important packages
17:49
with the repository and the ISO image. And it's easier to file bug reports because you know exactly which version, which release of a package is buggy.
18:00
Using the openSUSE service repository, you know the package is built anytime and maybe you file a bug report that has been fixed on the next release. Using the update repository is added automatically and is not set as auto refresh.
18:23
You have to enable it. But the most important thing, as we told before, is that it contains patch infos. You see in the openSUSE updated applet what kind of change has been made on the package. If you agree with that change, you can install the package.
18:42
It is something you can compare before the installation. And it's really smaller than the main repository. We saw the metadata and it was just 150 kilobits. Again, it's four megabits for the whole repository.
19:04
We have to say thanks to lots of people starting from openSUSE, NUVELL, my Linux user group, the Linux, the BRILLOG, sorry, XTS, Tux4Kids, and Didaska is an Italian group that provides
19:22
open source ACDL. And all the others which have no logo, of course. Like communities and our developers and so on. But if you can see at this slide, what we want to do is to try to work together with Upstream,
19:46
work together with other partners to get openSUSE education spread around the world. That's why HPE and NUVELL started an education project. And last week maybe they fired news telling thanks to us for our work.
20:09
They and NUVELL looks like to work together with us to improve our packages and provide anytime at best and better add-on media for education.
20:24
Just for the information, currently we have around 20 packages alone in the education build service repository, which does not mean that these are all. We have many more people around the world starting testing.
20:41
By testing they are helping us or helping people with their packages. So if you look at the forums and search for education, you find many, many requests about packages for the application repository and already people in the forums helping each other to get this running. And even Upstream developers are now starting to work with us.
21:03
So if Upstream says, hey, it's a good tool, we can start something. For example, we have already packages for Fedora and some people already asked us to build also their packages, their software for Debian and Ubuntu. The only reason currently that we don't have such packages for Debian and Ubuntu
21:23
is that we are not Debian packages at the moment and we just have to learn it. So if somebody is able to package that, join us. Great to join you. Kiwi-LTSP is maybe the most important server project we are working on.
21:45
It's been awarded in 2008 of free open source software in India. What's Kiwi-LTSP? Well, Kiwi-LTSP is based on Linux terminal server project called LTSP5.
22:01
It provides simply a way to use from team clients, that means clients without an hard disk, application from the main computer. Lots of terminal server and many team clients,
22:21
many team clients means also very obsolete computers in schools. Supports PXC support. They are able to PXC boot. They can boot from the internet then. Well, we use also Kiwi to build our system PXC client.
22:42
We create an image of the whole operating system and a benefit using Kiwi is that Kiwi is widely used. It's a stable resource right now. It's used to the studio on build service. It's integrated into Yast.
23:01
It's easy to a local application and going on. How does Kiwi-LTSP work? Simply it uses LTSP to send a single image. But the single image is not a single application. It's the image of the whole operating system.
23:22
So team clients, computers without an hard disk, very obsolete computers are able to start the whole operating system with all application installed on the main computer. Right now with a computer with 4G gas or RAM, we are able to boot something like 30 team clients or something like that.
23:45
So with a very good PC you can create a nice computer lab in your school with just few money. Just by reusing old hardware which obsolete normally
24:04
and doesn't run the current applications. I forget to tell that Kiwi-LTSP is not limited to PXE boot. You can also, thanks to Kiwi, boot using live CDs, USB images
24:23
and everything else you have in your mind. We also provide an integration with the etalk and with ice cream to provide a kind of build farm. One moment. That's one reason why we use Kiwi.
24:42
It's really easy at the moment even if there is no GUI for it. But you just have to edit some configuration files, restart the build and for example if you have an old hardware, you have for example a Pentium 3 or something like that
25:01
and you said running this as normal thin client without really using the processor is not really useful for me because then everything runs on the terminal server. So we can try to find a way to way solution just saying something like
25:21
I integrate Firefox in the Kiwi image. It's just by adding the package name to the configuration file. Rebuild the image and now you have a Firefox running on your local client if you start it from there. So the terminal server doesn't have to run Firefox. All the clients run Firefox.
25:42
So you can test how much your hardware works and you can find the best solution for your setup by just adding packages which can be run locally. For example I don't think you want to have open office run on your local client but other apps maybe are useful for that.
26:02
And we have also Cyberorg and other developers that build a kind of GUI for Kiwi LTSP called Easy LTSP. It's an easy configurator that allows you to set up just few things
26:21
and press OK, stop, everything is working. But how can you install Kiwi LTSP? Well, the easiest way is to use the one-click install or maybe use our patterns provided on our frozen repository. And that's all. Install the packages, start Easy LTSP
26:42
and you have to configure at least the server IP address and ADX CP range. Those are the minimum requirements for Kiwi LTSP working. You can of course also add the packages you want to install. You can customize your configuration.
27:03
But that's the simple things you need to work. Once you did it, just press on OK. Easy LTSP will start the setup process, will start the TFTP server, the DX CP server and nothing else. You simply have to boot your thin clients from network maybe
27:21
or using CDs or USB sticks and whoa, you have now your thin clients working OpenSUSE with the educational software of course. Yeah, so I think this is the time where everyone can ask questions. No? OK, so, yeah.
27:48
I'm going to close here, sir. Hello, I'm Ziotov Gkompry, software in education. So you're talking a lot of the infrastructures that you built to deliver OpenSUSE
28:02
and you didn't talk a lot about the content itself. So where are we in terms of content? Are the teacher or the school can already find everything they need in OpenSUSE or in the free software community? Or do we still have some big miss in the application stack?
28:28
Yes, by the time, welcome Bruno. Yes, question about applications that are there or that are missing. It's not easy to answer because we have, as I told you already,
28:40
over 800 packages. Gkompry is one of the things PhysiCache or the other applications for small kids are also there. So if you like to compare the OpenSUSE release and other releases like Fedora or Debian, we are currently at the same stage.
29:00
So this is not the problem. The problem is that we need feedback from schools, from the users. That's the real reason that we have because we can package thousands of packages if nobody uses it or, better, nobody tells us which packages are useful.
29:22
It's not worth the work, at least. So for us it's really nice to see as HP starts and tells us, hey, here are 40 applications. We need those 40 applications.
29:40
That's when I start to ask, why? And HP tells us, yeah, we have marketing and marketing tells us that people want these 40 applications. That's why we want to work together with other parties because if you can get more information about what people outside need,
30:04
outside our developer brain, let's say so, we can just easily work for them. And if I told you in the beginning that we are trying to work for home users, every time I talk to people having kids at home,
30:21
they say, hey, yes, my kid want to get a PC, but I'm not sure if the Internet is the right thing for my kid. And that's where we should start thinking about why is this so and how can we solve this. And so in this process it's very important for us to get the feedback
30:43
out of the community, out of our users, and start adding those feature wishes to our bug seller to don't get them lost. So it's really important. Hopefully this is answering your question or?
31:01
So, yes, there are plans already for the next version. We are currently releasing open SUSE Education 1.0, which for us means at least we have all the packages that we think that are worth to have in our repository. The next version will be at least 1.1 or something like this,
31:22
having additional packages and the first applications developed especially for schools and for home users. So, for example, the Kivy LTSP is one of those. As we talk to teachers, they tell us, hey, terminal servers, wow, great, wonderful, but it's really difficult to set up and maintain it.
31:44
So we are going closer and said, okay, how can we reach this to make it easily to be installed by people not having the tech knowledge background. So they just should, well, at least take these three steps
32:00
and everything is up and running. So I really appreciate the Fedora success providing an USB stick where you can say, okay, put it in, boot it, and your terminal server is ready. Well, okay, that's the next step. Open SUSE will follow. But, yes, with such simply, simply systems,
32:24
it's really easy to reach the people outside and show them that it's really easy to use and that the packages that we have are also useful for them with the problems that people have tons of applications but no description.
32:43
And please talk with teachers. If they tell them, hey, it's a wonderful application. You can get your vocabularies learned automatically with a result at the end. They tell you, hey, where's the documentation in my language? And that's the main problem that we
33:00
and I think every other project has at the moment. My company does a lot of internal training, so it's not only for schools, I would say. And I'm an application engineer. Sometimes we do training on Linux, so we get the live CD and we can't store any of the results.
33:24
So that would be one of the key benefits of having a live CD that could directly connect to a server where you could generate automatically a home directory. So you could retrieve data. That would be a big benefit, I would say, if you had that type of function.
33:41
Okay, thank you. That's one of the features for our bugzilla. And it's not easy, not really complicated to implement because we have already such live ESOs you can put in. They're booting via PXE and don't touch your hard disk. So what we have to do is integrate that into the domain.
34:02
We also forget to say that we provided some months ago the first educational live CD, built using SUSE Studio, and allow you to try open SUSE education without installing stuff on your PCs.
34:25
What you also could consider is also instead of storing it on the server is that you boot from the live CD and then you have a USB key as your hard disk. That would also make life a lot easier.
34:45
Okay, I think Debian has a popularity contest which when you sign and you say, okay, use no afterwards, Debian will collect how many programs and which programs you used.
35:03
I think something could give you automatic feedback from your users. Just put it into the one-click install and add, okay, you may send it and you get information. One suggestion. The other one is, I'm from OLPC Switzerland.
35:20
Do you package also sugar on it? Yes, we have packages for sugar but they're currently in our development repository. We don't say they are ready for use. But you are working on it? You can test it if you want.
35:41
I have a question about your development model. Do you froze the build service repository? Is it the same thing we have in the frozen repositories?
36:02
So, if I look for an application on your build service, it would be the same version as in the frozen? Yeah, kind of. When we reach the frozen state, we disable building and sometimes also updating on the build service repository.
36:26
Then we go to download everything, real packages. All that one we consider stable enough. And then with the simple bash script that Lars wrote, we are able to resize everything.
36:40
They are simple. The same package coming from the build service for compatibility reasons. Sorry, because it must be built using the open source software repository and stuff like that. We simply download and resign adding on the frozen repository.
37:00
Then we go to recreate the whole repository structure using tools like CreateRepo. And the repository is ready for use, right? They should be the same. It's a really big pack, yes.
37:25
You're talking about open school server. I don't know exactly what it is. Does it operate with a school tool? The system that made Ubuntu to administrate a school laboratory or the school infrastructure?
37:41
And how could we work with the application? Because many schools don't have a login per user. Some have, some don't have. And they want any way to get, or they may be interested to have feedback from the application to the user to save the data in the user directory,
38:03
even if there is no login, because they don't want to. So there are a lot of questions around this. I don't know if you have some ideas or investigated or how can we work in this area. Well, currently we are working on a YAS model that should be able to manage writes on clients,
38:24
on students and teachers' PCs. And using Kiwi LTSP, you are also able to create one single user and allow login for everybody. Or also if your school is integrated into an active directory domain,
38:43
if you install an SSH server on your Windows server, you are also able to login in Kiwi LTSP using active directory accounts. So, one thing I have in mind, thinking about storing results of tests and so on for users
39:06
is something we already evaluated with the school server. We have two options at all. One option is to use the LDAP. So, what we have to do is patching each application
39:21
to allow using LDAP and to tell the developers how to patch so it works. Another option is to use a generic database backend. And that's something the KDE developers are already working on it with their KDE Edu applications.
39:42
But it's in a very, very early state. They are currently just talking about the API and so on. So, it's not really that kind of stuff that you currently can say outside users, they can use it. But there are discussions about this already, but not a real solution.
40:02
And I just want to wait until we have one or two solutions which can work before we start a more generic discussion with our people to get these things working for all applications, hopefully.
40:20
But it's in the discussion, yes. Do you think that this is usable for remote education? You have a server in Stockholm and you're running your training here.
40:44
Yes, absolutely. But depending on your bandwidth, that's the reason we have already in Germany. Germany schools have normally a free internet account, but this account is very, very limited in bandwidth. So, schools can download nearly everything,
41:03
but if people sitting at home and trying to reach the school server, they're sitting there and saying, hey, my modem is faster. So, at least I think theoretically it should be possible and I know already schools are working like this. I know at least one school in Germany have a 10 megabyte
41:23
or something like that bandwidth, and teachers working at home just connecting their web stuff to their home directories on the school server. So, yes, even that's possible, but it's a point-to-point decision.
41:45
Depends on your users. It's not really unique to say, okay, you need at least this bandwidth. Depending if you want to start with video editing or audio editing, don't try this.
42:01
But for the normal user trying to work with open office or something like that, it's really small bandwidth. It works. But transferring the whole application or making an X connection, something like this, it's sometimes kind of funny. But free and X and so on already works.
42:22
If there's another question, I think we can... Okay, can we have one question? Our time is up. Just a single one. A couple of years ago at the introduction of educational software, you mentioned that the software and the education part was written with the Spanish language and English language.
42:43
How easy is it at this day to translate it to other languages? That's the developer question. We're working on a web front end to translate at least the package description and so on. But translating the packages, the applications,
43:03
it's hopefully something we can do together with upstream. So every distribution will benefit of it. Okay, so if you have further questions, please contact us at the booth. We will be there at least until we go to sleep.
43:21
Thanks.
Recommendations
Series of 10 media