The only information I have seen reported on this was from a post by Dan a week ago.
It stated: "We're providing rather detailed judging guidelines intended to help judges calibrate their scores. We also plan to post-process the results looking for outliers (such as cases where one judge gave a score that varies significantly from the others') to help make sure the results are fair. Panel size will be at least 3, depending on how many judges we have; currently the panel size is expected to be 4." Source: http://groups.google.com/group/android-challenge/browse_thread/thread/9a91f426422fed32/9b31c4cae6f2507a#9b31c4cae6f2507a On Apr 24, 3:15 pm, finnk <[EMAIL PROTECTED]> wrote: > 1. How many judges on each panel? > > 2. Will there be one or more Google staff on each panel? > > 3. How much time will a judge spend reviewing each application? > > 4. Will there be more than one test session? (for the first phase) > > 5. Do the judges collaborate in scoring? > > 6. Are judges allowed to contact a contestant? > > The reason I ask these questions is my entry is a client server > application and from the server logs it does not look like each judge > reviewed every feature, nor read the documentation. Maybe I went a > little far on the documentation, it is 14 pages, but it does include a > quick start guide. The instructions are hopefully very clear with the > in application icons next to each section. The application also > includes toast popups (can be turned off in preferences) for each > activity giving specific instructions. > > However, there is one important instruction (repeated in multiple > places), without which the testing experience would suffer: > > Center DPad to Pause/Resume moving along the LBS track. (Hoping maybe > judge will read this :)) > > I spent a lot of time making sure all the features in the application > were functional. I wrote a complete system for simulating LBS, moving > along subdivided tracks that would makes sense for testing/demoing the > application (using data from Google Earth). This was done after > reading that there might not be "adb push" on the groups, however, the > new system was superior so I do not regret doing it. (If you read this > Dan Morrill, thank you for pushing me in that direction, whether or > not I misunderstood what you meant it turned out better. I blame any > misunderstanding on having too much to do and not enough time to > sleep, it was crazy the last month.) > > As it is TeeDroid Caddy is ready for phones, it is feature complete > and field tested. You can check out details on:http://www.teedroid.com. > The site is a work in progress, just something I put together in the > days since the deadline closed to show off the system. > > Finn > > http://www.teedroid.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Challenge" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-challenge?hl=en -~----------~----~----~----~------~----~------~--~---
