Closed oyvindln closed 4 years ago
Sounds possible, definitely interested. Having more dependencies under a single organizational structure does makes sense to me also due to bus factor. The customary configuration would be publish for the publish team while keeping your access the same as project lead, and contributor acess to the git repository itself. Does it sound like a favorable way to setup publishing, repo access otherwise we could slightly differ from that?
That sounds good to me.
You could use this issue from imageproc
as a short guide to the transition. One main point is that permissions for a team can only be added by a team member but otherwise it should be straightforward.
Okay, so I add the image-rs team + you and fintelia as owners of the crate, and transfer the repo to image-rs?
That's how I understand the process. Here is some more information on adding owners. As soon as the crate is under the organization the rest of the setup will be done by administrators. I'm not completely sure if you need to be part of the image-rs
organization to move the repository, you'll get an invite in any case if you want.
It seems I need to have permission to create repositories under image-rs
. I presume I would need to be invited to ìmage-rs` and given permission to create a repository. The permission can be remove once the repo is transfered.
Right, I forgot. Invite should be sent now, it's not a problem, quite the opposite if you've basically contributed a whole crate to the org :)
Okay, the repository is transfered. I wasn't sure what to set on the permissions page though, so you may want to change that if needed.
I've also (tried at least) invited image-rs:publish as an owner on crates.io
Don't know if that works directly, you need to invite me directly so I can add the team. I think teams can only be added by a member of said team.
Before I forget, if you have the time you can also add a project page to the image-rs
overview. There is no particular guide (yet) but other projects (in the _projects
and _summaries
directories) should give a rough overview of the structure and we can sort the rest out in PR/draft comments.
Just a small idea here: should we now try to merge the inflate
and deflate-rs
crates so that we can have one crate that does both DEFLATE compression and decompression?
Would you be interested in/okay with taking ownership of deflate as well? It's used in png decoding together with the inflate crate that is already under the image org. I dislike being the sole person with commit access to it, and since inflate is already hosted here I think it would make sense to move that one here as well.