Offering to maintain Label Help [#3237326]

Label Help has been automatically opened to new maintainer applications, as it has releases for Drupal 8 which will be marked unsupported on 2 Nov, 2021, but no release yet for Drupal 9. Your Drupal 7 releases will not be affected.

This is an adaptation of our existing process for transferring project maintainership.

After the standard 14-day waiting period from this issue being opened, and if an existing maintainer has not closed it, this project becomes eligible for new maintainers. Those new maintainers will not need to wait for existing maintainer approval.

Next steps:

An existing maintainer may close this issue and opt out of this accelerated process.
A prospective new maintainer can take this issue after the 14 day window has elapsed and take the following steps to be added as a maintainer:
- Comment here explaining why you would like to maintain the module.
- If the project is opted in to security coverage, confirm that you have previously received security coverage opt-in permission.
- If an existing maintainer has not commented, move the issue to the Drupal.org Project Ownership queue, by editing the “Project” field on this issue.
The Drupal.org site moderators will review the issue, and if it meets the requirements can grant you maintainer access.

Comments

Comment #1

20 September 2021 at 21:14

System Message created an issue. See original summary.

Comment #2

jwilson3

English

Ecuador

commented 26 October 2021 at 16:52

At Bluespark we've created a clone of the project at https://github.com/meladawy/drupal-label_help in order to create a 2.x branch that fixes the Drupal 9 compatibility issues.

I've also spent time working on this module a few years ago, contributing time and a large patch to expand support to different field types in Drupal 8, which were never accepted or even reviewed by maintainers here: #2948501: Improve Drupal 8 field compatibility.

I'm offering to maintain this module, particularly since Drupal 8/9 now has core feature that lets users place the description #before or #after. Therefore several features from this module could actually be moved to core features.

There is still space for a module like this because core still has several issues with their field description implementation, and this module could be the place to house fixes for contrib module fields that would never be supported properly by core.

I have previously received security coverage opt-in permission.

I maintain or co-maintain a few other modules and themes.