#metabrainz

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.

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.

(oops)

We started putting together a list of the achievement types we'd like to see: https://docs.google.com/document/d/1yuFMTVifYiy...

And we're aiming to discuss a solid plan/set of milestones for implementing the system at next week's BB meeting.

fin.

LordSputnik: no, silly, Sirius are the supporters.

Leftmost: Go!

No Leftmost?

Leo_Verto: Go!

No? stanislas, go?

chrisskye: I was copied on the sirius mail, will answer tomorrow

alastairp: Go!

alastairp apologizes for his late appearance to the meeting

yeah, that is it. yeah.

Does that mean he's not around right now?

If so, chirlu: go!

he should've appeared by now...

I reappeared and did a number of schema change tickets.

No chirlu either? Man.

Oh.

LordSputnik: Strikes usually work best when you announce that you're striking.

I’ve also prepared auto-pestering for banner message editors so that they will take down banner messages sooner.

Fin.

chirlu: It is fully intentional that I haven't taken the Discourse one down. You're free to click the x when you don't want to see the message anymore.

rahulr: Go!

Mine end semesters ended last week. That's quite a relief for me.

I wrote a small blog post about gsoc selection.

Freso: even with that, I still think it makes sense to have a "reminder" every week or two that it's still up :)

reosarevok: Possibly.

nice

Resumed working on picard-258, that is about visual feedback on coverart changes.

Discourse isn’t “new” anymore after ten weeks.

And looking forward to discuss some project implementation details with bitmap later on this week.

fin.

(oops, "nice" was about something five minutes ago)

bitmap will be available after some sleep. he says goodnight to all!

But anyway, since the banner will be needed for its original purpose, the Discourse announcement will be gone soon.

here

QuoraUK: Go! :)

'ello

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 :D and will work on project planning ~thursday once my exams for the week are over :p

should get a new post up friday detailing ready for discussion saturday :D

fin.

Thanks QuoraUK :)

armalcolite: Go!

Hello,

This week i was focused on doing task which ruaok had assigned

Created a new PR: https://github.com/metabrainz/listenbrainz-serv...

It is an attempt to store 30-90 days of listens in postgres for analytics generation.

Oh, rahulr QuoraUK and others, feel free (that is: please ;)) link blog posts when you refer to them :D

I

- Added support for listenstore.conf in listenstore. (It was mentioned as TODO in the source code)

- Added support for storing listens in postgres, includes updating schema and code modifications.

- Added Support for scheduling jobs using apscheduler. Job for clearing postgres DB every 24 hours to maintain 90 days listens.

- A new script to push listens to postgres instead of cassandra, "listenstore-kafka-to-postgres-writer.py" in addition to older one.

The listens can be pushed to any of them by just switching a single line. (Provided the schema is correct)

- Reading listens for display on site from postgres instead of cassandra. (This also can be switched by changing a single line)

Thats it. fin.

apscheduler looks interesting

Thanks armalcolite :)

hellska: Go!

Hi :)

alastairp, ruaok: waiting for your reviews. :D

last week worked most of the time on the project!

rewriting the proposal after the meeting and answering the comments

Sorry about that. :D, Here -> http://rahul-raturi.github.io/2016/05/14/got-se...

;_;

digged into the AB database schema to understand where to make changes

followed the reviews on dataset API and dataset validation

fin

Thanks hellska :)

kartikgupta0909: Go!

Hi :)

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 :)

thats it for now

Cool. Remember to add the track (and yourself) to MB when it's done. :p

cetko: Go!

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! :D

</html>

:D

:)

Before moving on, I have an addendum:

I also added the MetaBrainz blog to https://planetgsoc.github.io/

Students with a blog may want to add themselves there as well.

Okay. Done with reviews!

Schema change announcement!

who was that?

me?

ruaok already pretty much said it in his review, but we've pushed the schema change a week to try and be sure we have enough time to check that nothing breaks critically.

ruaok: Me. :)

phew

https://blog.musicbrainz.org/2016/05/16/importa... for more details.

ruaok: dev priorities!

right.

once the schema change is in the bag, hopefully in 8-9 days or so, I'm going to publish our near term dev priorities.

simply put:

MOVE!

?

1. Hotfix critical bugs as they appear.

2. Coorindate with Zas to identify and fix issues that prevent us from moving to NewHost.

rindate?

That's it.

Yes.

All hands on deck until we can move to NewHost.

Sounds good.

I am taking the busywork, paperwork side of things.

zas is the chief architect. bitmap is the lead engineer and Gentlecat will be a senior level minion.

Gentlecat^^

the primary goal is: move to NewHost in an MVP (minimally viable product) fashion.

zas is da real MVP.

if a task needs doing and it is either: 2 days or 3 weeks, the answer will nearly always be 2 days.

which then acts as a nice transition to picard and reosarevok.

Who has been designated Most Valuable Player?

you!

:)

reosarevok: let me guess: picard is not usable anymore because of 503s?

Yes

Oh, HTTP 503's?

Yes

And I was wondering if that fancy new ratelimit allows us setting better limits to Picard's useragents

Yes. Because of the concurrency limit we set up

so, the short term game is shuffle the beach chairs on the deck.

we're going to steal from headphones and give to picard.

but ssssh about that, no one tell headphones about this.

currently we refuse requests when we reach 250 req/s

It's not steal if it isn't theirs to begin with ;p

basically, we're going to carefully evaluate who is getting what.

all the while trying to squeeze out every bit of request our system can give.

Sounds good to me.

in the end people are not going to be happy, but we're going to try and make people less unhappy.

short term, ask people to chill. point them to the article on the blog.

zas and I will continue to work on this.

Yes

once we have something we can really share about how things have changed/improved, we'll share.

I hope that addresses your topic, reosarevok