I started a new job at Automattic last week (WordPress-focused, not Drupal), and my wife and I are expecting a baby at the end of May. Consequently, I took a hard look at my available free time for volunteer contributions going forward, and concluded that I won't be able to continue maintaining Drupal 7.
My plan is to continue with it for the next month or so, to help transition and hopefully get another Drupal 7 release out, etc.
It's been a pleasure! (Hard to believe I've been doing this for nearly 6 years now.) And I'll still be involved with Drupal, so I'll certainly still see people around the issue queues, etc.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 2959509-2.patch | 507 bytes | David_Rothstein |
Comments
Comment #2
David_Rothstein commentedHere is a patch. Will plan to self-commit this around a month or so from now, as described above.
Comment #3
quicksketchThank you David! You've been a source of calm, thoughtful feedback for thousands of Drupalers during your core maintainership tenure. A comment or review from you has always been a little present of awesomeness that makes our shared software better. Good luck in your new venture, they are very lucky to have you working on WordPress!
Comment #4
klonosThank you so much for all your hard work David! ...all the best with your new job, and with becoming a dad (join the club :) )
Comment #5
David_Rothstein commentedAw, thanks for the nice comments, @quicksketch and @klonos!
Comment #6
ayesh commentedCongratulations on the new job and baby! Thanks for all the awesome contributions to Drupal too, and hope you'd rock Wordpress too!
Comment #7
David_Rothstein commentedThanks, Ayesh!
Comment #8
mcdruid commented@David_Rothstein thank you for all your contributions as a core maintainer! and congratulations on your news.
You mentioned that you hoped to "get another Drupal 7 release out".
Do you have any idea how likely that is (considering your shifting commitments etc..)?
I'm wondering if it's worth filing a follow-up issue to track the fact that there are now quite a few commits in the 7.x-dev branch which have not yet made it into a release; only security releases since 7.55 around 11 months ago, AFAICS.
I'd be happy to file that issue, but it might be a bit redundant if you've already got it covered.
Comment #9
robpowell@David_Rothstein it was great working with you. I wish you best of luck in your new adventure.
Comment #10
joseph.olstadThanks @David_Rothstein, you did a fantastic job.
Comment #11
joseph.olstadDavid, one last request, before you go, can you please commit these ;P ?
looking forward to running php 7.2 asap.
and also this one:
#2900373: [D7] When a theme has a managed_file field and a submit callback, call to undefined function error is thrown.
:) pretty please
Comment #12
amateescu commentedThank you @David_Rothstein for all the work you did on Drupal throughout the years and for being an inspiration to many of us in the community!
Comment #13
damienmckennaThank you, David, for all of your contributions over the years, good luck with your new gig - they're very lucky to have you!
Comment #14
polThanks David, good luck for the future!
If you look for someone to help in D7 maintenance, just let me know.
Comment #15
joseph.olstad+1 to add Pol as a D7 core co-maintainer/maintainer.
Comment #16
manuel garcia commentedThanks for all the work @David_Rothstein, and best of luck in your future adventures :D
also +1 to add @Pol as maintainer
Comment #17
David_Rothstein commentedSorry, I wasn't paying attention to this issue for a while. Thanks for the nice comments in the meantime!
It happened, but unfortunately it wound up having to be (yet another) security release that month, whereas I had hoped I would do a regular release. I didn't have time for both.
I'll see if I can manage to spend a little more time helping with a non-security release or two. I'm on paternity leave now, so it depends on how often the baby naps :)
Looks like it happened in the meantime - https://groups.drupal.org/node/521072 - congratulations!!!
Comment #18
damienmckennaDavid: do you still intend to work on core or can we RTBC this?
Comment #19
David_Rothstein commentedLooks like I never came back to follow up on this issue :(
I definitely can't do the role of a release manager these days, so it's fine to remove me. Maybe better to handle this as part of #3088938: Update the D7 maintainers list though, since it looks like that issue is focusing on what to do with all the "old" names on there at once. (I'm still on the security team, etc., and if it makes sense for me to stay on the list as some kind of emeritus maintainer who could help out in certain situations, I guess I'd consider that. But for the most part, I don't have much time right now.)
Comment #20
joseph.olstadHi David, none of us can assist with this action as none of us currently have access (unless you do it yourself), it's been 5 months without a commit in core (10 May, 2019), I'd sure love to pick up from where you left off (either by committee as a team or individually).
Thanks again for the support and your numerous important contributions that we've all benefitted from and continue to benefit from!
Followup to this:
#3086286: Offering to maintain Drupal core (@joseph.olstad)
#3088836: Rejuvenate D7, a need for more time spent committing and RTBCing Drupal 7 issues
#3088557: Volunteering as a D7 core committer (@mcdruid)
#3088696: Offering to maintain Drupal core - promote Pol to full committer
Comment #21
damienmckennaI don't think this needs to be cross-linked quite that heavily.
Comment #22
damienmckennaComment #23
brankoc commentedWith 3088938 having been committed, I believe this patch no longer applies. Does this issue still need to be open for something?
Comment #24
webchickNope, that's true, this was handled as part of the other issue.
Thanks so much for all of your wonderful years of contributing to Drupal, David! I've learned immensely from you and hope things are going awesome for you on the other side of the pond. :)