#metabrainz

Fin.

LordSputnik: Go.

This week we released a new BookBrainz into the wild! Release went fairly smoothly, and I set up replication of MusicBrainz area, gender and language tables once per day too. Had some issues with new constraints we've introduced on the database, which meant that I had to change some blank alias names/sort name and identifier values to dummy values. But nothing lost, since they should never have been blank

anyway.

CatQuest reported some issues with BB. I *think* the big issues he's seeing are easily fixable, and stem from the new Object.assign syntax not being converted to something older browsers can deal with. If he's around we can try a quick fix tonight. However, this doesn't affect any of our officially supported browsers - http://bb-user-guide.readthedocs.org/en/latest/....

^ actually Leftmost already diagnosed that earlier, but I hadn't read the logs back then ;)

I've now started looking into MB OAuth for BookBrainz login, and that's also working reasonable well. At the moment I can authenticate visitors to BB with their MB logins, and I've written some prototype code to link existing BB user accounts to MB accounts. Just needs to schema changes to add a new column to store the matched MB user.

I'm hoping to submit a patch to MB to add the editor ID field to the /userinfo endpoint, but my personal sandbox on Rika is out of date and broken, so I'll probably do it on my own desktop. (as a side note, if someone could nuke my sandbox and set up a shiny new one, that'd be very much appreciated)

zas: very nice

fin.

stanislas: Go.

LordSputnik, poke me about that later and I'll see if I can figure it out.

Or not. And kartikgupta0909 and armalcolite aren't here.

rahulr: Go.

Okay.

Worked on picard design a bit, basically the info dialogs.

Currently am working on displaying cover art changes in main window. Will propose a PR soon.

Freso, he was out of the channel when you said that.

Besides that, last week was super busy with college assignments and quizzes (all the deadlines hit me pretty bad).

that's all. fin. :)

Leftmost: Oh.

stanislas: Go. :)

No excuse now. :)

Okay then.

adesh: Go. :)

I started working a bit on CB-203

Tried to update and fix CB-36's PR and CB-198's PR

CB-36 PR has some weird issue

( https://tickets.musicbrainz.org/browse/CB-203 )

Couldn't successfully fix either of the PRs :/

done

( And https://tickets.musicbrainz.org/browse/CB-36 and https://tickets.musicbrainz.org/browse/CB-198 )

should i always attach the URL too?

adesh: Naw.

Hopefully we'll Soon™ get a bot to do it.

adesh: there used to be a bot, Freso is just standing in

okayy

Anyway, that's it for reviews!

thanks Freso :p

And we're not even a half hour in!

:o

Freso: Bot CoC!

I've made some slight changes to our Bot Code of Conduct as per our discussion two weeks ago.

I've put the revised version at https://gist.github.com/Freso/980691714a227fc1a... (original: https://musicbrainz.org/doc/Code_of_Conduct/Bots )

I believe all points that were brought up in the discussion on the forums ( https://community.metabrainz.org/t/rfc-revised-... ) have been resolved.

Any objections to adopting this?

Anyone approving of adopting this?

Freso: looks good to me

+1 to adopting

Alright then.

Freso: HTTPS!

Freso: 1/1 votes for adopting, I guess that's a majority ;P

Incl. me it's 2 of 2 votes. :p

Per the ticket, the reason we stopped requiring/forcing was because Picard didn't support HTTPS'ing. AFAIK Picard does HTTPS by itself now, so it would probably work now.

It it time to implement this?

zas bitmap chirlu?

re the bot stuff I haven't read all the changes but what I saw lookedgtm

same for me, looks ok

:)

Can other relevant clients access the WS via HTTPS?

Jaikoz? :p

Kodi should maybe be reached out to.

I'm pretty sure beets can.

I think it would be good to test picard with the minimum supported versions of pyqt and python just to make sure nothing there causes any problems

Blog about it and ask for feedback?

LordSputnik: Alright.

And also maybe contact the developers of any clients we know about besides Picard

Do we have an extensive list somewhere (on the wiki)?

Freso: at minimum I'd go with the affiliate taggers plus beets

zas: Perhaps you can grep the logs for what clients are using /ws/?

check all the official libraries, e.g. libmusicbrainz, etc.

And maybe acoustid uses the WS?

probably better to check the libraries than individual clients

Perhaps we can make musicbrainz.org/(!ws)/ go HTTPS and let /ws/ sit as HTTP+HTTPS for some time yet?

individual clients that we suspect aren't using the official libraries should be notified tho

(actually acoustid uses a local DB IIRC)

zas: ^

Freso: yes

Yes, AcoustID has an mbslave-run DB.

we can try making beta https-only first too so clients have something to test against

Would any object to making non-/ws/ HTTPS-only and then we can blog and contact devs about possibly making /ws/ HTTPS only later on?

bitmap: +1

*anyone

what Freso suggested sounds fine too I think

Yes; we'll do it on beta first

thought /ws/js should also be https if the site is

*though

Doesn't that already use // links?

possibly, yeah

But resolution is fine in general and we can see if we stumble over something while implementing it?

sounds fine in general

👍

Motion carried then.

Freso: PYMB!

https://tickets.musicbrainz.org/browse/PYMB is not used; they use GitHub for ticket tracking. alastairp said earlier: "I think I asked for it be created... Maybe 6 years ago?" and said it was fine to delete it.

Any objections?

Fine ;) it shouldn't be change anything :P

Not at all.

I just like to ask before doing what amounts to a destructive edit.

(The name changes I did without asking first could easily be reverted, it will be somewhat more work to restore PYMB once I delete it.)

Okay, I guess motion carried again then.

Freso: ISNIs!

After 2½ years of nothing happening, we have started up talk again about becoming an ISNI member. So yay for that. :)

We have also been offered a recent dump of the ISNI database, if anyone wants to write a bot or something to scrape the data and add it to MB.

Do anyone want to write a bot or something that gets the data into MB? :)

Or have any other questions about ISNI stuff? Not sure how much I can answer, but some stuff maybe. :)

I.e. the existing MBIDs in the ISNI database?

I would assume that they're part of the dump, yes.

Freso, I'm curious what our obligations are and how we benefit, but that might be a bit broad of a question for the meeting.

Leftmost: Yes, and I'm not sure what obligations would be, but I understand that one benefit would be API access.

I'll have them send the dump to info@meb and we (me, reo, ruaok) can forward it if someone steps up and wants to look into it, so just let us know.

Anyone have any final comments?

;)

I'm thinking it might also be interesting for BB.

Definitely.

Alright, let's close up the meeting then.

Thank you for your time. :)

</BANG>

With more than 12 minutes to spare. :)

I felt the reviews ran much smoother today.

Agreed.

If I want to update my bio on the MeB site, who do I submit that to?

chrisskye and zas got a bit pressed for time, but otherwise it seems like everyone had enough time and we managed to get them done in less than half an hour.

Leftmost: https://github.com/metabrainz/metabrainz.org/pulls ;)

You mean I have to learn how to use git? Boo!

^ I'll do it for ya if you wanna be lazy ;)

Leftmost: Yeah, we haven't switched that project over to Mercurial yet. Soz.

I miss the days of CVS. Didn't have to worry about all this branching and pushing and pulling. You just wrote your changes and committed!

"I miss the days of CVS" <--- not me ;)

All this modern “version control” stuff … I don’t know, you only need the most recent thingy, don’t you?

zas, it's typical that I have to tell my coworkers how much I love git a couple times a day.

Interactive rebase before push, good branch management, cherry-pick, format-patch, bisect...

The more I use it, the more I love it. Like vim.

:)

i remember when i first used git, that was on the ELinks project, because Pasky (Petr Baudis) was patching this almost abandonned project that was Git at this time and was contributing to ELinks as well, and we started to use it for ELinks sources (and it was awful... at the start), that was back to ... 2005 (see http://elinks.cz/download.html : "Note, as of

2005-09-15, the ELinks CVS interface has been obsoleted. We have moved to GIT, ..."

RCS++