Offering to co-maintain Condition Query

Thanks @Fernly. Super important to keep the module alive and make it D10 compatible asap!

Hi @fernly, thanks for the offer! Sorry I haven't had any time for this module.

That said, I don't add co-maintainers that I've never seen any work from. 😅 This is the first time I've seen your username in this issue queue. If you're still interested, please do some other contributions in the queue (reviewing & testing existing issues, improving them, etc). Once I get more of a sense of your approach to maintaining, I'll reconsider adding you as a co-maintainer.

Meanwhile, since the D10 issue was so trivial, I just committed it the patch and tagged 8.x-1.4. So maybe you're not going to care about this module for another 2 years (just like me). 😂

Anyway, feel free to set this back to 'Needs review' once you've got some contributions to this project that I can verify.

Thanks again!
-Derek

Understandable and no problem for me. Glad to see there is a stable D10 version. Thanks for that.
I don't have time at the moment to proof my worthiness, so this issue can be closed as far as I'm concerned.
Hopefully it doens't really take 2 years to get traction in the issue queue though ;-). But I understand there isn't always time to spare.

Kind regards,
Lennart

I don't have time at the moment to proof my worthiness

I'm sorry it landed that way. It's not about "worth". It's about your approach as a maintainer and coder, which I'm unfamiliar with.

And whoops, the link you put in the summary is pointing at condition_query, so I didn't see https://www.drupal.org/project/condition_path → and missed all that. You seem to be a careful maintainer, at least from a brief skim of the project page! And I completely relate -- I don't have time, either. 😉

Hopefully it doens't really take 2 years to get traction in the issue queue though

Whoops, that's not at all what I was trying to say. 😅 I meant given that this tiny module seems to mostly just work, and only needs another || ^X+1 in the .info.yml file every few years, that probably no one will care about this project again until then. 😂

If I close the issue, you won't be able to reopen in the future. So let's leave this in the queue as "postponed" so that you could reactivate it if you want to. Other people will also see it, and it can help to document the maintainer situation.

Thanks again for your offer! Feel free to re-open this if/when you've got interest.
-Derek

I understand what you're saying and I can relate.
We just weren't sure the module was still maintained and were trying to get things done. Mission accomplished ;-).

Leaving it Postponed is perfect in that case.

Thanks for your time!