Phase 1 Initiate the project

• Make a micro-site explaining the project (started)
  • Tiki bug with truncating menu
  • Make it possible to print the whole microsite in one page
    • get structure going or make PluginInclude have an option to note execute maketoc in included pages
  • Find a way to force perspective for suite.tiki.org (ex.: A test on category and perspective, and a redirect)
• Identify people willing to participate
• Identify projects/communities as part of the Tiki Suite
  • Get in touch with them and see their interest (through developer channels)
• Explore avenues for external assistance by foundations & associations who would likely like to see this happen.
• Dogfood with select communities
• Document "manual" assembly (recipe) of the Suite
• Communities start collaborating
• Add config panels in Tiki and in other apps
  • Tiki already has an admin panel for BigBlueButton and Kaltura
• Identify potential service providers
  • Current service providers in each of the components which can easily add services
  • Service providers that currently provider these types of services (ex.:Savoir-faire Linux)
• Add sections to suite.tiki.org to focus on documentation, but reports, feature requests, related to the Suite (but keeping application-specific stuff on their respective sites

Phase 2 - FOSS service companies that will be ready to eventually offer Tiki Suite services.

• The components are all confirmed
  • This assumed that all went well until now. If some components are not working out for technical, community or whatever reasons, we want to resolve as soon as possible.
• Establish a governance model for components of the Tiki Suite.
• Document business models to encourage SaaS offerings and services ecosystem from within each of the existing communities.
• Branding/Marketing/Promotion/Community events to FOSS developers
  • Promote the Suite on each component's site
  • Present at FOSDEM, OSCON, etc.
• Service providers start offering consulting services

Phase 3 - FOSS service companies that will be ready to Dogfood

• Generate a first semi-automated setup (ex.: apt-get all the components)
• Branding/Marketing/Promotion/Community events to the general public
• SaaS offerings are starting to be available
• Interoperability between the components is improving. Things look different, but issues are reported and fixed.

Phase 4 - Tech-minded companies that will be ready to Dogfood

• The Tiki Suite is easy to deploy and available via appliances with tools to manage each part.
• A viable and growing services ecosystem exists in many countries.

Phase 5 - any small company

• Feature-wise and integration-wise, it's a among the best systems, FOSS or Commercial.

Phase 6 - any medium-sizes company

• Improving scalability and redundancy