It would be very helpful if we could have the migrator "call home" periodically. This could be an opt-in feature, i.e. we'd ask the user whether they would allow us to send anonymous data from time to time, so as to improve the tool.
If the user accepted then we could persist the choice by saving an artefact to the file system in the package, i.e. .migratorc.json.
To begin with, it would be good to collect:
Number of times the migrator was run overall
Number of times the migrator was run per-app
Number of times the migrator ran successfully
Number of times the migrator ran per-app
Number of times the migrator failed
Step at which the migrator failed (possibly including error message)
@pmgrove I'm interested in your opinion on this one, from a Product perspective
It would be very helpful if we could have the migrator "call home" periodically. This could be an opt-in feature, i.e. we'd ask the user whether they would allow us to send anonymous data from time to time, so as to improve the tool.
If the user accepted then we could persist the choice by saving an artefact to the file system in the package, i.e.
.migratorc.json.To begin with, it would be good to collect:
@pmgrove I'm interested in your opinion on this one, from a Product perspective