> a way of investigating possible unconscious bias
There's other ways to address that too. I've used https://textio.com/ in the past for job ads and it's really interesting to see examples of how seemingly minor word choices can land depending on the reader. It'd be a relatively simple task to run documentation, RFCs and Github comments of core team members through such a service and automatically generate a report (which wouldn't have to be released publicly, but could be sent to authors to aid in using more inclusive language going forward).
The thing that's really difficult to do is to be inclusive in a way that doesn't feel exclusive towards people who aren't in the target demographics. Using these types of automated tools doesn't have that downside. Has anything like this been suggested/done by the people working on Rust?
There's other ways to address that too. I've used https://textio.com/ in the past for job ads and it's really interesting to see examples of how seemingly minor word choices can land depending on the reader. It'd be a relatively simple task to run documentation, RFCs and Github comments of core team members through such a service and automatically generate a report (which wouldn't have to be released publicly, but could be sent to authors to aid in using more inclusive language going forward).
The thing that's really difficult to do is to be inclusive in a way that doesn't feel exclusive towards people who aren't in the target demographics. Using these types of automated tools doesn't have that downside. Has anything like this been suggested/done by the people working on Rust?