It's unfortunate that my article, that was only meant to reach fellow module developers after my messages were deleted from the VCV community, was Streisanded and misinterpreted like that. I stress the seems because it really is not entirely clear what took place. I talk regularly to the developer of Cardinal (mentioned below), which is another fork of Rack, and thus far, things between them and Andrew have remained reasonably cordial.Ĭertainly as the developer of another open source audio project, if someone behaved the way the MiRack developer seems to have done, I would likely seek to exclude them from our community too. I am not certain, but I suspect that this author acted in specific ways that upset Andrew. However, somebody then gave me a link to what is apparently one of the main threads in which they and Andrew Belt's main developer 'got into it', and after reading that I was much less certain about who was behaving badly here (if anyone). It made me reevaluate what I thought about Rack and Andrew's handling of the project. I cam across Aria's complaints about their experience as a developer within the Rack ecosystem, and I was very disappointed to read it. Being only for Apple devices makes it impractical for me to use, so moving my development to it isn’t an option, unfortunately, if it were on PC I might have done that. Any mention of it within the VCV community is immediately deleted, and its author is banned, so it exists completely disconnected from the VCV community, despite offering a smaller selection of the same modules with mobile support, which is something the community really wanted badly. > There’s MiRack, a fork of VCV for Mac OS and iPhone.

> It would be easier to continue my work if there existed a healthier fork to migrate to, but VCV has been trying to prevent forks both through legal and social means, so there’s no viable fork yet.

> That’s right: if I’m inactive for just one short little month, someone else can just go ahead and release software under my name, my name as a person, with no process in place for me to reclaim it later, even if their releases have low quality standards, even if they add ill-conceived features that work against my long-term plans. About making it possible by default for someone to take over my very name, Aria Salvatrice, and releasing their own fork of my software under my name. > The last straw concerned the policy about taking over inactive modules. Some context from a third party VCV Rack plugin developer:

Max msp audulus