70 likes | 310 Views
Chat Rooms Front or Back Office Service?. 23 rd August 2010 Tim Smith Thomas Baron, Jose Benito Gonzalez. Background. LHC video conferencing requirements (established within the LCEB study) 2009: Included chat, as a low priority 2010: became a high priority item EVO includes chat
E N D
Chat RoomsFront or Back Office Service? 23rd August 2010 Tim Smith Thomas Baron, Jose Benito Gonzalez
Background • LHC video conferencing requirements (established within the LCEB study) • 2009: Included chat, as a low priority • 2010: became a high priority item • EVO includes chat • Most (all) serious alternatives do not • Impediment to moving away from EVO • Non-VC use cases • Feedback: starting EVO to chat is heavy
Solution • Indico is our “meeting hub” strategy • Already: Request and Launch • VC, Webcast, WebLecture, Recording • Proposed: Promote chat from VC function to Indico • Enable chat-rooms associated with each meeting • Create optionally when book meeting • Only for CERN authenticated users • Logged and searchable
Status • Integrate don’t re-implement! • A market leader: jabber • Technical student assignment (~4 month) • Standard jabberd installation at CERN • Integrated with the CERN account system • Tested to several thousands of users connected • Indicouser interface integration for launch • Local chat client for each platform • Scheduled for production release in November
Extension: A New Service? • Experiment coordination meeting • Alberto Aimar and Denise • Shifter use cases: • ATLAS • 2 persistent chatrooms in Oslo, based on jabberd • 1 for virtual control room and 1 for distributed analysis • about 100 users, using external accounts (jabber, gmail and others) • CMS • one shifter is always connected on AIM with a predefined account • a list of experts is also on AIM and can be contacted • also using a Computing Logbook (elog) for keeping a permanent record • Meeting with ATLAS, CMS, and Indico • Strong interest in having a supported service (inside and) outside Indico