Can't Code? Squash a Few Bugs - page 4
If your bug report is ignored, there may not be a lot you can do. The devs may be overworked, or don't see it as serious enough to address, or are simply mean people who hate you. (This type of developer is a very tiny minority, but they do exist, and why they choose to support a product that is going to be used by other people is one of life's little mysteries.) Give it a couple of weeks, then try a polite reminder. Posting a duplicate report upstream (directly on the program's own bug-tracking system) might get quicker action.
Always be polite and factual. Most developers are polite and professional, but they are human and you will encounter the occasional dork. You'll score big credibility points by taking the high road.
Many FOSS projects have wish lists. These are the places to post your suggestions for features and improvements.
It takes a bit of work and care to write good bug reports. If you start feeling abused, just remind yourself how much work and resources went into all that great software that you are enjoying for free. And while you're at it, remember how unresponsive most commercial closed-source vendors are to bug reports, and how they are so encumbered with ridiculous EULAs and patents and DRM and NDAs that even if you have the resources to do so, you are prevented from fixing problems yourself. Rather like living in a house where you were not allowed to paint, or patch holes, or change lightbulbs, or remodel, or do anything except pay out money year after year to the builder just for the privilege of living there.
Share Tips and Howtos
A wonderful and easy way to support Free Software is to post tips and howtos somewheres. These don't have to be your life's work, but useful things you have discovered in your everyday work. For example, it might be that you figured out some advanced networking configuration options, or a quick OpenSSH tip, or learned some useful but little-known netcat options, or yet another way to filter Ethereal output to quickly home in on what you want to see. Put these on a blog, or post them in appropriate user forums, or anywhere Google can find them. Five minutes' of work translates into help for thousands of users.
Lawyers, Guns and Money
Well, probably not guns. But money is often welcome, or donations of hardware. In this era of attacking with armies of lawyers instead of guns, good legal assistance for warding off the greedy barbarian hordes is a very nice thing.
These horrid examples of bug reports are brought to you courtesy of Akkana Peck:
- Bug 60632 - Bug is rapid
- Bug 73360 - crashed application
- Bug 133113 - My wish-list i compiled for the last 1 1/2 years i used gimp
Example of a good bug report with a semi-happy ending:
This article originally appeared on Enterprise Networking Planet, a JupiterWeb site.
- 1Linux Top 3: Fedora 24, Peppermint 7 and Solus 1.2
- 2Linux Top 3: Alpine Linux 3.4, deepin 15.2 and Linux Lite 3.0
- 3Linux 4.7 Set to Boost Live Patching, Security and Power Management
- 4Linux 4.6 Charred Weasel adds USB 3.1 Support
- 5Linux Top 3: OpenIndiana 2016.04, Ubuntu 16.04 and Debian's New Leader