Repo cleanup and organization

[schneidergithub]

I would like to suggest a few ideas, but leave the decision up to the real repo owners:

1. Automatically delete merged branches (over 100 branches right now, this will cause long-term issues and only grow)

2. Automatically dismiss stale PRs, issues, etc. After a certain time limit, close and delete things that have not had any follow actions. If needed, they can be recreated.

3. Add roadmap / scrum board with auto-syncing to issues approved for work.

[1larity]

I have my vote.

[malanthrax]

Agreed.

[ChuxiJ]

Here’s my thoughts on the suggestions:

1. We need a way to automatically delete branches that have been merged and are older than one week.
2. PRs and issues with no activity or response for more than 4 weeks will be closed automatically (managed by a bot).
3. The roadmap needs further discussion. For now, we plan to organize it into three main areas:
   • User experience / entry point
   • Refactoring
   • New features

User experience (top priority)

Official iteration will start after the stable v0.1.0 release.

• Prioritize fixing known compatibility issues (quick start, installation, device differences).
• Provide multilingual documentation and higher-quality tutorials, with a proper management scheme to help users get started quickly and improve project visibility.

Refactoring

Aims to support better development and long-term growth.

• Clean up and refactor the existing codebase.
• Resolve redundancy caused by AI-generated code.

New features

• Integration with ace-step-daw.
• Improve the LoRA training experience and complete the LoRA training ecosystem.