You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oh, nice, didn't even cross my mind to have this added to their wikis.
For beets, sure. I took a quick look and it seems to be as simple as just making an issue/pull request to add it to the docs.
As for VocaDB org, I'm generally fine with it, but I'd need to know what it would entail for this repo (and myself?).
For example, if it's pretty much just url change to be under VocaDB org then it's completely fine.
After looking at their GitHub org, I do also wonder if this project really fits with their other repos?
As for VocaDB org, I'm generally fine with it, but I'd need to know what it would entail for this repo (and myself?). For example, if it's pretty much just url change to be under VocaDB org then it's completely fine.
I could ask them about the implications in the pr, and whether they're interested in adding beets-vocadb to their org at all
After looking at their GitHub org, I do also wonder if this project really fits with their other repos?
It might be helpful to have people involved who are familiar with the other end of the api. All documentation I could find is the ai generated api client, which is... not very helpful, at least for me.
I got beets-vocadb added to VocaDB's wiki
https://wiki.vocadb.net/docs/documentation/services-that-make-use-of-vocadb-apis#albumsong-taggers
Should I ty for beets's wiki as well?
Also, I had the idea of transferring this repo to VocaDB's organization. I didn't contact them about it yet. What do you think?
The text was updated successfully, but these errors were encountered: