So all of you out there you program Macs or iPhones no doubt know the keen pain of going to BugReporter, painstakingly spending great effort to document your problem as exhaustively and helpfully as humanly possible, and then getting back something along the lines of
31-Jul-2008 05:51 PM Stoney Gamble: This bug has been closed as Duplicate. We are aware of and tracking this issue under the Bug ID listed above in the bug State (Duplicate/XXXX). To check the status of the original bug report, please send an email to devbugs@apple.com referencing your Bug ID.
and being understandably all steamed up over not only wasting your own time, but having had no way to find out that this was a known problem before however many hours it was you spent coming to the conclusion that no, you actually were doing absolutely everything right, and it really was Apple’s fault that it wasn’t working.
Grr.
Well, now somebody’s done something about it! Meet OpenRadar, a place for community-minded developers to share their Radar bugs for the greater enlightment of all:
This weekend Dave Dribin suggested on Twitter that he’d like to build
an open database of Radars, something like a wiki that we could use as
a community-fed opt-in system. After exchanging some messages with
Dave and Joachim Bengtsson, I put together a simple demo app on Google
App Engine:It’s basic but enough to get us started. I’ve put the code on github,
and I am completely open to suggestion about this. If you think it’s
valuable, please start using it and we’ll add whatever missing
features we need.Also, to make it easy to get data out of this, there’s an api that
you can use to get a JSON dump of the entire store:http://openradar.appspot.com/api/radars
That will be good until we get up to 1000 radars.
If you have comments or ideas, please add them to the openradar wiki
on github: http://github.com/timburks/openradar/wikis/home
A most worthy endeavour indeed, which all Radar users should support. And interesting browsing material to boot!
h/t: iphonesdk!
