Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.In #3401657-11: Maintainership energy status survey @dww stated:
I'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.
Comments
Comment #2
dww+1 😂
Comment #3
geek-merlinAfter thoroughly reviewing derek's profile and issue acitity, i see many points for an no points against him being capable and a win for maintainership. Waited some time for other opinions, but none.
So finally: Welcome on board, derek! And the obligatory: With great power comes great responsibility!
Feel free to PM me about stuff here. Also see #3417658: Add @dcam as issue gardener.
Do you like to schedule a telcon / vcon to sync expectations?
Comment #4
dwwYay, thanks! Absolutely familiar with great responsibilities. I was root on d.o's servers for over a decade. 😅
I'm super slammed in the short term, and timezones are probably going to make a synchronous conversation a challenge. But I'm open to trying to make that happen sometime in February. Maybe we can do some Slack DMs to coordinate and leave this issue fixed.
Regardless, excited to try to help out on this very important module.
Thanks again!
-Derek
Comment #5
geek-merlin@derek:
Great!
> timezones...
Well, as CxO my chef sometimes allows me to work US-times (west coast) ;-)