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=Ray Vernag us:MAILTO:[email protected] ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Kevin Radc liffe: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: Friday\, July 31\, 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\nF or this session\, participants will drive. So if you have an IronRuby prob lem of any kind (bug\, feature\, your own app\, brainstorming) you need he lp with\, join us.\n\nProcess info from http://wiki.github.com/ironruby/ir onruby/debugging:\n\nPair debugging with experienced IronRuby developers\n \nSome experienced IronRuby developers may be available to debug a problem with you. Watching over their shoulder can help a newcomer to the code ba se learn debugging tips and techniques. To make this a fruitful exercise\, please follow the following guidelines:\n•\n\nEnsure that you can build and successfully run all of the RubySpec<http://wiki.github.com/ironruby/ ironruby/rubyspec> tests.\n• Try to restrict the problems to pure Ruby code which is known to work with MRI. Ensuring a clean working baseli ne functionality in MRI ensures that the problem truly in IronRuby. Withou t a known clean MRI baseline\, the problem can be in a component other tha n IronRuby which you are as well-equipped to diagnose as anyone else.\n• Set up a clean repro. Spend time ensuring that it is not a configur ation issue\, and that the problem can be easily reproduced on other machi nes. Document detailed information about your platform\, version of IronRu by\, and the steps to repro the problem.\n• Do basic debugging by yourself beforehand. This will ensure that you get the most out of the ses sion and can keep up with what’s going on over Live Meeting.\n• Set up Live Meeting<http://livemeeting.com> on your machine\, which will a llow you to watch the debugging session.\n• The Live Meeting invit e will be sent by email just before the scheduled hour.\n• The ema il invite will also contain a toll-free number to dial in to. If you canno t call in\, add the experienced developer as a friend/buddy in some Chat p rogram so that you can ask questions during the debugging session.\n\n\n SUMMARY;LANGUAGE=en-US:IronRuby pair programming DTSTART;TZID=Pacific Standard Time:20090731T100000 DTEND;TZID=Pacific Standard Time:20090731T120000 UID:040000008200E00074C5B7101A82E0080000000010FE34409C0FCA01000000000000000 0100000004D78EF1FB79D814A868205FFB8EC9B84 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20090728T231440Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION;LANGUAGE=en-US: X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-OWNERAPPTID:-1243842599 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
