To encourage members of the community to work together to help make the WDK the best it can be OSR is partnering with ITT Defense and Information Systems and working in cooperation with Microsoft to bring you the WDK Community Bug Bash Contest 2010.
We’re giving away free stuff to everyone who submits a valid bug on the WDK. Better yet, prizes will be awarded for the BEST bugs submitted. The prizes are pretty cool, too: HP Netbook, Apple iPod Touch, Visual Studio Ultimate Edition, and more.
The basic process is: Report a bug on the most recent release of the WDK to the bug bash. Somebody here at OSR will validate your bug. If it’s found to be valid, we’ll send you an award! AND if your bug is judged one of the BEST bugs submitted during the contest, you’ll win some REAL prizes.
Find out all about the Bug Bash (and check the official rules) at:
It’s all about community: Working together to try and make the tools that we use on a regular basis GREAT. The last time we did this (more than 10 years ago) we got TONS of problems fixed ranging from trivial documentation errors (“the word THE is repeated two times in a row on page…”) to serious bugs (there was a whole series of issues in terms of completion routines and marking IRPs pending in the sample drivers).
So, get to it and submit your bugs to the WDK Community Bug Bash!
Ah, this is the easy part. Basically, you find a bug, you report it, we send you free stuff, and you become eligible for the big prizes:
You find a bug in the most recent version of the WDK. Find a bug in the code, in the samples, in the utilities, or in the documentation.
You check to see if your bug has already been reported. Only the first person to submit a given bug gets an award and is eligible for a prize.
Assuming your bug hasn’t yet been reported, you submit your bug report to OSR by filling in a simple form here on OSR Online. You will receive an email confirming your submission.
We validate your bug. If it’s a legit problem and you’re the first to submit a bug on it, we’ll categorize it as either Editorial (which is a minor detail in the documentation) or Technical. If this is the first time you’ve qualified for an award for a bug in this category, we send you the appropriate award! But, even if you’ve qualified for an award previously, keep submitting bugs. Because the best bugs submitted by the end of the contest will win some cool prizes (see below), and in the end, you are still helping yourself and the community by your additional efforts!
We submit your bug into Microsoft’s bug tracking system, and keep the Bug Bash Bug List updated as to your bug’s status.
…
Peter,
Could we report bugs found in Windows kernel components, including drivers and libraries?
I could not find any category for such bugs in a Bug report.
This is not about OS bugs, but about kit bugs. That means if you find a bug in a library in the kit, by all means file a bug. If there is a bug in the kernel or some port driver, I don’t think this bash is really the forum for that (but I could be wrong…)
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Tuesday, August 10, 2010 10:12 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Announcing: WDK Community Bug Bash 2010
Peter,
Could we report bugs found in Windows kernel components, including drivers and libraries?
I could not find any category for such bugs in a Bug report.
“Doron Holan” wrote in message news:xxxxx@ntdev… This is not about OS bugs, but about kit bugs. That means if you find a bug in a library in the kit, by all means file a bug. If there is a bug in the kernel or some port driver, I don’t think this bash is really the forum for that (but I could be wrong…)
d
-----Original Message----- From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com Sent: Tuesday, August 10, 2010 10:12 AM To: Windows System Software Devs Interest List Subject: RE:[ntdev] Announcing: WDK Community Bug Bash 2010
Peter, Could we report bugs found in Windows kernel components, including drivers and libraries? I could not find any category for such bugs in a Bug report.
Well, in my opinion (unofficial, of course), it would certainly be a valid
doc bug submission until someone (official) indicates otherwise.
mm
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Maxim S. Shatskih
Sent: Tuesday, August 10, 2010 5:18 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] RE:Announcing: WDK Community Bug Bash 2010
And, if some MS’s API (described in the kit) misbehaves, then is this a
kit bug or an OS bug?
“Doron Holan” wrote in message news:xxxxx@ntdev… This is not about OS bugs, but about kit bugs. That means if you find a bug in a library in the kit, by all means file a bug. If there is a bug in the kernel or some port driver, I don’t think this bash is really the forum for that (but I could be wrong…)
d
-----Original Message----- From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com Sent: Tuesday, August 10, 2010 10:12 AM To: Windows System Software Devs Interest List Subject: RE:[ntdev] Announcing: WDK Community Bug Bash 2010
Peter, Could we report bugs found in Windows kernel components, including drivers and libraries? I could not find any category for such bugs in a Bug report.
OTOH, we WILL happily accept bugs files against driver support functions. Like, if you find that PoCallDriver suddenly stops working… by all means file the bug with the bug bash. While it’s not REALLY a WDK bug, it’s something that driver writers use and needs fixed. So, when filed against the WDK, it’ll just be reassigned to the right team.
And assuming it’s a VALID bug you’ve reported, it’ll qualify for an Award.
Then again, don’t file a bug such as: “I’m running Windows 7, and I’m using it to develop drivers, and when my laptop suspends to S3 it later won’t wake properly to S0.” Yeah, OK… that’s an OS bug, and it’s not a driver bug. The Bug Bash team would almost certainly reject that bug as “Not related to driver development.”
So… While we’re primarily trying to focus on the WDK, if you find a bug and it’s related to driver writing… JUST FILE IT with the Bug Bash. I’d rather have you file it with us, and send you a t-shirt, than have you forget to file it through other channels, you know? In the end, let’s just get stuff fixed.
Just about all of them. The documentation, the headers, the tools and utilities, the build environment, the sample drivers… We’ll even gratefully accept KMDF and UMDF bugs, and bugs in functions that are documented in the WDK (who knows… maybe you found a bug in the way CcUnpinRepinnedBcb works – If so, report that).
…