-
Notifications
You must be signed in to change notification settings - Fork 2.6k
docs(contrib): Expand the description of team meetings #15349
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 both includes the information for more people to attend while framing the purpose of the meeting to set appropriate expectations.
1ccfe14
to
3b5c6b5
Compare
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.
Thanks for the the write-up!
For discussing contributions, [Office Hours](../process#mentorship) would be more appropriate venue. | ||
|
||
[t-cargo-rfcs]: https://github.com/rust-lang/rfcs/pulls?q=is%3Apr+is%3Aopen+label%3AT-cargo | ||
[cargo-status-tracker]: https://github.com/orgs/rust-lang/projects/47 |
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.
Is the FCP project automated? Should we link to https://rfcbot.rs/ instead?
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 pulled the link from the meeting notes.
@ehuss, any preferences?
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.
The FCPs are only updated once a week by my script.
I'm fine with leaving it linked to the project tracker, though either is fine.
[t-cargo-rfcs]: https://github.com/rust-lang/rfcs/pulls?q=is%3Apr+is%3Aopen+label%3AT-cargo | ||
[cargo-status-tracker]: https://github.com/orgs/rust-lang/projects/47 | ||
[i-nominated]: https://github.com/rust-lang/cargo/labels/I-nominated-to-discuss | ||
[s-team-input]: https://github.com/rust-lang/cargo/labels/S-needs-team-input |
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.
This is nice! I didn't know labels have their own URL route.
Update cargo 10 commits in 307cbfda3119f06600e43cd38283f4a746fe1f8b..a6c604d1b8a2f2a8ff1f3ba6092f9fda42f4b7e9 2025-03-20 20:00:39 +0000 to 2025-03-26 18:11:00 +0000 - fix(package): update tracking issue for `--message-format` (rust-lang/cargo#15354) - docs(contrib): Expand the description of team meetings (rust-lang/cargo#15349) - feat(package): add unstable `--message-format` flag (rust-lang/cargo#15311) - feat(complete): Added completion for `--profile` (rust-lang/cargo#15308) - Uplift windows Cygwin DLL import libraries (rust-lang/cargo#15193) - do not pass cdylib link args to test (rust-lang/cargo#15317) - fix: revert the behavior checking lockfile's VCS status (rust-lang/cargo#15341) - Temporarily ignore cargo_test_doctest_xcompile_ignores (rust-lang/cargo#15348) - docs: fix typo in the "Shared cache" section (rust-lang/cargo#15346) - Fix some issues with future-incompat report generation (rust-lang/cargo#15345) r? ghost
What does this PR try to resolve?
The goal is to make Cargo team meetings more inviting. This PR includes both the information for more people to attend while framing the purpose of the meeting to set appropriate expectations.
How should we test and review this PR?
Additional information