Define mqtt (msg.alpinelinux.org) topic structure
We should define a structure to use for our mqtt topics. Currently we have:
- git/*
- build/*
- alert/*
- rsync/*
- monitoring/*
- issues/*
Are there any good design principles for topic structure?
(from redmine: issue id 8421, created on 2018-01-25)
- Relations:
- child #8468