Is this still maintained?

[favoretti]

Is the tool still actively maintained?
If not - I'd be happy to take it over (whether by forking or otherwise). We do use it, it's quite handy, but it needs a bit of TLC (updates, new platform binaries, stuff like that).

Don't wanna blatantly steal, so anyone from maintenance team still around by any chance?

[sgreben]

On it now. Sorry about the long wait!

[sgreben]

Ok, so this is in a somewhat more decent shape now.

The question of maintenance does still remain - there's really not much time i can put into this on a regular basis. Since I'm not actually using this at work right now it's entirely on-top of everything else for me.

@favoretti I'd be happy to have some support on this of course! What do you think should be tackled next? From my POV: the issues/PRs related to recursive/nested modules seem most important to look at. The features have been requested repeatedly by now & people have contributed several approaches.

Mainly I'd like to avoid going too far into fragile-bloat territory. Ideally we have a minimal feature set, but one that is solid & can be kept that way with minimal effort (because it's not like anyone will ever be getting paid to work on this).

[favoretti]

@sgreben We are using this at work, so I'm happy to contribute. That said - I'm usually time impaired as well, as we all are, but I guess two time impaired people are better than one? :)

Totally agree on keeping feature set lean. It's a great tool that does one thing really well, lets keep it that way :)