Contributing to Mustang: Contributor status granted

Just a little surprised, I got an answer to my faxed contributor agreement within two days. I had heard of unanswered faxes lingering, perhaps unseen or forgotten, for as long as a couple months...but that isn't my experience.

With my new contributor status, the next part is to hunt down a bug. There's a little catch...I don't have a MS Visual Studio environment. Does that prevent me from contributing? No it doesn't. As long as the problem is in documentation or Java code, I can still fix a bug and contribute. In the past, I was a little bummed about this...I can't contribute fixes to the native C/C++ code. However, I realize that there's a lot of Java code left...I doubt I'll need to dabble in the C/C++ code. And as Tom Ball commented in one of my blogs, if I really want to do any low-level Windows work, I have to "drink the Redmond kool-aid, like it or not," which means purchasing the SDKs, the developer subscription pack, etc. I don't like it, but he's right. Programming at the C/C++ level in the base VM isn't for a weekend Windows programmer like myself...perhaps I'd better stake out the higher ground and stay in the Java code.

Hey, wait a minute...while I've been playing around, Mustang work has continued. The build #53 code that I downloaded just a week ago is now old, outdated...history. Now build #55 is available. OK, I promise, after I get these latest bits, we'll go to the next step.

If you could submit a fix right now, what bug would it be for?