Skip to content
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

Closing issues on the rfcs repo #26

Open
Manishearth opened this issue May 12, 2021 · 3 comments
Open

Closing issues on the rfcs repo #26

Manishearth opened this issue May 12, 2021 · 3 comments
Labels
A-initiative Initiative the team is working on M-triage Topic for the Core Team weekly triage meeting

Comments

@Manishearth
Copy link
Member

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.

@Manishearth Manishearth added M-triage Topic for the Core Team weekly triage meeting A-initiative Initiative the team is working on labels May 12, 2021
@github-actions
Copy link

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!

@github-actions github-actions bot locked and limited conversation to collaborators May 12, 2021
@steveklabnik
Copy link
Member

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.

@Manishearth
Copy link
Member Author

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-initiative Initiative the team is working on M-triage Topic for the Core Team weekly triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants