[IMPORTANT] Future of this Module / H5P

Created on 6 May 2025, 11 days ago

The aim of this thread is to obtain clarity about the future of this great module. At the moment of writing 3,922 sites report using this module. Can the people running these sites keep using it, or should they start looking for alternatives?

Please note that I do not mean to blame anyone: Everything on Drupal is the result of volunteers and we should all be very grateful to the contributors of H5P. Nevertheless, it feels to me that clarity is needed, as people rely on this module, and this module seems to be slowly dying.

The facts seem to be:

  • At the moment of writing there are 251 open issues / 113 bugs.
  • Version 2.0.0 is in alpha since nov 2021
  • Module has status 'Seeking co-maintainer(s)'
  • Patches are not merged
  • The h5p PHP integration library seems barely maintained and has PHP 8.3 issues
  • The roadmap on the H5P.org website ends in 2023
  • The company behind H5P has been purchased by a large LMS vendor last year.

Nevertheless

  • Falcon (the project owner) seems to be positive about H5P staying Open Source
  • Shaundychko created a fork ( https://www.drupal.org/project/h5p/issues/3499799 🌱 Temporary fork supporting latest versions of dependencies Active ) which seems to work for people.
  • Several people opted for (co)maintainership.
  • I contacted Falcon and he indicated he is planning to hand over project ownership anytime soon

How do we move on from here? My proposal for the 2.0 version would be

  • Wait for falcon to hand over the ownership, update the list of maintainers
  • Aim for PHP 8.2. Of course 8.3 would be better, but our experience is that many contrib modules are not yet ready, so many folks won't able to use 8.3.
  • Let Shaundychko's version become the next dev version.
🌱 Plan
Status

Active

Version

2.0

Component

Miscellaneous

Created by

πŸ‡³πŸ‡±Netherlands koosvdkolk

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @koosvdkolk
  • πŸ‡¬πŸ‡§United Kingdom catch

    I was added as a co-maintainer in #3236765: Offering to co-maintain H5P β†’ which was originally won't fixed

    If we look at https://git.drupalcode.org/project/h5p/-/commits/2.0.x then the handful of commits I've made to the 2.x branch since then are almost the only commits that have happened.

    So I agree that more clarity would be good:

    1. Will https://h5p.group/ commit to maintaining this module (Drupal 11 compatibility etc.) over the next few months?

    or

    2. Can additional co-maintainers be added?

    (these aren't mutually exclusive).

    I do have an limited amount of work time to look at H5P issues that affect our client, but that is not nearly enough to be the sole active maintainer on the project.

  • πŸ‡ΊπŸ‡ΈUnited States ongdesign Portland

    Thanks for starting this thread! I do think it's pretty important that we target D11, as the current release, and thus PHP 8.3. My colleague sim_1 and I will be spending some time looking into it, since our company relies on the module for a number of client projects. Shaundychko's fork seems like a good place to start!

Production build 0.71.5 2024