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=Tim Chen ( SDO):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 24\, 2009 10:00 AM-12:00 PM (GMT-08:00) Pacific Time (US & Canada).\nWhere: (Live Meeting)\n\nNote: Th e GMT offset above does not reflect daylight saving time adjustments.\n\n* ~*~*~*~*~*~*~*~*~*\n\nRay\, Tim and I are meeting tomorrow. Tim\, I will n eed your MSN id.\n\nLet me know if anyone else wants to join in.\n\n\nFrom http://wiki.github.com/ironruby/ironruby/debugging:\n\nPair debugging wit h 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 base learn debugging tips and techniques. To make this a fruitful exercise\, please follow the following guidelines :\n•\n\nSend email to [email protected]<mailto:ironruby-c...@r ubyforge.org> asking if any experienced developer is available to help you \n• Ensure that you can build and successfully run all of the Ruby Spec<http://wiki.github.com/ironruby/ironruby/rubyspec> tests.\n• Restrict the problems to pure Ruby code which is known to work with MRI. E nsuring a clean working baseline functionality in MRI ensures that the pro blem truly in IronRuby. Without a known clean MRI baseline\, the problem c an be in a component other than IronRuby which you are as well-equipped to diagnose as anyone else.\n• Set up a clean repro. Spend time ensu ring that it is not a configuration issue\, and that the problem can be ea sily reproduced on other machines. Document detailed information about you r platform\, version of IronRuby\, and the steps to repro the problem.\n� � Do basic debugging by yourself beforehand. This will ensure that y ou get 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 your machine\, which will allow you to watch the debugging session.\n� � Add the experienced developer as a friend/buddy in some Chat progr am 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:20090724T100000 DTEND;TZID=Pacific Standard Time:20090724T120000 UID:040000008200E00074C5B7101A82E0080000000070C2DCF6810BCA01000000000000000 0100000009A00A2D7E9BA78498BBA39945F349B89 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20090723T174015Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION;LANGUAGE=en-US:(Live Meeting) X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-OWNERAPPTID:135755737 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
