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

Consider joining crate-ci org #22

Open
CAD97 opened this issue Feb 13, 2018 · 1 comment
Open

Consider joining crate-ci org #22

CAD97 opened this issue Feb 13, 2018 · 1 comment

Comments

@CAD97
Copy link

CAD97 commented Feb 13, 2018

cc @epage roblabla/cargo-travis#34

Would you be willing to join forces and move development of your crate to the crate-ci org?

I think this quote from killercup explains the value of a shared org:

There is no reason why so many popular crates should live in user-repos instead of in community-managed organizations (speaking in Github terms). Writing and then publishing a bunch of code as a crate one thing, but maintaining it, fixing bugs, replying to issues and pull requests, that takes up a lot of time as well. Time, that a lot of developers don't have, or don't want to invest. cargo-edit, for example, which lives under my Github username, has two wonderful maintainers, who are more active than I am. But should I create a cargo-edit organization and move the repo there? If there was a good and definitive answer, which would neither make me deal with the organizational aspects not result in accumulating lot of junk code, I'd be really happy.

You can see more about my goal for this new org on my rust2018 post

We still need to work out the governance model but you can maintain as much control over your crate as you wish.

@epage
Copy link

epage commented Feb 14, 2018

If you're interested in joining efforts with crate-ci and/or cargo-travis, let us know! I'll get write permission setup for you.

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