| Crash and Win's FAQ |
 |
|
| We know some info is missing from the BitDefender Crash & Win Competition web pages so we've compiled a short (probably soon to become longer) FAQ. Q. The rules weren't quite clear. What are we supposed to do in order to win? A. Send bug reports that have not been sent by someone else. They will be rated and a score from 1 to 3 will be announced by the judges in 24h max from the bug's arrival. At the end, the person with the most points wins. Q. Where should I send the bug report? A. Logon to http://beta.bitdefender.com and post it in the bug submission tracker under the "BitDefender Mail Protection for Enterprises" project. Q. Who will be judging? A. The Product Marketing Manager, the Business Line Manager and the head of the *NIX devel team. Very nice guys. At least when they're sober :) Q. Short list of the prizes please? A. To put it simple, there will be 3 winners for the 3rd place, 2 for the second and one for the grand prize. List of prizes, follows: 1st place: 1k beers, trip to see Dracula's castle, ipod+docking station 2nd place: 2 x ipod + docking station 3rd place: 3 x ipod Also, next 50 runners-up will receive t-shirts and other small goodies. Q. What should I expect from the product? A. Bugs, crashes, undocumented bugs in some modules. Like any beta release, some features are quite buggy. A beta test isn't "try before you buy" or "use the product for free". It is a test and besides our internal testing team, you guys (yes, YOU!!!) will be the first chosen to see the product. Q. How am I supposed to test this? What am i supposed to test? I don't know anything about your product! A. If you joined this competition and are planning to win it means you have some basic knowledge regarding mail servers, Linux and the importance of an antivirus solution filtering e-mail traffic. Just stress the product according to your needs and you'll do great Q. Any other prizes I should know about? A: Who have you been talking to ? :) Q. Who decides if a bug is important or not? A. We do. All you have to do is use your common sense to justify if a bug is important or "just is". Should it come to a difference of opinion and a bug is important from YOUR perspective and not from ours, we'll research it further and put your points in "pending". Q. A few hints as to "how to test"? A. I have moments when my imagination lets me down, too :) for starters, you could try the following: Send malformed e-mails Send MANY e-mails Mess around with the user/group management module and do the previous two steps Try setting conflicting policies in the user/group management module Use the product documentation to test if all the product functions work as advertised Q. Why didn't you give any hw specs in the announcement ? A. We only mentioned Linux and MTA for a specific reason. We want to see how the product behaves on ALL hardware, Linux distros and MTAs (yes, ALL). The only thing we forgot to add is the *x86 restriction. We don't apologize for that :). Q. How the heck are you gonna send 1,000 beers all the way to XYZ (this is where I live)? A. We have lots of money. The AV industry pays really really well :) Q. How to write a good bug report? A. A good bug report is as simple and to the point as possible. It is clearly written, in plain English, and is free of ambiguous wording and misspellings. Keep in mind that the Q&A team and the developers will need to wade through a lot of bug reports. The easier we can make it on them, by providing quality reports, the better they can make the product for us. Those who don’t speak English are an exception. Depending on what the product automatically logs for you, your bug report should include the following, if applicable: The actions that lead up to the bug, if the bug is repeatable. Standard format for SDRs(Software Defect reports) is: Description: How to Reproduce (if applicable): Expected results: Actual Results: BitDefender and the BitDefender logo are trademarks or registered trademarks, in the United States, EU and certain other countries, of SOFTWIN SRL, Romania. Additional company and product names may be trademarks or registered trademarks of the individual companies and are respectfully acknowledged. |
