Session schedule

Time Room Session title Speaker Language
11:00 G3 Agentic AI in Moodle Peter Mayer EN
12:00 G3 Moving to Moodle assignment at the OU UK Tim Hunt EN
11:00 H2.1 Monitoring Moodle Melanie Treitinger, Malte Schmitz EN
12:00 H2.1 Moodle meets Peertube Mareike Scheffe & Vadym Nersesov EN
12:00 H8.1 Vom Data Hoarding zu Green Moodle Lilia Grodde DE
11:00 H8.1 Workflow-based User Lifecycle Management for Moodle Niels Gandraß, @ngandrass EN
11:00 J3 A New Visual Courseformat Tobias Garske, Dunja Spechner DE & EN
12:00 J3 AG E-Assesment bei MaH gemeinsam gestalten AG eAssesment, Anton Tremetzberger DE
12:00 J4 Badges statt Anwesenheitslisten Stephan Robotta & Christine Lent DE & EN
11:00 J4 Practical Accessibility – find the barrier Gavin Henrick EN
11:00 J6 MDLShield – Expert: Moodle plugin security reviews Alexander Bias DE & EN
12:00 J6 The Future of Javascript in User Created Content within Moodle Andrew Hancox EN
11:00 J7 Knowledge Base: Was hilft am meisten? Klaus Steitz DE
12:00 J7 Moodle Marketplace Alternatives Petr Skoda EN
14:00 G3 More Than Words Júlia Verdaguer EN
14:00 H2.1 Using Mchef to manage development prospects Guy Thomas EN
14:00 H8.1 Guidance - Assisting teachers with course creation Stefan Scholz EN
14:00 J3 What's new in STACK Andreas Steiger EN
14:00 J4 AI Assistant Activity Martin Hanusch, Sophie Zimmermann EN
14:00 J6 Boost Union - hot new stuff Kathleen, Alex, Luca EN
14:00 J7 Adaptives Lernen in Moodle – für alle nutzbar Behsad Vahidi DE
15:00 G3 BBB & Moodle – Next Level Gerhard Schwed DE
15:00 H2.1 AI as a media acitivity with OpenWebUI Dennis DE
15:00 H8.1 Oncampus Goes Open Source Marius Rosenbaum, Joscha Sauerland DE & EN
15:00 J3 Let's feed the Moodle Tracker Laurent David EN
15:00 J4 Moodle UX Optimierung Andreas Hruska DE
15:00 J6 Boost Union, supercharged – Make it Your Moodle Stefan Scholz EN
15:00 J7 SEB Server Tutorat sourire Christine Lent DE & EN
16:00 G3 Start Over Again Martin Dougiamas EN

Documentation

Agentic AI in Moodle

Speaker: Peter Mayer
Language: EN
Room: G3
Time: 11:00
Session documentation
Moodle for Bavarian schools
1.6 million learners 175,000 teachers, 6000 tenants.

7 developers (including Peter)

Documentation
Bavarian cloud for schools, BYCS, does not utilize the subsstem ai, because of technical und legal requirements 

Agentic AI
* Multi-step tasks
* Recognises Complex tasks
* Respects user roles (student/teacher)
* Operates withing the platforms structures and processes

Defeault AI tools
* Missing context
* Lack of GDPR
* Bad UI/UX
* Cannot perform actions

Hence deeply interated is required.

We need to provide the AI with the best possible context.

So, Next step: RAG - with amdin and teacher control.
Work-in-progress. Worked on during DevCamp.

Step 3: AI Tool-Agent - Launch key funcitons directly from the chat - including automatically.
E.g. creating activities or even courses - but not one-shot. Needs to be iterative between the teacher and AI.
1. Create course ouline and/or individual activities.
2. Sequences of tasks.
3. (but perhaps not) entire courses.

Demo - creating a page about Einstein in Bern.

Behind the scenes using Moodle web services

Discussion of GDPR requirement and how that informs the design

Why AI tools for teachers to create 20th century courses - because that is where some fo them are right now - we need to take them on a journey, but starting from where they are.

Comment: While technology lets us improve how education is delivered - there are fundamentals about learning that do not change: it is about what happens in the student's brain, and how we promote that.

Back to top

Moving to Moodle assignment at the OU UK

Speaker: Tim Hunt
Language: EN
Room: G3
Time: 12:00
Session documentation
[A big thank-you to the person who took these notes of my talk. You did a really good job  -- TIm.]

Open University developed a bespoke e-assessment tool in 2003.
Started using Moodle in 2006
First use of Moodle assignment in 2025

150,000 students, 750,000 assignments a year

Phase 1: Moved student submissions first to Moodle, through integrations marking still happened in old system, then another integration moved feedback from old system to Moodle.
Phase 2: Moved marking to Moodle
Phase 3: Move back-office tasks??

OU submission page customised - modified instruction page, allow students to save as draft or submit, students agree to two statements.

Extension screens for students to request extensions, explain reasons, and staff to action.

Feedback page - moved feedback to the top of the page, Moodle assignment shows submission information at the top but students want their feedback first.
Display feedback on page, Moodle assignment shows feedback in a table.

Marking app
- ElectronJS framework
Desktop app
Works with Moodle Mobile app
Connects to Moodle

Dashboard page for markers with the submissions to mark.
Click into assignment to see submissions, and can download and upload feedback.

Simplifies user journey, allows markers to mark offline easily without going through Moodle. It works as an alternative UI in front of Moodle, tailored to OU staff marking practice.

Plugin that creates a fake group of student submissions so markers can practice using the marking app.

Approach taken to move from old to new system is based on https://en.wikipedia.org/wiki/Strangler_fig_pattern

Back to top

Monitoring Moodle

Speaker: Melanie Treitinger, Malte Schmitz
Language: EN
Room: H2.1
Time: 11:00
Session documentation
Slides: https://data.mlte.de/2026-06-02-moodle-moot-dach-tool_monitoring.pdf

DevCamp of Moodle Moot DACH 2025

Winning plugin from last year devcamp, see Link (please provide the link here 😉 Thanks!)
https://moodlemootdach.org/mod/forum/discuss.php?d=7086 
https://github.com/daniil-berg/moodle-tool_monitoring

What can we monitor: Usage of e.g. plugins, performance statistics

Public plugin released: 
    https://github.com/daniil-berg/moodle-tool_monitoring with detailled README
    Once in Moodle Plugins Directory it will be https://moodle.org/plugins/tool_monitoring (or Moodle Plugins Marketplace might exist at some future point in time)

Customizable, so you can choose which metrics you want to monitor
You can also add custom metrics by implementing a hook in a local plugin or any other plugin.

Exporter for Prometheus, which is a time series database, is delivered with the plugin.
Other exporters can be added as subplugins.

Token authentification for the API manually 


Questions:

Disabling a metric means it is not queried. You can also use tags to filter queries.

Is there a mechanism to not respond when there is a query still running? That is not possible right now, because the query is just a HTTP Request. Suggestion from Travis: do as little computation on the server and do that somehwere else.

Caching: is not implemented by design because that is done by Prometheus (query them as often as you need by tags). Implementing a scheduled task to query these values may alleviate loads. Essentially creating a cache of the data. Still querable and cacheable via Prometheus. We did something similar with our Sentinel plugin.

Fetching from a replica database? Needs implementation of another database connector.

Prometheus is querying all enabled metrics at once (filtered by tags). The metrics are called sequentially.

How to add more metrics to the system?
You can add the hook to any plugin and implement the metric.
You can also create one local plugin and add multiple metrics there.

Example plugin: https://github.com/melanietreitinger/moodle-block_foobar

Suggestion: collect community metrics and provide them at a central place.

Suggestion: Integrate Moodle Checks Subsystem (system and env checks)



---
Serhat:
Monitoring CPU load correlation with events on Moodle.
Prometheus https://en.wikipedia.org/wiki/Prometheus_(software) https://github.com/prometheus/prometheus endpoint.
Trying to create a generic exporter for other monitoring tools in the future.
 
 Is that basically a graphical interface in Moodle like Grafana https://en.wikipedia.org/wiki/Grafana https://github.com/grafana/grafana?
 
---

Back to top

Moodle meets Peertube

Speaker: Mareike Scheffe & Vadym Nersesov
Language: EN
Room: H2.1
Time: 12:00
Session documentation
An alternative to big tech video platforms, developed by french non-profit Framasoft.
lern.link hosts it with a partner that knows the In's and Out's of the product (Peertube is not easy to get and host out-of-the-box, if you're a newbie)

Advantages/USPs

Fediverse integrated

Peer-to-Peer concept, decentralized

If a video is going viral other servers kick in and share resources. So it's not only you, but everyone on the network hosting a peertube server.

Usually videos are too large for direct hosting on Moodle. It also doesn't support buffering and serving different resolutions device-based. Moodle just serves them as files. > Peertube might become the relevant "helper"?

Challenges
Missing Moodle integration (lern.link prototyped a first version of a plugin which need more work)
Need to protect specific, private videos vs. peer-to-peer concept
User onboarding

Is it worth the invest? What features are required to make it usable?
- General feedback: Yes, please continue with this work. 
- Good use case for the Fediverse integration of Moodle (DevCamp topic)
- Ideal solution: Full Moodle integration, a teacher never has to leave Moodle to work with their videos
- Protection solutions for links and critical data necessary
- "It needs to be a Moodle plugin."

Back to top

Vom Data Hoarding zu Green Moodle

Speaker: Lilia Grodde
Language: DE
Room: H8.1
Time: 12:00
Session documentation

Back to top

Workflow-based User Lifecycle Management for Moodle

Speaker: Niels Gandraß, @ngandrass
Language: EN
Room: H8.1
Time: 11:00
Session documentation
(https://gandrass.de)

Back to top

A New Visual Courseformat

Speaker: Tobias Garske, Dunja Spechner
Language: DE & EN
Room: J3
Time: 11:00
Session documentation 11:00

Session Title: A New Visual Courseformat


Session Presenter:
-  Dunja Spechner
- Tobias Garske

Documentation

Back to top

AG E-Assesment bei MaH gemeinsam gestalten

Speaker: AG eAssesment, Anton Tremetzberger
Language: DE
Room: J3
Time: 12:00
Session documentation
Login (Ersteinstieg):
https://forum.moodle-an-hochschulende 
  1. Auf Profilbild klicken
  2. „Einstellungen“ im Drop-Down-Menü wählen.
  3. AG E-Assessment auswählen.
  4. Speichern.
Kurs: AG E-Assessment in Moodle

Leitungsteam:
  • Antonia Bonaccorso (ETH Zürich)
  • Christine Lent (Berner Fachhochschule)
  • Anton Tremetzberger (FH Oberösterreich)
  • Maria Dorfer (TU Wien)
  • Pascal Fischer (Uni Kassel)
  • Julia Lee (FH Potsdam)

Zielsetzung & How-to-Forum: https://forum.moodle-an-hochschulen.de/course/view.php?id=26
  • Fragen in den Foren zum E-Assessment mit Moodle sind jederzeit herzlich willkommen. 
  • Der Sinn der Foren ist es, gemeinsam Wissen in der Community zu spezifischen Themen zu teilen.
  • Verschiedene Foren zu Themengebieten
-->Wichtig: wir tauschen uns gemeinsam als Community zu Themen aus, kein 1:1 Support durch Leitungsteam

AG organisiert 2 Präsenztreffen pro Jahr: MoodleMoot DACH & Moodle-an-Hochschulen-Treffen
MaH-Treffen: Harte Nüsse / begrenzt auf 20 Personen / vor dem Treffen/ Diskussion in Themengruppen/ Dauer: ca. 1 1/2 - 2 Stunden

Diskussion im Plenum: 
  • Kompetenzorientiertes Prüfen mit formativem Prüfen --> in der Praxis auch kompetenzorientiertes Prüfen mit summativem Prüfen
  • Separate Prüfungsplattform - dzt viele Personen im Raum, die es bereits nutzen; ein paar Hochschulen überlegen die Nutzung 
  • Nicht zu viele Foren - als Neuling oft Überblick schwierig; eher weniger & Forenbeiträge sinnvoll benennen & Tags benennen
    • nachträglich Tag-Lexikon, macht Kurs flexibler, wenn sich Themen ändern
  • Foren an Bedürfnissen ausrichten: 
    • alles in einem Forum wird schnell unübersichtlich
    • Vorschlag = Technisch-administrativ, Prüfungsorganisation, Methodik, Recht
  • altes SIG Forum nur mehr readable --> hier bitte nachschauen, ob es zum Thema bereits einen Beitrag gibt; wird nicht im neuen Kurs transferiert
  • Themen werden nicht vom Leitungsteam gebracht, sondern sollen von der Community kommen: Welche Themen interessieren euch momentan brennend? Was sind eure harten Nüsse?
    • Prüfungmoodle-Plattforum (Aufbau & laufender Betrieb - Was ist zu beachten? Good practices/ Erfahrungen) - Gergely (TU Wien)
    • Self-Assessment-Plattform für Aufnahmeverfahren (Aufbau & laufender Betrieb) - Franz (Uni Graz)
    • Betrugsversuche mit KI oder "begleitenden Prüfungen" (zugekaufte Leistungen von Anbietern) digital bzw. analog --> teilweise auch Zeugnisfälschung bei Aufnahmeverfahren
      • Vorgeschlagene Lösung: 
        • Abnahme von technischen Hilfsmitteln vor der Prüfung
        • kompetenzorientiertes Prüfen
        • abgesichertes WLAN (Prüfung nur darüber erreichbar) & Geräte vor Ort im abgesicherten Modus
    • Integration von Prüfungssoftware von Moodle (Austausch)
    • Idee Default-Prüfungsplattform zum leichteren Umstieg
      • Austausch von Einstellungen --> aber Achtung bzgl. Veröffentlichung (Schummelversuche werden erleichtert)
      • Termin für Austausch zu Prüfungsplattform - September 2026 --> siehe Umfrage im Forum https://forum.moodle-an-hochschulen.de/mod/forum/discuss.php?d=122
        • nächster Termin zu Einstellungen (wird von Maria organisiert, da keine Meldung aus Plenum)
    • Abgesicherte Prüfungseinsicht bei Open-Book-Szenarien & fehlender Chancengleichheit durch PDF-Kopien alter Prüfungen
    • Mit KI chancengerecht prüfen & didaktische Szenarien/ Prüfungsformen (nicht nur über Moodle, sondern auch z.B. mündlich, Problematik Kohortengröße, Ressourcen, rechtliche Rahmenbedingungen...)

Back to top

Badges statt Anwesenheitslisten

Speaker: Stephan Robotta & Christine Lent
Language: DE & EN
Room: J4
Time: 12:00
Session documentation
Plugin: https://moodle.org/plugins/view.php?id=4145
Extensive documentation of the CSV as well as templates for LibreOffice at: https://github.com/srobotta/moodle-local_attendance
Slides: https://moodlemootdach.org/pluginfile.php/48050/mod_forum/attachment/8091/MoodleMootDACH26_Badges_v2_EN.pdf?forcedownload=1

Documentation:
  • Attendance Course Creator Plugin: (Link wird nachgereicht)
  • Github: (wird nachgereicht)
  • benefits for teachers
    • no manual attendance tracking
  • benefits for admins
    • confirmation is generated automatically
  • quizzes sind nur 2 min offen, in der Hoffnung, dass das reicht,
  •  um das Passwort nicht per Messenger zu verschicken
    • + Appell, dass IP-ranges etc. eingeführt werden, wenn Missbrauch festgestellt wird
  • templates besser, damit die Original-Datei nicht überschrieben werden kann
  • Lehrende füllen Excel-Vorlage aus und speichern sie als csv ab und schicken sie an die Admins (kein Mehraufwand, da diese Infos bisher auf Papier festgehalten werden mussten)
  • die tatsächliche Einbindung findet dann durch das Technikpersonal statt
  • es entsteht ein Link in den separaten Anwesenheitskurs
    • da mit dem Kursabschluss arbeitet, wird ein zweiter Kurs erstellt, da sonst in dem Hauptkurs kein Abschlusstest stattfinden könnte
    • dieser zweite Kurs wird aber komplett automatisiert erstellt mit jeweils einem Test pro Anwesenheitstermin
      • zum Zugang wird ein Passwort benötigt und dort ist dann immer nur eine Frage hinterlegt (Anwesend ja/nein)
      • lässt sich theoretisch didaktisch nutzen, anstatt der einfachen Fragen, inhaltliche Fragen zu dem Termin
    • Quiz läuft 1min
    • Quiz wird von den Lehrenden geschlossen
  • Vorteile gegenüber dem attendency plugin
    • lässt sich viel fein-granularer einstellen
    • durch den separaten Anwesenheitskurs lassen sich auch Szenarien über mehrere Haupt-Kurse hinweg ermöglicht
  • Externe Referenten, die keinen Zugriff auf Moodle haben, haben verhindert, dass eine Datenbank-Aktivität innerhalb von Moodle genutzt wurde, daher bisher Excel
  • andere Herangehensweisen aus der Runde:
    • Vorwissen vor den Terminen abfragen
  • Thema Microcredentials / Badges / Open Badges


Feedback:
Nick (TH-Augsburg): wir haben eine andere, viel hemdsärmeligere (manuelle, aufwendig für Lehrende) Lösung für Anwesenheit: https://www.tha.de/Anwesenheitsliste.html Eure ist wesentlich elaborierter! Gut gemacht!

Back to top

Practical Accessibility – find the barrier

Speaker: Gavin Henrick
Language: EN
Room: J4
Time: 11:00
Session documentation

  • Accessibility Self Assessment.
  • Accessibility Cards.  (Empathy training: )
  • Accessibility Zines.
  • Accessibility Cubes. 
  • Tip Cube Framework Slides.

Back to top

MDLShield – Expert: Moodle plugin security reviews

Speaker: Alexander Bias
Language: DE & EN
Room: J6
Time: 11:00
Session documentation
Slides
https://share.ssystems.de/s/5FkFdXoYWqX6eSQ

Documentation
MDLShield is a commercial service by LMScloud Ltd., Marina Glancy, not affiliated with Moodle HQ
MDLShield is an AI code review that knows the whole Moodle core and the best practices
It is part of Anthropic Cyber Verification Program, https://support.claude.com/en/articles/14604842-real-time-cyber-safeguards-on-claude-opus-and-sonnet

Moodle plugins have to adhere the same security guidelines and best practices as Moodle core.

MDLShield helps you to find and fix vulnerabilities of plugins you developed with suggested fixes.

The audit doesn't stop at security, but also checks for best practices and quality.

Planned features
  • Release monitoring with automated triggers for reviews
  • Automated pull request with fixes
  • A summary function with a score that doesn't reveal issues, just an overall score for advertisement.

Pricing: Free credits
Intended for verified open source community plugins
2 AI reviews per month for free (Scan, Fix, Re-Scan, Publish an A-rated plugin) for non commercial, published  community plugins

Pricing: Paid credits
Intended for anyone. developer or vendor, commercial or non commercial. open or closed source.
25$ / review, use MOOTDACH26 promo code for 50% discount (valid until July 4th)

Developer decides if and when the report results are published, for example after fixing found issues
Publishing reports (hopefully) increases trust in the plugin
Published reviews earn a graded badge developers can use to show off their results (earning trust)

Assumption of value: Anthropic Cyber Verification Program

Scanning a private plugin with the "bring your own device" service works with any git server/provider

With the "bring your own device" service there's no 100% security against bad guys handing in your code/repository for checking. But there's some control by Marina who knows a lot of maintainers - Community plugins require ownership verification to be reviewed, external git repositories are gated by paid credits and unpublishable. Any obvious signs from bad actors will be dealt with by staff.

No false-positive flagging available right now - false positive and review annotation exists, and will be coming in the near future.

Q: Are there many flaws found that aren't found by e.g. linters? We shouldn't lose our security to AI.
It shall not replace every other tool, Alexander Bias is using Moodle Plugin CI and this tool only after.
A: Yes, most community plugins are using linters and many review results surface flaws in both security and coding aspects. MDL Shield does not intend to replace linters or existing developer tooling, but compliment them.

Back to top

The Future of Javascript in User Created Content within Moodle

Speaker: Andrew Hancox
Language: EN
Room: J6
Time: 12:00
Session documentation
Flexibility vs. security. What is HQs position on this?

What do we do, if JavaScript exploits are posted publicly, i.e. some code that can be posted into an assignment or forum?

Is it possible for students to trigger incidents? Typically it is more an issue if teachers are doing something accidentially, but there are definitely ways how students can use JavaScript exploits, too.

My students aren't smart enough to do harmfull stuff. That is nonsense. Exploits are published on the internet and can just be copy-pasted into forum posts or submissions.

Less teachers need full JavaScript capabilities. How can we increase security without breaking cool stuff?

We need more tools in Moodle to identify security problems in user generated content.

The default should be that nobody can insert any JavaScript. This capability should only be given to trusted persons with detailed knowledge of the risks.

Snippet library with trusted JavaScripts that can be used safely.

A tool could detect all JavaScript and extract it into a library in a tokenized form (i.e. there is not the JavaScript in the user generated content but only a reference token to the script). Then instance admins can accept scripts to be safe.

There are global config option something like force_clean and enable_trusted_content

Sandbox with a second domain without access to cookies. Then you have to put things in iframes.

We have a moral obligation to roll out a platform that is secure.

Back to top

Knowledge Base: Was hilft am meisten?

Speaker: Klaus Steitz
Language: DE
Room: J7
Time: 11:00
Session documentation
  • Diskussion zur Session im MootDACH-Forum: https://moodlemootdach.org/mod/forum/discuss.php?d=7171
  • Link zur Knowledge Base: https://kb.moodle-an-hochschulen.de/
  • Software: Bookstack (https://www.bookstackapp.com/) gehosted durch MaH e.V.
    • Aufgebaut wie eine Bibliothek (Regale, Bücher, Kapitel, Seiten)
  • Inhalte sind ohne Login aufrufbar – Inhaltliche Mitarbeit nur mit Account (Kontakt zum Redaktionsteam aufnehmen)
  • Zielgruppe: unsere Community (Admins, Support, ...) – nicht Studierende / Lehrende direkt
  • Themenpatenschaften
    • wo sind die einsehbar? 
  • Artikel zu den Editoren (Markdown vs HTML), was funktioniert in großen Teams besser?
    • erstmal keine klare Antwort in der Runde, aber die Idee den Prozess oder Schwierigkeiten als Artikel festzuhalten
  • Öffung für der Plattform über Hochschulen hinaus?
    • Vorstand: generell offen, Accounts können gerne angefragt werden
    • Namensänderung des Vereins aber nicht realistisch, da mit viel Aufwand und Kosten verbunden
  • Anleitungen für Plugins (auch über die Community-Plugins hinaus) bzw. Sammlung von bestehenden Hilfematerialen
  • Thema Anleitungen generell – wurde in der AG schon ein bisschen diskutiert, wenn dann auf Textbausteinbasis, da Screenshots meist Hochschul-spezifisch gewünscht sind
  • Thema Plugin-Erstellung – wo fange ich an?
    • Verweis auf die AG Plugins und den Hinweis, dass die Inhalte, die dort entstehen, dann auch in der KB landen oder mindestens verlinkt werden
  • Thema Erfahrungssammlung von Problemen bei Major-Updates
    • Plugin-Infos: Plugin hat noch keine offizielle Versionsfreigabe, funktioniert aber trotzdem – verhindern, dass immer alle alles selbst testen müssen
  • Thema Einbindungen von anderen Systemem (z.B. Campusmanagement, LTI, Mediamanagement/Videoplattformen (z.B. Panopto), externe Wikis (z.B. Confluence per LTI))
    • neues Regal mit Peripherie / Integrationen / Anbindungen?
    • Artikel zu LTI
    • Stand Anbindung HISinOne als Buch
  • Wo wird neben MoodleDocs und den Foren noch nachgeschaut?
  • Wie sieht das interne Wissensmanagement aus?
    • können wir bei der Entwicklung der KB aus euren internen Prozessen lernen?
    • können Inhalte aus den internen Inhalten generalisiert in der KB gesammelt werden?
  • Wie verhindert man von der Vielzahl an Inhalten erschlagen zu werden?
    • Auffindbarkeit
      • Chatbot-Integration
      • Suche sollte möglichst einfach sein
    • Austausch und persönliche Inhalte
      • Lunch & Learn mit neuen hilfreichen Inhalten aus der KB
      • Community of Practice
  • Wie geht man mit Hinweisen zur Sicherheit um?
    • es ist technisch möglich
  • Kontakt vereinfachen → die AG-Mitglieder irgendwo direkt mit Kontaktdaten auflisten um die Leute nicht in der Gegend rumzuschicken oder Funktionsemailadresse?
  • SSO für Vereinsmitglieder um Inhalte zumindest für sie einfacher sichtbar zu machen?
    • oder geheime Inhalte werden ins Vereinsmoodle übertragen

Back to top

Moodle Marketplace Alternatives

Speaker: Petr Skoda
Language: EN
Room: J7
Time: 12:00
Session documentation
discussion area in matrix: https://app.element.io/#/room/#openpluginsdirectory:matrix.org

Why not official Marketplace?
  • competing products banned
  • enforced Stripe payment processor
  • region restrictions
  • non-refundable fees
  • 25 % fee + Stripe processing fee
  • loss of user trust - too many low quality and outdated plugins
  • lack of security reviews and reporting
  • no core changes possible

What do you loose?
  • discoverability
  • web installer
  • lang packs
  • stats
  • protection against hostile takeover of installed plugins

An open alternative?
  • web site with catalogue of plugins
  • fork of composer installer
  • analytics plugin and endpoint
  • approval/review system to block AI slop and malicious plugins


What do you lose when not using Marketplace?
  • discoverybility
  • web installer
  • language packs
  • stats
  • protection against hostile takeover of installed plugins

If you're using a future date in your version.php it will not be deployed by marketplace.

Back to top

More Than Words

Speaker: Júlia Verdaguer
Language: EN
Room: G3
Time: 14
Session documentation More Than Words 14:00 G3
(Júlia Verdaguer)

Diese Session wird aufgezeichnet

Moodle's Product Writing guidelines: https://moodledev.io/general/category/product-writing-guidelines

New! Moodle's Design system https://design.moodle.com/98292f05f/p/913230-moodle-design-system - WIP - keep an eye out for new components (https://design.moodle.com/98292f05f/p/877c50-button) being added! Each component has usage guidelines and includes content design guidelines as well. 

Back to top

Using Mchef to manage development prospects

Speaker: Guy Thomas
Language: EN
Room: H2.1
Time: 14
Session documentation
https://www.citricity.com/mchef
https://github.com/citricity/mchef

Requirement: PHP8.3, Docker

Recipe driven docker wrapper

Uses Moodle HQ Docker image as base: https://github.com/moodlehq/moodle-docker

In a recipe the features of the to be crested instance are defined.
Sample data can be integrated.
Moodle Plugins are defined via repo url and branch.

Several instances can run in parallel (mind the port setup - in future these might be autoselected)
-> see the "proxy" command as well

Wordpress Env. (like mchef but for wordpress)

Back to top

Guidance - Assisting teachers with course creation

Speaker: Stefan Scholz
Language: EN
Room: H8.1
Time: 14
Session documentation
https://github.com/stefanscholz/moodle-tool_guidance

This plugin is the result of two-days dev camps. Please do not use it in production!

In part based on the ideas of the already existing plugin https://moodle.org/plugins/format_kickstart

Improvement ideas for the Guided Flow UI
* Go back link
* Icons
* Descriptions
* Preview images

New moodlers usually do not find the block region on the right side. --> Use boost_union theme to have a block region above the content.

Call to action:
  • Test & Feedback
  • Help us create rules
  • Help us create decision graph
  • Help us create templates

Back to top

What's new in STACK

Speaker: Andreas Steiger
Language: EN
Room: J3
Time: 14
Session documentation
Slides: https://people.math.ethz.ch/~asteiger/2026-mootdach/stack.html

Documentation
  • ...

Back to top

AI Assistant Activity

Speaker: Martin Hanusch, Sophie Zimmermann
Language: EN
Room: J4
Time: 14
Session documentation
  • AI Assistant as an Moodle Activity
  • Connected by admins through the AI subsystem
  • Teachers can activate ist as an acticity from the list and tick all materials which should be included in the RAG for a course bot
  • => Comment 07.07.2026: This sounds similar to the RAG-activity that was developed by moodle.nrw and oski.nrw. Here, you can also add the activity and choose from the course materials, which documents should be included for the chat. So you can have different activities with specific knowledge.

  • Next steps: Assignment feedback, ...

  • Separate AI platform, Moodle plugin will create groups (and transfer roles) on the platform
    • Plugin ist designed for the ETH AI platform, but is supposed to be generalised in future

  • Terms of Use are tricky in many aspects


Questions: 

  • Is there still a repo so see the code? Will you release it Open source?
    • Needs some cleaning and abstraction from the ETH AI platform which it is tailored for, but yes.

Back to top

Boost Union - hot new stuff

Speaker: Kathleen, Alex, Luca
Language: EN
Room: J6
Time: 14
Session documentation
Kathleen Aermes - Uni Jena
Alexander Bias - ssystems
Luca Bösch - BFH

Slides
https://share.ssystems.de/s/F6J97mioq2yee66

Presentation
  • Current number of sites with Boost Union: 8468 and increasing 
  • Core design principle: behave like Boost, but allow more customizations to be activated
  • New features: 
    • Options for Login Page
      • More login provider layouts (such as accordion and tabs)
      • Better Shibboleth WAYF integration (based on auth_shibboleth, but also for SWITCH AAI users) 
      • For even other Login options, use the Java-Script inputfield to integrate it.
    • New branding options
      • Separate Button/Link colors in case your brand colors are incompatible with accessibility
    • Smart menus
    • Enhanced course headers
      • More beautiful, more useful
      • Custom image, instructor information, custom course field, course progress, course details, global defaults with ability to customize per course
      • Have ideas for useful layouts? Please create a GitHub Issue ❤️
    • Recommendations
      • More consistent now, moving all the recommendations to a dedicated page with some autofix options
      • Have ideas for best practices? Please create a GitHub Issue ❤
  • Progress bar has the same issues of unexpected percentages as core Moodle, which should be fixed by the core Moodle tracker. 
  • What's next? 
    • (As always) Need more funding to make new features happen (check the needs-funding tags in GitHub), but even if Alexander is hit by a bus, there is continued support for the theme 
    • Please help us support this wonderful community. Everyone can help in their own way. Contact us, we will early welcome you too the team.
    • And we accept money 💰, such as end of year money
    • MoodleMoot DACH website will switch to Boost Union 🎉

Back to top

Adaptives Lernen in Moodle – für alle nutzbar

Speaker: Behsad Vahidi
Language: DE
Room: J7
Time: 14
Session documentation
Der Link auf dem alle Ergebnisse liegen: https://www.miau.ruhr-uni-bochum.de/

Back to top

BBB & Moodle – Next Level

Speaker: Gerhard Schwed
Language: DE
Room: G3
Time: 15
Session documentation
BBB erlebte mit Covid einen ersten Boom, fehlende Funktionen, Best Practices, Hosting-Hürden wurden schrittweise deutlich.

Von BBB3 an gibt es neben neuen Features eine offene Plugin-Architektur, die (endlich) modulare Erweiterungen möglich macht, ähnlich wie Moodle gibt es Open Source und Paid-Varianten.

Kernfeatures BBB3:
    - Plugin-Architektur
    - neue technische Basis, die z. B. eine stabilere Verbindung erlaubt
    - Chat mit Antwortfunktion
    - Quiz-Funktion mit Auswertung
    - Unified Layout
    - Learning Analytics (Beteiligung, Umfragen, Quiz-Ergebnisse etc.)

Documentation on BBB plugin architecture: https://docs.bigbluebutton.org/plugins/

Plugin repository: https://github.com/bigbluebutton/plugins

Zukunfts-Idee: Dedizierter Client: Mini-Browser vorkonfiguriert, mit dem alles direkt funktioniert und nicht erst einzeln die rechte für Mikrofon, Webcam und Screen-Sharing freigegeben werden müssen.

Plugin-Architektur:
    - Core bleibt unverändert
    - Erweiterungen können individuell ein-/ausgeschaltet werden (auch aus Moodle heraus)

Back to top

AI as a media acitivity with OpenWebUI

Speaker: Dennis
Language: DE
Room: H2.1
Time: 15
Session documentation

No session documentation is available.

Back to top

Oncampus Goes Open Source

Speaker: Marius Rosenbaum, Joscha Sauerland
Language: DE & EN
Room: H8.1
Time: 15
Session documentation

Back to top

Let's feed the Moodle Tracker

Speaker: Laurent David
Language: EN
Room: J3
Time: 15
Session documentation
https://docs.google.com/presentation/d/1PWBv1uS9NohdH-Bfl3bFtAzeaBEYqhVCOUDeC_9q4KQ/edit?usp=sharing

Why create tickets:
  • To get a bug fixed
  • To get a new feature added
Sometimes search doesn’t find the item - so prioritise creating a new ticket over being certain it is not a duplicate
Stages:
  • Ticket reported - try to describe in a way that will help others to find it when searching
    • Make sure that bugs can be reproduced on unmodified sites
  • Triage - check bug can be reproduced, check to see if improvement is reasonable; may close tickets if they are not going to be addressed
  • Development - Moodle HQ or external developer
  • Peer review - someone else checks the code (anyone with some development experience can volunteer to do this, with documentation guidelines available), to make sure it is sensible, check the approach taken, make sure automated tests are present, check code guidelines
    • Peer review can step back and say they are not qualified to sign-off peer review
  • Component / integration review - a more senior review
  • Manual testing
At any stage, can be sent back to development for fixes
Sometimes frustration about integration review pushing back on method chosen, or doing a lot of work on an issue, but it is never accepted, so feels like wasted time
Moodle has established a community contributions team to (hopefully) get better at accepting community contributions
Prioritisation can feel opaque from the outside - how is it chosen which ticket to work on
  • Hard to understand why minor accessibility CSS fixes can get in quick, when a critical bug fix breaking sites can take weeks
  • Integration exposed shows integration queue is growing, not shrinking
Code submission:
  • Make github clone of Moodle
  • Create branch for each branch being fixed (main only for new features)
  • Add info about diff + repo
Security fix process:
  • Flag ticket as security when creating it - it will then be hidden from most users
  • Patches are submitted directly onto the ticket, rather than posting in public github repo
Code review advice:
  • Easy to spot things that are wrong in the lines of code shown
  • Harder to spot the related things that should have been done

Few links:
  1.     https://moodledev.io/general/development/process
  2.     https://moodle.atlassian.net/jira/
  3.     https://moodledev.io/general/development/process/triage
  4.     https://moodledev.io/general/development/process/peer-review
  5.     https://moodledev.io/general/development/process/integration/clr

Back to top

Moodle UX Optimierung

Speaker: Andreas Hruska
Language: DE
Room: J4
Time: 15
Session documentation

Die Userexperience (UX) in einer Moodle Plattform kann auf verscheidenen Ebenen angepasst werden.
Als Premium Moodle Partner hat eDaktik (https://www.edaktik.at) einflick in VIELE Moodle Instanzen und die UX-Anpassung reicht von "Oh, man kenn ein eigenes Logo hochladen" bis zu kompletten Custom Plugin Sets die in Betrieb sind.

Ziel dieser Session ist es die einzelenen Ebenen auf denen Anpassungen möglich sind zu beleuchten und einen Überblick darüber zu gewinnen wie die Wünsche und Pläne im Hochschulbereich bezüglich den bestehendne Möglichkeiten und dem was uns mit Moodle 5.3 und dann 6.x bevorsteht aussehen.

FEEL FREE to ADD your comments!!!

## Anpassungsebenen

- Theme
- Navigation & Information
- Kursformat
- Formatvorlagen
- Interaktive Elemente

### Themes



- Boost
- Boost_union https://moodle.org/plugins/theme_boost_union
- ...

### Navigation & Information

- block_cohortspecifichtml https://moodle.org/plugins/block_cohortspecifichtml

### Kursformate

- boost
- boost_union https://moodlemootdach.org/?theme=boost_union
- onetopic https://moodle.org/plugins/format_onetopic
...

### Formatvorlagen

- tiny_styles https://moodle.org/plugins/tiny_styles
- tiny_c4l https://moodle.org/plugins/tiny_c4l
- tiny_elements https://moodle.org/plugins/tiny_elements
...

### Interaktive Elemente

- H5P https://h5p.org/
- Bootst
rap https://getbootstrap.com/
.. the "new Book" from Petr Skoda (MootDACH 24)

### Other considerations

Markdown vs. HTML

### Premium Moodle APP

- Additional CSS


This pad text is synchronized as you type, so that everyone viewing this page sees the same text. This allows you to collaborate seamlessly on documents!

Get involved with Etherpad at https://etherpad.org

Back to top

Boost Union, supercharged – Make it Your Moodle

Speaker: Stefan Scholz
Language: EN
Room: J6
Time: 15
Session documentation
Presentation
  • Features are developed for Moodle Workplace, but are planned to publish for Moodle as well
    • "Dash" works as a block within Boost Union
  • "Go to course" button on My Moodle page leads directly to the last/next activity instead of top of the course
  • Separate plugins for different properties, widgets to tick

  • Question: Tested for accessibility?
    • "Technically it is" (beware of unsuitable contrast and colours)


demo site: https://bdecent-wp51.eledia.de 
The company behind the shown features: https://bdecent.de/
the dash plugin page: https://bdecent.de/dash/

Back to top

SEB Server Tutorat sourire

Speaker: Christine Lent
Language: DE & EN
Room: J7
Time: 15
Session documentation
https://safeexambrowser.org/about_overview_de.html

https://github.com/SafeExamBrowser/seb-server

SEB Server User Guide: https://seb-server.readthedocs.io/en/latest/overview.html

SEB Server Installation Guide: https://seb-server-setup.readthedocs.io/en/latest/overview.html

Simple SEB-Server Tutorial: https://github.com/ramhee98/seb-server-installation-guide

Hint: There is a new version with better UI in progress!


BFH Settings for SEB Exams (Templates):
OpenBook with/without Proctoring
ClosedBook with/without Proctoring

What is useful to life monitor?
- WIFI
- Battery Status
- Ping


How to start?
Ramon Heeb can provide a basic tutorial... https://github.com/ramhee98/seb-server-installation-guide


Community ressources:
    https://github.com/SafeExamBrowser/seb-server/issues
    https://github.com/SafeExamBrowser/seb-server/discussions


SEB for Linux is being developed, but it will take some time (Linux is difficult in this matter).

SEB Alliance: Become a member to support the development!
https://safeexambrowser.org/alliance/members.html 

Back to top

Start Over Again

Speaker: Martin Dougiamas
Language: EN
Room: G3
Time: 16
Session documentation
Been in research the last years

Human cultures are important.
Current systems have deficiencies.
  • Moodle is 24 yrs old
AI is here to stay.
  • We're in the "going down phase" of the Gartner Hype Cycle
  • Most of us are desillusioned by the companies, not the concept of AI.

Martin has a locally run open source LLM that works as his personal assistent, accessible through a VPN.

We have to chose ethical solutions regarding AI.

Software is becoming easy to make.

VibeOS seems to be based on Windows XP source code.
(https://vibeos.sh/)

AI will be in everyone's pocket.
It makes no sense to only learn from your AI.

Go learn face to face, online learning does not beat real physical learning opportunities.

Good standards promote interoperability and global adoption.
Too many or too complex standards .......
Lifelong education needs a subset of open standards.
Organisations will always structure knowledge and set learning policies.
Credentials still matter.
There are better languages than PHP.
First 2 moodle prototypes were python based.
Go (https://go.dev/), Swift (https://www.swift.org/), Kotlin (https://kotlinlang.org/)

Open EdTech Learning Ecosystem
Learner-owned. AI-guided. Institution-connected. Standards-based.
goal is for you to learn
Coach (Learner-Owned)
  • Learner's lifelong learning hub (local-first app) – portable, exportable (YAML/JSON), interoperable
LMS (Organisation System)


OpenEdTech


Get in touch
  • mail: martin@dougiamas.com
  • mastodon: @martin@openedtech.social
  • my site: dougiamas.com
  • music: mantisaudiogram.music

Discussion

Back to top

Modifié le: mercredi 8 juillet 2026, 12:12