BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20090626T170000Z DTEND:20090626T180000Z DTSTAMP:20090624T040201Z ORGANIZER;CN=Sugar Labs Meetings:mailto:h9cfuk10894em7a8moemquu...@group.ca lendar.google.com UID:1otu9cnhhqd7s7a19i3n9kc...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;cn=de...@lists.laptop.org;X-NUM-GUESTS=0:mailto:devel@lists.laptop.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;cn=i...@lists.sugarlabs.org;X-NUM-GUESTS=0:mailto:i...@lists.sugarlabs .org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;cn=sugar-de...@lists.sugarlabs.org;X-NUM-GUESTS=0:mailto:sugar-de...@l ists.sugarlabs.org CLASS:PRIVATE CREATED:20090624T040200Z DESCRIPTION:http://webchat.freenode.net/?randomnick=1&channels=sugar-meetin g&prompt=1\n\nAgenda\n- How to move forward with updating Activities via AS LO. Should at\nleast be on roadmap to synchronise work and expectations.\n- Reduce redundant information on w.sl.o\, w.lt.o and ASLO. Factors to\ncons ider:\n -- Expectations of existing user base.\n -- Update mechanism at e xisting deployments.\n -- Reduce overall confusion.\n -- Reduce workload on Activity developers.\n -- Scalability of solution.\n\nView your event a t http://www.google.com/calendar/event?action=VIEW&eid=MW90dTljbmhocWQ3czdh MTlpM245a2M4NzggZGV2ZWxAbGlzdHMubGFwdG9wLm9yZw&tok=NTIjaDljZnVrMTA4OTRlbTdh OG1vZW1xdXVzbWdAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbTg3YmEyMDZjYjg4ZjE4ZmM3ZGM xNTNhZjI5NmZlYzllM2RhNjRiNDc&ctz=America%2FNew_York&hl=en. LAST-MODIFIED:20090624T040201Z LOCATION:irc://irc.freenode.net#sugar-meeting SEQUENCE:0 STATUS:CONFIRMED SUMMARY:Activity Team Meeting TRANSP:OPAQUE END:VEVENT END:VCALENDAR
invite.ics
Description: application/ics
_______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
