#metabrainz

/

      • Leo_Verto
        Congrats, all of you did a great job!
      • 2016-02-08 03931, 2016

      • Freso
        Except that now there's...
      • 2016-02-08 03935, 2016

      • Freso
        GSoC!
      • 2016-02-08 03942, 2016

      • CatQuest
        Freso...
      • 2016-02-08 03947, 2016

      • TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | MeB meeting agenda: GSoC (Freso), tagging tickets (chirlu), DR: MBS-4502 (reo), MBS-8542 (reo), schema change (bitmap)
      • 2016-02-08 03955, 2016

      • Freso
        CatQuest…
      • 2016-02-08 03958, 2016

      • Gentlecat
        woot
      • 2016-02-08 03906, 2016

      • Leo_Verto
        It's a conspiracy by Google to keep you busy, Freso :P
      • 2016-02-08 03939, 2016

      • Freso
        GSoC applications are now open. I need to figure out the new Google for Business MetaBrainz thing before I make an account on the new GSoC site (no more melange!).
      • 2016-02-08 03939, 2016

      • ruaok does a little happy dance
      • 2016-02-08 03954, 2016

      • Freso
        Once I get access, I will start poking at the application process.
      • 2016-02-08 03955, 2016

      • Freso
        But!
      • 2016-02-08 03955, 2016

      • ruaok
        no more melange. woot!
      • 2016-02-08 03912, 2016

      • Gentlecat
        new problems, yay
      • 2016-02-08 03915, 2016

      • ruaok
        it should, in theory, start working soon.
      • 2016-02-08 03918, 2016

      • Freso
        If you can think of ideas for possible GSoC projects, please add them to the wiki. :)
      • 2016-02-08 03935, 2016

      • ruaok
        oh, speaking of google apps stuff.
      • 2016-02-08 03942, 2016

      • Freso
        I don't think there's a 2016 specific ideas page yet, but I'll get around to making it later or tomorrow.
      • 2016-02-08 03952, 2016

      • ruaok
        there is a migration tool, that allows you to import mail from another account.
      • 2016-02-08 03956, 2016

      • Freso
        If you really need to get an idea out, feel free to create the page yourself. ;)
      • 2016-02-08 03904, 2016

      • ruaok
        so, if you have a private account that you'd like migrated, ping me.
      • 2016-02-08 03920, 2016

      • Freso
        ruaok: But will it allow to import Google privileges/settings from another Google account?
      • 2016-02-08 03931, 2016

      • ruaok
        TBD. my migration is running.
      • 2016-02-08 03933, 2016

      • Freso
        Anyway, let's take that post-meeting.
      • 2016-02-08 03937, 2016

      • ruaok
        but 15 years of mail is... taking a while.
      • 2016-02-08 03947, 2016

      • Freso
        So, yeah.
      • 2016-02-08 03923, 2016

      • Freso
        We have already had some GSoC hopefuls asking questions and poking at code in here, so candidates need to get ready!
      • 2016-02-08 03944, 2016

      • Freso
        (Of course, there's no guarantee that we'll be accepted, but I'm hoping!)
      • 2016-02-08 03950, 2016

      • Freso
        Any questions?
      • 2016-02-08 03936, 2016

      • TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | MeB meeting agenda: tagging tickets (chirlu), DR: MBS-4502 (reo), MBS-8542 (reo), schema change (bitmap)
      • 2016-02-08 03941, 2016

      • Freso
        chirlu`: tagging tickets!
      • 2016-02-08 03921, 2016

      • chirlu`
        So, during and before GCI, there was some trouble identifying suitable tasks.
      • 2016-02-08 03937, 2016

      • Freso
        ^
      • 2016-02-08 03913, 2016

      • chirlu`
        And people were saying, “Oh, we’d need bug tags, like good-first-bug or something”.
      • 2016-02-08 03927, 2016

      • chirlu`
        Which of course at least our ancient JIRA doesn’t support.
      • 2016-02-08 03953, 2016

      • chirlu`
        So I thought we maybe could restart using the custom size field?
      • 2016-02-08 03911, 2016

      • Gentlecat
        yeah, would be great to have a way to mark "beginner" tickets
      • 2016-02-08 03927, 2016

      • bitmap
        custom size field?
      • 2016-02-08 03927, 2016

      • CatQuest
        can't we just update our jira already?
      • 2016-02-08 03928, 2016

      • CatQuest
        (when the anti-update-shit guy is telling you to jsut update...)
      • 2016-02-08 03932, 2016

      • reosarevok
        Aren't we supposed to update jira soon?
      • 2016-02-08 03947, 2016

      • Freso
        Leftmost?
      • 2016-02-08 03950, 2016

      • chirlu`
        bitmap: There is a “Size estimate” field for MBS at least.
      • 2016-02-08 03907, 2016

      • chirlu`
        With options ranging from “House” to “Planet”.
      • 2016-02-08 03908, 2016

      • bitmap
        ohh, that
      • 2016-02-08 03933, 2016

      • bitmap
        well, sounds reasonble since we don't use that currently
      • 2016-02-08 03947, 2016

      • chirlu`
        So the idea was, when we look at a bug/feature request and don’t want to work on it immediately but have some idea
      • 2016-02-08 03904, 2016

      • chirlu`
        about how much work/how difficult it would be to resolve, we could set that field.
      • 2016-02-08 03909, 2016

      • ruaok
        (jira is after discourse)
      • 2016-02-08 03932, 2016

      • Freso
        Oh, so the sooner I get around to setting up Discourse, the sooner we get new Jira?
      • 2016-02-08 03946, 2016

      • Freso
        That's some incentive. :p
      • 2016-02-08 03904, 2016

      • ruaok
        yep
      • 2016-02-08 03907, 2016

      • chirlu`
        The field is searchable, so we could get a list of all House tickets, say.
      • 2016-02-08 03935, 2016

      • chirlu`
        Of course, capturing the difficulty in one dimension isn’t perfect, but it would be an improvement.
      • 2016-02-08 03901, 2016

      • chirlu`
        Because I at least can’t remember potentially easy tasks when prompted to do so …
      • 2016-02-08 03918, 2016

      • Freso
        Yeah.
      • 2016-02-08 03933, 2016

      • chirlu`
        It wouldn’t be necessary to set the field for all tickets (not even for most of them).
      • 2016-02-08 03939, 2016

      • Freso
        And once we get New Jira™, it'll be easy to find and "re"-tag the issues.
      • 2016-02-08 03944, 2016

      • chirlu`
        So, any objections or better ideas?
      • 2016-02-08 03950, 2016

      • Freso
        +1 from me
      • 2016-02-08 03913, 2016

      • bitmap
        +1
      • 2016-02-08 03925, 2016

      • ruaok
        +1
      • 2016-02-08 03928, 2016

      • bitmap
        dunno if the current dimensions need tweaking, I could do that though
      • 2016-02-08 03936, 2016

      • Leo_Verto
        I've done some research into how to upgrade Jira a while ago, not sure if that is still relevant
      • 2016-02-08 03950, 2016

      • chirlu`
        Yes, house sounds a bit large.
      • 2016-02-08 03910, 2016

      • chirlu`
        Perhaps grain of sand/pebble/rock/mountain or something?
      • 2016-02-08 03946, 2016

      • ruaok
        quark'
      • 2016-02-08 03905, 2016

      • Freso
        Birdhouse
      • 2016-02-08 03923, 2016

      • Sput|Away
        Freso: Discourse tomorrow plz :P
      • 2016-02-08 03929, 2016

      • Sput|Away is now known as LordSputnik
      • 2016-02-08 03937, 2016

      • chirlu`
        Well, I guess we can define that later.
      • 2016-02-08 03956, 2016

      • LordSputnik
        Quantum of Hackage
      • 2016-02-08 03909, 2016

      • Freso
        LordSputnik: I have some final GCI stuff I want to get done first, so I can close that door for good. (For now...)
      • 2016-02-08 03926, 2016

      • Freso
        Once that's done, I'll try and poke at it.
      • 2016-02-08 03948, 2016

      • Freso
        But I also have some other backlogged things I really want to clear out.
      • 2016-02-08 03900, 2016

      • Freso
        We'll see. It's definitely up there.
      • 2016-02-08 03910, 2016

      • Freso
        Anyway. I guess motion carried.
      • 2016-02-08 03913, 2016

      • Freso
        reosarevok: First DR!
      • 2016-02-08 03939, 2016

      • reosarevok
      • 2016-02-08 03945, 2016

      • reosarevok
        Do we still want this?
      • 2016-02-08 03906, 2016

      • bitmap
        I didn't know it existed
      • 2016-02-08 03909, 2016

      • reosarevok
        ("Send me a notification if the artist has a new release")
      • 2016-02-08 03912, 2016

      • reosarevok
        Well it's not working
      • 2016-02-08 03925, 2016

      • reosarevok
        But I don't think it matches well with the way we get data
      • 2016-02-08 03927, 2016

      • ruaok
        this ticket kinda bugs me.
      • 2016-02-08 03927, 2016

      • chirlu`
        It was working pre-NGS.
      • 2016-02-08 03936, 2016

      • ruaok
        we have all of this data we're sitting on.
      • 2016-02-08 03937, 2016

      • ruaok
        amazing data.
      • 2016-02-08 03951, 2016

      • ruaok
        yet any time we try and do something with the data, people just want that feature gone.
      • 2016-02-08 03900, 2016

      • ruaok doesn't understand
      • 2016-02-08 03905, 2016

      • reosarevok
        (since we don't get feeds or anything, there's no guarantee that the releases are added near to the time they're released, so it's more like "send me info of new releases that someone happened to add")
      • 2016-02-08 03922, 2016

      • ruaok
        but clearly people don't want this, otherwise it wouldn't have languished for 5 years.
      • 2016-02-08 03923, 2016

      • ruaok
        kill it.
      • 2016-02-08 03925, 2016

      • reosarevok
        I'd like this option if it was a consistent way of getting informed of all new releases
      • 2016-02-08 03956, 2016

      • reosarevok
        But we don't have the consistency because of the way we get data - and we could make it "when a new release is added" instead but then it'd be less relevant
      • 2016-02-08 03956, 2016

      • Leo_Verto
        maybe us release dates?
      • 2016-02-08 03956, 2016

      • ruaok
        reosarevok: it may not be, but if people like the service it is a tool to draw in more people to add releases.
      • 2016-02-08 03958, 2016

      • Freso
        I'd be happy to see what muspy done directly in MB.
      • 2016-02-08 03959, 2016

      • LordSputnik
        This seems more like a "music/social media/events" feature than something MB should deal with, I guess?
      • 2016-02-08 03906, 2016

      • Leo_Verto
        s/us/use/
      • 2016-02-08 03919, 2016

      • Freso
        But I also don't think it should be something we should spend developer money-time on.
      • 2016-02-08 03926, 2016

      • ruaok
        and the more people use it, the more people add, the better it gets.
      • 2016-02-08 03927, 2016

      • CatQuest
        ugh er dere ferdig snart så jeg kan soppe paying attention
      • 2016-02-08 03932, 2016

      • reosarevok
        Leo_Verto: that was the idea of this script, it's just that there's no guarantee that the release will be added soon at release time
      • 2016-02-08 03946, 2016

      • ruaok
        perhaps this could go back to a feature for GSoC for whence it came?
      • 2016-02-08 03951, 2016

      • Freso
        LordSputnik: I would love to see more "music/social media/events" features in MB proper.
      • 2016-02-08 03900, 2016

      • ruaok
        yes, that.
      • 2016-02-08 03907, 2016

      • ruaok
        please add that to the ideas page.
      • 2016-02-08 03915, 2016

      • Freso
        CatQuest: 3 minutes.
      • 2016-02-08 03931, 2016

      • Freso
        Alright. Kill ticket and add mention about it on GSoC page. Motion carried!
      • 2016-02-08 03934, 2016

      • Freso
        !next
      • 2016-02-08 03938, 2016

      • Freso
        reosarevok: DR!
      • 2016-02-08 03953, 2016

      • chirlu`
        Uh, in that case the ticket should be reopened, not killed.
      • 2016-02-08 03905, 2016

      • reosarevok
      • 2016-02-08 03925, 2016

      • reosarevok
        It's a request to block jaikoz from adding barcodes from the ws
      • 2016-02-08 03937, 2016

      • chirlu`
        +1 to removing barcode submission altogether.
      • 2016-02-08 03939, 2016

      • bitmap
        I think I agree with deprecating barcode submission
      • 2016-02-08 03939, 2016

      • reosarevok
        I'd happily do that, because I have barely ever seen a correct barcode add edit from there
      • 2016-02-08 03948, 2016

      • CatQuest
        oh about that ticlet. I'll love an ability to get an email every time an album (not comp or va) is added to the artists of my chosing
      • 2016-02-08 03952, 2016

      • Freso
        I'd be happy to indulge the request, I'm not a fan of removing submission altogether.
      • 2016-02-08 03956, 2016

      • reosarevok
        But yeah, in general I've barely ever seen *any* correct barcode ws submission
      • 2016-02-08 03909, 2016

      • Freso
        I want to see more things being editable via WS, not less.
      • 2016-02-08 03913, 2016

      • reosarevok
        It tends to involve adding it to any release that matches the tracklist, which is usually unrelated
      • 2016-02-08 03915, 2016

      • ruaok
        the idea was to submit barcodes from the mobile apps
      • 2016-02-08 03927, 2016

      • reosarevok
        (or well, not related enough)
      • 2016-02-08 03943, 2016

      • ruaok
        Freso: we should work to improve submissions. I agree with you, not kill them.
      • 2016-02-08 03901, 2016

      • ruaok
        so, +1 from me on 8542
      • 2016-02-08 03907, 2016

      • TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | MeB meeting agenda: DR: MBS-8542 (reo), schema change (bitmap)
      • 2016-02-08 03911, 2016

      • Leftmost
        Freso, hmm?
      • 2016-02-08 03913, 2016

      • ruaok
        (if people feel that this is in fact a valid issue)
      • 2016-02-08 03916, 2016

      • chirlu`
        ruaok: The original version, that is?
      • 2016-02-08 03921, 2016

      • Freso
        Oh, snap. I hadn't seen bitmap adding a topic too.
      • 2016-02-08 03927, 2016

      • bitmap
        those are autoedits now, right? we could probably make them not if submitted that way
      • 2016-02-08 03932, 2016

      • ruaok
        chirlu`: sorry?
      • 2016-02-08 03940, 2016

      • ruaok
        bitmap: +1
      • 2016-02-08 03941, 2016

      • Freso
        bitmap: Long thing? Or a short update?
      • 2016-02-08 03946, 2016

      • bitmap
        re schema change, I don't have anything concrete to say, just that we should probably confirm the schema change date and set a deadline for tickets in the coming weeks
      • 2016-02-08 03952, 2016

      • chirlu`
        ruaok: Wondering what you are +1ing – blacklisting jaikoz?
      • 2016-02-08 03902, 2016

      • ruaok
        chirlu`: conditionally yes.
      • 2016-02-08 03905, 2016

      • Freso
        bitmap: Let's do that first thing next Monday?
      • 2016-02-08 03912, 2016

      • bitmap
        sure
      • 2016-02-08 03915, 2016

      • Freso
        (Well, after review.)
      • 2016-02-08 03917, 2016

      • ruaok
        bitmap: the first question is this: what schema changes to people wnat?
      • 2016-02-08 03918, 2016

      • Freso
        Alright!
      • 2016-02-08 03919, 2016

      • ruaok
        want?
      • 2016-02-08 03920, 2016

      • Freso
        </BANG>
      • 2016-02-08 03931, 2016

      • ruaok
        collect your desired features and bring them next week, please.
      • 2016-02-08 03936, 2016

      • CatQuest
        ZZZzzzzz
      • 2016-02-08 03938, 2016

      • CatQuest
        *___*
      • 2016-02-08 03942, 2016

      • TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | MeB meeting agenda: Reviews, schema change (bitmap)