mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 08:05:57 +03:00
[GH-ISSUE #999] is this project even alive? #442
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#442
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 @sewnie on GitHub (Jun 17, 2022).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/999
there has been no commit since November of last year, many issues and pull requests has been made but nothing has been done since.
@Rigellute hellooooo...?
@aromeronavia commented on GitHub (Jun 22, 2022):
Me and my friend @drarbego wanna keep adding stuff to this. Maybe we should fork?
@sewnie commented on GitHub (Jun 22, 2022):
you can try.
just post it on a r/unixporn and everyone will be coming in like crazy if it offers something more to this dead project@aromeronavia commented on GitHub (Jun 23, 2022):
We can play around https://github.com/aromeronavia/spotify-tui
@aromeronavia commented on GitHub (Jun 23, 2022):
Bring your issues with that repo and we can start experimenting 👍 also, we can make a discord for communication about this
@sewnie commented on GitHub (Jun 23, 2022):
the only issue is an outdated rspotify. it would require rewrite of spotify-tui, i would love if that can be changed, which is why we need a discord so i can hear about progress.
sure i suppose.
@drarbego commented on GitHub (Jun 23, 2022):
Maybe we can start by checking the issues and pull requests in this repo, so we either send our own PRs to a fork fixing stuff and/or encourage people to send PRs to a fork.
@viridivn commented on GitHub (Jun 29, 2022):
@aromeronavia you should consider enabling issues in your fork, see here
@sewnie commented on GitHub (Jun 30, 2022):
looking at @aromeronavia 's fork. i see nothing changed other than just a text change.
@Rigellute commented on GitHub (Jun 30, 2022):
Project update: #1000