BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2007 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T020000 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN=Shri Borde:MAILTO:[email protected] ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ryan Riley :MAILTO:[email protected] ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=ironruby-c [email protected]:MAILTO:[email protected] DESCRIPTION;LANGUAGE=en-US:When: Thursday\, August 06\, 2009 10:00 AM-12:00 PM (GMT-08:00) Pacific Time (US & Canada).\n\nNote: The GMT offset above does not reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\ n\nFor this session\, participants (Ryan at this point) will drive. So if you have an IronRuby problem of any kind (bug\, feature\, your own app\, b rainstorming) you need help with\, join us.\n\nProcess info from http://wi ki.github.com/ironruby/ironruby/debugging:\n\nPair debugging with experien ced IronRuby developers\n\nSome experienced IronRuby developers may be ava ilable to debug a problem with you. Watching over their shoulder can help a newcomer to the code base learn debugging tips and techniques. To make t his a fruitful exercise\, please follow the following guidelines:\n•\n\n Ensure that you can build and successfully run all of the RubySpec<http:// wiki.github.com/ironruby/ironruby/rubyspec> tests.\n• Try to restr ict the problems to pure Ruby code which is known to work with MRI. Ensuri ng a clean working baseline functionality in MRI ensures that the problem truly in IronRuby. Without a known clean MRI baseline\, the problem can be in a component other than IronRuby which you are as well-equipped to diag nose as anyone else.\n• Set up a clean repro. Spend time ensuring that it is not a configuration issue\, and that the problem can be easily reproduced on other machines. Document detailed information about your pla tform\, version of IronRuby\, and the steps to repro the problem.\n• Do basic debugging by yourself beforehand. This will ensure that you ge t the most out of the session and can keep up with what’s going on over Live Meeting.\n• Set up Live Meeting<http://livemeeting.com> on yo ur machine\, which will allow you to watch the debugging session.\n• The Live Meeting invite will be sent by email just before the scheduled hour.\n• The email invite will also contain a toll-free number to dial in to. If you cannot call in\, add the experienced developer as a fr iend/buddy in some Chat program so that you can ask questions during the d ebugging session.\n\n\n\n SUMMARY;LANGUAGE=en-US:IronRuby pair programming DTSTART;TZID=Pacific Standard Time:20090806T100000 DTEND;TZID=Pacific Standard Time:20090806T120000 UID:040000008200E00074C5B7101A82E008000000002007F60CB315CA01000000000000000 010000000BC09C97A2BC0CC46BFA682403923CFF8 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20090805T165649Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION;LANGUAGE=en-US: X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-OWNERAPPTID:646285273 X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:0 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT15M END:VALARM END:VEVENT END:VCALENDAR
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
