#MetaBrainz Meeting 2017-11-06
I’ve been working a bit on putting together GCI tasks. Turns out, it’s a little fiddly to log in to GCI if your GCI account isn’t your primary Google account, but I’m working around it. I’ll get some tasks posted there in the near term.
last week, because I am full of fail:
actually made progress on instruments again!!!
added the vuvuzela!
added some gci tasks!
submitted some modifications to a loujine script.
futzed about on wikipedia because https://www.wikidata.org/wiki/Q3346567 and https://www.wikidata.org/wiki/Q4700654 are probably the same thing, but have different pages and also https://en.wikipedia.org/wiki/Nyabinghi_rhythm#Drums (so anyone who edits wikipedia and/or knows about Rastafarian drums, assistance is greatly appreciated! :o)
and… drumroll plz
finally started working on updating my browser! I’m upgrading one version at the time in order to be able to move all stuff over and such. yaaay!
OTHER-310: Add Jira workflow for design/UI/UX/etc. tickets
Design Kanban Board
I just wanted to ask, how should I ask for feedback on specific tickets. Should I ping people personally, or have a bi-weekly design slot/meeting where I run the team through tickets which need feedback?
There was some discussion about @chhavi’s questions, but no clear consensus, other than the Kanban board probably not being the best way to proceed and most involved parties wanting to be somehow pinged directly or semi-directly instead of having to remember to check the Kanban board themselves.
Get test.mb up before GCI
it’s probably a good idea to get
test.mb.org up and running before gci starts, it 's a great place to tell newbies to “go wild and experiment” to test things, and not to worry about making an error or mess up data.
it’s much easier to get people to “dive in” and learn what does what, when they don’t have to worry about breaking anything.
this is true regardless, but especially for gciers
@Bitmap said «it should be faily simple» and that he’d work on it.