#musicbrainz-devel

/

      • kepstin-laptop
        IMO, should move the ISWC column after type and language
      • the later are probably more important
      • might actually make sense to merge the ISWC and attributes columns (i.e. treat iswc as an attribute)
      • navap
        What are attribute again?
      • kepstin-laptop
        stuff like jasrac id, key, raga, etc.
      • navap
        Oh right
      • kepstin-laptop
        hmm. I've never really liked the way that bootstrap line-wrapped tabs look
      • nikki would rather see attributes as columns (and a way of deciding which columns to show)
      • nikki
        like type, raga and tala are all pretty irrelevant to me, but I'd generally like to see jasrac id and iswc... non-japanese editing people probably couldn't give a shit about jasrac ids :P
      • navap
        +1 to that, but maybe for later....
      • nikki
        so in the meantime I'd just leave it as it is
      • kepstin-laptop
        well, reordering language before iswc so it's more visible on phone screens probably still isn't a bad idea :)
      • nikki
        that makes sense, yes
      • navap
        It makes sense to go through and optimize column order in a lot of places
      • Since we brought up the footer, what do we do with it and all those links?
      • hawke1
        nuke them from orbit?
      • navap
        Well google analytics does suggest no one uses most of those links...
      • nikki
        getting rid of h1-sized headings would help
      • navap
        heh and I just decreased all of the heading sizes earlier today
      • nikki
        (they're h2s, it seems, but for some reason the h2s are the same font size as the h1s)
      • kepstin-laptop
        at the very least, remove everything but about, contact, and maybe developers
      • navap
        The headers in the footer are 16px, whereas regular text is 12 px
      • hawke1
        +1 kepstin…I was just working on saying basically that. ;-)
      • nikki
        both h1 and h2 are 25px for me
      • navap
        nikki: Sounds like a caching issue
      • hawke1
        kepstin: All the rest could go in a single 'documentation' page, yeah — a landing page on the wiki that can take you to all that other stuff.
      • nikki
        navap: same in chrome and I haven't loaded it in chrome before
      • navap
        h2's should be 18px and they're now 12px in the footer
      • I reduced h2's from 25px to 18px a few hours ago. Have you ever loaded my sandbox in chrome? I still think it's a caching issue
      • derwin
        I wish that the new pop up artist stuff
      • wasn't just over one page in size
      • so that I don't have to click outside of the modal
      • and then page down
      • nikki
        uh, possibly weeks ago?
      • derwin
        and then inside the modal
      • and then page down
      • nikki
        same in firefox..
      • loading safari now
      • navap
        Is anyone else seeing 25px h2's?
      • nikki
        safari is the only one which hasn't
      • I could maybe understand it in opera, but why the fuck would chrome and firefox be loading weeks-old (at least) cached stuff?
      • hawke1
        I show 16-px in chrome's document inspector
      • ianmcorvidae
        LESS compiles it to localStorage, which is very annoying
      • this may be related
      • kepstin-laptop is definitely getting 16px in his firefox
      • if you open a console and run localStorage.clear() that'll ensure it, anyway
      • kepstin-laptop
        it's a pity that firefox has no UI to view or clear local storage yet :/
      • nikki
        will that clear it for all sites or only the current one?
      • ianmcorvidae
        just the current
      • fwiw, doing so on navap.mbsandbox for me changed them from 25px to 18px (along with a page refresh of course)
      • nikki
        it seems like it's a bit pointless having the in-browser compiling stuff if it means you can't just edit the styling as you like anyway
      • navap
        Wow, chrome shows I've got a ton of different common.less cached from jan 30th
      • ohrstrom joined the channel
      • Whenever I edit the less I just regular refresh chrome and it works right away
      • I haven't run into cache issues
      • ianmcorvidae
        it seems to be fairly finicky in terms of when it does and doesn't bother to refresh things
      • nikki has just got into the habit of using the compiled one and then doing touch lib/DBDefs.pm
      • navap
        If I had to wait for my server to restart each time I edited the less I'd quit... :(
      • Where my server == rika
      • nikki
        downloading all the less files isn't very fast anyway :P
      • nikki shrugs
      • it seems problematic though if you can never be sure other people are seeing what you are
      • navap
        Oh yeah, hang on, I'm tacking on a timestamp to the less file so that you should always get the latest version. So I wonder how you ended up with that cached version
      • Freso
        kepstin-laptop: Heh. I was trying to figure out where "pity" was a pain in.
      • kepstin-laptop is missing some context for that
      • navap
        hawke1, kepstin-laptop: Given that the footer height is the same now that I've removed the extra taggers section, does it still make sense to remove more of the columns?
      • Or rather the footer height won't change by removing more columns
      • kepstin-laptop
        you could make the links in each section multiple columns to make the footer wider and less tall
      • misterswag joined the channel
      • hawke1
        navap: I guess nikki might be the one to say if it’s short enough now.
      • Freso
        kepstin-laptop: "it's a pity that firefox has no UI to view or clear local storage yet :/"
      • nikki
        well, the headers are still gigantic for me
      • but fewer links is good
      • it would probably also help to have one footer, not two :P
      • I wonder if "downloads" is a good idea... we already get people who think we're providing music downloads, I thought
      • spinza joined the channel
      • navap
      • nikki: refresh
      • Gentlecat
        navap: I feel like body needs some margin on left and right sides
      • nikki
        still getting gigantic headers... the sections feel a bit too spread out now though
      • (maybe centred would be better)
      • I dunno...
      • when I said I agreed with removing links, I wasn't quite thinking of leaving a small selection at the top and dumping loads of others at the bottom instead
      • hawke1
        I would be fine with removing a bunch more links — maybe keep the three kepstin mentioned (about, contact, developers) as links to /doc landing pages for each?
      • (and have nothing under them)
      • navap
        Only providing links to those pages is just repeating the top menu though
      • hawke1
        Not really — those are (presumably?) less-used links.
      • i.e. top bar is for editors to actually do stuff, while the bottom is reference stuff
      • navap
        Offtopic: What's a word we could use to describe both customers and sponsors?
      • nikki would just link to those from "about" anyway
      • hawke1
        partners?
      • (that feels like kind of a loaded business-word which might imply more than it really is, but…)
      • nikki
        supporters?
      • hawke1
        Hey, I’m a supporter. :-p
      • navap
        hawke1: And you're listed buried in the small print on the sponsors page ;)
      • hawke1
        (I would tend to associate 'supporter' more as people who donated or something, not customer)
      • am I?
      • navap
        Oh wait, that's just donaters
      • hawke1
        which is a line-item on sponsors I guess
      • Freso
        I don't think "Partners" would be a bad word.
      • Sure, it's business-y, but that's not necessarily a bad thing.
      • nikki
        partners seems wrong to me
      • Freso
        And there are many ways to be a "partner".
      • hawke1
        I think it would be OK, but sometimes it implies … working-together-on-a-joint-project-in-something-formal.
      • Freso
        "Money sources"
      • nikki
        to me it implies we're working together, which isn't the case if someone just donates money in the way that sponsors do, nor is it the case for most of our customers
      • I dunno, why are you even looking for a single word, navap?
      • Freso
        hawke1: Which we do! We work together in that they provide MeB funds to run MB.
      • hawke1
        Freso: yeah — it’s not a bad word at all.
      • Freso
        (Which is not an uncommon type of partnership in the business world, IME.)
      • navap
        nikki: To find a way to remove one of the links in the footer for you :p
      • nikki
        remove both, link to them from the about page? :P
      • navap
        I want to give them as much visibility as possible. Customers add legitimacy to us
      • hawke1 notes that the 'donate' page is not easy enough to find. :-)
      • bitmap
        or just name the link Customers & Sponsors or something :P
      • navap
        Side note: I'm moving those two pages into the MB namespace
      • nikki
        I can't say I've ever gone "I really need to know who metabrainz's customers are! oh, thankfully musicbrainz links directly to it from every single page!" :/
      • navap
        bitmap: Yeah, but then what's the url?
      • Freso
        nikki: Sure. But you're already part of MB.
      • bitmap
        well, I thought you were combining them somehow anyway since you wanted a single word
      • nikki
        Freso: I can't say I've ever gone to any site and needed to find a direct link to their customers
      • navap
        bitmap: I think I'm not too sure on what I want to do with those two words/pages...
      • nikki
        I'd either expect it as part of some "about" text or on the main page
      • navap
        nikki: You're also not someone who is willing to pay thousands of money per year on music data
      • thousands of dollars*...
      • ianmcorvidae
        heh thousands of money
      • navap
        s/willing/looking/ is probably more accurate
      • kepstin-laptop could spend thousands of japanese yen per year on music data without issue ;)
      • kepstin-laptop
        why don't we have a single 'about' link that brings you to a page with info about musicbrainz, people, and a customers section?
      • navap
        On the topic of customers, what are people's thoughts of showing some logos on the home page?
      • nikki
        I guess what I'm saying is that it feels out of context, it's not really a page designed to get people to give us money (that's probably closer to "donate"), nor is it really promotion, since it's just a link sitting there where almost nobody will click it
      • hawke1
        I’d expect to see it maybe on the front page, but not in the footer of every page
      • nikki
        yeah
      • navap
        hawke1: Logos? Yes that's all I had in mind
      • nikki
        but yes, I'm not a big company and definitely don't understand how they think :P
      • hawke1
        navap: some sort of Customers heading with highlights.
      • Something like what community/database/developers is on the front page now.
      • Just saying I wouldn't necessarily expect it on every page.
      • navap
        Can someone tell me which language link/box to use? Bordered or unbordered?
      • ianmcorvidae
        navap: I hadn't looked before, do you have a link handy for what the two look like?
      • navap
      • (at the bottom)
      • ianmcorvidae
        where it's sitting right now it doesn't look like it's clickable unless it's bordered
      • so what I'd say is
      • if it's going to be isolated away from other menuy things then border, if it's alongside other things that are obviously links, unbordered
      • navap
        I've removed the sponsors/customers links and also moved some of the links at the bottom up into the big footer. All that I've got left is a link to donate and to twitter
      • ianmcorvidae
        (well, the arrow would help with making it clear it's clickable without the border, but I think I'd still go with the border for that)
      • navap
        Bordered it is.
      • kepstin-laptop
        you definitely need 1px dotted borders around everything
      • ;)