Phase 1

• 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
• 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)
• Setup a dedicated website to focus on documentation, but reports, feature requests, related to the Suite (but keeping application-specific stuff on their respective sites
• 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

Phase 2

• Document business models to encourage SaaS offerings and services ecosystem from within each of the existing communities.
• Branding/Marketing/Promotion/Community events
  • Promote the Suite on each component's site
  • Present at FOSDEM, OSCON, etc.
• Generate a first semi-automated setup (ex.: apt-get all the components)