We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback
00:00

Formale Metadaten

Titel
AlekSIS
Serientitel
Anzahl der Teile
637
Autor
Mitwirkende
Lizenz
CC-Namensnennung 2.0 Belgien:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
As part of the schul-frei project of Teckids e.V. we curate free software and offer it to educational institutions. Besides the general equipment of schools with free software, an equal involvement of students in the development is for us important. One of the solutions presented by the project schul-frei is AlekSIS, a web-based school information system that is being developed jointly by Teckids e.V. and students of the Katharineum in Lübeck. The django-based platform provides data structures that can be used by separately developed apps. The special feature of this project compared to other information systems is that apps can be developed that cover specific application areas of a school. AlekSIS is a framework for apps that can be developed together with students in computer science classes, for example, because the development of such apps with python is easy to follow. Since AlekSIS is just a part of the free software curation, it can be excellently combined with other services or network accounts that are used in school. In our talk we will show, how this framework concretely looks like and how people can contribute to this project or use this system, for example at schools.
179
Vorschaubild
20:09
245
253
Vorschaubild
30:06
294
350
Vorschaubild
59:28
370
419
491
588
Vorschaubild
30:18
FontCodeComputeranimation
Physikalisches SystemSystemprogrammierungSoftwarewartungSoftwareCodierungstheorieCachingProjektive EbeneSoftwareDigitalisierungSystemtechnikVollständiger VerbandForcingSoftwarewartungComputeranimationProgramm/QuellcodeXML
Physikalisches SystemDatenbankSystemprogrammierungCachingFreewareOpen SourceSystemtechnikSoftwarePhysikalisches SystemProjektive EbeneTermProgramm/QuellcodeXML
Gradientt-TestSoftwareDatenverarbeitungssystemGebäude <Mathematik>MAPFokalpunktSoftwareGradientSoftwarewartungGebäude <Mathematik>FokalpunktNeuroinformatikProjektive Ebenet-TestSchreiben <Datenverarbeitung>DatenverwaltungTelekommunikationFamilie <Mathematik>JSONXML
Physikalisches SystemSelbst organisierendes SystemSoftwareDigitalisierungFreewareSoftwareentwicklerBildschirmfensterSelbst organisierendes SystemFreewareSoftwareTrennschärfe <Statistik>LernprogrammBridge <Kommunikationstechnik>Projektive EbeneSystemplattformMereologieDienst <Informatik>Anpassung <Mathematik>Natürliche ZahlZweiSpeicherabzugt-TestFlächeninhaltEigentliche AbbildungOffice-PaketComputeranimationProgramm/Quellcode
SoftwareOpen SourceRechter WinkelProjektive EbeneFeuchteleitungLokales MinimumTermForcingInklusion <Mathematik>Inverser LimesFlächeninhaltProgramm/QuellcodeXMLComputeranimation
Physikalisches SystemZoomSystemplattformGruppenkeimGruppenoperationSoftwareentwicklerProjektive EbeneDienst <Informatik>DifferenteFlächeninhaltGruppenoperationMAPÄußere Algebra eines ModulsTermEreignishorizontPunktForcingGüte der AnpassungKategorie <Mathematik>SystemplattformSummierbarkeitCASE <Informatik>SichtenkonzeptQuellcodeOpen SourceProxy ServerFunktionalInklusion <Mathematik>VirtualisierungZweiGesetz <Physik>SoftwareE-MailKlasse <Mathematik>AdressraumFreewareXML
LoginStrom <Mathematik>MIDI <Musikelektronik>Informationt-TestPhysikalischer EffektOffice-PaketStrömungsrichtungMenütechnikLoginBildgebendes VerfahrenMapping <Computergraphik>p-BlockMomentenproblemComputerspielPerspektiveWidgetTypentheorieXMLFlussdiagramm
TabelleGruppenoperationProgrammierumgebungEindringerkennungWurzel <Mathematik>Substitutiont-TestInformationAutomatische HandlungsplanungEreignishorizontSichtenkonzeptMenütechnikXML
VakuumSubstitutionSharewareUnendlichkeitFrequenzKlasse <Mathematik>RechenwerkRuhmasseExplosion <Stochastik>RückkopplungFAQBildschirmsymbolSoftwaretestGarbentheorieComputersicherheitAuthentifikationTeilbarkeitMereologieEreignishorizontSystem FARM <Computerarchitektur>SystemverwaltungInformationSoundverarbeitungWorkstation <Musikinstrument>Klasse <Mathematik>NeuroinformatikDifferenteIdeal <Mathematik>Weg <Topologie>MultiplikationsoperatorFokalpunktSubstitutionGefangenendilemmaFunktionalAutomatische HandlungsplanungBildschirmmaskeDatenverwaltungt-TestMenütechnikRückkopplungDateiformatNabel <Mathematik>Mailing-ListeEinfügungsdämpfungRechter WinkelIntegralAuthentifikationE-MailComputersicherheitPhysikalisches SystemAdressraumSichtenkonzeptTermPunktDigitalisierungStrömungsrichtungHauptidealÄhnlichkeitsgeometrieMathematikComputeranimation
Physikalisches SystemAbstraktionsebeneKlasse <Mathematik>SchnittmengeAbfrageDatenverwaltungSchnittmengeAbfrageFunktionalSoftwareentwicklerQuellcodeNeuroinformatikKlasse <Mathematik>App <Programm>MAPJSONXML
Physikalisches SystemFreewareModul <Datentyp>Prozess <Informatik>App <Programm>DigitalisierungKlasse <Mathematik>InformatikProzess <Informatik>GraphfärbungInternetworkingNeuroinformatikPhysikalisches SystemKlasse <Mathematik>ComputerspielAngewandte PhysikProjektive EbeneBitDatensatzProgrammierumgebungTermApp <Programm>SoftwareentwicklerModul <Datentyp>GruppenoperationHochschulinformationssystemSpeicherabzugCodierungt-TestKartesische KoordinatenXMLComputeranimation
Physikalisches SystemSpeicherabzugApp <Programm>RuhmasseBitSystemaufrufSoftwareMereologieComputeranimation
App <Programm>SpeicherabzugPhysikalisches SystemGeradeCASE <Informatik>AuswahlaxiomFrequenzMultiplikationsoperatorComputeranimation
App <Programm>SpeicherabzugPhysikalisches SystemTrägheitsmomentMultiplikationsoperatorFrequenzSoftwareComputeranimation
App <Programm>SpeicherabzugPhysikalisches SystemSoftwareComputeranimation
SpeicherabzugApp <Programm>Physikalisches SystemSoftwareProdukt <Mathematik>MathematikOffene MengeComputeranimation
App <Programm>SpeicherabzugPhysikalisches SystemAuswahlaxiomPunktBitBeweistheorieAusnahmebehandlungComputeranimation
App <Programm>SpeicherabzugPhysikalisches SystemBitTermQuick-SortSoftwaretestProdukt <Mathematik>SoftwareDienst <Informatik>Gesetz <Physik>AeroelastizitätWorkstation <Musikinstrument>Computeranimation
App <Programm>SpeicherabzugPhysikalisches SystemEnergiedichteGüte der AnpassungGesetz <Physik>Translation <Mathematik>Formale SpracheFlächeninhaltComputeranimation
SpeicherabzugApp <Programm>Physikalisches SystemFormale SpracheFlächeninhaltInhalt <Mathematik>Gruppenoperationt-TestComputeranimation
App <Programm>SpeicherabzugPhysikalisches SystemBitSoftwareMAPGüte der AnpassungKartesische KoordinatenComputeranimation
App <Programm>SpeicherabzugPhysikalisches SystemEnergiedichteGüte der AnpassungWeb-ApplikationMAPSoftwareSpannweite <Stochastik>NeuroinformatikMultiplikationsoperatorComputeranimation
App <Programm>SpeicherabzugPhysikalisches SystemOISCRPCComputeranimation
SpeicherabzugApp <Programm>Physikalisches SystemTermProdukt <Mathematik>Automatische HandlungsplanungProzess <Informatik>FreewareMathematikMixed RealityVollständiger VerbandSoftwareentwicklerKontinuumshypotheseProzess <Informatik>BitFeature Driven DevelopmentAutomatische HandlungsplanungJensen-MaßVerzweigendes ProgrammMathematikBetafunktionGrenzschichtablösungSoftwarewartungResultanteComputeranimationXML
Physikalisches SystemSystemplattformTelekommunikationInstantiierungSchnittmengeAggregatzustandFreewareSoftwareSystemplattformEinfach zusammenhängender RaumXML
Physikalisches SystemSpeicherabzugBetragsflächeExogene VariableRückkopplungPatch <Software>FreewareGerichtete MengeSummierbarkeitMagnetbandlaufwerkSpezialrechnerGüte der AnpassungFormation <Mathematik>Prozess <Informatik>SoftwareentwicklerInformationssystemInformationGruppenoperationt-TestKontinuumshypotheseJSONXMLProgramm/QuellcodeComputeranimation
Physikalisches SystemRückkopplungSpeicherabzugPatch <Software>Gerichtete MengeSummierbarkeitBetragsflächeExogene VariableMagnetbandlaufwerkTUNIS <Programm>SGMLSoftwareentwicklerComputerspielKartesische Koordinatent-TestMobiles InternetExogene VariableRegulärer GraphRückkopplungProgramm/QuellcodeXMLComputeranimation
RückkopplungPatch <Software>SpeicherabzugGerichtete MengeBetragsflächeSummierbarkeitExogene VariablePhysikalisches SystemMagnetbandlaufwerkTUNIS <Programm>App <Programm>RichtungSummierbarkeitKartesische KoordinatenKlasse <Mathematik>DigitalisierungProgramm/QuellcodeXMLComputeranimation
RückkopplungPatch <Software>SpeicherabzugGerichtete MengeSummierbarkeitBetragsflächeExogene VariablePhysikalisches SystemMagnetbandlaufwerkTUNIS <Programm>ProgrammierumgebungSGMLMereologieSoftwareentwicklerExogene VariableProgrammfehlerRichtungProgramm/QuellcodeXMLComputeranimation
Physikalisches SystemRückkopplungSpeicherabzugPatch <Software>Gerichtete MengeSummierbarkeitBetragsflächeExogene VariableMagnetbandlaufwerkSGMLFreewaret-TestCASE <Informatik>Patch <Software>Web SiteSummierbarkeitQuaderFigurierte ZahlProgramm/QuellcodeXMLComputeranimation
Physikalisches SystemRückkopplungSpeicherabzugPatch <Software>Gerichtete MengeBetragsflächeSummierbarkeitExogene VariableMagnetbandlaufwerkTUNIS <Programm>Freewaret-TestLateinisches QuadratTranslation <Mathematik>Programm/QuellcodeXMLComputeranimation
Physikalisches SystemMagnetbandlaufwerkRückkopplungPatch <Software>SpeicherabzugGerichtete MengeSummierbarkeitBetragsflächeExogene VariableChi-Quadrat-VerteilungProzess <Informatik>SystemplattformGüte der AnpassungGruppenoperationKartesische KoordinatenTranslation <Mathematik>Klasse <Mathematik>Offene MengeProjektive EbeneOpen SourceProzess <Informatik>NeuroinformatikSoftwareentwicklerForcingDigitale PhotographieSoftwareSystemplattformProgramm/QuellcodeXMLComputeranimation
Physikalisches SystemMatrizenrechnungWeb SiteKonfiguration <Informatik>E-MailFreewareE-MailProjektive EbeneGarbentheorieJSONXMLComputeranimation
Web SiteE-MailKonfiguration <Informatik>Physikalisches SystemElement <Gruppentheorie>Chatten <Kommunikation>Computeranimation
Computeranimation
Element <Gruppentheorie>Computeranimation
Transkript: Englisch(automatisch erzeugt)
Hello everyone and welcome to our talk about digitization and education, how the Alexis project fosters co-creation of school software by young people.
My name is Tom, I am a 16 years old apprentice systems engineer from Germany. In my free time, I am a systems engineer and software maintainer at the TechEtsifau and I like coding and DevOps or traveling to force conferences.
Hi, my name is Dominik and I am chairperson of TechEtsifau. I am accompanying Tom today and my goal with TechEts is to really get young people into free software and getting them to contribute.
I am a systems engineer at Kritativ GmbH, which is a German company who has committed to really high quality open source support for business. One of my hobbies is traveling open source conferences, helping young people present, running booths for free software and education and
also giving talks about what to expect and what to care about when trying to help young people contribute to projects. Hello, my name is Jonathan and I am one of the maintainers of the Alexis project.
I am 17 years old and from a city in the very north of Germany, Lübeck. I am a student in the 11th grade at the Catarina of Lübeck High School. My personal interests are primarily in software development, of course, building
things with computers and electronics, like with an ESP or an Arduino. As a third thing, in-stage technology with a focus on lightning.
Dominik and I are both members of the TechEtsifau, the probably only free software youth organization in Germany. The goal is to set up a free software community for children and youth. To reach this goal, we provide educational organizations with readily available free software, both as community-driven software as a service platform and individually hosted.
The core principle is children and youth are involved in all parts of our work, both in technical and organizational areas, to make being a contributor second nature to them. We are also contributing to free educational software such as Alexis or Debe and Edu. One of the free public projects of TechEts is called Schulfrei, which is
an idiomatic pun of school and free, translated as off-school in proper English. The Schulfrei selection currently includes free educational software like Moodle, Nextcloud, BigBlueButton, Alexis and Debe and Edu. Schulfrei's goal is to create a bridge between teachers, developers, students and companies. Schulfrei provides many opportunities for adaptation and participation, so please feel free to participate.
Force projects should include everyone. Everyone means every person who wants to contribute to open source affairs, so children and youth are also included in everyone. Typical barriers are for example terms of use if they limit the user's rights because they are not legally acceptable by children.
So please keep barriers to your minimum. Choose a free and non-discriminating license and make sure that your terms of use are illegally acceptable for children. It is important to understand that young users are also contributors. Most of them are passive
contributors, that means that they use the software, give feedback, they are making and sharing experiences. So young users are an important target group. Some young persons are also active contributors. They are developing their own software or contributing to the software they are using.
One example for very young active contributors, during the TechEd workshops, children as young as 10 years are patching tools they are using in their workshops. Non-free and in the worst case discriminatory platforms are very widespreadly used in free software development.
Unfortunately many projects do not pay so much attention to the terms of service of the tools they use, but this is a critical starting point to really get everyone included in development and in contribution to the project.
For example, GitHub is the most widespread platform for source code hosting and collaborative development. Also there is GitLab.com as an alternative and Bitbucket and some other platforms. All of them share the property that they discriminate against young people.
They have some legal reasons to do that, because for example under US legislation there is the copper law which forces them to restrict access to under 13 year olds under some circumstances. These circumstances are somewhat based on other terms these services have in their legal texts.
So what can happen here is that there are some people, not only young people, who cannot use these services.
They are basically excluded, or even if they aren't excluded, they are turned into second class citizens. This is, they maybe can contribute by using a proxy, by getting another person to post an issue in their name. Or they can use another channel, they can find some private email address
of one of the developers and send them their opinion or question or contribution. But they are not on the same level as other contributors. So at the very least, every project, be it for development, for discussion or as a technology conference, need to find ways how to get everyone included.
For example, a technology conference will do almost everything for a venue where people get for in person events. They will do everything to not log out like wheelchair users.
And even for people who have certain views, like vegetarians, they will have alternatives for lunch maybe. And it's very important to also carry this idea into the virtual world, into virtual venues, into software development, into discussion. But the groups of people that are excluded in this area are different.
For example, children and young people. So for development, for discussion, use, if you can, use at least one channel that is accessible to everyone. If you can make it the only channel, this is ideal. If you cannot make it the only channel, there should be an alternative that can really, really be used by everyone.
If accessibility for every group of people is ensured, then the next step is how we can design projects that are easy to contribute to and that are easy to contribute to for people that are still under education.
Now I would like you to show how Alexis looks like in life from the perspective of a normal student. First of all, each member of the school society has to log in with his or her credentials.
We will do this for Max Musterman. After a normal student logged in, first of all he sees his personal dashboard. We have three types of dashboard widgets. For example, in this dashboard, on
the very left side, that's a dashboard widget who shows you upcoming events. In the middle, that's a dashboard widget, which is showing news from SV, here from the V Software Foundation.
And on the right side, they are showing the current timetable for today or tomorrow and for tomorrow if it's on the weekend. So a student can see all relevant information directly after the login. On the left side, you can see the menu with three important menu items I would like to show you.
First of all, we have the menu item timetables. If a student clicks on my timetable, he sees his timetable like on the dashboard, which is current for today.
This means that substitutions and extra lessons and events and exams and so on are directly included in this plan.
So the student can find all information directly in one view. Then there is a menu item which shows all plans that are available on this alexis instance.
So a student can log if a room is free or wears a teacher so he can speak with the teacher. For example, if I click on this room, there is a full plan for this week of this room.
And also in this plan, substitutions, room changes and similar things are directly included. So the students and the teachers don't have to look in an extra list or combine information from different data sources.
Also, you can go through the weeks using these buttons. For example, now you can see that there were holidays in this week, so there are no lessons. So if we go again to the left side, there is a third point in the timetable menu.
This shows substitutions if there are some substitutions. On this day, there are no substitutions in our demo system. Then as the next important point, we have the digital class register called ICG.
And there is a button which shows the current lesson. There is a button which shows the current week, for example. And if you click on one of these lessons, a student can see all information that were written down in this lesson.
For example, if a teacher writes the homework or the lesson topic in the digital class register, every student can see that. And if a student is at home, he also can see this information and is up to date with the students who were in school.
Then a very important view for students is my overview.
In my overview, students can see directly if they have some unexcused absences. They can see when they were not in school, how many days they already were missing in this school term.
And they also can see if they forgot their homework or excuse for some particular reason. So this shows how customizable ICG is. You can set your own excuse types, you can set your own extra marks like homework forgotten or off.
And as a third app, I would like to show you the integrated support system
which can be used by schools to manage their IT infrastructure and get feedback about Alexis. As a first point, there is a view to report an issue to the school system administration.
For example, if there is a school computer which has problems or there are some other problems with the school network, students and teachers can directly write an issue in this form. So the system administration gets directly feedback.
As a second view, we have a feedback view for Alexis that students and teachers and other members of the school society can give us feedback about Alexis and we can improve things in Alexis.
So it's easier for everyone to work with Alexis. As a third point, we have an FAQ view which can be dynamically
filled by the school system administration or also by the school administration in general. So the principal or other members of the school administration can write questions and answers. So maybe all questions who could be asked can handle it directly here.
If the question is not in this list, you also can go and ask your question and then the question is directly emailed to a pre-set email address set in the preferences of Alexis.
Then for security reasons, of course, there is the ability to activate two -factor authentication and also each student, each teacher can make some own preferences.
For example, he wants that his name is addressed or on the channel he wants to be notified or some special preferences for the timetable.
At Alexis, we are trying to use best practices everywhere we can because we want Alexis to be a textbook example in school so that computer classes can learn with Alexis source code. We are using very complex and complicated things like query sets or managers to manage Alexis data, but these functions are mostly well documented and generally reusable.
With these functions, it is very easy to develop own apps and manage Alexis data. As we already explained, Alexis uses an app-like modularity system provided by the
Alexis core and features of the school information system can be added by installing apps. Apps are basically what they are, they are Django applications with a bit of glue around them that makes them compatible with the Alexis ecosystem.
The idea is that real-world processes are encapsulated into separate apps. When a school has one process they want to digitize, like lending schoolbooks to students at the beginning
of the school term, then we call this a process and this process can be turned into an app. This can either be done by the Alexis development team, by some professional software developer or even by a computer or coding class inside the school. This is actually what we want to see happen, we want coding classes to create something that is used in the
real environment that provides benefit for the real world, that provides value they can see in their day-to-day life. So they do not only learn for throwaway projects in their computer science classes, but they
really can turn the learning efforts into something that they know what it is good for. Licensing of Alexis is another topic that needs a bit of thought to make it easy for young people and a broad mass of people to contribute.
All these legal issues around software licensing, about contribution agreements and the like are somewhat difficult, in parts maybe even more difficult than the technical aspects of contributing to software. Some licenses are really short, they can be read easily like the MIT license or the BSD licenses and
there are other licenses that are quite longish and contain a lot of corner cases and explanations like the GPL. This is one aspect, so the natural choice here would be a short license that can
be read and explained in a short period of time to new contributors and especially young contributors. But these short licenses normally don't provide much protection. Now, as a person who really likes openness, who really wants to foster open software, I
tend to use the MIT license because I want to give the most freedom I can. Sometimes I play with the thought of using a copyleft license to ensure that software will stay open and I can understand that people find this important too.
And when I work with young people or when we work with young people at TechEd, we also tend to use copyleft licenses because we think that it is easier for the young people to understand what the consequences of opening the software are.
If they know that others will have to keep the software open and cannot just take the work they do into a commercial product without caring about keeping the software open or providing changes back to the community. The choice we made at some point was to use the EUPL, which is the European Union Public License.
It's a bit special because it is not that widely adapted, but it is an OSI-approved license and the Free Software Foundation has approved it. It resembles the GPL a bit with aspects of both the LGPL and the AGPL.
So it has terms about running software as a service and it also has terms about linking with products under other licenses. So it offers both good protection for users and contributors, especially within the EU because it is somewhat bundled with EU copyright law.
But it is also workable for legislations outside the EU. One special thing about the EUPL is that it has official translations into all EU languages.
So there is an official license text in every language we encounter in the EU, including English of course, which makes it understandable in more areas of the world. But for, let's say, a Spanish group of students who have already enough to do understanding the content of the license,
we can remove the need to understand the legal English text and we can provide them with a Spanish text because this license is actually made for citizens, not only for lawyers.
The SAIS protection is a bit easier to implement in practice than with the AGPL. I do not want to discuss this in detail here. But in general, we get a good level of protection for web applications while also keeping
the software quite open and above all the legal stuff understandable by a wide range of contributors. Also, it clearly has the place of jurisdiction in the license, which is important because we do not want
to impose the danger of having any legal stuff to do in very remote places if anything should ever happen.
Because the Alexis team is geographically a bit pulled apart, our development process is based on a mix of scrum and feature-driven development. That means that we have two week sprints with a review and planning meeting with a team at the Catarhenium every second Friday. We are working with milestones for every release and also for alpha or beta releases.
Everything is committed to separate branches per issue. If the work on an issue is done, a merge request will be created and the changes will be reviewed by one of our maintainers and the dev meeting and if everything is okay, it will be merged into the master branch.
Alexis is represented by the deputy headmaster of the Catarhenium and the chairperson of TechEds. If you are developing software, we would ask you to use free platforms that can be used by everyone regardless of their age or anything else. For example, you can use our own self-hosted GitLab instance, EdoGit, to
develop your software and the connected BigBlueButton instance and MeasureMouse to communicate with others. You also can use our plate instance to translate your software. Now that we describe the general development process of Alexis, the school information system, let's look at the most important school in this process, the Catarhenium in Lübeck.
Alexis is mainly developed by a group of students and one teacher at the Catarhenium, together with one other student and a professional software developer from TechEds. And they have established the development of this application somewhat in their general all-day school life.
There is regular feedback from teachers and students, normally very positive feedback. They say that the application is fast and clean, that they like the responsive and mobile-friendly design. And that they can send direct support requests through the Yelp app at
the digital class register called Alcigil, which is Arabic for the class register. It has features they really like and they couldn't have gotten that easily in commercial applications, like automatic summation of absent hours and such things.
They also think that they really benefit from the development team being part of their school as well, because they get prompt response to bugs and feature requests. They can have a chat with the young developers, they can exchange discussion directly.
And they know that both the teacher who helps developing Alexis and the students use it from day to day and they really know what's going on and they really understand what the use cases and the user stories are.
And there are also some patches from students outside the core team. Sometimes there are minor bugs, be it as simple as typos, that are fixed by some student who does not regularly contribute to Alexis.
They have some students that contribute translations, they have a team that cares about a Latin translation even, which is maybe not that important in practice, but is another good example of how developing such an application can be a benefit for learners.
And for the more practical languages, they also have a group that helps translate Alexis into French. If you plan to contribute to free software in education, the most important thing is to adapt an open, minor-friendly development process and to use open platforms which everyone can use.
Please make sure your software can be used by computer classes to learn with it and contribute to it. Don't be afraid of young users or contributors in the open source communities. If possible, it would be very helpful if you donate to the TkTzefau to foster educational FOSS projects and children as users and contributors.
So thank you for listening our talk. If there are any questions, please ask them in the Q&A section, which is directly after the talk. You are invited to visit the project's websites. If you want to help or connect, please contact us via email to foss at tkts.org.
To chat with others about Schulfrai, you can use the Schulfrai chat feature.
Are you finding it useful in this project? Or something that you couldn't have done without using Python?
That's a good question. I think it's not a specific feature.