Older documentation. Start with the current guides.

Adoption and Sustainability

Adoption and sustainability

Go Micro does not collect mandatory runtime telemetry. Application prompts, payloads, service names, source paths, credentials, agent conversations, and business data must never be collected for project analytics.

Signals

The project uses privacy-preserving, aggregate signals that already exist:

Any future CLI reporting must be proposed separately, be disabled by default, be disclosed before use, document deletion and disable controls, and collect only coarse version/platform/command-category data. It must not be a condition of using the framework.

Quarterly review

Maintainers should publish an aggregate review when enough data exists to avoid identifying respondents. It should cover:

Sparse data should be reported as unknown rather than inferred. Survey answers are voluntary, and maintainers should not publish small cohorts that could identify an organization.

Use the repository’s Production user survey issue template to collect the voluntary inputs and the Quarterly adoption review template to publish a report. A review period should be named as YYYY-QN; unanswered fields remain Unknown, and free-form responses must be aggregated rather than reproduced. The first period is 2026 Q4: maintainers track the voluntary survey and aggregate review in public.