mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 09:25:49 +03:00
[GH-ISSUE #264] Rename spotify_player? #1069
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1069
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 @jacksongoode on GitHub (Oct 3, 2023).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/264
This is random but its about the naming of the project. The cli/binary is called
spotify_playerwhile the project is calledspotify-player. Should the binary also be namedspotify-player?This is also a suggestion that the project might want to not use Spotify in its name as I believe its trademarked. This is more of a long term thought.
@PetrichorFlavour commented on GitHub (Oct 11, 2023):
Yes, absolutely agree. The name is not searchable at all, very hard to find this project. Just something somewhat similar to Spotify would be much better. Like Spottie, Saponify, Reticuli, Rancidify, Interstratify anything ending with -ify or contains spot would work.
@jacksongoode commented on GitHub (Oct 11, 2023):
Other short options:
@jacksongoode commented on GitHub (Oct 26, 2023):
Any thoughts @aome510 ?
@aome510 commented on GitHub (Oct 27, 2023):
Hey, thanks for the discussions guys. I'm still in favor of keeping the name as-is mainly not to create any confusion for old users.
Regarding the trademark, I believe that as long as I don't profit from the project, Spotify won't do anything (hopefully).
spotify-tuiis another project withspotifyin its name and it has been there for a while now.spotify-tuiis significantly more popular thanspotify_player.@jacksongoode commented on GitHub (Oct 28, 2023):
Would it make sense to change the binary from the underscore to the dash then? There is some inconsistency there, unless there's a good reason for it?
@aome510 commented on GitHub (Oct 28, 2023):
Agree there is some inconsistency between dash and underscore. I would avoid making such change for backward compatibility.
spotify-playershould only be used as the Github project's name. Uses in other places should bespotify_player. Feel free to make a PR to update README or other documents if you found any inconsistency in the use of the project name.@sewnie commented on GitHub (Nov 2, 2023):
in it's current state it is dead. i've been paying attention on the internet lately and have been moving a significant amount of spotify-tui users to spotify_player
@sewnie commented on GitHub (Nov 2, 2023):
related: #101
@catgoose commented on GitHub (Nov 3, 2023):
I think this project is the only option since spotify-tui is no longer maintained. If there were another project that was more like spotify-tui I'm sure it would be the favored choice over
spotify-player/spotify_player@TornaxO7 commented on GitHub (Jan 27, 2024):
May I suggest another name?
spotifyers(Pronounced: "spotif-fires!")@kensad-ops commented on GitHub (Feb 7, 2024):
May i suggest
yatsstand for:yet another tui spotify(took inspiration from yay initial through wasyast : yet another spotify-tuibut it have been taken)@sewnie commented on GitHub (Feb 7, 2024):
spirefrom Spotify and rust file extension.rs@gbostock commented on GitHub (Mar 23, 2024):
Maybe just change the name of executed binary instead of the whole project? It's a little bit annoying to start
spotify_playerin terminal. As I know, spotify-tui's command is the shorterspt.@sewnie commented on GitHub (Mar 23, 2024):
Given
sptfor spotify-tui,sp.