3 - want incompatible data format
4 - .top* is namespace pollution, want .topbloke/*
5 - need new dependency tracking
6 needed for dependency removal
7 - need new data versioning
8 needed to allow future forward-compatible-only changes
10 needed to allow branch "removal" (ie, hiding)
12 - want new terminology
14 - therefore project needs new name
16 - existing code has bugs
17 merge .topmsg, .topdeps
20 - wrong implementation language IMO
22 - maintainership change
24 So overhaul and review needed of all core functions to support new
25 semantics; result is not compatible; not much code will end up copied