It would be good to write down what to do with language feature requests that are opened as issues on rust-lang/rust.
Currently I close them and direct the author to the RFCs repo and the internals forum, but it would be useful to have a reference for what to do, so that we don't inconsistently enforce this. For example, I'm thinking that just transferring the issues to rust-lang/rfcs instead of closing it might be better (not that there's a big practical difference, but it might be nicer towards the issue author).
We also might want to add an issue "template" for feature requests that links to IRLO
Similar to the one for security vulnerabilities
Strong :thumbs_up: on these, I've wanted to write up a policy for a long time. FWIW I think the way to go here is for someone (perhaps you?) to write this up on forge.rust-lang.org and we can FCP it with T-lang/libs for their "areas" of feature requests, I imagine the policies might be a bit different.
Started by opening https://github.com/rust-lang/rust/pull/78161
Opened https://github.com/rust-lang/rust-forge/pull/463 to add issue triage guidelines to the forge
but rfcs repo use issues for rfcs right? might be misleading to just transfer it
They use PRs IIRC
No, the issue tracker there is basically just a wishlist that anyone can add to, so that fits
Transferring is more work than closing though, so I think we should keep closing them
Why is it more work?
Because you need to label it after transfering it?
No, because it requires more actions and a page refresh because the transfer isn't instant
ah right, got mixed up, then fine
i will assign one person from wg-triage for this as well in the next meeting (unless anyone wishes to volunteer now :stuck_out_tongue: )
Last updated: Jan 29 2022 at 11:01 UTC