Contrib.social

[Policy] Deprecate History module

Open on Drupal.org →
Created on 24 January 2023, over 1 year ago
Updated 31 May 2024, 18 days ago

Idea summary

What is the problem to solve?

Make core more maintainable by removing modules that do not provide foundational capability or strategic value for the product roadmap.

History is currently used on 76% of sites, which is low, because it is a part of the Standard profile. It is also a frequent cause of database bloat.

Result: what will be the outcome?

A smaller, more maintainable codebase that focuses resources on foundational capabilities and the strategic roadmap, with smaller database storage requirements on many sites.

How can we know the desired result is achieved?

The module is moved to contrib.

🌱 Plan
Status

Needs review

Component

Idea

Created by

🇺🇸United States xjm

Live updates comments and jobs are added and updated live.
  • Needs product manager review

    It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).

  • Needs framework manager review

    It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

  • Needs release manager review

    It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.

  • Needs subsystem maintainer review

    It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.

Sign in to follow issues

Comments & Activities

  • Issue created by @xjm
  • Comment over 1 year ago →
    🇺🇸United States xjm

    @andypost is the maintainer for History, so he should be given an opportunity to provide feedback before this is committed.

    The committer team recently reviewed our scoring exercise on all core modules. There is a reasonably strong consensus that History is neither a foundational capability nor strategically valuable to the product roadmap, so it should be moved to contrib. I am marking RTBC, but leaving the tags on to give maintainers a chance to confirm that they agree.

  • Comment over 1 year ago →
    🇺🇸United States xjm

    Actually marking RTBC, and fixing parent.

  • Status changed to Needs review over 1 year ago
  • Comment over 1 year ago →
    🇺🇸United States xjm

    Sounds like this one could actually use further discussion. Points raised were:

    1. It's more useful than the other modules on the list for D11 removal.
    2. It's entangled with Comment architecturally.
    3. It is "used" (or at least installed) on 75% of sites currently (due to being in Standard). Whether or not they actually rely on the functionality is harder to say.
  • Comment over 1 year ago →
    🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10

    From a framework manager point of view, I'm happy for it to be moved to contrib. It isn't a feature needed unless you're building a community site. Not removing the tag as giving others a chance to chime in.

  • Comment 8 months ago →
    🇫🇷France andypost

    As maintainer I'm ++ for move to contrib as the module "wired" into comment/tracker/forum at least and it's hard to make it work with other entities.

    Contrib has less requirements and could iterate faster in 2.x branch

  • Comment 7 months ago →
    🇬🇧United Kingdom AaronMcHale Edinburgh, Scotland

    Speaking as the person who filed 📌 [Policy] Move book to contrib in Drupal 11 Fixed , I have no objections here!

  • Comment 5 months ago →
    🇳🇿New Zealand quietone New Zealand

    Removing versions from the title. They can be added back if this is approved.

  • Comment 18 days ago →
    🇳🇿New Zealand quietone New Zealand

    This doesn't have signoffs yet, so removing it as a child of the core issue.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024