#MetaBrainz Meeting 2017-10-16
Further work on improving server reliability. A lot of the changes will end up being configuration, and I am thinking about ways to improve our default behavior in this area. Major touchstones are handling the redis server being unavailable and behaving better when elasticsearch goes down. Still to come, dockerization of the service.
working on instruments, researching
sorna vs zurna
if they are the same or not (anyone with any input is welcome to give it here)
trying to find out if the https://tickets.metabrainz.org/browse/INST-301 should be closed a “we already have fujara and this seems to be a simple variant” or not, again anyone with input here or on the forum post that will follow is welcome to do so :)
So I and Freso discussed about setting up a workflow in JIRA for design tickets earlier this week.
Most of my time this week went into a lot of invisible design work. Did a brief competitive analysis of last.fm, discogs, iTunes, etc. Basically to figure out what we can learn from them and not reinvent the wheel
reosarevok CatQuest helped me get started with editing and other doubts
Almost done with the artist page mockup, will run through it tomorrow with Ruoak hopefully and put it up for feedback And with reo’s help, trying to edit/add things
This week I started working on SpamBrainz, coming up with some kind of rough architecture for the project, writing a database schema and then mostly scrapping it in favour of something NoSQL. I also had some kind of enlightenment last night and drew something that may involve viking robots, I’ll scan that later.
GitHub community recommendations
I was looking at the “Insights” tab on GitHub repos and noticed a new tab underneath, “Community”. All repos should have this page.
https://github.com/metabrainz/listenbrainz-server/community On the page, it has a few recommendations for things to do for your project, and I also learned that GitHub has some way to access this in the API. Like for Hacktoberfest, DigitalOcean was highlighting projects that had a complete community profile.
Two easy things I noticed:
We have a “
HACKING.md” file in a lot of repos, but if we rename it to “ CONTRIBUTING.md”, it will match the GitHub requirement We also have a
code of conduct. We could either copy+paste that to all repos or just add a file for Code of Conduct that links to that page for all MeB projects.
I was going to do
#1 for ListenBrainz, but I was curious if there was a preference for #2
Some discussion happened about our Code of Conduct needing a revamp and whether we should link to it now or wait for it to get fleshed out. There was also some discussion related to how we’re not fully using GitHub (e.g., GitHub is not used for issue tracking), so we may not be able to get 100% “completion” on the community page.
It was decided to 1) link to the CoC rather than copy+paste it into all repositories, 2) link to the current CoC rather than wait for the revamp, 3) do as much of the “GitHub community recommendations” as we can/makes sense as it might help discoverability on or via GitHub.