Plugin host in Teapodo is done in two main modules:
- The Teapodo audio engine provided "plugin slots" for the application to mount plugin instances to (in a thread safe way), which is written in Rust
- The plugin format parsers to understand each plugin formats (e.g. VST3, AU) and create plugin instances from, which is written in C++ and is just a thin wrapper around JUCE
We did think about building our own plugin format parsers from scratch, but since we are really small (only 2 devs) we ended up using an existing solution for now. Maybe we will come around and do it at some point (I certainly hope we could!).
As for releasing the source code, that's definitely a possible option. We've seen some interest in the implementation of the project, and we will start by writing about it soon, so stay tuned!
This is the experience team-managed projects should have out of the box in Cloud if using kanban.
You create a kanban team-managed project and it'll pretty much be a Trello board. If you want sprints or a backlog or reports you can go into the project features page and flip a switch.
But neither supports a markup language AFAIK. They used to support Markdown but they dropped that long ago and never replaced it. Now the only choice is their garbage WYSIWYG editor.
Jira isn't great but the Confluence editor causes me more frustration than anything. And good luck getting anything in or out of Confluence with their document model.
Confluence is definitely their worst product. It's like they took the idea of a Wiki, but removed all it's good aspects and then combined it with a terrible CMS system. A competitor could just use an ancient WikiWikiWeb installation and be better.
https://rnbo.cycling74.com/