> To make the most of being open-source, we believe that there should be an appropriate infrastructure for documentation and quality assessment of code contributions. Our current focus is to lay the foundation for an MVP and release a public standalone version 1 by the end of the year.
> If you want to help programming please be patient and wait for openDAW to be fully open-source. We will communicate this step loud and clear. Until then, we appreciate any feedback, testing and suggestions. Please log into our Discord server.
> Yes, the offline native app will have VST support at some point in future.
That's a pretty weak response to "why isn't your product with Open in the name open-source yet." They don't need to provide documentation or accept code contributions at all in order to release the source code they're working on.
That kind of logic gives me the impression they may not ever open-source it if they get successful enough to sell it somehow (and, if it flops, it's a coin-flip as to whether or not they get around to open-sourcing it before it disappears).
Does 'MVP' in this context mean they want to sell something as a business, or just that they want a good functioning version (like, be out of alpha stage)?
> If you want to help programming please be patient and wait for openDAW to be fully open-source. We will communicate this step loud and clear. Until then, we appreciate any feedback, testing and suggestions. Please log into our Discord server.
> Yes, the offline native app will have VST support at some point in future.
Source: https://opendaw.org (FAQ)