Search 404 is a wonderful and widely used module. Still, it seems the current maintainers are no more active and there are lots of issues waiting for commit or review.
So I'm willing to offer my help as Co-Maintainer to push things forward here. We're using the module in many projects in combination with search_api so we're very interested to have it working well.
Have a look at my drupal.org profile for references.
Thanks! :)
| Comment | File | Size | Author |
|---|---|---|---|
| #43 | 2025-01-30 09_01_52-project _ search404 · GitLab.png | 21.21 KB | grevil |
Comments
Comment #2
anybodyComment #3
anybodyIf the maintainers are completely inactive, of course I'd also appreciate full maintainership. Changing the title and still waiting for response.
Comment #4
grevil commentedI would also volunteer as a co-maintainer for this lovely module! :)
Comment #5
avpadernoComment #6
anybodyMoving this over to Drupal.org project ownership (2209259) after 14d without a reply.
Request should fall back to co-maintainership, if maintainership isn't an option for the currently inactive maintainers.
Comment #7
avpadernoI am going to contact all the users with the permission to administer co-maintainers/maintainers for that project.
Comment #8
avpadernoI contacted four users. This is the message I sent to the project owner.
Comment #9
anybodyThank you @apaderno. The most important point for me is, that this great project is more actively maintained again in the future :)
Many helpful improvements are ready to be integrated.
Comment #10
avpaderno(By the way, one of the maintainers logged in after I contacted them.)
Comment #11
vimaljoseph commentedHi Alberto,
Thank you for reaching out to me regarding Julian's offer to maintain Search404. While I appreciate Julian's interest and willingness to contribute. At this time, we are not looking for co-maintainers for the project.
I kindly decline the offer, but I want to thank Julian for his interest in the project and valuable contributions such as patches/fixes and suggestions.
Thank you for your understanding.
Best regards,
~vimal
Comment #12
anybodyHi @vimaljoseph,
thank you very much for your reply. My co-maintainer offer still stands. As written above, the most important point from my perspective is, that your super helpful and useful module is actively maintained.
Are you planning to invest more time in the project in the near future?
Feel free to contact me at any time, if you need co-maintainer help! As you're still active as maintainer, I'll change the title accordingly.
Comment #13
vimaljoseph commented@Julian,
Thanks for the offer. I will let you know if any help is required. I plan to put more time into making a new release in the coming 2-3 months. I also will update the roadmap so that everyone using this module knows what to expect.
Comment #14
anybodyThanks @vimaljoseph, we'll prepare some MRs for Search 404 in the meantime, trying to convince you of co-maintainership ;) :)
We can close this won't fix then.
Thank you all!
Comment #15
anybodySorry @vimaljoseph but I think we should reopen this.
We're happily using search404 since the early days, but despite your reply, the module still doesn't seem to be actively maintained.
As I saw in #190083: Seeking maintainer zyxware took maintainership years ago and I very much appreciate that and all your work on the module. Still for such a widely used module (26,610 sites report using this module) active maintainership is important. Or to say it with Spiderman's words: "With great power comes great responsibility"
So there are absolutely no bad intentions or disrespect for your maintainership and work on the module, but key features are reported to not work correctly, RTBC'd issues are open since > 6M without a reply and the list is growing.
As this is open source I'd once again kindly ask you to accept our offer to help maintaining the module. I wouldn't want to fork this great one, but if there's no progress in fixing important issues, that would be the alternative.
Perhaps @apaderno can help a bit to moderate this or we can find a good solution for both of us of any kind?
Thanks a lot in advance for your work on this.
Comment #16
anybodyPS: My offer comes for free and you can have a look at our Drupal.org profile for references, so could you perhaps give reasons for not accepting our offer to help?
Comment #17
avpadernoComment #18
grevil commentedI would also kindly apply as a co-maintainer, if that is possible!
Comment #19
avpaderno@Grevil If maintainers do not reply here, it is better to create a new issue for your offer. The answer already given is that they do not need more co-maintainers, though.
Comment #20
ressa@vimaljoseph: I can vouch for @Anybody and the rest of the good people at DROWL. They do a stellar job with the modules they maintain. See for example https://www.drupal.org/project/glossify which they recently made Drupal 10 ready, with a fresh release.
I hope you will consider adding @Anybody as co-maintainer.
Comment #21
anybodyThank you for your kind words @ressa! :) Much appreciated.
Comment #22
dasginganinjaThis module needs love. +1 for Anybody as a co-maintainer
Comment #23
grevil commented@apaderno OK, I will create a follow-up issue in the future, but having @Anybody as a maintainer would already help a lot!
+1 for Anybody as a co-maintainer.
@apaderno, should we contact @vimaljoseph once again? Or how should we proceed here?
Comment #24
anybodyAs of #13 I don't think that will happen... But in the last days there was some action in the issues again, so I'm still hoping.
Comment #25
grevil commented@Anybody, yes by @mitthukumawat, but unfortunately he isn't a maintainer.
Update: But he does work for the same company as @vimaljoseph, so you might be correct! 👍
Comment #26
avpadernoThe following is the list of who can add co-maintainers/maintainers. The first account could be a shared one.
I will update the list with an indication of when they last logged in.
Comment #27
anoopjohn commentedI have set up 'Anybody' as a maintainer on the project.
The project is maintained by the company and different developers working in the company are requested to look into these issues when they are allocated to work on this. However, I definitely do agree that the module could do with some 'love'. Hope @Anybody will be able to bring that to the table.
Comment #28
anybody@anoopjohn thank you very very much! Yes, for sure! We're using the wonderful module in all our projects, wo it's also a benefit for us.
Could you also grant @Grevil Co-Maintainer permissions? He implemented a lot of fixes in the issues and is my teammate. Or should we open a separate request for that?
This would speed things up.
Watch out for updates here in the next weeks :)
Comment #29
anoopjohn commentedYes, he has been contributing in the queue as well. Thanks @Grevil. I have also set you up as a maintainer.
Comment #30
avpadernoComment #31
grevil commentedThanks a lot @anoopjohn! Unfortunately, I'll take some time off in the near future, so I won't be too active. But I am ready to go once I am back!
Comment #33
anybodyI'm reopening this, as I was not able to contact any active maintainer to fix https://www.drupal.org/project/search404/issues/3360959 for weeks and it seems they're all inactive.
My co-maintainer role is not enough, so I'm requesting maintainer access to be able to fix that. Thanks!
Comment #34
anybody@avpaderno what can we do? Move this over to the Drupal.org project maintainership issues?
Comment #35
anybodyMoving this to Drupal.org project ownership (2209259) as of #34 for clarification. Thanks all! :)
Comment #36
avpadernoI take that in the last comments by anoopjohn, maintainer should be replaced with co-maintainer.
If the given role was effectively maintainer, but somebody changed that to co-maintainer, I would like to hear from the person who did that change.
Anyway, tomorrow morning I will contact all the maintainers.
Comment #37
avpadernoComment #38
anybodyThank you @avpaderno - I'd just like to fix things and push it forward.
Comment #39
avpadernoThis is the first message I sent. I will contact the other two maintainers right after posting this comment.
Comment #40
avpadernoI contacted all the maintainers.
The status has been changed because we are waiting for a reply.
Please post a comment after 14 days, if your offer has not been declined. It will show you are still interested in maintaining this project and it will serve as reminder an action is required for this offer.
Comment #41
anoopjohn commentedI have asked the developer assigned to this to look at the issue. Apologies for the omissions in pending issues. We will address those quickly.
@Anybody - You should already have the permission to make commits and create releases. Please let me know if otherwise.
Comment #42
anybody@anoopjohn thanks for the reply! I have permission to make commits and create releases, but now switch the base branch in GitLab - that needs the "Administer Maintainers" permission.
Also, I don't have permission to edit the project page (which is okay).
Would be great if we could fix this asap, thanks! Unsure what you're afraid of. Let me know, if I can help.
Comment #43
grevil commentedYea, the problem is, that the search404 default branch is set to "8.x-1.x", instead of "2.x":
(https://git.drupalcode.org/project/search404)
This can be quite annoying, when creating merge requests, as they automatically use the default branch as the target and this can be overseen quite easily.
Comment #44
anoopjohn commentedI have updated the default branch to 2.x
Comment #45
grevil commentedThanks! I think that would be enough for @anybody. If not, he can reopen this issue!