Roger, I will reiterate Kynn's comment. There are ways to contribute
without writing code or paying money.
On the other hand, anyone that uses something for free gets what they
paid for.
If you are contributing by writing code, beta testing, bug squashing,
cheering on those that are, or supporting the work they have already
done in news groups, mailing lists, and other forums, you are no
longer using it for free. You have contributed.
Asking for enhancements, bug fixes, new features, etc. is not a
contribution. Asking for them to be included with the package
because you have already written, tested, debugged, and proven
it works IS contributing.
Just because one person (or more) suggest something, does not make
it a good suggestion. I could "suggest" that you participate more
by contributing your time to this list. That does not mean that
you like, agree with, or will follow my suggestion. Does it mean
I whined by giving you that suggestion? I don't think so. I am
not saying that you do not already contribute to this group, just
using it as an example.
I have invested hundreds, if not thousands (of hours) in this
product alone (majordomo) simply by answering questions on this
list. Man this free stuff is expensive! <G> I was not (am not)
a code junkie, but I have learned enough to be able to even spot
a few bugs (and how to fix them) and reported both back to this
list. I even wrote a couple tools to make administration of
majordomo lists a little easier with the full intent of being
able to give something back to the internet community, of which
I have been a leech for so many years. They are attached to
messages here somewhere, and might even be on Joe's patches
site. Not bad, considering I still travel 15 hours a week to
be able to work another 60 hours a week, and still find as much
time for this list and this product as I do my family.
<Can I have some cheese with that whine?>
I feel sympathy for those that won't contribute. (notice I did
not say can't) Mostly because they will always be the leeches
that I used to be.
Dan Liston
Follow-Ups:
References:
|
|
