This d.org issue was recently brought to my attention: https://www.drupal.org/project/ideas/issues/2582955
Background
Now that we have a new release cycle, we have the possibility of new features in minor releases, i.e. although we are in RC1 for 8.0, that doesn't mean we can't add new features until 9.0. Provided they are backwards-compatible, we can add new features in 8.1 and 8.2.
After recently taking over maintainer-ship of the core contact module @andypost and I, in consultation with @berdir have formulated a draft roadmap for the features we'd like to see in contact module in the future. Why not make this the guinea pig for how these initiatives and features might work in future versions of D8.
High-level goal
To provide the 80% use-case of webform. i.e. allowing creation and submission of feedback forms from site-users; and providing editing, listing and administration of submitted form values.
Webform contains lots of features, we're only after expanding contact module slightly to add storage and administration and in the process meet the basic use-case of webform in core.
Note that some of these items have been developed in contrib as the Contact Storage module. They can continue to mature there during 8.0 with the view to include in point releases eg 8.1, 8.2.
Recent comments
Re PHP 8.5 compatibility: not ready yet for review, but tests are passing now. So, still work in progress with issue #7008.
November 20th 2025 Weekly Meetings
This issue in the API module is blocking any upgrade of docs.backdropcms.org to later PHP versions. I had a look but not sure how this can be fixed: https://github.com/backdrop-contrib...
November 20th 2025 Weekly Meetings
The number of questions about lost configurations support my argument. Who knows how many developers use version control systems... UPDATE: The option to store in a database was added...
I need to understand how active and staging folders work – configuration management