Looking for maintainer

[moxley]

Hi everybody, I'm the owner of the ruby-test project. I haven't actually used ruby-test in a real-world situation in over a year.

I still use Atom, and I do testing, but I write very little Ruby code these days. The primary backend language at my work is Elixir.

If you're curious, this is my testing workflow: 1) Test file open in Atom, 2) Cmd+Shift+P to open Atom's command pallet, 3) Find "Editor: Copy Project Path", 4) Cmd+Tab shift to an already-open terminal, 5) Type mix test , paste the test file path, and hit Return. If you think that's a lot more complex than hitting Cmd+Ctrl+T, you're right. The thing is, these days, my job is about 70% management, 30% coding, and I'm having to do a lot of context switching, and I don't have the availability to work on longer-term projects, where getting my editor super customized would be a concern. So, the above workflow is fine for me for now, and it works in other languages too.

This does not bode well for the project. At least not with me as the primary maintainer.

If you've excited about ruby-test and you've contributed to it before, consider taking over the project, or at least taking on pull request and issue response duties. If you are interested, come talk to me via Twitter direct message: https://twitter.com/moxicon.

Thank you!

[nolanpro]

Hey @moxley . Looks like your atom-ruby-test is still in wide use and very useful. I too have switched over mostly to VSCode from Atom however I have some time on my hands now and would be glad to take over as maintainer (I'm the guy that added platformio TTY a few months back). Let me know what you think. Thanks!

[moxley]

Hi @nolanpro, thanks for offering to take over maintenance. Please contact me via Twitter direct message (https://twitter.com/moxicon), where we can work out the details.

[nolanpro]

@moxley I'm unable to DM you from my twitter (https://twitter.com/nolanpro). Maybe it's because you're not following me but not sure since I don't use twitter all that much. Thanks!

[moxley]

I'm still looking for a maintainer. I sent an invite to @nolanpro for repo access years ago, but they did not accept it.