Notes from #MetaBrainz Meeting 2017-12-04

MetaBrainz Meeting 2017-12-04

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

Reviews

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@iliekcomputers

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@naiveaiguy

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ferbncode

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leftmost_Cat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@drsaunde

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@anshuman73

IRC Logs for #metabrainz | MetaBrainz Chatlogs

Google Code‐in

IRC Logs for #metabrainz | MetaBrainz Chatlogs

OTHER-77: Unify all markup syntax to simple markdown syntax

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@ApeKattQuest_MonkeyPython and @anshuman73 confirmed and @naiveaiguy was satisfied with their answers.

BrainzBot functions

IRC Logs for #metabrainz | MetaBrainz Chatlogs

For 1., it was pointed out that there has been some work/thoughts made on this, which should be gathered in OTHER-123.

For 2., @Freso mentioned that MemoServ essentially already covers this.

For 3., it was pointed out that this would be harder than just checking for whether a given username wasn’t seen before.

For 4., it was pointed out that we already have this, but some people find the current syntax complicated/non-intuitive.

In the end, @Freso said they were all reasonable ideas and encouraged @naiveaiguy (or others) to make tickets for the ones that did not already have them.

3 Likes