sntx

I'm heavily leaning towards putting the plugins into a seperate repo (all of them). The overall process for us would look like this: 1. Define how plugin repos should look...

I'll cook up an example.

I've put together [this example github organisation](https://github.com/anyrun-template-sntx). And checked it can be build and used, by adding it to my system config (c.f. [this diff](https://git.sr.ht/~sntx/flake/commit/e69e22ed21a70ab0fc5a5140478b8ccdfb85ed6a)). Please keep in mind that...

Yes, the readme looks better, than it is accurate. It's written by our favorite artificial intern, since I didn't want to invest too much time on secondary details and focus...

> I would rather preserve the anyrun_plugin create, as with some of the suggestions in other issues there is room to add more functionality in that crate to reduce code...

I'd like to contribute, feel free to invite me.

Sounds good. Well have to look into packaging `anyrun-org/plugin` quickly with [crates.io](crates.io), so that the plugin repos won't have to depend on the git repos. I've also created a [project](https://github.com/orgs/anyrun-org/projects/1)...

I've transistioned the plugins over to `anyrun-org` and added a few tasks to the roadmap/project. What do you think should be worked on next? What could I help you with?

Another thing to think about: When moving the `Kirottu/anyrun` repo to the org, should we rename it to `anyrun-org/gui` instead? Since it's mostly that, all other components were abstracted away...

> Well, the plan was indeed to move the main project to that org, but real life got in the way and in general I haven't found the motivation to...