mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 00:05:55 +03:00
[GH-ISSUE #95] Fork? #82
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#82
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/95
Thursday Oct 26, 2017 at 14:57 GMT
Originally opened as https://github.com/plietar/librespot/issues/263
Is michaelherger's fork the official one?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Thursday Oct 26, 2017 at 14:58 GMT
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
@sashahilton00 commented on GitHub (Jan 29, 2018):
Thursday Oct 26, 2017 at 15:00 GMT
I don't know but when I took a look at Fork it seems like this master has been merged to michaelherger's
@sashahilton00 commented on GitHub (Jan 29, 2018):
Thursday Oct 26, 2017 at 15:05 GMT
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...
@sashahilton00 commented on GitHub (Jan 29, 2018):
Thursday Oct 26, 2017 at 15:09 GMT
Anybody here who feels experienced enough and has time to do an official fork?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Wednesday Nov 29, 2017 at 18:57 GMT
Any clear winners here?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Wednesday Nov 29, 2017 at 19:54 GMT
At the moment there is nobody who wants to win. I'm new to Rust and I think many others too
@sashahilton00 commented on GitHub (Jan 29, 2018):
Wednesday Nov 29, 2017 at 20:00 GMT
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.
@sashahilton00 commented on GitHub (Jan 29, 2018):
Wednesday Nov 29, 2017 at 22:37 GMT
That's where I'm at too, re: just learning rust. Not a bad idea, @janLo. Is @plietar responding to any librespot noise at able to do that?
@sashahilton00 commented on GitHub (Jan 29, 2018):
Thursday Nov 30, 2017 at 02:49 GMT
Nobody has stepped forward so there's nothing to respond to. I think that's the first step here.
@sashahilton00 commented on GitHub (Jan 29, 2018):
Monday Jan 29, 2018 at 00:02 GMT
@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
@ComlOnline commented on GitHub (Jan 29, 2018):
We're in the new fork.