#metabrainz

oh, sorry Freso, reosarevok, and code_master5. Didnt see it coming :)

rihan: Just go. Seems like there's a long time between pulkit6559's messages.

i also read a paper "Corpus Analysis Tools for Computational Hook Discover by Jan Van Balen" which i intend to implement in coming gsoc

(If you have more to add.)

eh. pulkit6559 will say "fin" at the end

Freso: i'm Fin :)

yay!

rihan: Got more for your review?

Worked in the end. Yay!

Yes

adding to what I said earlier. I am working on opened tickets on BB. Also on the design proposal for implementing web API for programmatic access to BB database

done!

Alright! On my word: onwards!

ruaok: MBH-513: dev security policies

MBH-513: Metabrainz policy for software dependencies / package upgrades https://tickets.metabrainz.org/browse/MBH-513

so, one of the key players who needs to help decide this isn't here this week.

not sure what to do. bitmap & co: do you guys have any questions or burning things to discuss?

otherwise it might be best for next week when everyone is here.

just some general thoughts, nothing urgent

let's hear your general thoughts, then we'll call it done for today.

👍

sure

ruaok's momma is fat

Freso: this was the agenda you were talking about?

Wait, about this specific topic?

for the github security alerts I think we should review them within the same week they appear, but if they turn out to be not relevant to us (because we don't use the code in question), I'd prefer to not upgrade until it's convenient...

reosarevok:

That seems reasonable

forcing an upgrade when it's not necessary frequently opens cans of worms, e.g. we can't update less right now because less-plugin-clean-css breaks with newer versions

bitmap: agreed.

bitmap: How can we watch/share such reviews?

I'd suggest we keep a google doc to track the security alerts that aren't relevant, and open tickets for the ones that are

but maybe there's a better method

I wonder if we can track that in jira. seems more fitting than a disconnected google doc.

grafana?

but something easy to spot where everyone can see it and we can hold each other to keeping up.

yeah

lets think about this more for the next week.

for the docker base-image, the ideas I have would be to rebuild it automatically with cron and push the updated image to the same tag (so that MB picks up the new base image automatically when we release next), or just copy the `apt-get upgrade` line from the base-image into our derived Dockerfiles...

any thought on using any tools to automate this process?

Jira tickets, per project or as its own project (SEC) ?

in the repository itself? .everythingisundercontrol

loi

I think we should try out greenkeeper(?) for the JS dependencies at least, I'm not sure if there's anything similar for Perl

jira with a separate project makes sense to me.

Greenkeeper has been quite useful on BB

storing this info in the repos isn't very visible.

aight, let's leave it be for now.

i think some security reports may concern more than one project, so we could have a "meta" ticket and sub-tickets (in various concerned projects)

let's pick this up next week.

bitmap: Any more general thoughts? Or fin for now?

Freso, keep the topic, back to you.

fin for now

Alright.

That's it for tonight then.

Thanks for your time everyone!

</BANG>

बैंग!

pristine--: did you say it started working?

No

pristine--: Hi. :) So "agenda" is *all* the items we have on the meeting. These (usually) change every week, but "Reviews" are always the first item. This week we had one more _agenda item_ (the security alerts).

The hidden agenda is making fun of ruaok

Mr_Monkey: can you answer my earlier question :) ?

:D

बैंग! means?

Sure thing rihan !

reosarevok: lemme tell you. Your sense of humour is wow. I cannot stop laughing

CatQuest: spelling og bang in hindi

pristine--: You can see the agenda in the /topic after the "Meeting agenda:"

I think you might have a low barrier for laughing :p

Freso: oh, okay.

uh

spelling og bang?

Anyone can edit the /topic, so anyone can add items to the agenda if they have something they want to discuss.

reosarevok: it is a good thing, isn't it

Probably :D

wait where?

We should have it as a classical music genre, but...

Freso: that is interesting. I mean a good thing

That's so not going to work

(Usually you shouldn't have discussion items/questions as part of your review. Those should go into an agenda item instead.)

Mr_Monkey: the switch from elasticsearch to solr.

Two main reasons we want to move from ElasticSearch to Solr: 1. Ease of hosting on Metabrainz' servers, that already has everything in place to run and scale Solr and 2. ES is a resource hog, doesn't scale well and doesn't run very well on slow-ish computers

reosarevok: use norwegian: romantikken

Not sure that'll fly :p

:D

I'm updating the GSOC Ideas page with those reasons, thanks for asking :)

(Of course, some quick advice can sometimes be appropriate to ask for in reviews, but if it turns into a lengthier discussion, it should be its own item.)

ruaok: after your build, I used ./spark-submit.sh create_dataframes.py

But it said no module named numpy

So did you include the numpy command in your .dev

I see the problem.

working out what the problem is

On a related note: That would be neat to describe interactions between repositories in a central place, because GitHub Dependencies is not enough.

Freso: agenda should be passed?

Mr_Monkey: I see, does solr has support for distributed scaling ?

pristine--, amCap1712, Cyna, pulkit6559, rihan: Hi. :) If you want to be part of the "permanent roster" of the reviews, just say "Freso, I want to permanently be on the review roster!" :) I currently only have staff/team as well as CatQuest on my list (and CatQuest because he explicitly requested it). I group GSoC students in with the staff/team during the GSoC period (after students have been accepted), so I'll add you in then (if

you get accepted), but until then I'll only add you if you ask me to. :)

Like okay, it can be discussed

rihan: Yes, that too :)

pristine--: Like I said, anyone can add agenda items. No need to get acceptance from anyone. :) If I have no idea what it's about, I'll usually ask about it before the meeting.

aw come on. im'l ike. psudo staff evne if i'm not paid :P

Freso: I want to be permanently on review roster :)

+1 pristine--

ruaok: what was it?

CatQuest: but you are already?

still working to fix it

CatQuest: Well, alastairp and drsaunders too (and LordSputnik and Leftmost previously), but they're not active here on IRC during the meetings, hence me not adding them.

Okay. Lemme know if I can help in any way.

pristine--: "I currently only have staff/team as well as CatQuest on my list" (and becasue ir equested it)

I will wait otherwise.

le sigh

Oh. Okay

सोमवार

somvaar

CatQuest: Paid MeB team has it as part of our job to be in the meeting, you do it on a volunteer basis and will have no repercussions for not being around during it. I'm not saying this to diminish your contributions (you're doing a great lot of work! Seriously!), just to make you understand why I'm doing it this way. :)

Wow

aha. right

:)

Freso: thanks for letting us know :)

GSOC results are announced in may start, right?

thanks for explaining it Freso! that makes sense

Also, pristine--, noted. :)

Freso: youtube or roster?

Lol

cockadoodledo?

🐓

Freso, I want to permanently be on the review roster!

I'm planning on sticking around atleast till all the templates have been converted to React

CatQuest: is that a review rooster?

idk?

ruaok: here :)

btw is the meeting over ?

yes

Freso, I want to permanently be on the review roster! :)

Cyna: the meeting is over when Freso says </BANG>

(and we try to never have it last more than one hour

)

legoktm: wiki visual editing seems to be broken: apierror-visualeditor-docserver-http-error: (curl error: 7) Couldn't connect to server.

I guess people don't realize that you have a 10 year servitude to MB to be added permanently to the roster.

I had a query about the convertion of c.uri_for_action to React

only paying freso 10Kg in chocolate gets you off the list.