I'd typically fall into the 'down with big brother' group with things
like this wanting to report data back home, however in the case
monotone, as everything is out in the open (don't trust the binary,
here's the source) I'm less concerned. I also agree that having this
type of info is invaluable, at least during the rapid development
phase of the project...after 1.0 hits, this need would (hopefully)
decline as much planning went into the early stages (eg: now).
In that regard, I'd suggest two things.
1. A wrapper around mtn supplied in contrib that would do logging with
timestamps of commands run and any other environmental data deemed
important. This data collection would be completely optional. A
default install should always use the binary, forcing the user to
override this behaviour explicitly. Data should be logged locally
only.
2. A second script that would submit the logged data should also be
supplied with contrib. Again, it would be up to the user to cron data
submission or handle batching it off manually at their leisure.
As someone who attempts to avoid phone home scenarios, I'd feel
comfortable with the above and would likely contribute data. The
things that make me more comfortable are that the process is voluntary
and I can see exactly what is logged and submitted. I'd also have
control over frequency, etc.
Thoughts?