Specifically I'd like to know how to test it: what URL to request from the search server, and what response to expect.
2009-10-05 27840, 2009
djce
thanks for any help :-)
2009-10-05 27845, 2009
luks
I think it's /ws/1/track?type=track&fmt=html&query=xxx
2009-10-05 27857, 2009
luks
and the tagger link should contain the same UUID as the release link
2009-10-05 27811, 2009
luks
currently it uses the track UUID, which is wrong
2009-10-05 27828, 2009
djce
ok thanks
2009-10-05 27833, 2009
djce tries to find a test case
2009-10-05 27836, 2009
djce
hmm not quite, the responses don't contain tagger links at all
2009-10-05 27837, 2009
luks
oh
2009-10-05 27839, 2009
luks
sorry
2009-10-05 27846, 2009
luks
add &tport=8000 to the url
2009-10-05 27847, 2009
djce
ah, tport
2009-10-05 27849, 2009
djce
yup
2009-10-05 27823, 2009
djce
bingo. Thanks luks :-)
2009-10-05 27808, 2009
outsidecontext joined the channel
2009-10-05 27857, 2009
jacckk joined the channel
2009-10-05 27833, 2009
aCiD2 joined the channel
2009-10-05 27801, 2009
warp
almost!
2009-10-05 27805, 2009
aCiD2
:)
2009-10-05 27806, 2009
warp
hello!
2009-10-05 27809, 2009
aCiD2
hi warp!
2009-10-05 27814, 2009
warp
anyone else here? :)
2009-10-05 27816, 2009
aCiD2
got your captain hat on today?
2009-10-05 27852, 2009
navap is around
2009-10-05 27814, 2009
warp
aCiD2: if the captain hat means being able to set the topic, then no.
2009-10-05 27819, 2009
aCiD2
lol
2009-10-05 27829, 2009
warp
<BANG>
2009-10-05 27841, 2009
nikki is here too
2009-10-05 27850, 2009
warp
hello everyone, ruaok is in the middle of a conference and can't be here for this meeting.
2009-10-05 27810, 2009
warp
I do have some updates from him I'll start off with
2009-10-05 27825, 2009
warp
then I assume aCiD2 will be able to tell us something about his week
2009-10-05 27831, 2009
murdos joined the channel
2009-10-05 27833, 2009
aCiD2 nods
2009-10-05 27835, 2009
warp
I'll touch on the style guidelines
2009-10-05 27843, 2009
warp
do we have anything else ?
2009-10-05 27806, 2009
aCiD2
I wouldn't mind discuss what to do about "stuck reviews"
2009-10-05 27842, 2009
warp
ok
2009-10-05 27834, 2009
warp
so, imagine we have a topic which contains: review (ruaok), review (acid2), style guidelines, stuck reviews.
2009-10-05 27859, 2009
warp
i'll just copy/paste from his e-mail:
2009-10-05 27805, 2009
warp
- was sick for a couple of days :(
2009-10-05 27828, 2009
warp
- worked on updating the relax NG schema for the XML 2.0. I'll finish it up and put it up for review on Wednesday.
2009-10-05 27853, 2009
warp
- worked on hosting with Dave. We are working to rearrange some servers to expand our overall capacity.
2009-10-05 27811, 2009
aCiD2
sounds like an ok week for rob :)
2009-10-05 27820, 2009
warp
Pcworld.com is ready to publish another Picard Pcworld.com is ready to publish another Picard Dave is working on this today/tomorrow.
2009-10-05 27820, 2009
aCiD2
shame about the illness creaping in again
2009-10-05 27825, 2009
warp nods.
2009-10-05 27843, 2009
warp
(I've been somewhat ill these past few days too, which is annoying).
2009-10-05 27859, 2009
warp
hm, that paste went wrong.
2009-10-05 27808, 2009
warp
copy/pasting from mutt is also annoying :)
2009-10-05 27827, 2009
warp
Pcworld.com is ready to publish another Picard review, but I want to hold them off until we have these changes in place.
2009-10-05 27837, 2009
warp
Dave is working on this today/tomorrow.
2009-10-05 27856, 2009
warp
- worked on streamlining paying Oliver, but dealing with banks takes too much time. :(
2009-10-05 27817, 2009
warp
that's it for ruaok, any questions on this you'll have to ask him yourself when he's back
2009-10-05 27822, 2009
warp
:)
2009-10-05 27843, 2009
aCiD2
cool
2009-10-05 27848, 2009
aCiD2
want me to take over?
2009-10-05 27806, 2009
warp
cool indeed, it's fun when the press mentions us :)
2009-10-05 27810, 2009
warp
yes, please take over.
2009-10-05 27812, 2009
aCiD2
ok
2009-10-05 27832, 2009
aCiD2
my week was a bit slower than I really wanted... I carried on chipping away at the release editor, but I'm really hitting a blocking point until I get the reviews through
2009-10-05 27836, 2009
aCiD2
nontheless, here's where we are:
2009-10-05 27807, 2009
aCiD2
we have editing for overlays, the label lookup is "complete" to the best of my knowledge, I've also rewritten the track/medium arranging code to just do it manually, and it happens to work a treat
2009-10-05 27809, 2009
aCiD2
the artist credit editor is in a semi-finished state locally, but I don't really want to work on that until the label lookup works
2009-10-05 27810, 2009
aCiD2
well, is shipped even
2009-10-05 27811, 2009
pronik is back
2009-10-05 27811, 2009
aCiD2
Still to be done is creating new tracks/mediums, and then I think it's done though :)
2009-10-05 27812, 2009
warp
pronik: yay!
2009-10-05 27853, 2009
warp
aCiD2: want to continue on to the stuck reviews?
2009-10-05 27801, 2009
aCiD2
sure
2009-10-05 27822, 2009
aCiD2
basically, these reviews have been waiting for a final ship it or more feedback for a few days now, so I see to options. we either wait, or we ship as is
2009-10-05 27842, 2009
aCiD2
it depends on what our view on reviews is actually for -- is it to guarantee complete functionality, or is it to prevent small bugs in individual commits?
2009-10-05 27853, 2009
warp
are you waiting for ruaok, luks, either, or both of them to review these commits?
2009-10-05 27803, 2009
aCiD2
anyone really, just a final nod of approval
2009-10-05 27808, 2009
pronik
I'd say ship it if they've stayed in queue for longer than a couple of days
2009-10-05 27818, 2009
aCiD2
if we're using reviews for the latter, I think we may be ok with a "expiry" date on reviews
2009-10-05 27846, 2009
aCiD2
it just starts to get annoying having to juggle work that depends on 2 branches, and having to constantly merge all sorts of stuff on changes, which is why it's slowing me down
2009-10-05 27847, 2009
luks
I think it's ok to ship them
2009-10-05 27854, 2009
aCiD2
great
2009-10-05 27806, 2009
luks
I'm sorry for not reviewing the patches, but I've been quite busy lately
2009-10-05 27806, 2009
aCiD2
if I can ship them I can move them into more testing with #mb people too
2009-10-05 27813, 2009
warp
aCiD2: I'm not an MB developer ofcourse, but from seeing you people use them I would say most of the benefit is in catching design flaws early
2009-10-05 27822, 2009
aCiD2 nods
2009-10-05 27826, 2009
warp
aCiD2: does this solve your reviews issue, or are there multiple reviews waiting, some of which you think need to actually be reviewed?
2009-10-05 27842, 2009
aCiD2
no, I think the reviews have had the most pressing issues ironed out now
2009-10-05 27852, 2009
warp
ok :)
2009-10-05 27852, 2009
aCiD2
I wouldn't ship without any feedback, but the ones I'm waiting on have at least had that
2009-10-05 27857, 2009
aCiD2
so that clears that up! thanks
2009-10-05 27809, 2009
warp
out of curiousity
2009-10-05 27818, 2009
warp
luks, aCiD2: what will you be working on this week?
2009-10-05 27832, 2009
aCiD2
release editor for more, maybe picking up some small perl tasks if I get bored
2009-10-05 27844, 2009
luks
nothing mb-related, I'm afraid
2009-10-05 27847, 2009
aCiD2
oh, I should add in - uni starts again now for me (started today), so i'll be back to fitting work in between
2009-10-05 27854, 2009
warp
luks: ok
2009-10-05 27811, 2009
warp
aCiD2: ah, right. how many hours on average will you be able te spend on mb?
2009-10-05 27821, 2009
aCiD2
going back to scheduling 16 a week
2009-10-05 27826, 2009
aCiD2
at least
2009-10-05 27807, 2009
warp
ok, I think that's it for all the actual development stuff
2009-10-05 27806, 2009
warp
regarding the style guidelines,..
2009-10-05 27822, 2009
luks
I probably won't do much MB development this month
2009-10-05 27836, 2009
luks
this is the last month at my current job, also I'm working on my thesis so that I can finally finish the school
2009-10-05 27809, 2009
warp
ah, right.
2009-10-05 27842, 2009
aCiD2
nice
2009-10-05 27845, 2009
warp
With the help of nikki I've put together a table-of-contents for the post NGS styleguidelines
2009-10-05 27853, 2009
aCiD2
good luck luks :) will you still be around just for little discussions for time to time?
2009-10-05 27859, 2009
warp
(some of you probably know this already :)
2009-10-05 27836, 2009
warp
I was hoping brianfreud could have a look at them before this meeting too, but I haven't seen him around much.
2009-10-05 27848, 2009
luks
aCiD2: yes
2009-10-05 27840, 2009
aCiD2
warp: are they online?
2009-10-05 27841, 2009
warp
One of the things I want to do to the style guidelines is not just improve the content
2009-10-05 27815, 2009
warp
aCiD2: my toc.txt is only on my computer at home ( http://frob.nl/~warp/toc.txt ), as it was for now just intended for this group here.
2009-10-05 27832, 2009
warp
aCiD2: but I'll post it to mb-style soon to get more feedback there.
2009-10-05 27840, 2009
aCiD2
ok
2009-10-05 27805, 2009
warp
But, I also want to improve our presentation of the guidelines, to make it more accessible to new users, etc..
2009-10-05 27813, 2009
warp
for this, I need some help :)
2009-10-05 27833, 2009
warp
pronik: can I poke you with some ideas after the meeting?
2009-10-05 27813, 2009
pronik
warp: yeah, np
2009-10-05 27836, 2009
warp
also, does anyone here happen to know anything about what currently drives the transcluded pages on musicbrainz.org/doc ?
2009-10-05 27846, 2009
nikki
how do you mean?
2009-10-05 27830, 2009
warp
how is that rendered, is it screenscraped from mediawiki? or are we called their renderer, or do we have our own renderer with a subset of wiki-syntax?
2009-10-05 27845, 2009
warp
s/called/calling/
2009-10-05 27856, 2009
nikki
there's a mediawiki thing which just outputs the content
2009-10-05 27813, 2009
nikki
and as far as I know, that gets embedded in the page
2009-10-05 27821, 2009
warp
ah, ok
2009-10-05 27837, 2009
aCiD2
yea
2009-10-05 27839, 2009
navap
There's an argument you can add to an article URL and it gives you just the html of the article, than we have a separate css file that formats it.
2009-10-05 27853, 2009
aCiD2
Same as moinmoin, basically
2009-10-05 27807, 2009
warp
ok, so if we want to customize that look, we can very easily muck with the .css, but anything else will be much more work.
2009-10-05 27849, 2009
navap
If you change the html in the article, that change will be reflected on /doc as well, so it's not too hard.
2009-10-05 27858, 2009
warp nods.
2009-10-05 27811, 2009
navap
I'm not sure how the new /doc will work though.
2009-10-05 27817, 2009
MBChatLogger
pronik probably meant ' iirc we still don't have fixed version transclusion, i.e. musicbrainz.org/docs shows the latest wiki version, right? '
2009-10-05 27817, 2009
pronik
iirc we still don't have fixed version transclusion, i.e. mb.org/docs shows the latest wiki version, right?
2009-10-05 27820, 2009
aCiD2
same type of thing navap
2009-10-05 27826, 2009
navap
pronik: No that was fixed.
2009-10-05 27835, 2009
pronik
oh, must have missed that
2009-10-05 27840, 2009
aCiD2
different code, same procedure though
2009-10-05 27842, 2009
navap
aCiD2: But the css in /doc is not the same as on wiki.
2009-10-05 27859, 2009
navap
So making changes will be harder because it will look different in bth places.
2009-10-05 27834, 2009
aCiD2
What do you mean?
2009-10-05 27839, 2009
aCiD2
oh right
2009-10-05 27845, 2009
aCiD2
but we have that problem now anyway
2009-10-05 27817, 2009
navap
Curently the css is about 99% the same in both places, so what you see in wiki is what you should see on /doc.
2009-10-05 27832, 2009
warp
I don't think that's too much of an issue. if /doc looks significantly better for example, we just need to point people at the /docs version everywhere -- and consider the wiki versions just as the backend for mb-style.
