Continued relevance of the Features module

In 2025, the Features module, https://www.drupal.org/project/features , still fills a relevant tooling role for building and maintaining Drupal sites. Drupal's Configuration Management API provides a robust solution for maintaining individual site configuration but does not provide a robust mechanism for shipping and updating subsets of configuration across multiple sites. Drupal's Recipe API provides a robust way to introduce new configuration to multiple sites, but doesn't provide a mechanism for updating that configuration on an existing sites.

Current state of Features module maintenance

The most recent release of the Features module was on 8 December 2023. Drupal 11 was released in August 2024, and although there has been some activity by one maintainer on #3447460: Drupal 11 compatibility for Features module, clearly other Drupal priorities have intervened to prevent a Drupal 11-compatible release of this module.

My offer to co-maintain

  • I am willing to offer my contrib module expertise to "minimally maintain" Features -- providing bugfixes and compatibility maintenance, though I do not have the time to commit to new enhancements.
  • I am an active contributor to Drupal for more than 12 years https://www.drupal.org/u/mark_fullmer
  • I have contributed to Features in the past: https://www.drupal.org/u/mark_fullmer/issue-credits/401392
  • I take my work seriously and put a high value on not introducing regressions or backwards compatible changes

Thank you for your consideration!

Comments

mark_fullmer created an issue. See original summary.

mark_fullmer’s picture

mark_fullmer
he/him
Primary language English
Location Tucson
commented
Project: Features » Drupal.org project ownership
Version: 5.0.x-dev »
Component: Miscellaneous » Maintaining offer

It has been two weeks since I created this issue and reached out to a project maintainer via the Contact tab. I'm therefore transferring this issue to "Drupal project ownership" per https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... . Thanks for consideration and any communication from the maintainers of the Features module regarding this offer!

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Component: Maintaining offer » Co-maintaining offer
Assigned: Unassigned » avpaderno
Status: Active » Postponed

I will contact the maintainers who logged in at least once in the past year. This means three out of four maintainers.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

This is the message I sent to the project owner.

Hello Mike,

I am contacting you because Mark (https://www.drupal.org/u/mark_fullmer) offered to become co-maintainer for Features (https://www.drupal.org/project/features), a project for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3541216 about accepting or declining the offer? Please do not reply via email; we need a reply on the offer issue.
Without a comment posted on that issue in the next 14 days, Mark will be probably made co-maintainer.

Project moderators will not remove the existing maintainers/co-maintainers; the project owner will not be replaced either. Maintainers cannot change the project owner; co-maintainers/maintainers can only be removed/added by people who have the permission to administer co-maintainers/maintainers.

I am contacting all the people who can administer co-maintainers/maintainers for the project.

As last note: This offer is about being co-maintainer, which is different from being a maintainer. A co-maintainer is a person who does not have all the drupal.org permissions on a project. Even though being co-maintainers could mean having just a single permission, we expect a co-maintainer to have the following permissions on the project: Write to VCS, Edit project, Maintain issues, Administer releases.
If there is any reason for not giving all those permissions, please explain that on https://www.drupal.org/project/projectownership/issues/3541216. We need this to know it was intentional and not a misunderstanding on what the offer required.

Best regards,
Alberto Paderno
-- Drupal.org project moderator
-- Drupal.org site moderator

I am still contacting the other maintainers.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Category: Support request » Task

I contacted all the maintainers who can be considered still active on drupal.org.

The status is Postponed because we are waiting for a reply.

Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.

mark_fullmer’s picture

mark_fullmer
he/him
Primary language English
Location Tucson
commented

Posting a comment to show that I am still interested in becoming a co-maintainer of the Features module.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed » Fixed

I added mark_fullmer as co-maintainer.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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