For the purpose of updates with FontAwesome and Drupal 12 planning and issue triage, I volunteer to be a maintainer for this module. I have permissions to opt-in to security coverage. I have contributed to this module and I have experience maintaining several other modules as well. https://www.drupal.org/u/shelane

Along with FontAwesome 7.1.x compatibility and code updates that are needed to pass phpstan, I would like to also bring the module page up-to-date. I'm also sending this message directly to both current maintainers.

Project Page

Comments

shelane created an issue. See original summary.

avpaderno’s picture

Title: Offering to maintain FontAwesome Icons » Offering to maintain Font Awesome Icons
shelane’s picture

Project: Font Awesome Icons » Drupal.org project ownership
Version: 3.0.0 »
Component: Code » Maintaining offer
Issue summary: View changes
avpaderno’s picture

Assigned: Unassigned » avpaderno
Category: Support request » Task
Status: Active » Postponed

I will contact the project maintainers between an hour. Both the maintainers will be contacted.

shelane’s picture

Hi,

Have you heard back from the maintainers? Is there an estimate for when this might be approved?

Thanks

avpaderno’s picture

When I contact maintainers, I send the message to my email address too. In this case, I did not find that message in my email box.

I will contact the maintainers.

avpaderno’s picture

This is the first message I sent. I will contact the other maintainer right after posting this comment.

Hello Daniel,

I am contacting you because Shelane (https://www.drupal.org/u/shelane) offered to become maintainer for Font Awesome Icons (https://www.drupal.org/project/fontawesome/), a project for which you are project owner and maintainer.

May you post a comment on https://www.drupal.org/project/projectownership/issues/3569397 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, Shelane will be probably made maintainer.

I am contacting all the project maintainers, and the project co-maintainers with the "Administer maintainers" permission, who logged in at least once in the past 12 months.

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.

As last note: This offer is about being maintainer, which is different from being co-maintainer. A maintainer is a person who has all the drupal.org permissions on a project: Write to VCS, Edit project, Administer maintainers, Maintain issues, Administer releases. A person who does not have all those permissions is a co-maintainer.
If there is any reason for not giving all those permissions, please explain that on the offer issue. 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

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 that a project moderator's action is required.

truls1502’s picture

Status: Postponed » Postponed (maintainer needs more info)

Thanks a lot for the offer, we really appreciate it.

Before adding anyone as a maintainer or co-maintainer, we’d prefer to see some contributions through issue queues and merge requests (MRs) first, if possible. That helps us get a better sense of collaboration and whether it’s a good fit before granting additional responsibilities and permissions.

Also, if there are any specific issues currently blocking your ability to contribute or delaying the release of fixes, please let us know. That would help us understand where support or permissions are most needed.

Please feel free to open issues and submit MRs, and then we can revisit the maintainer role later.

shelane’s picture

Hi, thank you for your consideration. I did submit an MR on this issue: https://www.drupal.org/project/fontawesome/issues/3380581. The patches on the issue didn't solve the problem, but I have been using the changes from that MR for over two months without an issue. But, I also need an update to FontAwesome 7.2.0 that others are working on. I was seeing a lot of out of date information on the project page as well and no commits to the project in over a year. I would still be willing to jump in and help with these issues.

truls1502’s picture

Hi, and thanks again. That context was very helpful.

It is absolutely fine to start by opening an issue for anything you think should be updated on the project page. You can also look at the revision history (“View history”) to see examples of previous changes, including feedback from non-maintainers about project page updates.

Even though there have not been any commits for a while, please feel free to review the open issues and continue contributing there, or open new ones for things you think should be addressed. These are all good ways to help move the project forward, and they do not require maintainer or co-maintainer roles.

If there is a specific issue or area you would like to start with, please go ahead, and let us know if you need anything from us along the way.

avpaderno’s picture

Assigned: avpaderno » Unassigned
truls1502’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

I am going to close this issue for now, since there does not seem to be any current blocker that requires maintainer access.

That said, please feel free to continue opening issues and submitting MRs. If anything is missing or if you run into a specific blocker that requires maintainer support or permissions, please let us know so we can revisit it.

Thanks again for your willingness to contribute.

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

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

Maintainers, credit people who helped resolve this issue.