|13||13||On the server side it turns out that there are many tasks that we might like to offload to trusted or anonymous clients (ie not just `cabal-install`), so we would really like a framework for managing reports. That would probably include a way of defining the schema of each report and versioning them. A simple example of a report might be a http://www.dwheeler.com/sloccount/ `sloccount`] report where a client downloads a package, runs `sloccount` over it and reports the results. The server would add this information to the a package stats page. There are dozens of similar ideas for discovering useful information about packages, from simple things like sloccount to generating docs, running tests and code analysis.