#MetaBrainz Meeting 2016-05-16
Schema change announcement
I’ve been suffering from a chest infection more than a week, so a bit sluggish. That said, managed to do a lot of correspondence. Lots of new sign-ups. A few are paying supporters, some non-profit and community orgs and numerous start-ups. Rob and I continue with the usual run-around trying to get service hook-ups to the new office and dealing with the new Spanish bank account. I’m off to Calgary, Canada tomorrow. Will be working from there. So closer to Pacific Coast time, than European time.
I received an email from SiriusFM (Sirius XM, red.) just now…asking a lot of questions…but basically wanting to sign an agreement for Unicorn Tier.
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
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
(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)
added new customers to
meb.org page reviewed GSoC work
hacking on new rate limiter
This week I did some planning for BB OAuth, and I’ve mapped out the flow that users should go through to register, log in and link existing accounts to MeB accounts.
I’m quite happy with all that now and if I get time this week it’ll be on our beta server by next weekend
Leftmost and I also had a long discussion with QuoraUK to plan various aspects of his GSoC project. We’ve decided on the principles of the system, which QuoraUK can talk a bit more about later in his review.
We started putting together a list of the achievement types we’d like to see: https://docs.google.com/document/d/1yuFMTVifYiyoiTS73TcaneNlQKLe6_gX0xtgksB4o4s/edit?usp=sharing
And we’re aiming to discuss a solid plan/set of milestones for implementing the system at next week’s BB meeting.
did a number of schema change tickets
also prepared auto-pestering for banner message editors so that they will take down banner messages sooner
wrote a blog post about the design for the gamification system, which we discussed in the BB meeting, got some good ideas for achievements in the doc above, Got a package from Google today
and will work on project planning ~thursday once my exams for the week are over
should get a new post up friday detailing ready for discussion saturday
Finalised some of the details about the project with alastairp, which will help me get started about the project
We have decided on making a PPA for the offline dataset training tool
and will make that PPA this week itself so that next week I can devote time to write the installation shell script.
and also I started working on my first track as a music producer
Hi! I’ve been working on creating tickets for AB for the first few weeks of GSOC:
#125, #126 and #127 for now. I’m focusing on designing the schema which I hope I’ll kick off this week but I’m still waiting for Felipe to answer the last email alastairp sent about me getting access to his storage bucket so I can play with BigQuery. Otherwise, I’ll do it on my own account but I’ll have to load the summary data myself to cloud storage. Other than that, I’ve cloned the repo of the acousticbrainz server, set up my virtualenv and poked around a bit but to get a feel for the code because I’ll have to change it at some point when uploading data to bigquery. Last week I completely forgot about the meeting! [OT] Yesterday I arrived in Dublin! Wooo! Schema change announcement
http://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3593088/ Developer priorities
@Rob that once the schema change release is out, the development priorities will get shuffled around a bit:
Hotfix critical bugs as they appear.
@Zas to identify and fix issues that prevent us from moving to NewHost. Picard 503
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.