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
Retire the mailing list and make all decisions on zulip #649
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed. cc @rust-lang/compiler @rust-lang/compiler-contributors |
@rfcbot fcp merge |
Team member @compiler-errors has proposed to merge this. The next step is review by the rest of the tagged team members:
Concerns:
Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
Per comment above, I'll mark a concern that this is waiting on unanimous approval. @rfcbot concern unanimous-approval |
adding another concern: We preferably want to have automatic sync between zulip and folks joining/leaving @rfcbot concern automatic-sync |
@rfcbot concern single-point-of-failure-via-stream-archival As I noted in Zulip, I'm a little nervous about the semi-destructive nature of Zulip's archive command. It might be good for us to have some backup mechanism for streams that are used to capture long-term decisions. (I feel email is fundamentally different here due to its distributed nature, in that we all sort of have a "shared backup", collectively...) (I'm still torn about whether to treat this as a formal concern, i.e. something that should block progress here, or just as a warniing that all archive actions need to be done with care, at least until/unless zulip adds an "undo" for archive commands...) |
@rfcbot resolve unanimous-approval |
Proposal
We already have a private zulip stream. I propose to use it for discussing things like moving a compiler contributor to the compiler team, or adding a new compiler contributor. Similar to how one can reply privately to compiler team leads on email, people should send private zulip DMs to them in case they don't want their comments visible to the entire compiler team and the compiler contributors.
Mentors or Reviewers
N/A
Process
This MCP will not get seconded, but FCPed. Unlike other FCPs, this one requires unanimous approval.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.
The text was updated successfully, but these errors were encountered: