#MetaBrainz Meeting 2016-08-01
I updated IRC hooks on github for our projects. so now we no longer get notifications about pushes into LB repo, which were pretty noisy and not so useful
now we do get notifications about PRs not just for LB though
also done some review of code
started writing some contribution guidelines that we were thinking about for a relatively long time now
continued dockerizing stuff (CAA redirect, LB)
finally figured out how to jenkins with docker
or docker with jenkins
Looked a bit into failing travis builds of Picard, which was due to recent mutagen changes.
Added some documentation into my soc code.
Improved my album dialog for better display of search results. Git branch: https://github.com/rahul-raturi/picard/tree/embed_search_(release)
Spent some time trying to understand how picard handles coverarts downloading. I’m trying to display covers alongside search results.
Got two pr’s up this week, one merged, one almost ready. Added JSdoc to my achievement module. And a bunch of rebasing to clean up my commits and make them much easier to merge.
Tests are still being added as I go along, rebasing all my old work and cleaning it up still
looking on track to finish in time for the deadline
@dukeja (jduke) talked about the discussions happening on starting a VideoBrainz project.
They have created a GitHub organisation for the early versions of their thoughts on the project:
@dukeja also asked for advice on getting a development environment set up, which @Rob volunteered to help advice on. Crowdfunding relationships
Continuing discussion from the forums (
Donation / patronage relationship (STYLE-327), Crowdfunding relationship (STYLE-546)), @reosarevok asked for thoughts/opinions on the possibility of fraud with these links.
There was a bit of discussion back in forth. In the end, it was decided to not treat these relationships different from those of e.g. shop links and trust the community to weed out bad ones before harm is done.
We also touched a bit on how we’re already disclaiming that we have «No warranty or liability for errors […]. [Data] is provided “as is” without warranty of any kind for correctness or completeness.» even if it is stated in a probably
less than optimal location and that it might be good to move, or at least copy it, to (an)other place(s). No resolution was reached on this though.