Ben Hutchings: > On Tue, 2019-12-31 at 04:31 +0000, Ximin Luo wrote: >> Package: wnpp >> Severity: wishlist >> Owner: Ximin Luo <infini...@debian.org> >> >> * Package name : rust-spotify-tui >> Version : 0.11.0 >> Upstream Author : Alexander Keliris <rigell...@gmail.com> >> * URL : https://github.com/Rigellute/spotify-tui >> * License : MIT or Apache-2.0 >> Programming Lang: Rust >> Description : Spotify for the terminal written in Rust > > Why is the implementation language relevant for an application package? >
I just copied upstream's github repo description. > Also, including Spotify in the name might be a trademark violation. > IANAL but there's lots of other similar examples of a tool that interfaces with a service S being called "something-S-something", e.g. "calendar-google-provider". The description is pretty clear that this is not an official spotify product. If the law actually has a problem with this, I'd be at a loss to think of how we could possibly name such a tool *without* referring to "S" verbatim in the name. Prefix everything with "unofficial"? I've never seen that in any other FOSS project. > Ben. > >> spotify-tui needs to connect to Spotify’s API in order to find music by name, >> play tracks etc. Instructions on how to set this up will be shown when you >> first run the app. >> >> This app uses the Web API from Spotify, which doesn't handle streaming >> itself. >> So you'll need either an official Spotify client open or a lighter weight >> alternative such as spotifyd. >> >> If you want to play tracks, Spotify requires that you have a Premium account. -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
