Skip to content

Roadmap

FedMS is a pre-1.0 framework under active development. This section summarizes the direction of travel and the work that is queued up.

In this section

  • Open issues — a curated catalog of the open issues across the framework, grouped by area.
  • Known limitations — things FedMS does not do (yet).

The big themes

Federation (in progress)

The structural foundations of federation are in place; the transport layer is the next major piece of work. See Federation for the model and the open issues on fedms/components/federation for the in-flight work.

Specific items:

  • Notification system — patterns, templates, delivery (fedms/components/federation#23, #25, #27, #29).
  • Dynamic event/session syncing (#31).
  • Activity logging (#22).
  • Calendar invites (#33).
  • Status fields for groups and notifications (#20, #21).
  • Require timezone for users (#28).
  • Launch button on events (#32).

The Notification subsystem

A consistent notification subsystem — patterns, templates, delivery, recipient resolution, audit — is one of the major pieces of work ahead. It will tie together:

  • The Send Email recipe.
  • The easy_email integration.
  • Event/session lifecycle (see task_api).
  • Federation transport (notifications-to-peers).

The successor modeler

The current ECA modeler is bpmn_io. A successor modeler is coming and will replace it. The data model stays stable; the UI gets a cleaner UX. Don't write tooling that hard-codes BPMN.io specifics.

Test framework

A three-phase test framework is being established (see fedms/components/profile#20):

  1. Per-component linting and tests — already in place.
  2. Full end-to-end tests running daily against the demo site — in progress via Playwright on the feature/advanced branch.
  3. Deployment tests on each customer site — nightly, against a copy of the live database, to verify that updates won't break the site.

Permissions matrix

The full permission matrix for the FedMS group roles is a known work item (see fedms/components/profile#10). The current state ships sensible defaults; the finalization is in flight.

Event templates and example orgs

A pre-defined "event templates" feature is being designed (see fedms/components/content#5, #6). This lets a customer enable a pre-populated "templates" org for quick setup of new events.

MTW — Milestone Task Widget

The widget that renders a group's open tasks grouped by milestone is being formalized at fedms/components/tasks#28. This will become the canonical "what's left to do" component on every event/session page.

Conditional fields

Native conditional fields on event/session types (fedms/support#50) — show field X only when field Y has value Z — is a common request, especially for sessions that vary by virtual platform.

Documentation roadmap

Specific to this documentation site:

  • Per-role user guides will grow as the UX stabilizes — currently they describe the model; over time they'll include concrete screenshots and step-by-step walkthroughs for each role.
  • Permission matrix auto-generation from roles_permissions.yml (currently hand-maintained).
  • E2E test alignment — every documented user journey will have a corresponding Playwright test, written in a follow-up session.
  • Federation transport — once the transport lands, the Federation page will be rewritten to describe the as-built model.

Next steps