-
Couldn't load subscription status.
- Fork 215
Document project groups #831
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
Conversation
This imports RFC 2856 (Project Groups) without modification (to indicate which changes will follow).
This is intended to make it easier to see specific upcoming edits instead of dealing with re-wrapping noise.
This removes anything that is framed as a proposal, or using the RFC template that is not applicable to long-term documentation.
I think it is better to first define what a project group is before showing how it works.
I'm not sure what this was for, but it was unused in the original.
These are not particularly good examples, since for example rustup is now a real team, and it's not clear what the long-term outlook is for triage.
The core team no longer exists, and I don't think there is anything additional to add here.
I don't know if it was intentional, but this ends up looking a little strange to me in how it rendered. This ensures that the lists are contained as sub-lists.
|
rustbot has assigned @Mark-Simulacrum. Use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I gave a quick proof-read, found a few typos but otherwise looks great. Thanks
Co-authored-by: apiraino <[email protected]>
This imports RFC 2856 to live here as permanent documentation for what a project group is and how it works.
This includes some minimal edits shown in the individual commits of what changes I have applied from the original RFC text.
Rendered