Notes from #MetaBrainz Meeting on 2016-05-16

metabrainz-meeting-notes
Tags: #<Tag:0x00007f2a0bde3dc0>

#1

#MetaBrainz Meeting 2016-05-16

Meeting start: http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592894/

Agenda

  • Reviews
  • Schema change announcement
  • Developer priorities
  • Picard 503

Reviews

@Freso

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592900/

@chrisskye

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592906/

@reosarevok

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592912/

  • dealt with support, including delegating some stuff to chrisskye (yay!)
  • got tired of not being able to set user emails when they didn’t get our verification, so I wrote that code
  • it’s in beta now, and I already had to use it once, so I’d say it was a success :stuck_out_tongue:
  • spent the second half of the week worrying about opening the museum I volunteer / intern at, which means 2-in-1 release groups and other boxsets (STYLE-330, STYLE-331, STYLE-335) still needs me to decide stuff which gah I’m sorry I’ll get to it :frowning:
  • (it’s not very straightforward at all so I need to consider it carefully and I just haven’t had enough peace and quiet to think about it)

@bitmap

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592932/

  • did schema change stuff

@Gentlecat

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592931/

  • added new customers to meb.org page
  • reviewed GSoC work

@zas

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592934/

  • hacking on new rate limiter
  • search servers

@Rob

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592939/

@LordSputnik

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3592980/

@chirlu

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593002/

  • did a number of schema change tickets
  • also prepared auto-pestering for banner message editors so that they will take down banner messages sooner

@rahulr

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593011/

@Quora

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593026/

@armalcolite

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593039/

@hellska

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593053/

@kartikgupta0909

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593068/

@gcetusic

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593079/

Schema change announcement

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593088/

Developer priorities

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593097/

Announcement from @Rob that once the schema change release is out, the development priorities will get shuffled around a bit:

  1. Hotfix critical bugs as they appear.
  2. Coordinate with @Zas to identify and fix issues that prevent us from moving to NewHost.

Picard 503

http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593132/

Basically we’re seeing a lot of complaints about Picard users being pretty much unable to do anything due to getting 503’s from MusicBrainz, so @reosarevok asked if we could tweak the new rate limiter a bit. Short answer: yes, @Rob and @zas will continue to work on and tweak the rate limiter so hopefully Picard users should get a better experience shortly.