project-gauntlet
Open to contributions?
Found this gem while looking for a Raycast alternative, very interesting project that I'm excited for. It looks as if you're the only one currently (which, mad props for, very cool). I was wondering if this project is in the state yet for additional contributors? Might be interested to help, but wouldn't want to impose haha.
Thank you for your interest. So far, as you noticed, this has been a one man show, mostly because there wasn't anybody interested, but I am open to contributions.
Now, what those contributions could be really depends. I'd say you can just try it out, integrate in your system, see how it is, report any bugs, maybe try to fix them, see what it is missing, etc. Your profile also has NixOS specified, so you may be interested in contributing a flake, join our discord, people there have been trying to create one and there is some work already done. Right now even just cleaning up the code and fixing all clippy warnings would be a welcome contribution.
Application like this is also very reliant on the plugin ecosystem so creating a plugin would also be really valuable.
In the next week or so I will make a new release after which I will finally be able to add application to various package managers to make installation easy. I will also try to create a better roadmap and move some items from my backlog to issues to make the development more visible.
I have also created a Raycast feature parity list https://github.com/project-gauntlet/gauntlet/issues/13 with a lot of feature tasks, some smaller, some bigger. Feel free to also look at that
@Exidex thanks for the detailed response! I'll probably start by helping set up a flake when I get a chance, then browsing the source for a bit, maybe finding or picking up an issue, or simply finding a good plugin to implement. Has anyone contributed plugins before, so that I could look around them as well? Or is there a defined way to do that set up somewhere?
Also, massive thank you for the update on the issues list, can already see and understand the situation a lot better (I love GitHub tags :p).
Has anyone contributed plugins before
It is worth separating creating a plugin and contributing a plugin to Gauntlet.
When it comes to contributing a plugin, I think for now I will hold off on accepting new bundled plugins to keep the scope in check.
But for creating a plugin in general, to my knowledge nobody has created a public one yet. Documentation is scarce at the moment, the README is pretty much all there is, so please read through that. There is a plugin template you can use as a starting point. There is also the plugin i use for development which has examples of pretty much every added feature and the plugin I use for readme video demo but it is pretty basic
@Exidex this is impressive project.
i wonder if we can have a runtime/sdk to allow user to run LLM generated code/view without the need to build plugins.
this will unlock huge creativity for normal everyday users, and remove the burden from developers.
@kanielrkirby One correction to my previous message which for some reason escaped my mind when I wrote that. I do actually plan on bundling a set of plugins that are universally useful for every user. The list is documented in https://github.com/project-gauntlet/gauntlet/issues/15
I am gonna close this issue as there was no activity for some time. I am open to contributions, ~please do (˶˃ ᵕ ˂˶)~. If you have any questions, open a new ticket or ask on discord