-
Notifications
You must be signed in to change notification settings - Fork 5
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
configure crates.io owners? #60
Comments
I'm noticing that I didn't know about this group, sounds good It would be cool if something in the cookiecutter template dialog just printed at the end like "template created, please remember to add mobilecoinfoundation:cratesio as a crates.io owner when you publish" |
I got the same error with that one:
|
Yep, as discussed, the ideal case is to have this happen with release automation, but let me add you to the Edit: You've been added now (we were adding folks on an "as-needed" basis). |
One other thing I'll note: only user accounts can add/remove owners on crates.io, that's why we've got myself, nick, and eran as owners for the sgx crates. |
One issue is, when you cookiecutter out a repo like this and
cargo publish
it for the first time, you will be the only owner, and the only one who is authorized to put it on crates.io.Then, if such a person leaves the company, it may be impossible for us to publish any later versions of it on crates.io if we can't get a hold of them.
You can see owners on crates.io pages like here: https://crates.io/crates/aligned-array
For instance, with
aligned-array
, I made sure I addedmobilecoinofficial/eng
as a co-owner so that if I get hit by a bus, the show can go on.It would be nice if something in the cookiecutter template would prompt people to do this, otherwise a lot of people will likely forget. I almost forgot this with
mc-rand
just now.One issue I also ran into with
mc-rand
just now is:So I am not actually authorized to add coredev to repos that I create -- it might be that James or Nick or someone has to be in the loop for this process. Or I guess I can give mobilecoinofficial/eng ownership over repos in mobilecoinfoundation?
The text was updated successfully, but these errors were encountered: