#metabrainz

scruff trouser jazz?

bitmap: ping

bitmap: is there something wrong with CAA ? cover art are not showing on the front page

morning :)

LordSputnik: sounds good to me too, will be happy to help! Only thing, I don't know what we will be working on. Can you help me get started a bit here.

Leftmost: Send your GCI Google account mail to freso@meb.

reosarevok: It wasn't really. I was actually thinking once in bed that SpamBrainz might be fine as an OTHER component for now, until it's a bit more of an actual project.

Good morning peeps o/

samj1912: Moirning :) Tell chhavi_ that I'm around for poking/brain eating, whenever she's ready.

Eh. Head eating.

Oh, she's already written in here.

chhavi_: I'm around for poking/head eating whenever you're ready. :p

Helo Freso. In like 20 mins? Does that give you time to be a little more awake as well? :p

chhavi_: Well, it'll give me more time, sure, but no promises. :)

Freso: Let's do this?

chhavi_: Alright!

So, exactly what is it we're doing? :x

So I made myself a JIRA account and looked into how presently our projects are being managed. Quite enlightening :)

^this is what I would like somewhat. Each project having a design component.

Using "UX", "GUI", and "branding" labels?

In my head, it's sub categories. And the following four "needs feedback, mockups, front end, back end" as labels/tags

You tell me how we can do this best! :)

Well, Jira is structured with Projects at the top-level. Each Project can have 0 or more Components. Components has no sub-levels per se.

Okay so I guess labels should work. We can add more than one labels right?

A Ticket belongs to exactly 1 Project, but can belong to 0 or more Components (as long as these are Components of its Project).

Labels are Jira-wide. A Ticket can have 0 or more Labels and they are independent on what Project or Components a Ticket is filed under.

Additionally.

chhavi_: https://tickets.metabrainz.org/browse/OTHER-302 - notice the "Status"

OTHER-302: Add links to MB user pages on Discourse profiles

This would be where something like "Needs feedback" would most appropriately be placed.

(Since it's reflecting the (current) status of the ticket, rather than something intrinsic to the specific ticket.)

Something like "needs mockup" could also be a status.

"frontend" and "backend" sound more like labels and/or components (depending on Project).

chhavi_: Does this all make sense, or am I confusing you more now? :)

Okay so correct me if I am wrong. We can have "design" as a component. "UX, UI, Branding" as labels.

Yep. All that sounds good to me. :)

Now about status

(UX is already a label: https://tickets.metabrainz.org/issues/?jql=labe... )

Yeah I saw that :)

(Just not very widely used yet. :))

I am thinking about status now. So typically (I am assuming) status of our design task could be : ideation, feedback, mockup. But it is more of a stage

status == stage

Status would be open, closed etc. I don't think we want to change that for now

chhavi_: That's resolution.

We basically need to indicate "needs feedback, needs mockup, front-end, back end" for a design task.

How do we do that, whatever you say fits best!

chhavi_: Some different statuses currently in the system: "open", "reopened", "in progress", "decision required"

"decision required" is very close to "needs feedback" which is very close to "needs mockup".

MBS-341 seems like an obvious thing to add to the Design component.

MBS-341: Pagination is painful https://tickets.metabrainz.org/browse/MBS-341

Does "backend" make sense for design?

Give me a minute to type in my thoughts here.

Seems like MBS at least already has a "User interface" component: https://tickets.metabrainz.org/issues/?jql=proj... (which would be Design/front-end/UI)

Freso: I will just share a few links of how other FOSS orgs are dealing with it. Okay?

Sure. :)

(Esp. if any of those other FOSS org.s are using Jira!)

See how they are using needs feedback as a tag. Anyone needs any suggestion, big or small or doubts. Or doesn't know where to fit in a design task, uses it

Freso, done.

Fedora uses Pagure.

chhavi_: Sure, but it's also GitHub issues, which have a very, very limited taxonomy.

Yes I get it now :)

Basically, they only have tags for describing issue status (beyond open/closed).

Idk. Labels are also cheap AFAIK, so we might also just go all in on those.

Easier for me to delegate the tickets as well when I am through with it from my side.

So if a design ticket shows up, we know what needs to be done with it next.

Alright. I think I'd actually be fine with just lobbing most of it into the Labels.

bitmap, yvanzo, samj1912, iliekcomputers: ^ any comments/caveats?

yes so I think so too. For now, it should work fine!

(Being the primary users of Jira, I don't want to go ahead with this if you expect it to severely impair your workflow. :))

So should I just summarise?

Sure.

But let's hold on for a few hours to put it into effect to give our devs a chance to object. :)

We make a "design" component. We have "UX, GUI, Branding" as labels. We also have "Needs Feedback, Needs Mockup, Needs Front-end changes, Needs Back-end changes" as labels. Though I am open to finding shorter labels for these!

Freso: yes sure. :)

ruaok: your thoughts on this too please :)

Sounds

Good to me

Is there a way to add this to the work flow instead of using labels?

It should be possible to create a special flow for UX tickets that allows "Needs Feedback", "Needs Mockup", etc. as additional steps in the process, but I'm not sure how involved that is or whether that's something you'd even want.

:)

Freso: How do-able is what Leftmost is talking about? That would make our lives easier. workflow for "design tickets".

We have that at work, but I've intentionally kept myself away from the inner workings of our Jira process, so I can't be too helpful.

I don't think it's possible to make workflows for Components, only at the Project level.

iliekcomputers, Leftmost, chhavi_: ^

It can be at the project level, but there's some way that our UX tickets end up starting in a UX workflow loop before being pushed to devs. It may be a system whereby a ticket can be moved specifically into the UX parts which are earlier than the other steps.

I can look at our Jira on Friday and see how it's done if that'd be useful.

Sure, yeah, it's possible to put a UX loop into the main project workflow.

doing it for every project might be a bit too much work in one go, but we could do it as design tickets come for each project?

I don't think all projects need to a Design component either. E.g., BrainzUtils, FreeDB Gateway, Instrument Requests, Area Requests, etc.

Hm.

You can create workflows per-issue-type.

So maybe we could make an issue type "Design" and make a workflow for that.

that sounds ideal to me

And tickets that require some design stuff could get dependent tickets made for them.

chhavi_, samj1912, bitmap, yvanzo, ruaok ^ does that sound reasonable to you?

I think having a workflow to manage things would be much better than labels. yes

Alright. I'll wait for at least yvanzo and bitmap to also chime in before changing anything, but this does seem like it might be a viable option.

*path

We've done GSoC since... 2006?

7?

2007

Dangit. The French are striking and delaying my flight back to BCN. *shakes fist at zas and yvanzo*

So that you will have time to visit us, it is not striking, it is promoting local tourism ;)

^ 👍

I'm not even in France! :P

I'm in Amsterdam.

Do you have another flight at least?

They haven't cancelled, just delayed, so not too bad. It's a good thing I left a night between my flight to BCN and my flight out of BCN. :P

Freso, bitmap: UX is probably a decent opportunity to start using epic and story ticket types.

ruaok, zas: BookBrainz Google cloud server seems to be unavailable. May have crashed... would be very grateful if either of you are able to poke it alive :)

It's been a few months now without an actual server crash, I wonder what went wrong...

MajorLurker: thanks for helping the BBC artist! :)

LordSputnik: it's hope that kills you