#@deprecated

The History Module was approved for removal in 🌱 [Policy] Deprecate History module in D10 and move to contrib in D11 RTBC .

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 📌 [meta] Tasks to deprecate the History module Active and the removal work in 📌 [12.x] [meta] Tasks to remove History module Active .

History will be moved to a contributed project after the Drupal 12.x branch is open.

Oh, flood control only blocks further login attempts, it doesn't ban the IP. Thanks for the clarification.

Flood control doesn't depend on the ban module - it's a core subsystem.

I'm the maintainer of the CrowdSec → module, which depends upon the Ban module, and we do have plans for moving that forward. So, I'm interested in maintaining the Ban module moving forward. Short term, I don't have much availability, but it looks like the process of managing the deprecation is already in good hands.

Just wondering, what's the plan about Drupal core's flood control as it depends upon the ban module as well. Are we deprecating flood control too?

I don't use the ban module, but I'm motivated to assist in removing it from core. So I'd be happy to maintain a 1.x version, but would need to find others to maintain the proposed 2.x version.

Asked in #core-development for someone to maintain the contrib module.

Wonder if the summary could be updated with what's next?

The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".

This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.