- 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!
- π³π΄Norway paalj
Hi,
@sim_1 and @ongdesign: I have added you as maintainers with the following permissions:
- Write to VCS
- Maintain issues - π¨π¦Canada ydahi Waterloo, Canada
Thanks all for your recent efforts.
Can I suggest that we organize a meet in the coming months to plan the near and far future for this module?
There is a Slack channel for #h5p, maybe we can organize there (or anywhere else).
Topics might include:
- Roadmap to beta-1 / rc-1
- Roadmap to 2.0
- Future of this module and open source h5p
- Schedule for regular meetings