xinjian0101
57993f8a3e
Add maintainer ownership, governance, roadmap, ecosystem and adoption documentation, release and security processes, Dependabot, structured adoption reporting, and automated maintainer-health checks.
1.6 KiB
Adoption and Usage Evidence
Continuity Director does not include telemetry. Adoption evidence is collected only from public GitHub signals or information users choose to submit.
How users can report adoption
Use the Adoption report Issue form and provide only information you are comfortable publishing:
- Operating system
- ComfyUI and Python versions
- Installation method
- Workflow category
- Nodes used
- Optional public project or workflow link
- Optional compatibility notes
Do not include private workflows, credentials, personal information, private model links, or proprietary production assets.
What maintainers may publish
Maintainers may summarize:
- Verified public adoption reports
- Public GitHub stars and forks
- Public release download counts
- Issue and pull-request participation
- Compatibility environments reported by users
- Repository traffic and clone trends without identifying individual visitors
No user count, download count, organization claim, or production claim should be published without a verifiable source.
Current baseline
The project is in maintained preview. Automated validation covers Python 3.10–3.12, ComfyUI lifecycle import, unit tests, frontend smoke tests, and installable-package validation. Real-world compatibility evidence is tracked separately from automated test coverage.
Maintainer review cadence
Adoption and compatibility evidence should be reviewed during the monthly roadmap review and before each public release. Material findings should update README.md, ROADMAP.md, release notes, or the support matrix.