#MetaBrainz Meeting 2018-02-12
Well! it seems finally a solution to my macomputer is in sight! I’ve rung them and sent email, the guy has sent me an answer that he’s working on it tonight and tomorrow!
Hopefully this means I’ll be getting the machine back asap!
Still doing some works on releases and instruments. I’ve now almost finished the 3 /Dvořák/ releases I rented before yul (lol) -__-
So this week, I and bitmap finally set up our design system repo, for the "grand redesign"
It’s still empty, but yes, we are on it.
Also fiddled with bootstrap and react to set up a POC for it, with help of samj1912
Final-ish rounds of mockup ready for Artist entity. Will put them for feedback this week. Once done, we can start slicing them into components for our design system
Having a basic template and components, will make it faster for designing/developing other entity pages. We should be rolling with this redesign more rapidly in a month or so, in my estimation! (hopefully)
Apart from that, helped zas a bit with picard log viewer and a banner for our latest cleanup.
This week, I
created a PR in CB for creating db tables in test container before the tests run. This would prevent tests failing due to code running while running and setting up the test app (as in https://github.com/metabrainz/critiquebrainz/pulls/164). Will try to improve this by adding test.sh (like in LB, AB), so that there is no need to remove containers explicitly.
This week I created 3 tickets(LB
308, 309, 310) and created 3 PR’s on LB ( LB-148, 308, 309). these deal with Last.fm compatible API. I need to discuss some problems that i’m facing then continue further work.
GSoC idea design tickets
Syswiki for community-run services
I’m doing a fresh install of BrainzBot and samj asked me to document it, where should I do that? The syswiki seems like the obvious place but I don’t (and definitely shouldn’t) have access to it. This seems like it’d affect all projects run by non-MeB employees (e.g. also BookBrainz). Should this kind of info go into the project repositories? The wiki? I’d love to just have a central place for storing and finding that kind of info.
also is there any monitoring stuff that we should plan to integrate?
Some discussion and clarification happening, but ultimately there was consensus that installation and deployment documentation should be in the related project’s repository, to the extent possible (ie., nothing secret, like credentials).