Deprecate this module in favor of core functionality (>=10.2)

We could also think about automating the migration to the core settings releasing a 3.x version, which transfers the configuration from this module to the file.settings core config and afterwards uninstalls itself. What do you think?

Other deprecated modules which were merged into core or other contrib modules, did similar in the past.

We could also think about automating the migration to the core settings releasing a 3.x version, which transfers the configuration from this module to the file.settings

Let's do that in a follow-up issue! If needed!

Set the module deprecated in favour of the core functionality, at least once Drupal 9 is EOL

I don't think we should do that, since Drupal 10.0.x and Drupal 10.1.x will then be still in use. These instances will also have the deprecation notice then if we use the

lifecycle: deprecated
lifecycle_link: xxx

approach in the info.yml. This can be quite confusing.

I guess the current implementation should be enough. Otherwise we could create a ^10.2.x only version and use the lifecycle properties, but I don't think that is necessary.

Please review!

@Grevil: Thanks, just one comment for clarification on the module overview page.

Afterwards RTBC!

Could you ping the last active maintainer please to take a look at this issue? No maintainer activity here yet.

Also a note should be added to the module page and the module status should be changed.

Done, please review again.

I send https://www.drupal.org/u/adubovskoy → an email!

Perfect!

@Maintainers: Also a note should be added to the module page and the module status should be changed.

@Grevil, @Anybody thank you for your input! The module page is updated.

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

If we're uninstalling this module and using the new "Sanitize filenames" settings at /admin/config/media/file-system, I assume we'd want to enable all the options and leave the Replacement Character as the dash? Thanks!