The desire for feedback and usage stats on your code makes sense, but I think you need to respect the privacy of your users as well - why should they be forced to tell you that they're using your code? (Unless you're putting that in your License).
I would suggest you handle this in a passive way - my two favorite examples on doing this are Pine and OpenBSD. In the case of Pine, all you need to do is hit <CR> on a specific field the first time you run it. On OpenBSD, they ask you the following:
If you wish to ensure that OpenBSD runs better on your machines, please do us a favor (after you have your mail system configured!) and type something like: # dmesg | mail -s "Sony VAIO 505R laptop, apm works OK" dmesg@openbsd.org
Why not provide a simply perl script in your package, and finish off your installation with a message saying something to the effect of "I would like to hear about people using package XXX, please run the following script to send me a quick email containing your info"?
In reply to Re: Gathering module usage statistics
by swngnmonk
in thread Gathering module usage statistics
by Juerd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |