Problem/Motivation

The Umami installation profile has so far been referred to as an "experimental" profile, reusing the concept of experimental modules that has been in Drupal core since 8.0.0.

However the concepts are sufficiently different that reusing the "Experimental" concept for the Umami profile is misleading and potentially confusing.

It is aspired that experimental modules pass through increasing levels of stability until they become non-experimental, IE first class citizens within Drupal core. If this doesn't happen within an agreed time frame*, they are removed from core. This is not the case for Umami, which is intended to retain its current level of stability in perpetuity.

There is also a difference in the context in which we call modules and profiles experimental. A module is experimental because the Drupal community are encouraged to experiment with it to find the rough edges and help gauge whether it is suitable for use in core going forward. The Umami profile is experimental because people who install it might be experimenting with Drupal. They might well not be experimenting, they might be demonstrating Drupal to others, or incorporating it in a training course, or using it to build documentation. It's not a given that the use is experimental.

I think there is potentially a use case for something called Experimental profiles - imagine we hadn't identified the need for Stark, and wanted to introduce something similar in core. Or decided that we wanted to offer a decoupled Drupal installation profile. We could then introduce an experimental profile with the intention it progresses through increasing levels of stability until it becomes non-experimental, in exactly the same way that modules do.

But that's not what Umami is. And labelling it as such would make it even more confusing if we *did* want to introduce a profile that better fits our concept of experimental components in core.

* we potentially may have bent the rules for Inline Form Errors here? But if we did, the aspiration was still there and this doesn't invalidate this point.

Proposed resolution

Change references to Umami being an Experimental profile to being a Demostration profile.

Build documentation on D.O explaining what that is.

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Data model changes

TBD