Deprecate Ban module

@andypost, thanks for starting the issue. If you like, I will setup the issues for the other planned removals.

@quietone thank you, makes sense

Situation here seems a bit different/more complicated than some other core removals as there are multiple alternative modules and additions. We use it in combination with https://www.drupal.org/project/perimeter → and https://www.drupal.org/project/auto_unban → , which also overlaps with autoban and advban.

Should we consider to deprecate ban in favor of an existing contrib project like advban? Or do the opposite, and merge those additional features into the ban contrib project and attempt to establish a new 2.x release branch of that as the canonical solution for some of these ban features?

I'll ping a few of the current maintainers of those projects on slack.

Or do the opposite, and merge those additional features into the ban contrib project and attempt to establish a new 2.x release branch of that as the canonical solution for some of these ban features?

That would definitely be my personal favourite!

@berdir in terms of core I think a 1.x version that provides continuity with core is enough to remove it, but consolidating the various similar/extending contrib modules into a single contrib project, which could be the ban 2.x branch, sounds great.

Regarding of idea 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active I've added the ban reason field to the latest release of advban → module. This was the only concern I read with advban.

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

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.

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?

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

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