-
Notifications
You must be signed in to change notification settings - Fork 12
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
Passing on maintainership #12
Comments
I'm happy to chip in occasionally, but I have no Rust, so I'm unlikely to be useful for technical issues. |
If no-one else wants to do this (@carols10cents ?), I'd be prepared to take on maintainership, although I'd very happily defer to someone else! |
My interest is mostly because crates.io uses license-exprs to validate uploaded crates' licenses, so this crate is important Rust infrastructure. I'm happy to have someone else maintain it, and now that it's under rust-lang-nursery there are more folks who can help manage permissions and such :) I'm going to create a license-exprs team, invite wking and ltratt to it, and give yinz permissions to maintain this repo :) |
@withoutboats when you have a chance, could you add rust-lang-nursery:cargo and rust-lang-nursery:license-exprs as owners on crates.io? |
added cargo, only a member of a team can add it so i couldnt add license-exprs |
That's very strange. Does the crate owner really have to join a team before they can add the team as a team-owner? We may need a crates.io admin to get the crate unstuck. Also, from the docs it seems like this project will need at least one named owner to manage access. @carols10cents, would that be you? I'm also ok with making everybody with write access a named owner of the crate ;). |
Actually, it looks like we need someone with the rust-lang-nursery owner bit (list here) to unstick this for us. |
@withoutboats I added you to the license-exprs team, sorry about that, so you should be able to add that team as an owner now. You can also/instead add me as a named owner if you want :) |
Any update on maintainership of this repository? I would love to use this library for parsing of licenses in I'm also more than willing to help maintain this library if you are still looking for more maintainers. |
I'm happy to review, and I have the commit bit here, but I don't have much Rust experience. I also still don't have push access to this crate on crates.io, which makes me merging things here not all that useful ;). @withoutboats, can you run: $ cargo owner --add carols10cents or: $ cargo owner --add wking so one of us becomes a named owner authorized of further crate administration? Alternatively, can someone with crates.io admin access make that happen directly? |
Any update here? I have a crate I wish to publish with a SPDX 3.1 license, and it appears to be blocked on someone pushing a new version of license-exprs to crates.io. |
I have added the |
That's probably enough for me to be able to push new releases, but we need a named owner to manage ownership (e.g. if another team should be added or removed later). @withoutboats, can you make either @carols10cents or myself (or both of us) a named owner? |
Added both of you as owners, didn't realize there was a restriction on team owners |
I don't have the time & interest to maintain this crate anymore, it would be awesome to have other people figure out how to distribute maintainership responsibilities.
cc @carols10cents @wking @ltratt
The text was updated successfully, but these errors were encountered: