#musicbrainz-devel

/

      • luks
        no, we discussed it and we decided to move it to the first name-credit element
      • 2009-10-01 27448, 2009

      • luks
        but the example was never updated
      • 2009-10-01 27400, 2009

      • ruaok
        oh.
      • 2009-10-01 27404, 2009

      • luks
        brian found the problem initially
      • 2009-10-01 27412, 2009

      • ruaok
        I must've missed that conclusion.
      • 2009-10-01 27414, 2009

      • ruaok goes to fix
      • 2009-10-01 27420, 2009

      • ruaok
        luks: wanna try google wave?
      • 2009-10-01 27405, 2009

      • luks
        why not, let's see what the hype is about :)
      • 2009-10-01 27413, 2009

      • ruaok
        join phrase fixed.
      • 2009-10-01 27445, 2009

      • ruaok
        its not much yet, since none of my friends are online.
      • 2009-10-01 27453, 2009

      • ijabz
        ta :)
      • 2009-10-01 27405, 2009

      • ruaok
        not sure when you'll get an invite... but I just invited you.
      • 2009-10-01 27416, 2009

      • ruaok
        when you get in, can you please invite other brainerz?
      • 2009-10-01 27427, 2009

      • ruaok
        I have too many people asking for invitations already.
      • 2009-10-01 27442, 2009

      • luks
        ok
      • 2009-10-01 27447, 2009

      • aCiD2
        oo, i wanna check wave out too :P
      • 2009-10-01 27413, 2009

      • ruaok
        luks will help you out when he gets in, k?
      • 2009-10-01 27447, 2009

      • nikki
        what is it supposed to be?
      • 2009-10-01 27432, 2009

      • ruaok
        a new, threaded (wave) form of communication that blends a bunch of communication methods....
      • 2009-10-01 27450, 2009

      • nikki
        hmm...
      • 2009-10-01 27453, 2009

      • ruaok
      • 2009-10-01 27423, 2009

      • nikki wonders if live transmission as you type means everyone can see your mistakes or what...
      • 2009-10-01 27405, 2009

      • ruaok
        aCiD2: if you can hook me up with timesheets for the first and last weeks of sept, I can hook you up with a paycheck.
      • 2009-10-01 27424, 2009

      • aCiD2
        cool, I have timesheets for last week, first week I really don't know about though :(
      • 2009-10-01 27448, 2009

      • ruaok wags finger at aCiD2
      • 2009-10-01 27421, 2009

      • aCiD2
        i'll try and work out what I did from git commits and stuff
      • 2009-10-01 27436, 2009

      • ruaok
        luks: actually, it looks like wave invites take a while to go out.
      • 2009-10-01 27453, 2009

      • ruaok
        I'm going to invite aCiD2 on this first round so all three of us can start playing.
      • 2009-10-01 27406, 2009

      • aCiD2
        cool :)
      • 2009-10-01 27414, 2009

      • navap
        nikki: Mistakes and all :p
      • 2009-10-01 27446, 2009

      • navap
        I would also love to check out Wave, just throwing that out there ;)
      • 2009-10-01 27443, 2009

      • aCiD2
        :P
      • 2009-10-01 27458, 2009

      • ruaok
        navap: get on aCiD2 and luks' good side.
      • 2009-10-01 27406, 2009

      • ruaok
        I've already spent most of my invites.
      • 2009-10-01 27418, 2009

      • nikki
        how many do you get?
      • 2009-10-01 27438, 2009

      • navap
        That reminds me, why does gmail sill have invites.
      • 2009-10-01 27452, 2009

      • navap
        I have 95 gmail invites left :/
      • 2009-10-01 27454, 2009

      • nikki
        haha
      • 2009-10-01 27415, 2009

      • ruaok
        8
      • 2009-10-01 27425, 2009

      • nikki
        ah right
      • 2009-10-01 27438, 2009

      • navap
        That's a decent number of invites.
      • 2009-10-01 27448, 2009

      • navap
        I think gmail started out with 3 invites.
      • 2009-10-01 27419, 2009

      • ruaok
        its more critical here since you can only wave with other wavers.
      • 2009-10-01 27436, 2009

      • aCiD2 nods
      • 2009-10-01 27436, 2009

      • ruaok
        where gmail was more useful even if you were the only one using it.
      • 2009-10-01 27435, 2009

      • navap
        So...what do aCiD2 and luks need getting done :p
      • 2009-10-01 27446, 2009

      • ruaok
        lol
      • 2009-10-01 27418, 2009

      • ruaok runs off to the office
      • 2009-10-01 27450, 2009

      • warp recommends gtimelog to aCiD2
      • 2009-10-01 27458, 2009

      • aCiD2
        warp: thanks, i'll check that out!
      • 2009-10-01 27401, 2009

      • aCiD2
        i'm using timeclock.el atm
      • 2009-10-01 27409, 2009

      • aCiD2
        but I always struggle to find a good time logging system
      • 2009-10-01 27437, 2009

      • warp
        I liked gtimelog because of how little effort it takes to record what you're doing
      • 2009-10-01 27445, 2009

      • aCiD2
        yea, looks very clean
      • 2009-10-01 27448, 2009

      • aCiD2
        hamster is pretty nice too
      • 2009-10-01 27409, 2009

      • warp
        just type 'arrived' at the start of the day, and then with each context switch type what you've been doing, and it records how long you've spent doing it.
      • 2009-10-01 27431, 2009

      • warp
        any entry suffixed with two asterisks is considered non-productive.
      • 2009-10-01 27444, 2009

      • aCiD2
        cool :)
      • 2009-10-01 27455, 2009

      • aCiD2
        maybe logging non productive stuff will get me being more productive too :P
      • 2009-10-01 27424, 2009

      • aCiD2
        thanks warp, i'll bookmark this
      • 2009-10-01 27451, 2009

      • warp
        recent versions also allow you to enter '-30 foo bar', for those times where you forgot to switch context 30 minutes ago.
      • 2009-10-01 27426, 2009

      • aCiD2
        neat!
      • 2009-10-01 27440, 2009

      • warp
        I don't use it anymore because our in-house tool at work is workable, but I used it about a year before that.
      • 2009-10-01 27400, 2009

      • warp
        for about a year.
      • 2009-10-01 27414, 2009

      • warp
        now back to thinking about the style guidelines.
      • 2009-10-01 27415, 2009

      • warp
        :)
      • 2009-10-01 27425, 2009

      • warp pings brian once more.
      • 2009-10-01 27452, 2009

      • nikki is watching this video about the spelling correction thingy in google wave...
      • 2009-10-01 27459, 2009

      • aCiD2
        warp: you didn't see my message? :p
      • 2009-10-01 27419, 2009

      • navap
        nikki: Have you seen the mass collaboration part yet?
      • 2009-10-01 27440, 2009

      • warp
        aCiD2: you said that brian yesterday said he would be away for 24 hours. surely 24 hours have passed by now.
      • 2009-10-01 27445, 2009

      • nikki
        no, I wasn't likely to start with that one, was I? :P
      • 2009-10-01 27415, 2009

      • warp
        ooh, wave. some of you have accounts?
      • 2009-10-01 27420, 2009

      • aCiD2
        warp: let me find the time
      • 2009-10-01 27440, 2009

      • aCiD2
        warp, hrm sent 22 hours ago
      • 2009-10-01 27444, 2009

      • aCiD2
        so he should be back in 2 apparently
      • 2009-10-01 27450, 2009

      • warp
        haha, ok :)
      • 2009-10-01 27401, 2009

      • warp
        ooh. warp20.
      • 2009-10-01 27402, 2009

      • ruaok joined the channel
      • 2009-10-01 27418, 2009

      • ruaok
        navap: what is your email that you want to use for google wave?
      • 2009-10-01 27440, 2009

      • navap
        pchander [at] gmail
      • 2009-10-01 27444, 2009

      • navap
        Thanks! :D
      • 2009-10-01 27418, 2009

      • warp needs user interaction / graphic design people
      • 2009-10-01 27409, 2009

      • warp
        navap: hm, did you do layout stuff on mediawiki for mb?
      • 2009-10-01 27434, 2009

      • navap
        I designed the theme, but the layout is essentially the same as the default mediawiki theme.
      • 2009-10-01 27446, 2009

      • ruaok
        navap: pronik should be inviting you
      • 2009-10-01 27447, 2009

      • warp
        well atleast my memory isn't failing me then :)
      • 2009-10-01 27456, 2009

      • navap
        s/designed/did the colours for/ :p
      • 2009-10-01 27403, 2009

      • navap
        :)
      • 2009-10-01 27428, 2009

      • warp
        navap: any idea how easy we can change the layout of specific pages?
      • 2009-10-01 27437, 2009

      • navap
        What did you have in mind?
      • 2009-10-01 27440, 2009

      • warp
        I'm working on revamping the style guidelines for a post NGS musicbrainz
      • 2009-10-01 27420, 2009

      • warp
        What _I_ would like, is some way to clearly distinguish on a particular guideline page the core guideline, and all the examples and edge cases that go with it.
      • 2009-10-01 27429, 2009

      • navap
        So is separating via headings (<h2>,<h3>) not what you had in mind?
      • 2009-10-01 27439, 2009

      • warp
        a bit similar to how creative commons has a human-readable page and a detailed legal page for a license, although the seperation shouldn't be _that_ drastic :)
      • 2009-10-01 27454, 2009

      • navap
        Do you have a mockup or something? I'm a bit confused with what kind of a layout change you would want to do.
      • 2009-10-01 27440, 2009

      • warp
        no, not yet. I was hoping to get some people here to help me on that. I also want to poke pronik on this.
      • 2009-10-01 27440, 2009

      • navap is finding it hard to take SortnameStyle and make it look as simple as a CC page. http://wiki.musicbrainz.org/Sortname_Style http://creativecommons.org/licenses/by-sa/3.0/
      • 2009-10-01 27409, 2009

      • navap
        But regarding layout changes, you can stick css into an article.
      • 2009-10-01 27437, 2009

      • warp
        we'll be rewriting most of the style guidelines
      • 2009-10-01 27440, 2009

      • navap
        So if you create a few css declarations you can add them to the wiki's css pages and use them from the articles.
      • 2009-10-01 27444, 2009

      • navap
        That's true.
      • 2009-10-01 27406, 2009

      • warp
        I intend to merge and simplify where possible :)
      • 2009-10-01 27430, 2009

      • jacckk
        Would a mediawiki template message do what you wish?
      • 2009-10-01 27432, 2009

      • navap
        I think what warp had in mind involved more than just reusing text on multiple pages.
      • 2009-10-01 27447, 2009

      • navap
        In fact that's the opposite of what we want to do I think. We want to avoid duplicating content.
      • 2009-10-01 27451, 2009

      • nikki
        yeah
      • 2009-10-01 27457, 2009

      • warp
        navap: actually, the sortname style is a fairly good example. the content under 'Guidelines' is the actual guideline, and should be clearly visible when you open the page.
      • 2009-10-01 27406, 2009

      • navap
        Yeah I thought it was one of our better organized guidelines, although I have a slight bias there ;)
      • 2009-10-01 27411, 2009

      • jacckk
        Ah okay, i dont see how its duplicating content though?
      • 2009-10-01 27413, 2009

      • warp
        navap: all the examples are less important, and mostly useful to those readers who want to confirm their understanding of the guideline.
      • 2009-10-01 27423, 2009

      • ijabz
        ruaok , so I've added code for MMD1 artists & releasegroups using ngs , the only problem is the V1 releasegroup schema only lets one artist be linked to releasegroup , so if have multiple name credits we can construct a single artist name from them np, but dont know what to do about the artistId element
      • 2009-10-01 27425, 2009

      • nikki suggested an expandable box
      • 2009-10-01 27427, 2009

      • navap
        jacckk: Because a template is designed to reuse the same content on multiple pages.
      • 2009-10-01 27441, 2009

      • navap
        Unless I'm misunderstanding what you meant..
      • 2009-10-01 27411, 2009

      • navap
        nikki: Yeah
      • 2009-10-01 27414, 2009

      • ruaok
        ijabz: why mmd1 and not 2?
      • 2009-10-01 27443, 2009

      • navap
        warp: Pronik had been poking around trying to get the expanding boxes like Wikipedia has at the bottom of the pages. But I don't think he had much luck.
      • 2009-10-01 27401, 2009

      • ijabz
        1st step fix code so can can generate existing output from new db, 2nd step generate MMD output
      • 2009-10-01 27420, 2009

      • navap
        By getting those working that would eliminate all the crap^wuseful links at the top of each article.
      • 2009-10-01 27425, 2009

      • navap
        And move them to the bottom.
      • 2009-10-01 27426, 2009

      • jacckk
        It's refrenced like {{templatename}} and then that is pulled from a template file. You know the messages on wikipedia that go like "The neutrality of this article is disputed.". If thats not what you were thinking of ;D
      • 2009-10-01 27459, 2009

      • jacckk
      • 2009-10-01 27407, 2009

      • warp
        navap: ok, that would help.
      • 2009-10-01 27414, 2009

      • nikki
        hmm...
      • 2009-10-01 27416, 2009

      • ijabz
        and I cant really fo 2nd step until i have a RelaxNG for MMD2, and a better idea of what fields you want to search for anyway
      • 2009-10-01 27429, 2009

      • navap
        jacckk: That is what I was thinking, and as I said the whole purpose behind that is duplication. You can use a template to avoid having to type out the same thing over and over, that's not what we want. We want to avoid duplication like that in the guidelines.
      • 2009-10-01 27435, 2009

      • nikki
        jacckk: it's more about within the actual page, not marking specific pages
      • 2009-10-01 27456, 2009

      • warp
        jacckk: not at all what i'm thinking of, no.
      • 2009-10-01 27457, 2009

      • jacckk
        ah right, sorry :)
      • 2009-10-01 27415, 2009

      • navap
        Since we're merging various guidelines, we can use the release/track/RG icons to diffrenciate between sections on th esame page. Vaguely emulating how CC does it.
      • 2009-10-01 27454, 2009

      • luks
        note that the wiki is not what we point users to
      • 2009-10-01 27421, 2009

      • MBChatLogger
        luks probably meant ' wiki is a way to collaborate on those pages, but musicbrainz.org/doc/Page is where the final version is '
      • 2009-10-01 27421, 2009

      • luks
        wiki is a way to collaborate on those pages, but mb.org/doc/Page is where the final version is
      • 2009-10-01 27422, 2009

      • warp
        luks: oh, well, I usually do :)
      • 2009-10-01 27415, 2009

      • warp
        luks: but you're right, it probably would suffice to have better interaction on the musicbrainz.org/doc/foo pages, instead of the wiki.
      • 2009-10-01 27432, 2009

      • ijabz
        ruaok In case you're worried Im wasting time here, don't be , 90% of the changes I've made are on the indexing side and will apply to MMD1 and MMD2
      • 2009-10-01 27444, 2009

      • ruaok
        I'm not. :)
      • 2009-10-01 27403, 2009

      • navap
        Should the wiki css be updated to reflect how it looks on the /doc pages?
      • 2009-10-01 27425, 2009

      • ruaok
        I dont think that is needed.
      • 2009-10-01 27428, 2009

      • luks
        warp: anyway, I think content is more important than how it's displayed here :)
      • 2009-10-01 27440, 2009

      • nikki
        oh, while people are here... what should we do about artists? being able to link more than one artist is going to open a can of worms when it comes to things like featuring artists
      • 2009-10-01 27400, 2009

      • warp
        luks: no, graphic design is the most important!
      • 2009-10-01 27401, 2009

      • warp
        ;)
      • 2009-10-01 27431, 2009

      • navap
        Featured artists in artist names should still follow the feat guideline which says move it to the track title.
      • 2009-10-01 27441, 2009

      • navap
        And if they're in the track name then they can't be linked to.
      • 2009-10-01 27405, 2009

      • warp
        luks: yes, content is most important. but I think improving the presentation also helps in getting people to actually read the guidelines.
      • 2009-10-01 27430, 2009

      • luks
        I don't disagree
      • 2009-10-01 27441, 2009

      • navap
        Simplifying the content could also be considered better presentation. ;)
      • 2009-10-01 27446, 2009

      • luks
        just saying that having those guidelines should be step 1, IMO :)