Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Although i think we should, drupal.org does not have a governance process for a maintainer to pledge, what energy they can and want to put into maintaining a module. So i'm starting this here. Our user base deserves to know.
Proposed resolution
geek-merlin
(2023-11) I can pledge to do maintainership duties on a regular basis, but have a tight schedule with other stuff. I currently have no additional contribution topics or itch to scratch.
I will work forward towards the stable release, but need help reviewing issues.
bojanz
(2023-11) I won't be spending time on this module at any point in the future. Feel free to remove me from the maintainers list.
dawehner
(2023-11) Always happy to talk about it, or be the fly on the wall. I am not contributing at this moment in time. Feel free to remove me from the maintainers list.
joachim
???
jsacksick
Commerce barely uses IEF nowadays, our plan is to redevelop the order items widget when the time/budget permits so we don't depend on Inline Entity Form anymore.
oknate
???
ram4nd
???
rszrama
Available for solution architecture discussion and patch review in the context of Commerce Core maintenance.
slashrsm
???
webflo
???
podarok
Was an active maintainer of v2. No need to restore access anymore
Comments
Comment #2
geek-merlinComment #3
bojanz commentedAdded my answer.
I don't think there is a way to make IEF for D8+ truly maintainable without a full rewrite. I started such a rewrite back in early 2020 but then changed jobs and mostly stopped using Drupal.
I do hope to see a 1.0 release and wish the other maintainers the best of luck in achieving that goal.
Comment #4
rszrama commentedComment #5
jsacksick commentedComment #6
dawehnerComment #7
joachim commentedI don't currently have time to give to this module at the moment. Feel free to remove me from the maintainers list.
Comment #8
podarokI'mI was actively working on this module as well as YMCA Website Services CommunityAll work will be moved to https://www.drupal.org/project/inline_entity_menu_form in Q1 2024
Please, do not remove tags of 2.x branch just yet from current module in order to avoid breaking 500+ sites.
Thank you and sorry for the inconvenience
Comment #9
podarokComment #10
geek-merlin@posarok: You have been PMed about #3401655: Revoke InlineEntityForm maintainership privileges of @podarok and the reasons stated there.
> Thank you and sorry for the inconvenience
Please elaborate for what you apologize. Trust can be re-built, but this is not for free.
Comment #11
dwwI'm not a maintainer, but I'd consider becoming one. Sounds like there aren't a lot of folks actively planning to work on this. I've often used IEF for my projects, and I'm in the middle of another build, so I've got interest in (safely) moving some things forward. Among many hats, I co-maintain address.module, so I'm familiar with high usage, high impact module maintenance with a high need for care and low disruption.
I don't want to complicate an already complicated situation. I'm happy to continue to contribute as a heavy-user-non-maintainer. But if another maintainer would be useful, I'm willing (at least for now).
Thanks!
-Derek
Comment #12
geek-merlinComment #13
anybodyStill relevant issue in my eyes, thanks @geek-merlin!
The module is very helpful and widely used, still most of the maintainers seem inactive here recently? Quite some RTBCd issues and even more to be reviewed.
Comment #14
bluegeek9 commentedI am starting to contribute to the IEF project. It is a dependency of the CRM project. As a maintainer of CRM, your bugs are my bugs.
anybody encouraged be to become a maintainer of IEF. I think it is too early for that.
I am focusing on bugs for 3.x