Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I find myself reviewing / fixing a bunch of update.module issues these days. I'm basically maintaining it once more. I'm willing to make it official again, so we can remove another ? from MAINTAINERS.txt
Wonder if @tedbow wants to join me. They're definitely the other logical choice.
Comment | File | Size | Author |
---|---|---|---|
#17 | 3116804-17.do-not-test.patch | 498 bytes | dww |
Comments
Comment #2
dwwComment #3
heddn+1 from me. Derek is the ideal choice.
Comment #4
tedbow+1 from me. I have worked with @dww on series of critical issues recently on the update module and they just got committed 🎉. Thanks for volunteering!
Thanks for saying so! I have thought about this and still thinking on this. Will let you know
Out of scope but we should create an issue to change this to the same name as in update.info.yml 😜
Comment #5
dwwThanks, @heddn and @tedbow, for the kind words and votes of confidence.
Re: #4: Sounds good. ;) #3116909: [PP-1] Change "Update UI" to "Update Manager" in MAINTAINERS.txt
Comment #6
benjifisher+1 from me.
I have worked on some of the recent issues mentioned in#4. Derek has valuable long-term knowledge of the system, attention to detail, and works to get feedback and buy-in as needed. As #4 shows, Derek is always ready to file the needed follow-up issue, not just do the fun part of writing the patches.
Comment #7
benjifisherThree votes in favor, none opposed. For good measure, I actually looked at the patch. Let's update the status of this issue.
Comment #8
jungle+∞ from me to @dww, my mentor :)
Comment #10
Krzysztof DomańskiRTBC++
Comment #13
SpokjeI wonder, what's holding this one back from being committed?
Comment #14
xjmHi @Spokje, we were doing some work with @dww to improve communication, patch review, and issue management, and wanted to make sure we had a good team for the Update module. And it has gone well!
@dww has done great work this past year, so if he is still interested I think we can go ahead with this appointment. We also want to make sure to appoint @tedbow at the same time so that the component has a good maintainer balance.
Thanks @Spokje and of course @dww!
Comment #15
tedbowOffering to help too #3218346: Add tedbow as a maintainer for Update module
Comment #16
tedbowComment #17
dwwGreat, thanks all around! Last I heard, @tedbow declined the invite. Happy to see that changed! Since #3218346: Add tedbow as a maintainer for Update module is RTBC without a patch, and since #3116909: [PP-1] Change "Update UI" to "Update Manager" in MAINTAINERS.txt seems best, let's just take care of it all with the least committer effort and fix it all here.
Yay,
-Derek
Comment #20
xjmAlright, I'm OK with the updated scope here. Normally these should all be three separate issues despite the merge-conflict-y-ness, but since all three are committable as far as I'm concerned, we don't need to do the busywork of a series of three commits with three tedious patches. :)
Committed to 9.3.x and 9.2.x. I didn't backport it to 8.9.x because we're putting that branch in security-only mode now.
Thanks @dww and @tedbow for volunteering for this!
Comment #21
dwwThanks, @xjm! You had also said: "We also want to make sure to appoint @tedbow at the same time..." so 1 patch seemed the easiest way to do that.
Anyway, huzzah! 1 more ? gone from MAINTAINERS.txt! :)
Comment #22
tedbowthanks @xjm!
Whoops, about not providing the patch on the other issue 🙃
Yay, on removing the "?" from maintainers.txt.
Congrats @dww, looking forward to working with you
Comment #23
webchickThanks so much, both! This is a particularly important '?' to eliminate. :D