LordSputnik: if one were adamant to run bookbrainz-ws, how would one go about doing that. (asking for a friend)
2017-04-09 09944, 2017
LordSputnik
justharshal: It's quite difficult now... You'd need to either create your own database using bookbrainz-schema and populate it yourself or get hold of a really old database dump
2017-04-09 09944, 2017
justharshal
Is it possible to get an old dump?
2017-04-09 09916, 2017
LordSputnik
You can pretty much see the ws output formats anyway if you take a look at the bbws/structures.py file
2017-04-09 09917, 2017
justharshal
LordSputnik: I was trying to better understand the existing webservice
2017-04-09 09935, 2017
justharshal
LordSputnik: what would you suggest
2017-04-09 09939, 2017
LordSputnik
I might have an old dump but I can't promise anything, will have a look for you today
2017-04-09 09954, 2017
justharshal
LordSputnik: thanks
2017-04-09 09925, 2017
kyan has quit
2017-04-09 09903, 2017
Freso
Is WolframAlpha not using MB data yet?
2017-04-09 09905, 2017
Freso
I've tried to run some queries based on https://www.wolframalpha.com/examples/Music.html but with people I know are in MB, but it doesn't recognise the names. (At first I thought it was hyphenation and Danish characters throwing it off, but even "rune barslund" or "baltic crossing" doesn't register.) Or do I need to feed it MBIDs directly?
2017-04-09 09905, 2017
Freso
Hm. Looks like it does use MB, but only for things that are also in WP, maybe? :|
Perhaps make a plugin API version 1.9.9 that plugins can be ported to as we go, since the final 2.0.0 API is in flux?
2017-04-09 09947, 2017
Freso
And it seems WA doesn't even pick up all artists with a en:WP page...
2017-04-09 09949, 2017
samj1912
Ugh, tests are failing because of py2.6 😐
2017-04-09 09954, 2017
samj1912
Freso: didn't get that
2017-04-09 09931, 2017
amanmehta joined the channel
2017-04-09 09923, 2017
arbenina joined the channel
2017-04-09 09902, 2017
Freso
samj1912: The 1.9.9 version thing?
2017-04-09 09927, 2017
samj1912
yup
2017-04-09 09943, 2017
Freso
Right now if we port plugins/develop new plugins against the master/2.0 branch, there is a chance that the plugin API might be changed to be incompatible before final Picard 2.0 is released.
2017-04-09 09958, 2017
Sophist-UK
Freso: Yes - that is true, however I just think we should give users and plugin-authors a warning somewhere.
2017-04-09 09932, 2017
Sophist-UK
We shuld probably warn on the page that links to the daily builds that they are alpha quality.
2017-04-09 09957, 2017
Freso
My point is not the current status.
2017-04-09 09941, 2017
Freso
My point is that once Picard 2.0 is released, there might be plugin API 2.0.0 plugins in picard-plugins:2.0 that are actually made against an earlier and no longer compatible version of the 2.0.0 plugin API.
2017-04-09 09904, 2017
Sophist-UK
Yes - I get you. But I think we are over complicating things here.
2017-04-09 09907, 2017
Freso
I don't care that right now things may be broken.
2017-04-09 09914, 2017
Sophist-UK
EXACTLY.
2017-04-09 09941, 2017
Freso
But I do care that they're not when 2.0.0 is released. Which is why I think we should use another plugin API version for the 2.0 development.
2017-04-09 09952, 2017
Sophist-UK
The 2.0 API should be stabilised by the time we get to Beta - and in the mean time stuff is so fluid that people have to expect to change stuff.
2017-04-09 09905, 2017
Freso
Exactly.
2017-04-09 09906, 2017
Sophist-UK
What we have to decide is where the responsibility will lie for: a. Porting plugins over to Picard 2 and b. Maintaining them if the API then changes.
2017-04-09 09939, 2017
Freso
a. + b.: whomever feels like it.
2017-04-09 09956, 2017
Sophist-UK
An obvious example is that if we switch to WS/2 JSON, any plugins that process WS responses will need to change.
2017-04-09 09903, 2017
Sophist-UK
Ok.
2017-04-09 09907, 2017
Sophist-UK
Sounds good to me.
2017-04-09 09908, 2017
Freso
Sure.
2017-04-09 09922, 2017
Freso
Which is why it would be good to use a plugin API version like 1.9.9 now.
2017-04-09 09904, 2017
Sophist-UK
I am about to start migrating some of my plugins - I don't mind which, but I will need to know.
2017-04-09 09905, 2017
Freso
So if someone gets updated to Py3 and Qt5 but doesn't make the WS switch (or other changes that might come later), the plugin API will still reflect that it's not the final 2.0.0 API.
2017-04-09 09913, 2017
Freso
*somee
2017-04-09 09917, 2017
samj1912
Sophist-UK: currently its my responsibility to port plugins to qt5/py3
Happy for you to do most of mine - BUT I want to work on Title Case and Artist Abbreviation plugins - so if you could leave those until I have done so that would be good.
its the output path for the json file, didn't change that, it was named that way in the previous generate.py
2017-04-09 09932, 2017
Freso
Leo_Verto: Apparently I can't SSH from here. :( I have a fixed picard-plugins-v2-git PKGBUILD, but I can't push it until Friday or Saturday.
2017-04-09 09951, 2017
CatQuest
is there a way to edit fix versionsafter ticket has closed? it's not good to eopen and then close again old tickets just to retroactivly apply a fix version
2017-04-09 09906, 2017
Freso
(By which time samj1912's gh:PP79 has likely been merged and I'll have to make more changes to it. :))
2017-04-09 09923, 2017
Freso
CatQuest: You should be able to just change it, no?
