-
Notifications
You must be signed in to change notification settings - Fork 510
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.
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
mention S-tracking-needs-summary under "what should i work on" #2053
Comments
From the label's description: Status: It's hard to tell what's been done and what hasn't! Someone should do some investigation. So it's less about summarizing what's been jotted down or discussed in the GH thread and more about gathering information from various possibly obscure sources like Idk how easy it'd be for beginners to take on such tasks. Altho it might be easier than I think, not sure. I'd say the hard part would be to figure out the major blockers and unaddressed concerns of a given feature which past contributors have never written down in the tracking issue for various reasons (e.g. if they used to actively develop a feature, got stuck2 and then became inactive or disinterested). This is just my own conclusion based on personal observations and experiences. Footnotes
|
fair, but how easy is the rest of that list, actually? contributing to clippy can be expecially rough due to the relative lack of issue triage |
summarizing long discussions is very helpful, doesn't demand reviewer attention, and doesn't (usually) require knowledge of rustc internals, and doesn't even require writing any code.
all of this makes it a good way for beginners to meaningfully contribute to the rust project.
The text was updated successfully, but these errors were encountered: