Problem/Motivation

I'd like to apply for co-maintainership of H5P. My main motivation is to get #3150110: Drupal 9 Deprecated report committed and publish a new release with Drupal 9 compatibility. However I've also been working on some other issues like #3098494: Make H5P content libraries deployable as they come up.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

catch created an issue. See original summary.

heddn’s picture

+1 on this request

catch’s picture

Title: Application to co-maintain H5P » Offering to co-maintain H5P
falcon’s picture

Thank you for offering and working on the H5P module for Drupal.

All H5Pmodules/ plugins (for WordPress, Moodle and Drupal) are maintained by the H5P Core Team, all core team members are employees of Joubel. The maintenance of the modules/plugins are coordinated within Joubel and it would be cumbersome for us to have people outside Joubel making changes to our modules/plugins. This might change in the future.

We will soon be releasing an early version for Drupal 9.

falcon’s picture

Status: Active » Closed (won't fix)
elusivemind’s picture

Perhaps the community needs to fork it.

thomasmurphy’s picture

This seems more like a formal move to mark the module as abandoned so the namespace is preserved, rather than forking it.

sokru’s picture

Status: Closed (won't fix) » Needs review

@falcon could you please reconsider the decision. The H5P ecosystem is fantastic and it would be great addition to Drupal, but at the current state the Drupal module has a lot to improve. I appreciate the time and effort that there has been so far for H5P Drupal module, but maintaining a open-source library is not an easy task. I understand your fears for granting new maintaining rights, but if you visit @catch's profile you can see a huge commit to Drupal core. Not very likely he would add anything without communicating with other maintainers and it would be tremendous help for any contrib module to get maintainer like him.

falcon’s picture

I am are aware that catch is a living legend. We had a discussion and found that we are open to try if catch is still willing?

ryan-l-robinson’s picture

+1 on getting some active maintainers, whether that's Joubel or catch or someone else. We've been sitting on a major bug for a couple of months causing us lots of problems: https://www.drupal.org/project/h5p/issues/3299839. We've had to start the conversation about what we'll do if this module has been abandoned.

catch’s picture

@falcon so my situation is that I have a client project using the H5P module, we currently have about six patches applied. I'd be primarily interested in getting RTBC bugfixes applied, PHP 8.1/8.2 compatibility if/when that comes up, and 10.x compatibility.

I'd be happy to leave patches RTBC an agreed amount of time before committing, or if you're in Drupal slack or similar channels to ping you with a heads up before anything goes in.

Would not expect to be particularly prolific/active but for example I'd very much like to see a 10.0.0-compatible release available within a month or two of 10.0.0 instead of just before 9.5.x going EOL.

falcon’s picture

@catch thank you for your willingness to help maintain the module. You are now a maintainer. There is no need to let RTBC issues wait, but please do not make any changes to the PHP code that is common to all PHP plugins. They are in the folders "library" and "modules/h5peditor/h5peditor". If changes are needed there please reach out to paalj or me through our Drupal contact forms.

falcon’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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