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

Maintenance: Consider moving to an organization #227

Closed
azriel91 opened this issue May 16, 2019 · 7 comments
Closed

Maintenance: Consider moving to an organization #227

azriel91 opened this issue May 16, 2019 · 7 comments

Comments

@azriel91
Copy link
Contributor

azriel91 commented May 16, 2019

Hiya @tomaka,

Thank you for this crate -- it provides one of the fundamental capabilities to the Rust ecosystem. Wondering, would you be open to making rodio a community maintained project? If so, I'm thinking https://github.com/rustgd (though I have yet to ask, but they're not far away ..and I've just joined).

@tomaka
Copy link
Collaborator

tomaka commented Jun 8, 2019

I wouldn't be against this, but the multitude of possible organizations it could be moved to makes it difficult to choose.

@azriel91
Copy link
Contributor Author

azriel91 commented Jun 9, 2019

Oh ya, the rustgd org members agree that RustAudio is more appropriate 🙂.

@erlend-sh
Copy link

The community is in agreement that RustAudio would be the best home for rodio (and by extension cpal as well imo).

As a relative newcomer to the Rust ecosystem in recent years I’m in awe of your involvement with so many fundamental libraries @tomaka 👏 🙏

As there’s only so much of you to go around, I’ve been thrilled to see the likes of winit/glutin mature into a more widely distributed community effort, driven forward by an organized team of core contributors.

I hope to see the same happen with rodio/cpal, and I’m confident it can, given how established and active the RustAudio community is.

@tomaka
Copy link
Collaborator

tomaka commented Aug 9, 2019

Done.

I don't really know how the RustAudio organization is organized, so I only gave write access to the people in the "Owners" team. Let me know if I should change that.

@est31
Copy link
Member

est31 commented Aug 9, 2019

@tomaka it's fine with me (one of the three people in that team). I personally think that rodio is a great addition to the RustAudio group of crates. The audrey crate which is a bit an alternative to this never really took traction, while this one is quite popular in the gamedev community (of which I'm a part too).

As for @mitchmindtree and @piedoom : are you fine with the move, as well?

@piedoom
Copy link

piedoom commented Aug 10, 2019

I think it's great! It seems as though the pattern is to give owners permissions and then add collaborators or team members (of which tomaka is already a member on this project). So everything looks to be in order :) though I am unsure if it grants you the ability to add collaborators.

I'm very grateful for the work you and the contributors put into this project!

@azriel91
Copy link
Contributor Author

Thank you very much 🙇‍♂️!

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

5 participants