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
Moving repository to CLI-WG org? #71
Comments
Sounds good to me. But off course, up to @philippkeller :) |
Guys, I'm so happy that this little project of mine gets a proper home and lives its independent live in a proper "organization" - I'm all for moving! Maybe you could mention me somewhere as the starter of the project? How would such a moving be accomplished? Would you fork the project and then we would reduce this repo to only the README page pointing to the new location? |
Definitively!
No, there's a github functionality named "Transfer ownership" or something like that. That has the additional benefit that links to https://github.com/philippkeller/rexpect/ automatically get rerouted to that new location, which is really neat! What you would do is: Transfer ownership to https://github.com/rust-cli. @epage will then accept this and that's all that needs to be done on your side as far as I can see. Maybe @epage knows some more details and where that actual button is? 😆 Lets hear what @petreeftime has to add to this topic and whether they're on board! |
Under "Settings", scroll down to the bottom in the "Danger Zone" is a "Transfer" button. |
Sounds good to me! |
Okay, so it seems that everyone is on board! I think you can go ahead, @philippkeller 🎉 |
I tried to transfer the ownership to |
ah I need to only put |
Sent you an invite |
and done, I'm writing this comment now from |
🎉 awesome yall! I am taking the liberty of closing this issue then! 👍 |
Hi!
In the last meetup of the CLI WG it came up that we want to make this crate to the CLI WG org.
The benefits that we would get from that would be the increased bus factor. I know we have three or four people that currently maintain this crate, and we wouldn't even increase that number any further when moving to the CLI WG org, but we would get the option of the WG having access to the repository settings and if it happens that we (the current maintainers) are all unresponsive, the WG can install new maintainers.
Please lets have a discussion about that.
@petreeftime suggested that after the maintainership thing got cleared up, we can talk about moving to a more permanent place (#43 (comment)) ... and that's what I'm trying here now! 😆
@souze is also a maintainer IIRC and of course
@philippkeller has the final say as the owner of the repository!
The text was updated successfully, but these errors were encountered: