About the recent slowdown in development speed

[ko1nksm]

I apologize for the recent slowdown in ShellSpec development.

Due to personal priorities, other development and article writing related to shell scripts has taken precedence, and I have not been able to find sufficient time. I don't have a specific timeline for resumption yet, but I plan to resume as soon as I can.

Critical bugs will be addressed on a priority basis. Please wait a little longer.

[ko1nksm]

If you are interested in my articles, you can find it here. But it's rough writing and Japanese.

[ko1nksm]

About what I'm currently doing.

ShellSpec is implemented in a shell script, but it applies techniques from common programming languages and uses many unfamiliar techniques. These are not clearly documented and do not adequately communicate the design policy of ShellSpec.

Therefore, I am the only one who can currently maintain ShellSpec correctly, which is a big risk for the future of this project. Therefore, I am writing articles (currently only in Japanese) to spread the word about these techniques.

[nao1215]

Hi, @ko1nksm

Thank you for creating such a great tool like ShellSpec.
I have high hopes for ShellSpec. So, I put its name out in the June 2022 issue of Software Design (It's japanese magazine).
(I'm just mentioning names, not explaining how to use ShellSpec)

By the way, I am concerned about the state of ShellSpec's development.
In a future book I will write, I planned to cover the details of ShellSpec. However, The speed of development of shell specs has been slowing for more than a year. I am concerned that the development of ShellSpec will come to stop.

Would you be able to resume development by the end of this year (2022)?
Also, if I submit a PR according to CONTRIBUTING.md, will it be merged?
First, I did small bug fixes (#265). If PRs are merged, I will continue to contribute.

[ko1nksm]

Hello, @nao1215 and guys.

I apologize for not updating this project for so long. I am still working on other things, but I think I have indeed taken too much time off. I will resume TODAY.

However, the test/build environment has become outdated during the long break and this needs to be updated first. The biggest problem is that Docker's automated builds are now paid for. I applied to the Docker Open Source Program and should have been accepted, but something went wrong and it is not working.

I also want to do multi-CPU architecture support, so I decided to change to building Docker images with GitHub Actions. I would appreciate if you could wait for a few days.

[nao1215]

Hi, @ko1nksm

Thank you for your reply.

but I think I have indeed taken too much time off. I will resume TODAY.

This is one of the best answers I could have expected.
However, you remember that you have the vacation called Golden Week.
No need to rush.

[ko1nksm]

Thank you for your concern. The decision to resume the project was made by me a few days ago and this is exactly what I had planned. 😋

[billmallard]

There are more of us out here glad to hear this news. This framework is valuable.

…

On Thu, Apr 28, 2022 at 10:10 PM Koichi Nakashima ***@***.***> wrote: Thank you for your concern. The decision to resume the project was made by me a few days ago and this is exactly what I had planned. 😋 — Reply to this email directly, view it on GitHub <#216 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUT7TFK5PKVQ2JNJQ2W7OCLVHNHIXANCNFSM44VZAOVA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mikedlr]

Hi, Just came across shellspec and was thinking of using it for http://github.com/spamgourmet/spamgourmet - it looks really useful for us.

I see that in the shellspec organisation there are no public members. Is there any chance of opening that up so that other people could back you up if you find it difficulties getting going with development other people could help?

[LukeSavefrogs]

I see that in the shellspec organisation there are no public members. Is there any chance of opening that up so that other people could back you up if you find it difficulties getting going with development other people could help?

This seems like a good idea; I would love helping with the development of this framework. It helped me a lot and i would like to see it grow.

[Crown0815]

Hey @ko1nksm,
It has been a year since the last comment and I am curious about the current state of this project. We recently came across it and think it is an amazing tool to write high quality shell functions and scripts.
Are there any plans to extend the number of maintainers and/or resume development?

[kyrofa]

I have gotten a ton of mileage out of this project over the last few years. I'd be happy to help maintain it, although I'm afraid I don't speak (or read) Japanese.

[ko1nksm]

Folks, I am very sorry that I have neglected this project. I have not abandoned this project. I promise to resume this project in a few days.

Future plans are as follows:

1. Adding tests in the latest environment
2. Fix broken CI
3. Fix some minor problems
4. Next version (0.29) release

After that I will work on some PRs and Issues. Thank you for your patience.

P.S. I have recently created a repository that showcases shell scripting technologies used as the basis for ShellSpec. Please take a look if you are interested.

[kyrofa]

Great to hear, @ko1nksm. If you need any help with those I'm standing by. Especially the CI and docker bits.

[sagiru]

Yea, that's great to hear. Maybe someone else will join to help.

Regards
Sascha

[LukeSavefrogs]

I have not abandoned this project. I promise to resume this project in a few days.

That's great!

I'll be happy to be of any help (already submitted a PR). 💪🏻

[ko1nksm]

Thanks, guys. Maybe I will ask for some help. But first I need to remember what I need to do.