Closed (fixed)
Project:
Drupal core ideas
Component:
Idea
Priority:
Normal
Category:
Plan
Assigned:
Unassigned
Reporter:
Created:
25 Sep 2024 at 22:49 UTC
Updated:
6 May 2025 at 11:09 UTC
Jump to comment: Most recent
Core has extensions that do not provide foundational capability or strategic value for the product roadmap.
A smaller, more maintainable codebase that focuses resources on foundational capabilities and the strategic roadmap, with smaller database storage requirements on many sites.
The module is moved to contrib.
Comments
Comment #2
quietone commentedThis was discussed at a meeting of the Core Leadership team at DrupalCon Barcelona 2024. Those present agreed to the removing the contact module from core and moving it to contrib. The product managers were not able to attend so tagging for their review.
Comment #3
andypostAs posted in other issue #3336276-11: [Policy] Deprecate History module
Comment #4
jibranI'm also +1 with moving it to contirb.
Comment #5
beautifulmindDuplicate of https://www.drupal.org/project/ideas/issues/3356824
Comment #6
beautifulmindComment #7
quietone commented@beautifulmind, thanks for triaging this issue. This issue is the one that should remain open. It contains a summary of committer discussion and comments from two of the 3 maintainers of the Contact module.
I am restoring the status.
Comment #8
quietone commentedThere are two comments in the duplicate issue that support keeping the module in core.
Comment #9
lauriiiI'm +1 to this because this aligns with the strategy to not compete with contrib. Webform provides clearly a stronger platform to build on top of which most people are choosing as a result. Form building is an important feature, so we may want to consider in future if core should be providing this feature, but it's clear that Contact isn't the right approach to start implementing that.
Comment #10
quietone commentedAll the sign-off have been given, so setting the status to fixed.