rust-lang
Sprint planning for "Improve contributor experience"
Meeting proposal info
- Title: Sprint planning for "Improve contributor experience"
- Type: it's complicated
Summary
We agreed at end of 2020 to have some sprints (I think two weeks long?) dedicated to the problem of improving the contributor experience.
It would be good to have a meeting where we lay out the specific focus areas for such sprints, and figure out when to hold them (in terms of when we expect stakeholders and experts to have the most time available to contribute).
About this issue
This issue corresponds to a meeting proposal for the compiler team steering meeting. It corresponds to a possible topic of discussion. You can read more about the steering meeting procedure here.
Comment policy
These issues are meant to be used as an "announcements channel" regarding the proposal, and not as a place to discuss the technical details. Feel free to subscribe to updates. We'll post comments when reviewing the proposal in meetings or making a scheduling decision. In the meantime, if you have questions or ideas, ping the proposers on Zulip (or elsewhere).
We had the meeting today. I should have announced its scheduling back when we scheduled it. But I can still make up for that, maybe, by posting about what we determined during the meeting itself.
The public zulip archive will serve as our record for this meeting: https://rust-lang.zulipchat.com/#narrow/stream/238009-t-compiler.2Fmeetings/topic/.5Bsteering.20meeting.5D.202021-01-29/near/224479767