A plan to deploy Tiki Suite "as is" for a company of 10-20 employees. Document everything along the way, and gather experience on interoperability and additional components. This company will dogfood internally, with the goal of offering as a service to their customers.

• October-November 2013

• How many employees in the test phase?
  • Will this be their main mail account and we transfer mails or we do this under a new domain, and this is progressive?

Install and configure the base packages "as-is", without 3rd party packages. We configure all three systems with built-in features and configure them to all work nicely together. We train users on these tools for their main use cases.

These three packages have so many features, it's just insane 😊

• https://doc.tiki.org/Features
• http://www.bigbluebutton.org/
• http://www.clearfoundation.com/Software/overview.html

They also manage internally the complexity of interoperability of a huge number of components, libraries, etc

• https://dev.tiki.org/External+Libraries
• http://www.bigbluebutton.org/components/
• http://www.clearfoundation.com/Foundation/integrated-code.html

We need 4 root servers (virtual servers are fine) on which we will install

1. ClearOS + Tiki + Zarafa
   • https://tiki.org/Tiki+on+Clearos
2. sipXecs
3. BigBlueButton
   • https://code.google.com/p/bigbluebutton/wiki/081InstallationUbuntu
   • Alternatively, for the test, we can get a hosted account at http://hostbbb.com/ and just need one server.
4. Test a virtualization solution

Basic integration to work: use LDAP

Make "rooms" available for team collaboration / project management which offers the features of Tiki / BigBlueButton / etc.

Here, we implement desired things that are not part of the base packages, but have already been implemented by others, following and improving the documentation. We interact with the various projects and think ahead for the new possibilities offered by HTML5 (like WebRTC, etc.). By the end of this phase, we'll have a clear idea of our options for the road ahead.

In this phase, no development, only configuration and training.

"The default groupware and mail solution is now based on Zarafa technology."
http://www.clearfoundation.com/docs/release_info/clearos_community_6.3.0/final_release_information
http://www.clearcenter.com/support/documentation/clearos_professional_6/6.3.0_release_notes

• http://www.clearfoundation.com/docs/howtos/freeswitch_with_sipxecs
  • The integration is not working well as of 2013-12, so we are keeping on separate servers for now
• BigBlueButton: We can add a 1-8xx phone number so people can call in from Skype and regular phones

Under the hood, a new engine for supporting web applications is also in development.

Once we have experimented enough with the various components, we can start improving interoperabiliy, adding missing features, and thinking of large scale deployment and maintenance

• Tight integration of users, groups, search, etc. between all systems
• Configuration Management and Systems Orchestration so we can deploy this automatically
• Make Tiki Webmail awesome (and associated features like Contacts and Calendar)