Tracking issue for collecting `config.toml`s and analysis of config/profile usage patterns and pain points

[jieyouxu]

Contributors often run into friction when using config.toml and profiles, and we would like to better understand the different workflows of different contributors and how contributors utilize config.toml and profiles to inform future changes and improvements.

Steps

• Identify what we want to know about (e.g. pain points, usage patterns) regarding config.toml, profiles and their usage patterns and contributor workflows.
• Figure out a mechanism to collect such info: survey? metrics initiative?
• Inform contributors that we would like to collect such info.
• Analysis of the collected information.
• Identify possible future steps and improvements/changes.