You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should perhaps turn off issue-filing on the repo (maybe archiving existing issues by mass migrating them if necessary) and update the readme to redirect people to Internals.
The text was updated successfully, but these errors were encountered:
This issue is an item on the Core Team's public agenda, and the team will discuss it every week during the triage meeting. The goal of the issue is to provide a public record of our discussion, so only members of the Core Team are allowed to comment here.
Please get in touch with the Core Team by emailing core-team@rust-lang.org if you have something to add!
As someone who participated in the first migration... you fundamentally need to give people some scratch space. That could be internals, that could be here, whatever.
Honestly, I personally don't think internals is really used seriously by the teams; so I'd go the other way if I were running everything.
I don't super care about the specifics, just that some place like this should exist in some form.
Yeah, I think internals does function as this kind of scratch space, which the teams can pay attention to (but essentially ignore threads that are going off into weird territory).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
A-initiativeInitiative the team is working onM-triageTopic for the Core Team weekly triage meeting
The RFCs repo has a lot of open issues, but these are mostly ignored by the teams.
We should perhaps turn off issue-filing on the repo (maybe archiving existing issues by mass migrating them if necessary) and update the readme to redirect people to Internals.
The text was updated successfully, but these errors were encountered: