What is the problem to solve?

Core has extensions that do not provide foundational capability or strategic value for the product roadmap.

Result: what will be the outcome?

A smaller, more maintainable codebase that focuses resources on foundational capabilities and the strategic roadmap, with smaller database storage requirements on many sites.

How can we know the desired result is achieved

The module is moved to contrib.

Comments

quietone created an issue. See original summary.

quietone’s picture

Status: Active » Needs review
Related issues: +#3476434: [discussion] Core Leadership module removal discussion

This 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.

andypost’s picture

Status: Needs review » Reviewed & tested by the community
jibran’s picture

I'm also +1 with moving it to contirb.

beautifulmind’s picture

Status: Reviewed & tested by the community » Closed (duplicate)
beautifulmind’s picture

quietone’s picture

Status: Closed (duplicate) » Reviewed & tested by the community

@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.

quietone’s picture

There are two comments in the duplicate issue that support keeping the module in core.

lauriii’s picture

I'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.

quietone’s picture

Status: Reviewed & tested by the community » Fixed

All the sign-off have been given, so setting the status to fixed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.