Rather than simply listing ideas or suggestions, write sentences that describe the idea or suggestion. This helps clarify at a glance what exactly you are suggesting, and what will be affected. It also makes it easier to take advantage of Wiki­Names.

Bad

• Better graphics

• Easier to find intructions

• Fix the nag screen

Good

• Tagger­Graphics - A few of the graphics used in the tagger aren't really distinct and obvious as to what they are. The single file one in particular, shows a folder. Also the arrow on both that one, and the folder lookup don't really seem to make sense.

  • This clarifies WHICH graphics you think need to be improved, and why. The Wiki­Names (which have been disabled on this page) could then lead to a proposal page where ideas for better graphics could be discussed with links to proposed samples.

• It took me a while to find the instructions for using the Tagger. I always like to know how to use something before I take the time to download it, and it really took some hunting to find the tutorial and stuff. I think you might need to Rearrange­The­Site­.

  • This one exposes a much bigger potential fix. It's not just the instructions that need help.

• My nag screen won't go away! I donated $20, cus yall do great work, but the nag screen is still there, and now it wants CHOCOLATE!! Do I need to enter some code somewhere??

  • We can see from this what exactly needs 'fixing' and can leave a note explaining why they still get the nag screen. This helps differentiate between known non-bugs and real bugs, e.g.;

• Nag­Screen­From­Hell - My nag screen is REALLY naggy. I know y'all need money to keep doing the great job you are doing, but 10 nag screens in a row that I have to click on to get to the program seems excessive.

  • Now we know they have a real bug, and can refer them to Source­Forge to submit a bug report.

CategoryWiki