Add www.rust-lang.org repository under automation

[Kobzol]

Repo: https://github.com/rust-lang/www.rust-lang.org

CC @dtolnay @Manishearth

Extracted from GH:

org = "rust-lang"
name = "www.rust-lang.org"
description = "The home of the Rust website"
bots = []

[access.teams]
website = "write"
security = "pull"

[access.individuals]
pietroalbini = "admin"
MarcoIeni = "admin"
senekor = "write"
Mark-Simulacrum = "admin"
rustbot = "write"
rust-pontoon-trial = "write"
Manishearth = "write"
rust-lang-owner = "admin"
jdno = "admin"

[[branch-protections]]
pattern = "master"
required-approvals = 0
pr-required = false

[[branch-protections]]
pattern = "deploy"
required-approvals = 0
pr-required = false
restrict-pushes = true
allowed-merge-teams = ["website"]

[[branch-protections]]
pattern = "try"
required-approvals = 0
pr-required = false

[Manishearth]

I should probably have admin.

I think the pontoon accounts are still used but it's been a while since I've poked at that integration

[Kobzol]

I know that it is currently only you, but perhaps we should then make it website = "admin" to keep it general?

[Manishearth]

I'm planning on growing the team soon (I'd like to add @senekor and @Turbo87) once I have a discussion with council and I don't want team membership to imply admin, though probably eventually most team members will have admin.

[Kobzol]

Ok, changed. Just out of curiosity, why is admin needed on this repo?

[rylev]

Perhaps we should note why @Manishearth needs admin rights so we can review this in the future.

This also makes me think that it would be nice to have a tool that collects all individuals with individual access to repos and generates a report that automatically gets posted somewhere every 3ish months for review.

[Kobzol]

(Marking as draft now, since sync-team doesn't set push allowances by default, which would change the branch protection on this repo).

[rylev]

I don't want team membership to imply admin, though probably eventually most team members will have admin.

I think the way we prefer to handle this is by creating a new team as a subteam which reflects these permissions.

[Manishearth]

@rylev it's for things like Pontoon and Heroku setup. Third party integrations, especially experimenting with them, often needs admin to go smoothly.

[Kobzol]

There are currently two people in the website team. @Manishearth would you be ok with giving admin to the whole team?

[Manishearth]

Yep!

[Kobzol]

Ok, I added admin access for the website team (and added an explaining comment on top of it), and added pr-required = false and allowed-merge-teams attributes to branch protections (these weren't supported when I originally created this PR).

[senekor]

I don't know why the try branch has branch protection. It's a 4 year old stale branch and its changes only have some text thanking our alumni. The website already does that, so I'm assuming the changes were merged in some way. I was cleaning out a bunch of stale branches at one point, the only reason I didn't delete this one is because I couldn't.

I think this branch protection can be safely removed.

[Kobzol]

@Manishearth Since you're an admin, if you agree that try is not useful, could you please delete it? I will then remove the corresponding branch protection from this PR.

[Manishearth]

I don't seem to have access to the branch protection rules and I can't delete it.

[Kobzol]

Right, I meant more deleting the branch itself from the repo. In any case, if you agree that the try branch isn't used anymore, I'll just remove the branch protection form this PR.

[Kobzol]

Removed the branch protection for the try branch. This should be ready now.

[Kobzol]

Oh, I just noticed that before, there was required-approvals = 0, but it isn't in the current state of this PR. @Manishearth Do you want PRs to be "self-approvable", or do you want to require approvals?

[Manishearth]

Self approvable is fine for such a small team imo

[Kobzol]

Ok, done. Now it should be ready 😆 Edit: nevermind, pr-required = false implies required-approvals = 0. I'm pretty sure I went through this already on this PR, several months ago..