Project maintenance

[falkTX]

Hi there.
I am opening a ticket as a discussion / request for information.

Helm has not seen any updates in 3 years.
It is not possible to build it as-is with latest juce anymore.

Do you still plan on maintaining helm? Do you need help?
In case you have no more interest on it, should someone else take over?

Helm is a great synth, but also a complex one.
Compared to more simple plugins, the level of maintenance is higher, so understandable it gets sidelined a bit for other (new) projects.

Mostly I am just wondering about your plans for Helm.
Thanks in advance.

[santiagofn]

Probably the maintainer isn't reading Github issues. The only way around I see is forking the project (if there's anyone with the motivation to do it).

[unfa]

I think forking would be unnecesary and counterproductive here. The repository's ownership can be transferred if @mtytel no longer wants to maintain this project and someone else volunteers to take over.

[mtytel]

Given my work on Vital and other plugins I don't really have time to maintain or work on Helm anymore.
I'm open to the idea of someone taking over maintenance but I don't really have time to bring someone up to speed myself.

[tpltnt]

@mtytel if you want I can start doing some maintenance work (and try to implement a MIDI feature I want). To to this I need the right to push code to this repository (to avoid the unnecessary fork as @unfa pointed out). This way maybe at least some things get adjusted and you keep (full) control for now. Later we may transfer ownership if it works out.

[BilldarBagdar]

Hi everyone,

Had I been a more practical or jaded-by-hard-experience person, I might have checked the maintenance status of this Helm project before cloning the repo and attempting to build for myself.

I just wanted to avoid dealing with PayPal (even for $0). So instead I cloned the repo, updated the projucer project to JUCE 7.0.2 (development), and added a Visual Studio 2022 exporter. Then, I fixed errors (not deprecation warnings) in the source code until I got a successful Helm_VST3 build and could test the fixes in the Juce Plugin Host.

I still have further testing to perform in my actual DAW computer(s), but I was checking in here thinking about possibly contributing "work product" if it passes code review when I discovered the sad state of affairs represented by this lack-of-project-maintenance thread.

Are there any active Helm forks these days?

@mtytel Have you appointed a maintainer who isn't you since you said you were open to the idea of another maintainer last year?

[hellocatfood]

@BilldarBagdar Useful Forks shows that this fork by @DatanoiseTV is the most active fork https://github.com/DatanoiseTV/helm . Might be worth forking or contributing to that