Looking for maintainers

[cordx56]

We are currently in need of more maintainers for RustOwl.
At the moment, the maintainers are my friends, but they are not specialists in Rust, VSCode, Neovim, or Emacs.

I can take care of the Rust code and the VSCode extension myself, but I don't have enough time to learn other domains or provide sufficient support to users on my own.

If you're interested in, please leave a comment here or contact me via email.
Priority will be given to those who have already contributed to RustOwl.

[EncodePanda]

I'm happy to document the Emacs experience (installation, usage)

[github-actions]

🤖 Bot: Issue has not seen activity in 30 days and will therefore be marked as stale. It will be closed in 7 days if no further response is found.

[MrDwarf7]

Know my own way around Rust very comfortably and fairly knowledgeable about Neovim (Though certainly no Tpope or Folke) - Anything in particular that's on the horizon/roadmap?

[cordx56]

@MrDwarf7 Thank you for reaching out to us!

We don't have any roadmap. We don't have enough knowledge of OSS development to create something like that. There are some issues which have not been resolved. And all the maintainers are so busy with reviewing PRs.
Can you help us? We especially want to know how to organize our project.

[MrDwarf7]

@cordx56 - I'll aim to look at the issues tomorrow. Seems many of them are already completed and waiting on merges though. I can have a look into a solution for #160 if it's not already resolved. Otherwise I can look at an implementation across the board on Err handling and error visibility as that seems to be a big one and should make reported bugs easier to locate and fix too.