YTDescGen is feature-complete; from 1.6.0 on it is maintained, not extended. Still accepted: scheduled dependency updates; fixes for high or critical CVEs and serious runtime issues; major language / runtime / framework upgrades; bug, UI/UX and accessibility fixes, and options added to or removed from the app's lists when people really need them; translation fixes; Cloudflare / Worker changes the platform forces and website incidents. - README: status, CI, Qodana and SonarCloud badges; a Project status section; Contributing and the Roadmap row follow it. - CONTRIBUTING: a Maintenance mode section, Option requests, issue and pull request rules, What We Want / Don't Want. - SECURITY, MAINTAINERS, CLAUDE.md: the policy where each one needs it. - ROADMAP: status block, a Maintenance mode section, Phase 5 and the backlog frozen. FEATURES: the extension points are frozen. - Issue forms: Feature request removed; Option request and Translation or wording fix added; Bug report and Accessibility barrier now carry the `needs-triage` label (`triage` never existed). config.yml points feature ideas at Discussions → Ideas. The PR template gains a Scope checklist. - maintenance-triage.yml closes, with a bilingual comment and the `out-of-scope` label, feature issues and `feat:` pull requests from outside contributors (scopes options, a11y and i18n stay open) and anything labelled `out-of-scope`. pull_request_target without checkout; listed under zizmor's dangerous-triggers ignore with the reason. Labels created on the repository: out-of-scope, needs-triage, i18n, option-request. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
Maintainers
Since 1.6.0 the project is in maintenance mode: no new features, only the changes listed in CONTRIBUTING.md → Maintenance mode.
Active Maintainers
@poli0981
- GitHub: https://github.com/poli0981
- YouTube (reference channel): https://www.youtube.com/@SkullMute
- Website: https://poli0981.dev/ · all channels at https://poli0981.dev/links/
- Email:
code@poli0981.dev(project) ·security@poli0981.dev(vulnerabilities, see SECURITY.md) - Areas of responsibility: all — core engine, locale management, UI, Tauri desktop shell, releases, CI/CD.
Maintainer Responsibilities
- Triage incoming issues and PRs, keeping them within the maintenance scope: the triage workflow closes feature requests from outside contributors, and anything labelled
out-of-scope, with an explanation. - Run the release process:
CHANGELOG.mdentry, version bump, build artifacts, signed tag. - Enforce the Code of Conduct.
- Review and approve locale translation contributions.
- Coordinate security advisory disclosure per SECURITY.md.
Where to Reach Us
- Bug reports, translation fixes and option requests: GitHub Issues
- Feature ideas, with no commitment while in maintenance mode: Discussions → Ideas
- Accessibility barriers: the Accessibility barrier form — see ACCESSIBILITY.md
- Vulnerabilities: privately, as SECURITY.md describes
Becoming a Maintainer
There is currently no formal pathway. The project has been solo since inception. If you'd like to help maintain a specific area — most realistically, native-speaker review for one of the AI-translated locales (JA / ES / KO / ZH / PT-BR / ID) — open an issue describing what you'd like to take on.
Persistent, high-quality contributions over time are the path. There is no application form.
Past Maintainers
None — solo project since v0.1.0.