Offering to maintain HTTP Cache Control

Created on 19 January 2024, 5 months ago
Updated 26 March 2024, 3 months ago

Problem/Motivation

I would like to become a co-maintainer of the HTTP Cache Control module → to resolve any pending and future issues.

You can view my profile → to see my history of work.

Proposed resolution

Review my profile and, if approved, add me as maintainer with appropriate permissions to merge code, manage issues, and create releases.

Remaining tasks

Add DieterHolvoet as co-maintainer of HTTP Cache Control.

💬 Support request
Status

Active

Version

2.0

Component

Miscellaneous

Created by

🇧🇪Belgium DieterHolvoet Brussels

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @DieterHolvoet
  • 🇧🇪Belgium DieterHolvoet Brussels

    I contacted the maintainer, Josh Waihi, which I forgot to do at first. This is my message:

    Hi,

    Could you post a comment on my offer to maintain HTTP Cache Control
    ( https://www.drupal.org/project/http_cache_control/issues/3415863 💬 Offering to maintain HTTP Cache Control Active )?
    I would like to become a co-maintainer of the module to resolve any pending
    and future issues.

    Thanks in advance,
    Dieter Holvoet

  • 🇧🇪Belgium DieterHolvoet Brussels
  • 🇳🇿New Zealand Josh Waihi

    Hi DieterHolvoet, can you give me an idea of what interests you have as a maintainer?
    I see you have a lot of contributions on your profile - do you have time to be a maintainer? Admittedly, my time is limited too.

    Something I am cautious about with this module is to limit UI configuration to help minimize potential issues users might get themselves into using this module. Though more advanced developers (who might have a better sense of what they're doing) can override UI config using config exports.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • 🇧🇪Belgium DieterHolvoet Brussels

    We're adding this module to all our projects at our Drupal agency so yes, I'll get enough (paid) time to maintain the module. Besides, it's a small module, so it won't need that much maintenance anyway, right?

    Are you referring to ✨ Allow choosing more fine-grained max-ages Needs review ? Because I implemented that as you proposed. But yes, I agree, we should be cautious to prevent people from shooting themselves in the foot, while allowing advanced users to have access to fine-grained configuration. I don't agree that advanced users should be forced to edit configuration directly, we could still provide a useful UI for those people. But we should probably discuss that further in the related issue.

  • 🇧🇪Belgium DieterHolvoet Brussels

    @josh-waihi any update here? Anything you need from me?

  • 🇳🇿New Zealand Josh Waihi

    Sure I'm happy to have you added as a maintainer. Perhaps we can connect at somepoint to discuss a 2.x branch. I'd like to add the ability to conditionally apply cache control rules (e.g. For matching URL patterns). Perhaps Rules module support.

Production build 0.69.0 2024