Notes from #MetaBrainz Meeting 2017-08-14

[Freso]

MetaBrainz Meeting 2017-08-14

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

• Reviews
• UX design opening discussion

Reviews

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

• Worked with Quesito to make lodging arrangements for the summit.
• Worked with Samj, Param and Chhavi to make visa arrangements.
• Started, but didn’t finish some LB code reviews.
• Discussed the KEXP situation with various people, trying to find a better way forward.
• Ate a lot of dutch snacks and saw many cute things in little Amsterdam, but didn’t do a lot of work.
• Back to BCN tomorrow.

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

Worked on statistics for LB this week! Opened a big PR, which calculates statistics for users, not ready to merge yet but close. Link: https://github.com/metabrainz/listenbrainz-server/pull/244
Did some more work on stats too, but it isn’t committed or pushed yet.

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

This week I worked on fixing the sentry error which was due to sqlalchemy’s autoloading and sending update queries. Working on this also solved (partially) CB-130.
Also, completed the PRs for using direct database access for artists and events (all five entites are finally done \o/).
Also, made modifications to the PR to sort the release groups of an artist by release year (putting release groups with no release year at the end) which is a step for solving CB-80.

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

not much, just doing loads of debussy.
will try to work on more instruments too

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

worked on getting picard-plugin-tools online the CLI is up and running and can now be used to package stuff via the new manifest plugin thing we have going on
will be working on its integration with picard next

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

Usual server maintainance, security upgrades mostly
Queen was rebooted, after bunch of upgrades, in an attempt to fix an issue we have with one container (mb website vs redis), but it didnt help, no clue atm
Also worked with samj1912 about last step of his GSoC project, that is mainly plugins V2 stuff
We had unusual traffic on the website during saturday’s evening (EU time), due to some stupid scraper, issue on my radar, i’ll take proper measures if it gets out of control
It caused significant load on bowie (db server), showing a potential lack of caching related to tags queries, we’ll see with bitmap if there’s something to improve

@Quesito

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Quesito

last week I did the usual supporter emails, et all.
I also helped with airBnB’s and visa stuff for the summit. AirBnB’s are booked. and thanks to our BDFL hopefully the visa letters are set!
I also spent some time working on MeB foundation paperwork, of which still needs some help.
and then i got to meet some of the team out with ocharles and gemma! which was very lovely!

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

did support and classical editing, mostly
Also reviewed the whole KEXP issue with ruaok a bit, and I’m now trying to translate the visa request letter into acceptable Spanish
I’m planning to deal with some style soon, I see hibiscuskazeneko has a lot of things she wants me to look into

@Gentlecat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Gentlecat

not much apart from CB reviews
yesterday worked on some improvements for CAA redirect
got a better error tracking now and some other things
tried debugging an issue in CB which causes it to not work with the spotify api properly
upgraded jenkins and sentry

@psolanki

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@psolanki

I continued the frontend work, facing some problems but will be resolved soon
Finding the right plugin
ws and docs part still to do this week

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

nothing to share but a wise advice: do not smash black kitten with a mirror under a ladder, and to bitmap: back.

@ListMyCDs.com

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ListMyCDs.com

Almost the same story as on last week. Testing and fixing some issues. Some cursing with Perl. In next couple of days I will also add Less/CSS style which is basically a copy of the style of edit search.

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

I mostly worked on bringing back selenium (browser automation tool) so we can write proper UI tests again
there’s a PR up that still needs work
I also worked on alt. tracklists, but was making a lot of changes that became very tedious to test. so, I wanted to write some basic UI tests first, and switched to selenium stuff

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

I’ve almost caught up with the meeting notes I’ve been behind.
Only last week’s and tonight to do now.
I dealt a slight bit with some editor reports. Still all the “heavy” ones to deal with though.
Oh, and I also has drinks and dinner with former MusicBrainz dev ocharles, his girlfriend, and Gentlecat and Quesito. That was a lovely evening. Had ocharles and SO visit the office the day after.
Other than that, just catching and keeping up with IRC and forums.

UX design opening discussion

IRC Logs for #metabrainz | MetaBrainz Chatlogs

Introducing @chhavi, a bachelor student of design, who’s recently been poking at some mockups for improving the UI/UX of MusicBrainz. One of the mockups she’s made so far:
https://goo.gl/HgJ4oq

Some discussion about how to decide on a final new UI/UX for MusicBrainz and the workflow for going forward with it.

It was proposed that we should have a session during the upcoming summit (which @chhavi will attend) where we could hopefully agree on how to approach this.

Another proposal was to have a half hour meeting once a week to discuss whatever pages are currently being reviewed.

@chhavi asked about how to collect feedback about the mockups, and @Quesito said she’s make a [Google docs] folder where feedback documents could be kept.

@samj1912 contributed this nugget of wisdom:

@samj1912

rather than asking people who dont know design theory, feedback about design, we should settle on extracting key requirements via user-study and surveys and then work on the deliverables
design is a very subjective and things that look good at first sight may not be that good in the long run ( eg - reddit design gets very intuitive after using it a couple of times)

@Freso suggested that @zas might be able to help with some statistics about which pages on musicbrainz.org are accessed the most.

[Quesito]

UX Design Discussion additional notes and links:

UX Design Meetings will be held at 18H CEST on the IRC channel.

The Google Drive Folder for UX:
https://drive.google.com/drive/folders/0B0y9CTG8sS0LVHppOW1wNXc1SWc?usp=sharing

The notes/comments page for the Artist Mock-up page:

Artist Page_Comments+Feedback

Comments and questions can be addressed to myself or @chhavi