Add a batch of 3 repositories for archival #2

[Kobzol]

These repositories are not yet archived!

Repositories were selected based on https://hackmd.io/@rust-leadership-council/Bk6ge9Xu6 and usage statistics.

• https://github.com/rust-lang/governance

Extracted from GH

org = "rust-lang"
name = "governance"
description = "The home for Rust's governance documentation, such as team charters."
bots = []

[access.teams]
security = "pull"

[access.individuals]
yaahc = "admin"
pietroalbini = "admin"
badboy = "admin"
Mark-Simulacrum = "admin"
rust-lang-owner = "admin"
rylev = "admin"
jdno = "admin"

• https://github.com/rust-lang/libbacktrace

Extracted from GH

org = "rust-lang"
name = "libbacktrace"
description = "A C library that may be linked into a C/C++ program to produce symbolic backtraces"
bots = []

[access.teams]
security = "pull"

[access.individuals]
jdno = "admin"
rylev = "admin"
pietroalbini = "admin"
badboy = "admin"
Mark-Simulacrum = "admin"
rust-lang-owner = "admin"

[[branch-protections]]
pattern = "rust-snapshot-2018-05-22"
required-approvals = 0
pr-required = false

• https://github.com/rust-lang/mirror-google-fuchsia-zircon

Extracted from GH

org = "rust-lang"
name = "mirror-google-fuchsia-zircon"
description = "Zircon Kernel, Core Drivers, and Services"
bots = []

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

[access.individuals]
rust-lang-owner = "admin"
kennytm = "write"
jdno = "admin"
Mark-Simulacrum = "admin"
pietroalbini = "admin"
rylev = "admin"
shepmaster = "write"
Kobzol = "write"
badboy = "admin"

[ehuss]

I'm actually not certain about monitorbot, since I don't know what it is. I would want to check with @pietroalbini to verify.

project-deref-patterns seems to have an uncertain status. There was an attempt to actually form the group in #606, but that seemed to fizzle despite there being work done. Additionally, in rust-lang/lang-team#88 as of last week it looks like @Nadrieril is attempting to resurrect the work. I don't know if they want to try to reform the project group, or use that repo, or if they would like to proceed without it. That said, I think it would be fine to archive it now and unarchive it if t-lang and @Nadrieril want to resurrect it later.

[Mark-Simulacrum]

monitorbot is actively running (though last I checked might be broken right now). It definitely shouldn't get archived.

[Kobzol]

Ok, removed monitorbot.

[Nadrieril]

Thanks for pinging me! I am indeed resurrecting the work, let's keep the repo for now

[Kobzol]

Thanks for pinging me! I am indeed resurrecting the work, let's keep the repo for now

Archiving doesn't remove the repo, it just marks it as archived as makes it read-only. There wasn't an existing team, so I went for archival, but it doesn't really matter, we can keep it unarchived for now.

[Nadrieril]

I've restarted some design discussions so it might come useful for that

[Kobzol]

Ok :) Created this, without a team for now.

[Kobzol]

The remaining three repos should hopefully be uncontroversial to archive.

[Nadrieril]

Ty!

[rylev]

@Kobzol is google-fuchsia-zircon still used by CI?

[Kobzol]

Seems to be unused since rust-lang/rust#99833. CC @tmandry, do you know if https://github.com/rust-lang/mirror-google-fuchsia-zircon is still used? (https://fuchsia.googlesource.com/zircon itself is marked as deprecated).

[Kobzol]

tmandry thinks that it is not used anymore. I think it's safe to say that https://github.com/rust-lang/mirror-google-fuchsia-zircon can be archived.