#metabrainz

/

      • Leo_Verto
        Eloquently yet simple
      • 2016-01-22 02214, 2016

      • Leo_Verto
        Almost as if it was a Wikipedia summary
      • 2016-01-22 02232, 2016

      • gcilou
        ^
      • 2016-01-22 02238, 2016

      • bitmap
        ;)
      • 2016-01-22 02222, 2016

      • Leftmost
        Probably need something longer than "Furthest to the left", eh?
      • 2016-01-22 02234, 2016

      • gcilou
        :)
      • 2016-01-22 02213, 2016

      • gcilou
        Freso, I'll make your latest changes when adding Leftmost
      • 2016-01-22 02220, 2016

      • darwin
        I talk about the "leftmost prefix" in my job all the time...
      • 2016-01-22 02221, 2016

      • Freso
        Leftmost: "Not exactly right."
      • 2016-01-22 02225, 2016

      • Freso
        So fitting in so many ways.
      • 2016-01-22 02251, 2016

      • Freso
        ;D
      • 2016-01-22 02259, 2016

      • Leo_Verto
        Leftmost, well, I was going to suggest the oxford dictionary definition, but apparently it's just that
      • 2016-01-22 02201, 2016

      • kepstin
        gcilou: should probably put a credit there to satisfy the wikipedia content license ;)
      • 2016-01-22 02219, 2016

      • Leo_Verto
        I mean, something like "furthest away from that right side" looks a lot better
      • 2016-01-22 02226, 2016

      • gcilou
        okay like link to wiki
      • 2016-01-22 02234, 2016

      • gcilou
        ?
      • 2016-01-22 02251, 2016

      • kepstin
        hmm, is that actually from wikipedia?
      • 2016-01-22 02256, 2016

      • Leftmost
        <3 u 2, Freso.
      • 2016-01-22 02212, 2016

      • gcilou
        Yes like the 2nd paragraph
      • 2016-01-22 02230, 2016

      • Freso
        4th :)
      • 2016-01-22 02242, 2016

      • gcilou
        same thing ;)
      • 2016-01-22 02249, 2016

      • kepstin
        wikipedia text is under CC-BY-SA, so just putting a small note saying "Content [CC-BY-SA], from [Wikipedia]" linking to the license and wiki page should be good.
      • 2016-01-22 02212, 2016

      • gcilou
        okay will do
      • 2016-01-22 02244, 2016

      • kepstin
        (I'd suggest using https://en.wikipedia.org/wiki/Wikipedia:CC_BY-SA as the license link if you do that)
      • 2016-01-22 02258, 2016

      • kepstin
        but http://creativecommons.org/licenses/by-sa/3.0/ is the same thing, and that's what we use for the inline wikipedia summaries on musicbrainz pages
      • 2016-01-22 02206, 2016

      • kepstin
        so, uh, whatever :)
      • 2016-01-22 02234, 2016

      • Freso
        I'd use the cc.org one.
      • 2016-01-22 02254, 2016

      • Freso
        As that's the authoritative one. But yeah, both should contain the same text.
      • 2016-01-22 02205, 2016

      • Freso
        And the bio blurb should be changed soon enough anyway.
      • 2016-01-22 02238, 2016

      • Leo_Verto
        So, "Blatantly ripped off of Wikipedia" is not a valid license note? D:
      • 2016-01-22 02217, 2016

      • gcilou
        link to wikipedia or link to bitmap page of wikipedia?
      • 2016-01-22 02233, 2016

      • kepstin
        link to the page where you got the text would be best.
      • 2016-01-22 02200, 2016

      • kepstin
        Leo_Verto: nah, with SA you need to include a license declaration so people can blatantly rip from you, too. (That would be fine without the share-alike clause tho)
      • 2016-01-22 02252, 2016

      • Leo_Verto
        Ah, are there actually any cases where not using SA would make sense?
      • 2016-01-22 02201, 2016

      • kepstin
        sure, it's approximately equivalent to using e.g. a BSD, MIT, Apache code license rather than GPL
      • 2016-01-22 02228, 2016

      • kepstin
        it just depends on which rights you want to give people using the work
      • 2016-01-22 02215, 2016

      • Leo_Verto
        Couldn't someone copy your code and release it under something like WTFPL allowing any third party to use it without any kind of attribution?
      • 2016-01-22 02244, 2016

      • Leo_Verto
        I mean, that's why non-SA CC licenses are probably so rare
      • 2016-01-22 02220, 2016

      • kepstin
        you have to read the full text of the license. The non-SA license doesn't allow you to redistribute under a license that removes the attribution clause, iirc
      • 2016-01-22 02238, 2016

      • Freso
        Leo_Verto: Even WTFPL/CC0 will not allow you to use the code without attribution in a number of jurisdictions.
      • 2016-01-22 02250, 2016

      • Leo_Verto
        Thanks for explaining that, I always wondered why SA isn't basically included in CC
      • 2016-01-22 02252, 2016

      • Freso
        s/code/"creative work"/
      • 2016-01-22 02210, 2016

      • Leo_Verto
        Yeah, which is kind of a problem :/
      • 2016-01-22 02250, 2016

      • Leo_Verto
        Taking the right of the owner to freely decide what to do with their work seems kinda odd to me
      • 2016-01-22 02241, 2016

      • kepstin
        Leo_Verto: SA requires you to grant all the same rights you have to people making derivatives of your work. BY is the opposite, it reserves a right (to redistribute), when not fulfilling a condition.
      • 2016-01-22 02214, 2016

      • kepstin
        (more or less, IANAL, etc.)
      • 2016-01-22 02249, 2016

      • Freso
        Well, if the owner of some IP has released said IP under WTFPL, they're very unlikely to press charges on you for not crediting sources properly.
      • 2016-01-22 02208, 2016

      • Leo_Verto
        Heh, true
      • 2016-01-22 02245, 2016

      • kepstin
        that said, commercial entities often avoid WTFPL stuff, particularly in europe, because it's untested and may not be a valid license in some places.
      • 2016-01-22 02251, 2016

      • Freso
        (And I would guess the same goes for most CC0 ones. If they cared about being credited, they'd've used CC-by.)
      • 2016-01-22 02220, 2016

      • gcilou
        Leftmost, is there a bio in the works?
      • 2016-01-22 02224, 2016

      • Leo_Verto
        Though it might be legally too risky to use those works when affected by these jurisdictions.
      • 2016-01-22 02258, 2016

      • kepstin
        according to what i've read, lawyers suggest that the WTFPL would *probably* be understood as the author intended in US courts.
      • 2016-01-22 02210, 2016

      • kepstin
        but it would be safer to use CC0 instead
      • 2016-01-22 02237, 2016

      • gcilou
        Freso, go on without Leftmost?
      • 2016-01-22 02249, 2016

      • Leftmost
        gcilou, I'll work on something, but it will likely be a few hours before I can get started.
      • 2016-01-22 02255, 2016

      • gcilou
        okay :)
      • 2016-01-22 02232, 2016

      • Freso
        So yes, go on to the right.
      • 2016-01-22 02200, 2016

      • gcilou
        ;)
      • 2016-01-22 02207, 2016

      • gcilou
        Freso, and submit?
      • 2016-01-22 02231, 2016

      • gcilou
        I did anyway
      • 2016-01-22 02201, 2016

      • LordSputnik
        opatel99: I've had an idea about examples
      • 2016-01-22 02212, 2016

      • LordSputnik
        But it can wait until after the guideline is accepted
      • 2016-01-22 02238, 2016

      • LordSputnik
        Leftmost: Leo_Verto: https://github.com/bookbrainz/bookbrainz-user-gui… acceptable for you?
      • 2016-01-22 02246, 2016

      • LordSputnik
        stanislas: your latest set of commit messages are definitely a huge improvement over what you were using before :D
      • 2016-01-22 02203, 2016

      • stanislas
        LordSputnik: I've figured out how to use git properly
      • 2016-01-22 02209, 2016

      • stanislas
        LordSputnik: :)
      • 2016-01-22 02212, 2016

      • Freso
        Wow.
      • 2016-01-22 02235, 2016

      • Freso
        Okay, I want to make a joke now, but I'm out.
      • 2016-01-22 02251, 2016

      • Leo_Verto
        LordSputnik, yep, seems good to me, I wouldn't mind fast-tracking the style process for this :P
      • 2016-01-22 02214, 2016

      • Leo_Verto
        Ah, sneaky commit, stanislas :P
      • 2016-01-22 02214, 2016

      • LordSputnik
        Freso: about? :P
      • 2016-01-22 02259, 2016

      • Freso goes to comemo(?) cena
      • 2016-01-22 02211, 2016

      • Freso
        LordSputnik: that there's a way to use git properly
      • 2016-01-22 02225, 2016

      • stanislas
        Leo_Verto: which one ?
      • 2016-01-22 02241, 2016

      • Leo_Verto
        The one you made two minutes ago
      • 2016-01-22 02228, 2016

      • Leo_Verto
        Freso, well, we actually have guidelines for that in (some of) our repos https://github.com/bookbrainz/bookbrainz-site/blo…
      • 2016-01-22 02229, 2016

      • LordSputnik
        opatel99: actually, if we could do examples like https://github.com/bookbrainz/bookbrainz-user-gui… (but using your examples, they're more well known), that'd be fantastic
      • 2016-01-22 02251, 2016

      • opatel99
        LordSputnik: The table?
      • 2016-01-22 02209, 2016

      • LordSputnik
        opatel99: Actually, stick with what I said before, let's do it in a new style update so we can get this task done
      • 2016-01-22 02217, 2016

      • Leftmost
        LordSputnik, opatel99, any reason that the standards aren't applied to Creators and Publishers when relevant?
      • 2016-01-22 02220, 2016

      • Freso
        Leo_Verto: Just because there are guidelines does not mean those guidelines instruct in using git *proper*.
      • 2016-01-22 02237, 2016

      • LordSputnik
        Leftmost: because those have official names
      • 2016-01-22 02239, 2016

      • opatel99
        Leftmost: Umm. Those are names?
      • 2016-01-22 02251, 2016

      • LordSputnik
        opatel99: technically titles are names too
      • 2016-01-22 02216, 2016

      • Freso
        Leo_Verto: Anyway, it was supposed to be a joke, and it didn't happen, so never mind. Move on.
      • 2016-01-22 02218, 2016

      • Leftmost
        They have official names, but generally not official capitalizations.
      • 2016-01-22 02220, 2016

      • Leo_Verto
        Freso, well, duh, it's our project so we obviously get to decide what's right :P
      • 2016-01-22 02228, 2016

      • LordSputnik
        The thing is, if there's an official source for capitalization, that should be used regardless of guidelines
      • 2016-01-22 02241, 2016

      • Freso
        Leo_Verto: Yeah. You miss the point of what would have been the joke.
      • 2016-01-22 02244, 2016

      • Leo_Verto
        and by project I mean repository
      • 2016-01-22 02245, 2016

      • LordSputnik
        "Artist intent" overrides everything
      • 2016-01-22 02201, 2016

      • Freso goes do cena f'realz
      • 2016-01-22 02224, 2016

      • Leo_Verto
        Freso, blame it on me being German, I guess
      • 2016-01-22 02226, 2016

      • Leftmost
        LordSputnik, as has been established on MB repeatedly, it's a rare case where there's artist intent involved in capitalization.
      • 2016-01-22 02211, 2016

      • LordSputnik
        Leftmost: ehh OK, I think "and Creators and Publisher where relevant" could work then?
      • 2016-01-22 02214, 2016

      • Leftmost
        If a book is explicitly titled "House Of Cards", we still capitalize it "House of Cards" because it's doubtful that the author thought, "I'm going to capitalize the o in of to make a statement".
      • 2016-01-22 02226, 2016

      • LordSputnik
        obviously with corrected spellings/punctuation :P
      • 2016-01-22 02200, 2016

      • kepstin
        do note that if something is a trademarked name, the trademark may specify particular capitalization
      • 2016-01-22 02205, 2016

      • LordSputnik
        Leftmost: well yeah, unless the author specifically spells out the capitalization, you have to assume that's a random decision by the publisher
      • 2016-01-22 02206, 2016

      • Leftmost
        Also curious about line 14. That seems... an odd addition.
      • 2016-01-22 02206, 2016

      • Leo_Verto
        Ohh
      • 2016-01-22 02216, 2016

      • kepstin
        which should be followed where applicable
      • 2016-01-22 02249, 2016

      • opatel99
        Should I split those up Leftmost ?
      • 2016-01-22 02251, 2016

      • LordSputnik
        ^ that sounds good kepstin
      • 2016-01-22 02210, 2016

      • LordSputnik
        opatel99: I don't think line 14 makes sense at the moment, have a look and see whether MB has that better
      • 2016-01-22 02234, 2016

      • Leftmost
        Line 14 should maybe be stricken, especially since it means a number of the examples are wrong. (It'd result in "How to win Friends and Influence People", for example.)
      • 2016-01-22 02249, 2016

      • Leftmost
        "Of mice and Men", "Brave new World".
      • 2016-01-22 02206, 2016

      • Leftmost
        "The old man and the Sea".
      • 2016-01-22 02231, 2016

      • opatel99
        Removed.
      • 2016-01-22 02253, 2016

      • LordSputnik
        opatel99: oh yeah, it comflicts with #2.3 from the MB guidelines we're including now
      • 2016-01-22 02235, 2016

      • LordSputnik
        opatel99: might be good to add in rules #3 and #4 from http://musicbrainz.org/doc/Style/Language/English too
      • 2016-01-22 02204, 2016

      • opatel99
        Paraphrase, or straight up add in?
      • 2016-01-22 02243, 2016

      • LordSputnik
        opatel99: they look good as they are, I think
      • 2016-01-22 02203, 2016

      • opatel99
        Did that.
      • 2016-01-22 02211, 2016

      • LordSputnik
        We might want to add a note saying these are based on the MB guidelines too
      • 2016-01-22 02210, 2016

      • LordSputnik
        eg. "These guidelines are heavily based on the MusicBrainz English Capitalisation guidelines, which have been developed over the course of several years by a group of volunteers"
      • 2016-01-22 02223, 2016

      • LordSputnik
        and link to the original page
      • 2016-01-22 02250, 2016

      • LordSputnik
        Actually, forget that, we'll stick that on the front page
      • 2016-01-22 02202, 2016

      • LordSputnik
        So we don't have to keep repeating it everywhere we borrow from the MB guidelines
      • 2016-01-22 02249, 2016

      • opatel99
        Ok. Caught up now.
      • 2016-01-22 02252, 2016

      • opatel99
        Though I am eager to have this contribution, I don't want us to overlook anything by acting rashly. I'm willing to wait the time...
      • 2016-01-22 02242, 2016

      • LordSputnik
        opatel99: I'd rather have incremental improvements than try and get it perfect first time
      • 2016-01-22 02229, 2016

      • LordSputnik
        Leftmost: Leo_Verto: I think we should also update the style process to discourage initially proposing in a PR, so that collaboration can happen more easily
      • 2016-01-22 02204, 2016

      • LordSputnik
        the more people that get involved early on, the more people invested in pushing the guideline along
      • 2016-01-22 02233, 2016

      • Freso
        👍
      • 2016-01-22 02200, 2016

      • Freso come cena
      • 2016-01-22 02210, 2016

      • Freso
        *como(?)
      • 2016-01-22 02235, 2016

      • Freso
        Did reosarevok go to sleep or why isn't he correcting me?
      • 2016-01-22 02239, 2016

      • opatel99
        I haven't heard from Mineo in a while. Did the auto sort get resolved with QSemaphore?
      • 2016-01-22 02203, 2016

      • Freso como cena: arroz y salsa
      • 2016-01-22 02210, 2016

      • gcilou
        Freso, so are we waiting for Gentlecat to look at it?
      • 2016-01-22 02247, 2016

      • Freso
        Yeah. I don't think I have any more comments, but Gentlecat is the ultimate code quality authority for this repository :)
      • 2016-01-22 02258, 2016

      • gcilou
        okay :)
      • 2016-01-22 02254, 2016

      • ariscop joined the channel
      • 2016-01-22 02210, 2016

      • gcilou
      • 2016-01-22 02225, 2016

      • Freso
        gcilou: It's unlikely that anyone else will claim the other MeB task, I think, so I guess you could start working on it, so you're ready to submit it when you can claim it, if you feel like it.
      • 2016-01-22 02235, 2016

      • gcilou
        okay
      • 2016-01-22 02214, 2016

      • Freso
        gcilou: Yeah, that looks a bit off. But looks like something that should be fixed with CSS/LESS rather than random <br/>'s :)
      • 2016-01-22 02235, 2016

      • gcilou
        hm. Leo_Verto?
      • 2016-01-22 02211, 2016

      • Freso
        Actually, I think it's "Yo como cena: ...", but "Él comen cena: ..."? reosarevok, y u no here?
      • 2016-01-22 02225, 2016

      • Freso
        Él come?
      • 2016-01-22 02228, 2016

      • Freso
        Jeez.
      • 2016-01-22 02245, 2016

      • Freso should go look at a verb table or something
      • 2016-01-22 02205, 2016

      • Leo_Verto
        sorry, in a dota match right now
      • 2016-01-22 02208, 2016

      • Leo_Verto
        will talk when dead
      • 2016-01-22 02215, 2016

      • gcilou
        ok
      • 2016-01-22 02213, 2016

      • LordSputnik
        Freso: I only know that "como" is part of "Como estas?" :P
      • 2016-01-22 02215, 2016

      • gcilou
        nevermind, I fixed it. Sorry for poking you prematurely.
      • 2016-01-22 02205, 2016

      • Freso
        "will talk when dead".