Problem/Motivation

I support a Drupal site that uses the open source h5p educational materials markup system maintained by the H5P Group (h5p.com, h5p.org). The recent update to v1.28 of that main library has created a breaking change in the Drupal module, as described in #3578071: resetHubOrganizationData since h5p-core 1.28 , of which I was the reporter and have submitted a Merge Request.

Since the MR is now 2 months old, I am offering to co-maintain the module in order to alleviate the burden on the current maintainers.

Update: I have requested input from paalj, one of the maintainers, via their contact form.

Comments

ldpm created an issue. See original summary.

ldpm’s picture

Issue summary: View changes
avpaderno’s picture

ldpm’s picture

Project: H5P - Create and Share Rich Content and Applications » Drupal.org project ownership
Version: 2.0.x-dev »
Component: Miscellaneous » Maintaining offer

This refers to: https://www.drupal.org/project/h5p

I opened this issue to offer to co-maintain in order to merge a MR that solves a currently blocking issue.

avpaderno’s picture

Issue summary: View changes
avpaderno’s picture

Component: Maintaining offer » Co-maintaining offer
Category: Support request » Bug report
avpaderno’s picture

Category: Bug report » Task
avpaderno’s picture

Assigned: Unassigned » avpaderno
Status: Active » Postponed

This is the first message I sent.

Hello paalj,

I am contacting you because Lawrence (https://www.drupal.org/u/ldpm) offered to become co-maintainer for H5P - Create and Share Rich Content and Applications (https://www.drupal.org/project/h5p), a project for which you are project owner and maintainer.

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

ldpm’s picture

Status: Postponed » Active

I am confirming that I am still willing to be a co-maintainer of this module. I will do my best to return the module to a working state, but I probably will not do a lot more than that.

avpaderno’s picture

Status: Active » Fixed

I added ldpm as co-maintainer.

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.

Status: Fixed » Closed (fixed)

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