Notes from #MetaBrainz Meeting 2017-10-16

MetaBrainz Meeting 2017-10-16

Meeting start: IRC Logs for #metabrainz | MetaBrainz Chatlogs

Agenda

Reviews

@bitmap

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@LeftmostCat

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@CatQuest

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@samj1912

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Rob

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Freso

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@paramsingh

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@reosarevok

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@yvanzo

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@chhavi

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@zas

IRC Logs for #metabrainz | MetaBrainz Chatlogs

@Leo_Verto

IRC Logs for #metabrainz | MetaBrainz Chatlogs

Summit notes/minutes

IRC Logs for #metabrainz | MetaBrainz Chatlogs

Google Code‐in

IRC Logs for #metabrainz | MetaBrainz Chatlogs

GitHub community recommendations

IRC Logs for #metabrainz | MetaBrainz Chatlogs

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.

1 Like