I think it is pretty obvious that there is interest from this community in a Rust LV2 crate, at least to be able to create safe LV2 plugins in Rust, and also maybe in the mid/long-term as a backend for an API-independent plugin interface.
Therefore, I’m making this topic to discuss how we should integrate the development of this crate into this community. Feel free to ask more questions than the ones I’ve raised here!
Note this is not a topic to discuss the LV2 crate’s implementation or design decisions however, I’ll make another topic for that.
While I have a bunch of ideas for the implementation of the LV2 crate (and designing stuff is what I really like to do), I don’t want to be the only maintainer. First because of the bus factor issue, and also because I cannot be always available to maintain the project, mainly due to my job and other real-life issues.
Obviously I first suggest @Janonard to join in as a co-maintainer, since he already made his initial implementation of an LV2. But if somebody else wants to step up and join, feel free!
Source code hosting
I really want this crate to be a community effort in the middle-to-long-run, so I think it would make sense for it to be hosted under the Rust-DSP github group, alongside the
vst crate for instance.
Are there any oppositions to this idea?
LV2 Crate on crates.io
The last issue I wanted to tackle is the fact that, as @Janonard already mentioned in his reddit post, there is already the lv2 crate on crates.io. However it is not maintained anymore, and it seems to not be very advanced (the creator themselves presents it as a “beginner’s programming exercise”).
Perhaps we could contact the author and ask them to give the crate’s ownership to this group?
Otherwise we would have to name the crate
lv2rs, which I believe is a bit of an antipattern in crate naming (and looks quite ugly in my opinion), though it isn’t that big of a deal in the end.