> Most definately! I sent the files in question (in one case, altering the
> original numbers so the data was bogus) to them the very same day.
>
> That is the easiest, and sometimes the most useful way to help a project.
> Everyone should do it. Even non-programmers provide valuable help that way.
As an active developer I can easily state that the three biggest things
you can do for a project are...
1. Use the software and give detailed feedback (both good and bad) Let
project maintainers know what they are doing right and what they are
doing wrong.
2. Test, Test, Test. If you have some favorite packages, grab the cvs
of them and help test. It's SOOO hard to find good reliable testers.
3. If documentation sucks, document how you use it and give it to the
maintainers, often its better than nothing and will encourage others to
'build on it'.
In a perfect world, I would say any package you use regularly you owe it
to the community to do your part and at least submit bugs if you
encounter them. With debian its as easy as report-bug packagename.
--
Derek Neighbors
GNU Enterprise
http://www.gnuenterprise.org
derek@gnue.org
Was I helpful? Let others know:
http://svcs.affero.net/rm.php?r=dneighbo
(text/plain)