[Policy] Move Search module to contrib

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.

Thanks to dinarcon for pointing out, in Slack, the copy/paste error in my comment above.

This seems like a bad idea to me. The functionality of this module seems pretty essential for Drupal core to have a minima feature set.

@pwolanin

Something like search API module is much too complex to set up and maintain if you want just a basic content search to work.

The idea is that once 🌱 Specification document for Advanced search in Drupal CMS Needs review is available in Drupal CMS (and once Drupal CMS is stable), then Drupal CMS will provide a pre-configured search recipe using search API and that would be the default search experience for most new users.

Drupal core won't have the standard profile any more (or not in its current form anyway), so then it becomes confusing having a search module that's not enabled in core by default and is completely replaced by Drupal CMS.

It's true that search API configuration is pretty complex, but you end up doing that anyway once you need something that core search doesn't provide out of the box, so as long as the Drupal CMS recipe gets people started sufficiently, then it should be a better situation than now.

@catch - that sounds like a lot of thing that may not come to pass.

Also - if I'm building a data-oriented web app, I don't think I'd start from Drupal CMS, and I think there needs to still be consideration for all the use cases that want to start from a reasonably fully functional Drupal core.

So, at the very least this issue sounds premature until the Drupal CMS being stable with a good search_api recipe is implemented. At that point, it sounds like the only concern is around user confusion?