Pietro Albini

So, I looked into this issue more, and it turns out the behavior of REUSE adheres to the SPDX 2.1 specification: > If license information for more than one license...

Opened a PR populating `LicenseConcluded`, with or without (by dropping the last commit) a CLI flag: https://github.com/fsfe/reuse-tool/pull/623

Sounds good @silverhook, thanks for the prompt feedback! I updated the PR accordingly.

Just a note, this repository will be a bit hard to move, as it serves a GitHub Pages website and rustc's CI pushes to it.

This is similar to what we're doing to use self-hosted runners in the Rust project. Our current solution of using a fork with a patch similar to this is far...

We don't plan to execute any pull request build on self-hosted runners, so a toggle to just reject all PRs (even if those are sent by owners) would be best...

Thanks for looking into this @hross! > This might be lulling you into some level of false security, since the runner config itself could be modified by some malicious entity...

> It's more about what does an inexperienced user think about a "security setting" and do they understand the implications of what you're explaining? Do we design for that (ideally...

You should create a new [team](https://github.com/rust-lang/team/tree/master/teams) (with the people responsible for arewewebyet) and [repository](https://github.com/rust-lang/team/tree/master/repos/rust-lang) (making this repo managed by our automation) in the rust-lang/team repository.

From an infra point of view, I think we can just remove the GitHub section, and have someone from T-rustdoc ping infra on Zulip when the move needs to happen....