Creating a public roadmap to guide community contributions

[yukazakiri]

Hi everyone,

First off, thank you @snowarch for the hard work on this project!

As the project continues to grow, I wanted to open a discussion about the possibility of establishing a Project Roadmap.

Currently, there are a lot of great ideas in the issues and discussions, but it can be a bit challenging for contributors (especially newer ones) to see the bigger picture or know what the maintainer is prioritizing for the upcoming releases.

The Proposal

I suggest we create a public-facing roadmap. This could be as simple as a ROADMAP.md file in the repository, or utilizing GitHub Projects to create a Kanban-style board linked to our issues and pull requests.

Potential Benefits:

• Alignment: Keeps everyone on the same page regarding the project's direction and short/long-term goals.
• Contributor Friction: Makes it much easier for community members to find relevant tasks to pick up, knowing they align with the current focus.
• Reduced Duplication: Helps prevent duplicate feature requests by making planned features highly visible.
• Transparency: Gives users and developers a clear idea of when to expect major changes or architectural shifts.

I’d love to hear the maintainer's thoughts on this.