Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add announcement for metrics initiative #1378

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

Add announcement for metrics initiative #1378

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f2c7cb7
Add announcement for metrics initiative
yaahc Aug 12, 2024
ff9654f
Update posts/inside-rust/2024-08-12-announcing-metrics-initiative.md
yaahc Aug 15, 2024
1b0f437
Update posts/inside-rust/2024-08-12-announcing-metrics-initiative.md
yaahc Aug 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions posts/inside-rust/2024-08-12-announcing-metrics-initiative.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
---
layout: post
title: "Announcing the Metrics Initiative"
author: Jane Losare-Lusby and Esteban Kuber
team: The Rust Compiler Team <https://www.rust-lang.org/governance/teams/compiler>
---

We ([Jane](https://github.com/yaahc/) and [Esteban](https://github.com/estebank)) are excited to announce the start of the Metrics initiative, an **opt-in** and privacy-preserving system for recording various metrics and metadata from Rust compiler invocations. These metrics can then be optionally uploaded by Rust users to provide us with useful information about how Rust is being used in the wild.

We're envisioning three use cases for metrics within rustc.

* Supporting feature development
* e.g., answering specific questions such as when the old and new trait solvers diverge or helping identify and resolve bugs before impacting users
* Guiding improvements to User Experience,
* e.g., knowing which compiler errors are causing the most confusion or are hit the most frequently, focusing on improving those first, and verifying that the improvements help
* Improving perf feedback loops and insight,
* e.g., helping identify pathological edge cases, similar to [work](https://nnethercote.github.io/2022/02/25/how-to-speed-up-the-rust-compiler-in-2022.html) @nnethercote has done manually in the past

We're at the point of the initiative where we would like to inform the project members about it and start implementing the metrics infrastructure in collaboration with their real-world needs.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussion: would we want to explicitly mention here that the initiative fully intends to respect user privacy (i.e. no automated uploads / networking)

NO TELEMETRY, NO NETWORK CONNECTIONS

as mentioned in the tracking issue?

Copy link
Member Author

@yaahc yaahc Aug 13, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My preference is to direct people to the tracking issue and keep the blog post as concise as possible.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's incredibly important to mention this in the first sentence in the blog post. If we don't say this clearly, people will get the wrong impression. Most people won't care enough to read the tracking issue or anything other than the blog post, and they shouldn't get wrong impressions from it.

Copy link
Member

@Noratrieb Noratrieb Aug 13, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For example,

to announce the start of the Metrics initiative, a privacy-respecting way to get user feedback.

"metrics" sounds very ambiguous

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've applied the suggested wording from @Kobzol below which I believe resolves this concern


For more information about the initiative, please check out the tracking issue and related links: https://github.com/rust-lang/rust/issues/128914.

**Please reach out with any use cases you have in mind!**
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: we probably want to make clear that we actively want and appreciate users to register their concerns, feedback and suggestions, and not just what the metrics infra could be used for.