March 21, 2007

Java authentication completed.  Greg and Dennis working on legalities of passing the code upstream.

Developer Source code from Jive available as soon as next week (for paying customers).  

Jive to soon publish Load Testing Whitepaper, which may inform our testing procedures. 

Roadmap development -

Discussion with potential customers is preferable to theoretical discussion among developers.

Library seems enthusiastic about a Click-for Chat solution.  

    Demo of Jive Fastpath would be easy for us to arrange, technically.  Would give us much information about what they would want, and what holes we would have to fill in Fastpath to meet their needs.  Dennis to inquire with Library when they would be available.

    Known issue - Fastpath requires an anonymous authentication step, which is not likely acceptable to us.  Greg will investigate solution/workaround options.

    Known issue - Library would want integration with their Request Tracker system, and we have not looked into how difficult that would be to provide.   

        If other departments are using Request racker, this provides a stronger motivation to build the integration.
 

    If Fastpath is not acceptable for some reason, we would need more resources or a very long timeline.

Helpdesk - not enthusiastic, fears additional communication channel would complicate, rather than simplify matters. 

    If we can provide high adoption rate, chat solution might simplify and consolidate, rather than complicate, their communications.

    Also calls for Request Tracker integration

Residential Computer Consulting - might also be a chat customer.

Dennis has meeting concerning SIP next week, may inform further chat functionality.

If Click to Chat does not gain traction from any customers, what functionality should we pursue for the platform?

    Speak with Stellar about possible use case for them.

    Class discussion group/chatroom functions a significant option. 

         Student information privacy issues come into play - Jive functionality with respect to limiting chat room entry to select list of individuals ought ot be explored.

  • No labels