Agenda, 13th ISC Meeting, Wednesday 24 August 2005, Nowy Sacz, Poland WSBÐNLU (Higher School of Business, National Louis University) Time: Immediately after GA Meeting scheduled to end at 12:00 Location: ISC Room, B006 Present: Zvonimir Bujanovic, Cesar Cepeda, Krzysztof Ciebiera, Gordon Cormack, Marcin Kubica, Jyrki Nummenmaa, , Krzysztof Stencil, Ismail Hakki Toroslu, Tom Verhoeff Absent (with notification): Mike Hatzoupolos, Luis Cruz Romo 1. Opening at 12:05 2. Finalize agenda: OK 3. Confirm minutes of previous ISC meeting (August 2004, Greece) 4. Chair of ISC: Tom 5. Announcements * Membership: Leaving members: Mike New members: Francisco Zaragoza Martinez (1993, Waterloo) Luis Cruz Romo Zvonimir Bujanovic (Zagreb, dept. math.) ASK "CV" * ISC role: advise next host, provide quality assurance, handle externally submitted tasks, supervise future development of IOI competition 6. Incoming and outgoing documents > Report to IC/GA: approved, but with proviso that explanation to lower "difficulty" level (2nd day: one contestant got 300 points after 1.5 hours into the contest) is included; next year (maybe): open task (to avoid ties at the top); ISC (esp. non-host members) misassessed the second day; there was no hard task to distinguish top 4 (although this is not required by IOI Regulations); Also include paragraph on rewriting Mountain < Proposal by China to eliminate task approval procedure Task preparation, selection, approval (who does what?) < Proposal by USA/GBR: HSC responsibility in task preparation We like it; separate the metaphor from the mathematical formulation (metaphor is optional) 7. Confidentiality * Conflicts of interest: Training and coaching involvement * Communication, PGP, keys * Reporting (to IC, to Host SC, to GA, ...) 8. IOI2005 * What was done, how did that go - 8 Externally contributed tasks (3 rej. before review; 2 used in practice/competition), consider the backup tasks for next year (Around Byteplanet, Wizard), ask the authors - Practice session (environment adjusted; late arrivals wanted extra session, but did not get it) - Compilers (gcc, FreePascal) - Developments environments (Linux, Windows, IDEs, ...) - Web-based competition services (Submit, print, backup/restore, test; results & their inspection) - Grading reports, solutions, testdata summaries - Surveys - Security (cell phones collected by leaders) - Competition booklet published at the end * What went well, what can be improved (brief summary) Marcin: tasks slightly too easy (four full scores; not kept busy) "50% rule": designed for IOI 2004 to be simple, didn't work too well here (easy solutions were "too easy"; include quantitive data); consider on task-by-task basis * Further analysis of tasks, solutions, results (future work) We will receive detailed results (need to specify) 9. IOI2006 * Preparation of the competition Call for Tasks: deadline 1 December 2005 Recommended: include local flavor in task metaphors * Differences from previous IOI competitions - Linux-only competition environment * Project plan, progress reporting to ISC * Review meeting: - date & duration: 17-23 March 2006 (propose 17 instead of 18) - decouple from IC meeting (no trip to Chichenitza equinox of spring?) - cost of travel (for member) and stay (for host) 10. General issues * Assignment of responsibilities, duties, deadlines (ISC & HSC) 2 to 3 weeks before review meeting: 1 March 2006 * Update the "Guidelines for IOI Competitions": - Post-competition reporting - Review procedure (Gordon) - Criteria for design of test data, incl. (adjusted) "50% rule" * IOI Workshop * ITWG report - Time line was presented to GA 11. Closing: 13:45