#musicbrainz-devel

ianmcorvidae: Any ETA for the release?

Flights booked, info on the summit page!

Although it worries me that I still have not received an email confirmation from the airline. I have a scary feeling I typed my email address in wrong

chirlu`: had forgotten about it entirely, doing it now

too much geordi makes Ian's brain fuzzy :)

Oh, good that I asked then. :)

ianmcorvidae: did you revert that thing that made some edits ISE?

or did you merge bitmap's fix?

I did not. I'll merge bitmap's fix, since it's a minor thing

I remembered it on the walk I was just taking, heh, so it at least would have still happened

I should stop doing them after midnight UTC though :P

chirlu` has changed the topic to: Greenhouse week | Agenda: (empty)

okay, I guess I should review and merge things :P

New post: blog: Server update, 2014-01-20 <http://blog.musicbrainz.org/2014/01/21/server-u...;

chirlu`: Aw. I had wanted to change it to "Chilli week" :p

:P

Freso: feel free. :)

But isn't it Chili?

Shh.

it's regional

I also can't be bothered right now. I should be going to bed instead.

chirlu` has changed the topic to: Chilli week | Agenda: (empty)

:)

question: I've seen (without even really looking for it) two people recently asking for help because they'd missed the trailing dot in "cpanm --installdeps --notest ."

So it makes sense to me to add something like "*note:* don't forget the trailing dot" in install.md

are you going to do a pull request for it? :D

but... I feel silly making a six workd pull request

er, "word"

nah, that wouldn't be silly

I've made smaller patches than that

heh

done it for smaller, yeah

if you get it up quickly, I'm reviewing now and then merging, so :)

I'm sure we've had several one character ones

okey dokey

fixing regexes, those are usually stupidly little :P

well, but important. six words in the docs somehow feels less so.

good docs are important :)

if for no other reason than if someone doesn't need to ask a question in here, it gives us more time for fixing regexes ;)

then I'd better shut up and do it

(said with that particular smiley because generally talking is not actually a problem :P)

I wish we'd use our own damn permanent ids internally...

heh

CallerNo6: I've sometime done one letter/character corrections in PRs for readmes etc.

okay, the flip side. how big is too big? Within a single file like 'install' or 'readme', how many things can/should I change in 1 PR?

for that, probably too big is when thematically unrelated changes start running together

(well, substantially so)

+1

I guess I'll get a feel for it eventuall.

y.

in general, for documentation, it's pretty hard to get too big

(I mean, for a change. the docs themselves can be too wordy)

chirlu`: still around? I'd like to get the reorder UI patch in, but I feel like I'm missing something obvious.

I guess not :P

also on the subject of docs, any pointers to especially well-done docs would be appreciated :-) (well, how-to or how-not-to would be equally good)

merginnnnng

ianmcorvidae: You really managed to miss me exactly. :)

yeah, I was literally typing it as you left XD

I just commented on the pull request.

yeah, I saw

unlike you, it sort of makes sense for me to get notifications for everything that happens on bitbucket, so I have the notifications on :)

It would be OK to get combined notifications for everything I haven’t looked at after X hours, but not for every single change.

yeah

suppose you could make them a ticket, but they might already know *shrugs*

Perhaps it is fixed in current JIRA? :) Haven’t checked, though.

I now look at the "merged" tab occasionally.

current jira? I thought you were talking about bitbucket

Oh yes, somewhat confused.

I wonder if they ever fixed that ticket I made for them. I haven't ever checked

(they had a weird thing where you could make the comment field jump mid-submission and end up with an inconsistent local state)

Hm, they have approximately as many open tickets as MBS.

“Debounce email notifications (BB-9917)” (Support staff writes “I'm pretty sure there's already another ticket about this, but I was unable to find it.”)

No, mb-chat-logger, I meant BitBucket. Please link to https://bitbucket.org/site/master/issue/8754/de... instead. ;-)

Doesn’t learn …

BB is the key for 'bookbrainz' on our jira :)

I know, but it could understand the context better. ;-)

i noticed last server update adds new cover art types (ie. liner), documentation at http://musicbrainz.org/doc/Cover_Art/Types wasn't updated, i would be _very_ nice to have those available from server as xml or json so we can easily update Picard (which needs those types for cover art selection)

the same goes for Packaging, more are available now

s/i would/it would/

technically it wasn't part of the server update

but it appeared with it

and http://tickets.musicbrainz.org/browse/MBS-4342 is the ticket for making info like that available via the ws

nikki: :)

only because ian did multiple things in a short period of time though

zas: it didn't appear with it, it appeared later at night when they were inserted in the database

(I just happened to remember the same day, that's all, heh)

Good point about the docs though

:)

(this should be on the server not the wiki, too, but meh)

imho, we should have each list with key, english label, optional english short description, optional english long description (or the like) at one place, and provide them via webservice for apps (and also online documentation which can be generated from that)

i think mostly about countries, languages, scripts, packaging types, cover art types, etc...

it is a must, because apps like Picard have their own list for now, which are eventually generated (ie. countries after PICARD-205), but still may be always out-of-sync (releases of Picard vs update of those lists), with a webservice app can use cached info (offline/no change) and refresh it when needed

i even wonder if webservice shouldnt provide translations too ..

Oh, Hibiscus updated http://wiki.musicbrainz.org/Release/Packaging :)

Cover art doc updated, anyway

btw, i just added a release which didn't fit in any packaging type, but it is still seen (sometimes): book-like with digipak-like trays (this one is a long box with 4 CDs and non-detachable booklet in the middle)

heh

A lot of releases don't fit any packaging type

But since packaging type is pretty much absolutely useless anyway, I don't really worry too much about it :p

(more types can always be proposed though and hopefully next time we won't forget to add them for 6 months :p)

well, I guess if picard could use packaging info, they would be slightly more useful :)

how would it use it?

just for tags

What would that be useful for?

If you have files, who cares :p

more complete data in your files, ofc :)

"Oh, these files I ripped totally came from a digipak!"

I said “slightly” ;)

packaging type is useful to differentiate some releases, sometimes this is the sole difference (same label,catalog number, barcode, etc... but digipak vs jewel case ie)

Sure, but for me that's a strange enough case that a disambiguation comment would happily suffice, and not require people to add yet more pointless info for 99% of the releases

(since our forms are big enough already :p)

But well

hm, why doesn't the BBC have a logo on http://metabrainz.org/doc/Sponsors ?

Because they have insane guidelines for logos

(as in, you have to renew permission to show the BBC logo every few months and whatever)

ianmcorvidae: I updated i18n (if you're awake and didn't see the mail).