please excuse typos, im on a very bizzare keyboard
2013-04-15 10530, 2013
ocharles
for the start of my week i was working on a new project, musicbrainz-email
2013-04-15 10501, 2013
ocharles
this is a separate service that listens on a message queue for email "requests" and then sends email
2013-04-15 10522, 2013
ocharles
i wrote this for sending out password reset emails, but it grew quite a bit over the week. hopefully we can deploy that tonight
2013-04-15 10524, 2013
warp
(ps. though I am hosting this meeting. I am currently is south america, where consumer internet connections are not very reliable. usually when the connection drops it reconnects in three minutes or so)
2013-04-15 10551, 2013
ocharles
then midweek we had a big outage so i had to be around for that
2013-04-15 10516, 2013
ocharles
it turns out our /browse pages absolutely hammer the database in terms of network traffic, and take half the site down
2013-04-15 10519, 2013
ocharles
not fun
2013-04-15 10534, 2013
ocharles
we flipped over to baron, so i had to spend a bunch of time reconfiguring slave replication
2013-04-15 10539, 2013
ocharles
but thankfully we're past that now
2013-04-15 10552, 2013
Ben\Sput
is that ws/ browse?
2013-04-15 10500, 2013
ocharles
i was motivated by all this to look into graphite and monitoring more, so we started to collect system stats via graphite
2013-04-15 10506, 2013
ocharles
no, the main website
2013-04-15 10535, 2013
ocharles
sadly, the graphite stuff runs on a vm that doesn't have good enough io performance in the current configuration, so i accidently took all our vms down
2013-04-15 10541, 2013
ocharles
oops :)
2013-04-15 10550, 2013
ocharles
along with that, the normal reviews
2013-04-15 10553, 2013
ocharles
fin.
2013-04-15 10557, 2013
warp
ok
2013-04-15 10537, 2013
warp
I don't have much interesting to report either. I probably spent about a day on the fire fighting ocharles already mentioned.
2013-04-15 10556, 2013
warp
some reviews, and the remaining time on making all the tests pass for the track identifier changes.
2013-04-15 10559, 2013
ocharles
excellent
2013-04-15 10501, 2013
Ben\Sput
warp: do you have any notes on the track id changes/docs?
2013-04-15 10528, 2013
warp
I also spent some free time trying to write a rate limiter in haskell. But I'm new to haskell, so obviously that's going to take a while.
2013-04-15 10547, 2013
warp
(and that was my internet bugging out for a minute)
2013-04-15 10555, 2013
warp
Ben\Sput: what kind of notes?
2013-04-15 10559, 2013
Ben\Sput
i was thinking it would be useful to give tagger people/luks a heads up as to how it will affect them
2013-04-15 10503, 2013
ocharles
i think thats looking good though
2013-04-15 10511, 2013
Ben\Sput
so, how they'll be accessible, mainly
2013-04-15 10550, 2013
Ben\Sput
(since luks may need to change acoustid to use track ids before we bring in the updated recording guidelines)
2013-04-15 10515, 2013
warp
Ben\Sput: no, I haven't properly considered the changes to the webservice yet. I first need to get all the tests to pass, then work on the UI changes.
2013-04-15 10528, 2013
reosarevok
Ben\Sput: I don't think luks had any intention to change that anyway :p
2013-04-15 10531, 2013
reosarevok
(ask him, but)
2013-04-15 10544, 2013
ijabz
is their an sql migration script for schema changes, and is it basically finished ?
2013-04-15 10556, 2013
Ben\Sput
reosarevok: judging from style he does, but anyway, back to warp :)
2013-04-15 10529, 2013
reosarevok
ijabz: last SQL patch I plan to finish post-meeting
2013-04-15 10530, 2013
warp
ijabz: the schema-changes-2013-05-15 branch contains (almost) all the changes.
2013-04-15 10537, 2013
reosarevok
(alastairp was very late so I took over)
2013-04-15 10549, 2013
reosarevok
Once that's done, I'm not sure how it goes :)
2013-04-15 10554, 2013
warp
ijabz: including the upgrade script (upgrade.sh)
2013-04-15 10559, 2013
ocharles
leftmost's work is also missing from that
2013-04-15 10508, 2013
alastairp
(and I appreciate it, sorry - had a bunch of stuff come up, but it all finished today)
2013-04-15 10512, 2013
warp
my cover art media-type is missing from it as well.
2013-04-15 10529, 2013
ocharles
i'd really like to see everything missing merged this week
2013-04-15 10541, 2013
ocharles
we're starting to run very fine - less than a month til testing
2013-04-15 10500, 2013
ijabz
I'm kind of waiting for this before try to update searchserver
2013-04-15 10501, 2013
warp
and I haven't even started on UI code yet :(
2013-04-15 10549, 2013
warp
but let's continue reviews. anyone else for review? :)
2013-04-15 10550, 2013
ocharles
i started some of my ui code today
2013-04-15 10550, 2013
warp
(looks like a no)
2013-04-15 10500, 2013
warp
Ben\Sput: relationships!
2013-04-15 10503, 2013
Ben\Sput
\o/
2013-04-15 10509, 2013
warp
warp has changed the topic to: Yakutsk | http://musicbrainz.org/#devel | Agenda: Relationships (Ben), doc/Recording (Ben), multiple barcodes (ocharles)
2013-04-15 10527, 2013
Ben\Sput
so, I've been doing the rfc for the proposal for changing the recording style guidelines
2013-04-15 10546, 2013
Ben\Sput
and also another proposal on audiobook guidelines (which is abandoned now)
2013-04-15 10558, 2013
Ben\Sput
but in both cases, people have been saying they'd like relationships to be easier to use
2013-04-15 10510, 2013
Ben\Sput
and would also like more features, such as inheritance in relationships
2013-04-15 10546, 2013
voiceinsideyou joined the channel
2013-04-15 10552, 2013
Ben\Sput
i came up with the idea of being able to make arbitrary groups of relationships which could be copied onto entities
2013-04-15 10514, 2013
Ben\Sput
and i was wondering if anyone else had any thoughts on how we could make them easier to use?
2013-04-15 10515, 2013
ocharles
there's a lot we can do with ui stuff without changing the data model
2013-04-15 10519, 2013
ocharles
like that grouping
2013-04-15 10526, 2013
ocharles
and i think we should look at all of that first
2013-04-15 10546, 2013
reosarevok
Having a tool to copy rels would be nice
2013-04-15 10555, 2013
Ben\Sput
It'd probably be good to have an option to clone all of the relationships from one entity to another
2013-04-15 10558, 2013
Ben\Sput
:P
2013-04-15 10504, 2013
reosarevok
Inheritance might be too, but it's more complex
2013-04-15 10512, 2013
reosarevok
(not only in code, also as a concept)
2013-04-15 10520, 2013
reosarevok
(since not everything should be inherited)
2013-04-15 10524, 2013
kepstin-work wonders if mocking up something as a userscript, like bitmap's artist credit copy/paste tool would be possible
2013-04-15 10529, 2013
Ben\Sput
I think inheritance is definitely something we should look at in the future
2013-04-15 10535, 2013
Ben\Sput
but the main improvement i'd like to see is definitely cloning/sharing of relationships, which would make recordings so much easier to add/maintain
2013-04-15 10543, 2013
kepstin-work
defining exactly how inheritance works would be a real pain
2013-04-15 10555, 2013
ocharles
the cloning/sharing stuff does raise questions of data redundancy though
2013-04-15 10502, 2013
ocharles
but that's all beyond the scope of this meeting
2013-04-15 10531, 2013
kepstin-work
for inheritance, we either need an additive model with the ability to 'black out' relationships that don't apply, or an override model, which means having duplication :/
2013-04-15 10534, 2013
Freso
I don't see how inheritance could work properly without a schema cange.
2013-04-15 10548, 2013
ocharles
Freso: it needs a schema change
2013-04-15 10551, 2013
Ben\Sput
it probably couldn't
2013-04-15 10511, 2013
reosarevok
A schema change and a shitton of work
2013-04-15 10524, 2013
Ben\Sput
it would be good then, if in the short term, someone could make a user script to copy relationships
2013-04-15 10537, 2013
nikki
inheritance sounds like a complete nightmare for everyone wanting to use the data :/
2013-04-15 10543, 2013
reosarevok
Yeah, there's that
2013-04-15 10555, 2013
warp
it all sounds too vague to say anything meaninful at this stage
2013-04-15 10512, 2013
reosarevok
I'd like "inheritance" as in being able to add and remove and edit relationships for several related things at the same time
2013-04-15 10520, 2013
kepstin-work
yeah, and that. we'd have to define the rules for how inheritance works so others can apply them - and probably have the webservice resolve the inheritance and show only the final relationships
2013-04-15 10520, 2013
reosarevok
I'd certainly want them to be stored separately though
2013-04-15 10524, 2013
reosarevok
Much easier to use
2013-04-15 10535, 2013
warp
Ben\Sput: can you work with a few people to put together some more concrete proposals, and/or prototype with userscripts, etc.. ?
2013-04-15 10556, 2013
Ben\Sput
warp: I'll see what I can do :)
2013-04-15 10517, 2013
warp
great :)
2013-04-15 10520, 2013
warp
let's move on
2013-04-15 10528, 2013
warp
Ben\Sput again! doc/Recording.
2013-04-15 10537, 2013
Ben\Sput
:)
2013-04-15 10555, 2013
kepstin-work
... isn't this a style issue? not sure why it's in the dev meeting.
I think we should probably replace the /doc/Recording page at the same time as the matching style guidelines are applied.
2013-04-15 10511, 2013
Ben\Sput
kepstin-work: yes, no problem with that
2013-04-15 10544, 2013
warp
Ben\Sput: after a quick read now it looks fine to me.
2013-04-15 10504, 2013
warp
what is the status of "the matching style guidelines" ?
2013-04-15 10514, 2013
Ben\Sput
we're close to agreeing on them
2013-04-15 10528, 2013
reosarevok
Yeah, they look surprisingly close to consensus
2013-04-15 10530, 2013
Ben\Sput
most of the issues that have been raised have been resolved
2013-04-15 10531, 2013
reosarevok
:)
2013-04-15 10534, 2013
kepstin-work
It's in RFC state with just minor squabbling over exact terminology and wording
2013-04-15 10536, 2013
warp
good
2013-04-15 10550, 2013
Ben\Sput
should be ready long before schema change
2013-04-15 10507, 2013
Ben\Sput
and then we have to wait for luks to do whatever he wants to do to ensure that acoustid isn't ruined :)
2013-04-15 10511, 2013
kepstin-work
there's no real schema change-related stuff involved tho, is there?
2013-04-15 10518, 2013
Ben\Sput
kepstin-work: track ids
2013-04-15 10557, 2013
warp
track identifiers are related, and some people want them before the new style guideline is in effect because with the new guideline many recordings will be merged.
2013-04-15 10517, 2013
kepstin-work
hmm; I don't see how acoustids attached to track ids is that useful, given the recording merges that are done already and the relative inaccuracy of acoustids
2013-04-15 10523, 2013
Ben\Sput
since the guideline will be much more permissive with merging, it has the potential to cause AcoustID to be much less effective at identifying tracks, so track ids are needed for luks to update links to avoid that
2013-04-15 10531, 2013
kepstin-work
(acoustids in general can't tell different tracks with the same recording apart anyways...)
2013-04-15 10537, 2013
kepstin-work
but that's up to luks :)
2013-04-15 10550, 2013
Ben\Sput
luks has certainly implied that he wants to do that
