I think the author deserves some gratitude for allowing you to use this software.
Let's get off of the high holy horse here, and get back to the real world. You write code and put it out on the internet because you think it's useful and/or cool, and you want other people to take it for a spin, in hopes they think the same and want to help you improve it. Perhaps you're putting the code out there to impress potential future employers. To be brutally honest, you are owed NOTHING. If you were owed something, it would be in your License.
That being said, I'm not opposed to the collection of information that helps drive your module development. I'm opposed to the method of collection. Want to talk about default behavior? Most people's default behavior, when confronted with opt-out code, is hostility.
A further thought - if you use perl -MCPAN to install your perl modules, a lot of times you end up with a big pile of dependencies to install (especially on a new system). I generally start the process, and walk off to do something else while the install process runs. Guess what? Your oh-so-friendly opt-out procedure is now broken.
In reply to Re: Re: Re: Re: Re: Gathering module usage statistics
by swngnmonk
in thread Gathering module usage statistics
by Juerd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |