Community

Where Extended Matrix lives.

News, two recurring meetings, two chat channels, one issue tracker. Everything is open — drop in, ask questions, share work.

Latest news

Short posts about releases, milestones, EU-project news and other day-to-day community signal. The full archive lives at /news.

All news →

Conferences, bazaars & talks

Yearly gatherings — EM Conference for users, EM Bazaar for developers — plus talks and workshops at partner venues. Recordings, slides and programmes are kept on each event page.

All events →

EM Hour

The Extended Matrix Happy Hour — recurring informal session on the second Thursday of each month at 14:00 CET. Open chat, screen shares, demos, "what are you working on this week?".

Upcoming

  • Thu, 9 July 2026
    14:00 · 60 min

    EM Hour — July 2026

    Second monthly EM Hour — Thursday 9 July 2026, 14:00–15:00 CET, on Microsoft Teams. Open agenda: bring projects, demos and questions. Topics will be finalised closer to the date via the Telegram group.

Past sessions

  • Thu, 11 June 2026

    EM Hour — first community happy hour

    First Extended Matrix community happy hour — Thursday 11 June 2026, 14:00–15:00 CET, on Microsoft Teams. Open chat about the brand-new EM 1.5 LTS, the redesigned extendedmatrix.org, the StratiGraph EU project, and what the community is building right now.

Development meetings

Monthly public coordination for the codebase. Open by default, notes-first, decisions are recorded so direction stays transparent — especially as more contributors arrive with AI-assisted workflows. Each meeting has its own page with TL;DR, attendees, decisions and action items; async agenda gathering happens on the Meeting Notes discussion category on the dev-site repo.

Past meetings

  • Tue, 23 June 2026

    Dev coordination — June public sync

    First public dev meeting of the post-1.5 cycle. Python-for-Blender pipeline, Oxigraph integration in EM, GraphML backups alongside the DB, EM Meter analytics with Jupyter, multi-national cataloguing mapping. Four action items assigned.

    Decisions:
    • Move Oxigraph integration directly into the Extended Matrix library so the knowledge-graph can be written to the triplestore from Python rather than only exported as Turtle and re-imported.
    • Adopt a parallel persistence model for the graph (DB + GraphML), so that recovery and external interoperability stay first-class even when the primary tool's database file becomes the source of truth.
    • Treat property-graph vs triple-store as a mapping question, not an architectural choice — the same EM dataset must be expressible in both, with national archaeological cataloguing schemas (Italian, German, Israeli, …) as the user-facing layer.
    • Adopt the Visual Studio Code + Jacques Lucke add-on workflow as the recommended Blender-Python dev loop (live reload, in-Blender debugger, no restart required).

Want to host a session, propose a topic, or just listen in? Say hello on Telegram →