Tracking issue for collecting `config.toml`s and analysis of config/profile usage patterns and pain points
Open
Nobody has claimed this yet.
A-bootstrap-config
C-tracking-issue
E-needs-investigation
T-bootstrap
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue checklist and define the questions to answer about config.toml, profiles, contributor workflows, pain points, and usage patterns. Determine a collection mechanism such as a survey or metrics initiative, communicate it to contributors, analyze the results, and document possible future improvements; no source files or tests are named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100