Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a batch of 4 repositories for archival #4 #1390

Merged
merged 1 commit into from
Apr 5, 2024

Conversation

Kobzol
Copy link
Contributor

@Kobzol Kobzol commented Mar 16, 2024

These repositories are not yet archived!

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

Extracted from GH
org = "rust-lang"
name = "rust-reach-www"
description = "the website for the rust reach program"
bots = []

[access.teams]
security = "pull"

[access.individuals]
jamesmunns = "write"
badboy = "admin"
deg4uss3r = "write"
skade = "write"
aidanhs = "write"
rylev = "admin"
japaric = "write"
spacekookie = "write"
avadacatavra = "write"
rahul-thakoor = "write"
Mark-Simulacrum = "admin"
pietroalbini = "admin"
jdno = "admin"
rust-lang-owner = "admin"

[[branch-protections]]
pattern = "master"
required-approvals = 0
pr-required = false
Extracted from GH
org = "rust-lang"
name = "rust-semverver"
description = "Automatic checking for semantic versioning in library crates"
bots = []

[access.teams]
bots = "write"
devtools = "pull"
security = "pull"

[access.individuals]
badboy = "admin"
rust-lang-owner = "admin"
rylev = "admin"
rust-timer = "write"
pietroalbini = "admin"
jdno = "admin"
ibabushkin = "admin"
Xanewok = "admin"
rust-highfive = "write"
JohnTitor = "write"
rustbot = "write"
bors = "write"
Mark-Simulacrum = "admin"
Extracted from GH
org = "rust-lang"
name = "rustc-timing"
description = "new rustc-timing repository for freshly collected data"
bots = []

[access.teams]
security = "pull"

[access.individuals]
Mark-Simulacrum = "admin"
rust-lang-owner = "admin"
jdno = "admin"
pietroalbini = "admin"
rust-timer = "write"
rylev = "admin"
badboy = "admin"
Extracted from GH
org = "rust-lang"
name = "web-presence-team"
description = "Home of the Web Presence Team"
bots = []

[access.teams]
security = "pull"

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

@rylev
Copy link
Member

rylev commented Mar 18, 2024

I'm unsure about rust-semver as, even though it's deprecated, it's still on crates.io and has some usage. In the off chance that there's a need for a patch release, it would be annoying to have to unarchive the repo.

Also, I'm unsure about https://github.com/rust-lang/rustc-timing - are we sure that is unused?

@Kobzol
Copy link
Contributor Author

Kobzol commented Mar 18, 2024

I'm unsure about rust-semver as, even though it's deprecated, it's still on crates.io and has some usage. In the off chance that there's a need for a patch release, it would be annoying to have to unarchive the repo.

Hmm, I see your point, but in theory we could say this about almost anything that is archived? E.g. rustc-serialize was archived for some time, and probably no one expected that we will need to unarchive it, but then we still had to do a new release, so I think that this can basically happen with anything.

This crate seems to be superseded by much more popular alternatives, and I don't think that it would be very easy to do a new release anyway, since it hasn't been updated in years, and probably getting it to work on a recent compiler would be quite difficult. I think that it depends on save-analysis, which was already removed, AFAIK. Furthermore, its own README states that it is deprecated. So I would personally archive this.

Its maintainer also suggested archival here, although he wanted first to publish a release with a deprecation notice, which probably never happened (?).

Also, I'm unsure about https://github.com/rust-lang/rustc-timing - are we sure that is unused?

I haven't interacted with it in any way in the last ~2 years that I have been maintaining rustc-perf, and I don't recall seeing any code in the current codebase that would be interacting with it. @Mark-Simulacrum are you aware of any current usage of this repo?

@Kobzol Kobzol changed the title Add a batch of 5 repositories for archival #4 Add a batch of 4 repositories for archival #4 Apr 5, 2024
@Kobzol
Copy link
Contributor Author

Kobzol commented Apr 5, 2024

Mark has confirmed that rustc-timing is no longer used, to his knowledge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants