Tracking Issue for RFC 3052: make the authors field optional #83227
Description
This is a tracking issue for the RFC "Make the authors field optional" (rust-lang/rfcs#3052).
About tracking issues
Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
- Implement the RFC
- cargo: stop including authorship information in
cargo new/cargo initand in templates - crates.io: start accepting crates without authorship information
- crates.io: stop displaying and serving authorship information
- docs.rs: stop displaying and serving authorship information
- cargo: stop including authorship information in
Implementation history
- start accepting crates without authorship information crates.io#3429 - start accepting crates without authorship information
- Remove "Authors" section from crate details page crates.io#3132 - Remove "Authors" section from crate details page
- RFC 3052: Stop including authors field in manifests made by cargo new cargo#9282 - Stop including authors field in manifests made by cargo new
- stop displaying and serving authorship information docs.rs#1322 - stop displaying and serving authorship information
- stop collecting author data and delete the old data docs.rs#1323 - stop collecting author data and delete the old data
Metadata
Metadata
Assignees
Labels
Blocker: Approved by a merged RFC but not yet implemented.Category: An issue tracking the progress of sth. like the implementation of an RFCRelevant to the cargo team, which will review and decide on the PR/issue.Relevant to the crates.io team, which will review and decide on the PR/issue.Relevant to the docs-rs subteam, which will review and decide on the PR/issue.