Dear users, where are we going with this project?

[seefood]

Hey my fellow users. a few weeks back I got the keys to this project after most of the original maintainers seem to have left it orphaned and PRs were becoming stale. I am no expert in Bash, I've only been a user for some 25 years when I discovered this repo, and I still would not call myself a master bash coder, just a power user.

While I have chopped down stale PRs, or adopted and merged them, I started refactoring my own dotfiles and remembered I once thought about trying zsh. well, I since discovered zinit and other fine tools and I have a feeling bash-it has simply reached the end of the line because bash is really in a feature-freeze, and zsh is where it is at. I think the maintainers before me realised it too. It seems like the only two people still active now are myself and @akinomyoga (warm thanks, Koichi-san!) and I now feel like I want to just stabilise the existing code base and mothball it, so it's still usable but doesn't have too many unfeathered or loose ends.

It is therefore my wish to try and close down any serious real issues, and not try and tackle any issues that are more about refactors and big changes, I will just let good enough alone unless something big happens (a bash v6 release?) that suddenly gives this repo an influx of new users and renewed interest, because right now all the cool kids seem to be moving to zsh or fish or whatnot.

So, your opinions please, users. do I mothball this project after stabilising it, with 3.2 or 3.3 being a last release, or does anyone feel this is not a dying shell env and needs more love? Your thoughts and help offers are called for duty.

[seefood]

in fact, I asked Claude for a summary of the open issues and PRs. I don't agree with all of the recommendations it gave but it is a start, we can discuss it from here...

Project Planning & Roadmaps

Strategic planning documents are maintained in docs/plans/:

• Quick Reference - TL;DR summary of current issues and action items
• Comprehensive Issue Analysis - Detailed breakdown of all open issues with categorization and recommendations
• 2025 Roadmap - 6-month technical debt reduction plan with phases and success metrics
  These documents guide ongoing maintenance, issue triage, and code quality improvements.