- Issue created by @quietone
- π¦πΊAustralia larowlan π¦πΊπ.au GMT+10
Happy to maintain it in contrib
- π«π·France andypost
Asked in slack access to the module https://drupal.slack.com/archives/C1BMUQ9U6/p1745586623875969
- π«π·France andypost
Filed child π Create 3.x branch to import core module Active
- πΊπΈUnited States thejimbirch Cape Cod, Massachusetts
Core's standard recipes have references to the Contact module in addition to the standard profile.
I updated the issue summary. Did the list of tasks come from a template? If so, we should update that also as recipes probably did not exist at the time that list of things to do was generated.
- π¬π§United Kingdom JamesOakley Kent, UK
Somewhere after
4. Create the contrib project with a stable release
should there be a step to find all issues in the Core issue queue that relate to the Contact core module, and move them to the contrib project (presumably with a brief comment explaining). Any issues would need fixing in contrib first, with optional backport to the core version.
(I came here from π Create contact form block Needs work , which is one example)
- π³πΏNew Zealand quietone
@jamesoakley, the tasks in this issue include marking the issues for the Contact module as postponed, with a message. The task to move them to the contrib project is part of the tasks to remove the module from core, which is worked on after the 12.x branch is open.
A search of core issue for issues that should be in the 'contact.module' is not done. It is assumed that issues have been triaged correctly.