-
Notifications
You must be signed in to change notification settings - Fork 186
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
Fork? #263
Comments
I think the plan was for Paul to nominate someone else as a maintainer so that we don't lose al issues/PR's by moving to a fork |
I don't know but when I took a look at Fork it seems like this master has been merged to michaelherger's |
NO! I only forked it as the base to apply the few changes I need for my Spotty plugin. But I have close to zero Rust experience... |
Anybody here who feels experienced enough and has time to do an official fork? |
Any clear winners here? |
At the moment there is nobody who wants to win. I'm new to Rust and I think many others too |
How about handing it into an organization of its own and invite known contributors as members. That would enable others than @plietar to approve and merge PullRequests. |
Nobody has stepped forward so there's nothing to respond to. I think that's the first step here. |
@Bebowi @michaelherger @janLo @dtcooper we've forked librespot into an organisation as a successor and have begun cleanup/implementing PR's and bug fixes. It's available at https://github.com/librespot-org/librespot |
Is michaelherger's fork the official one?
The text was updated successfully, but these errors were encountered: