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

Move Repository To rust-lang #33

Open
XAMPPRocky opened this issue Oct 29, 2019 · 3 comments
Open

Move Repository To rust-lang #33

XAMPPRocky opened this issue Oct 29, 2019 · 3 comments

Comments

@XAMPPRocky
Copy link

Hello, the current rust-lang-nursery organisation is considered deprecated, and the Rust Programming Language organisation is trying to consolidate managing Rust's GitHub organisations, as such we'd like you to consider moving your repository to the main rust-lang organisation instead.

How Do I Move To rust-lang?

You most likely won't be able to transfer your repository directly, if so you'll need to transfer your repository to @Mark-Simulacrum, who will then move your repository to the rust-lang organisation.

Deprecating

If you no longer intend to maintain this repository, please let us know and we will take of deprecating the project.

@evils
Copy link

evils commented Jan 30, 2021

hi, i got a bit annoyed at seeing warning: only one of 'license' or 'license-file' is necessary

it seems this issue is at the root of that,
there doesn't appear to be anyone taking care of this repo,
#34 has been left unmerged long enough to have gotten out of date
because of that the license i'm using isn't supported by crates.io, which means i should supply the license-file,
but removing a package.license entry from my Cargo.toml with an OSI approved license's SPDX identifier feels like a step in the wrong direction...

@evils
Copy link

evils commented Feb 22, 2021

@rust-lang-nursery is there anyone that can step in here?
this repo seems significantly neglected
which seems to be a blocking issue for @thedavidmeister at #34
and a minor annoyance for myself
i cannot imagine we're the only ones affected, but actually finding that this repo is the cause of the symptoms isn't straightforward, so it's probably significantly under-reported

@XAMPPRocky
Copy link
Author

cc @Mark-Simulacrum

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

No branches or pull requests

2 participants