Notes from #MetaBrainz Meeting on 2016-05-09

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

#1

#MetaBrainz Meeting 2016-05-09

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

Agenda

  • Reviews
  • Schema change
  • WS rate limiting

Reviews

@Rob

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

@Bitmap

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

@Freso

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

@chrisskye

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

  • been sick, so not very productive
  • still fighting to get the electrical service hooked-up
  • keep at the list of potential supporters
  • “I want to thank everyone for pointing me to leads. :)”
  • “I think it is really worthwhile getting the other Open Source, non-profits, academics signed up too.”
  • “One note. My suggestion regarding making a more direct link to the sign-up/donation page. This suggestion comes from others in our community!”

@reosarevok

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

@Gentlecat

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

  • finished implementation of OAuth on meb.org
  • started integrating it with our fancy office door opener microservice
  • fixed broken mbspotify deployment and related issues in CB
  • also added a couple of new customers on https://metabrainz.org/supporters because @Rob was at some fun conference
  • fixed MBS-8288 and MBS-8804, reviewed some code
  • met with @hellska and @alastairp to decide on details of gsoc project

@zas

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

  • most of the week on two things
  1. upgrade all servers due to serious security updates (ssl and nodejs), had to reboot all
  2. find a better way to rate limit our ws traffic
  • plus: usual supervision, minor fixes, minor changes to graphana, upgraded influxdb, etc…

@LordSputnik

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

@alastairp

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

  • coordinated with the AcousticBrainz GSoC students.

@rahulr

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

@Quora

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

@armalcolite

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

@hellska

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

Schema change

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

Discussion about the status of the various tickets. A few tickets still remain that are currently assigned to @LeftmostCat and @chirlu, but @Bitmap reckons that it isn’t unsurmountable, as long as patches/pull requests get merged before/on Friday the 13th.

WS rate limiting

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

@Zas talked about his tests with the new rate limiting and discussed some of his findings/results related to this.