New Maintainer

[pfirsich]

As some have noticed, I am not very invested in this tool anymore, because I simply don't use löve anymore myself (some years). If you are interested, let me know and I will consider it.

[josh-perry]

Sure, I'll put myself up for consideration.

[hollunder]

I guess this includes maintenance of https://github.com/pfirsich/love-appimages ?

[JimOfLeisure]

A benevolent dictatorowner is one option. You might also consider creating (or having one or some of us create) a GitHub organization to host the repo. Then you have a committee of owners who can argue over policy and direction take it in turns to be paying attention to the project at any given time.

Ups and downs either way. As a devops/automation person I had half an urge to volunteer to take over, but I don't have the community creds and may not have the attention span. I'd be for being part of an organization, though.

[poeck]

How about archiving and redirecting to actively maintained alternatives?

I've just released my own tool, which basically does the same as makelove, but with a few extras.
https://github.com/simplifylabs/love-packager

[pfirsich]

@poeck It looks good at first glance, but I don't want to advocate/vouch for a tool I have not used. I have made @josh-perry a contributor now. I wanted to do a proper handover, but considering I couldn't bring myself to actually do it, I started with the more important thing.

[pfirsich]

It seems like another maintainer is needed. I am considering to put a note at the top of the README about this project being unmaintained or marking it read-only. I know that people are using it, but I don't want to spend my time on it.