OSAF Hosted Service Roadmap - Sticky Plan

Sticky note categories

• User features
• Email features
• Operations
• Upstream software
• Marketing, branding, advertising, revenue

Synchronized releases

• M0 - Now
  • Upstream: OSAF server bundle 0.4-0.2
  • Feature: Chandler 0.6/0.7-dev synchronization support
  • Feature: RSS feeds available to end users
  • Feature: CalDAV draft 7 support
  • Feature: Ticket creation and management
  • Feature: Calendar creation and management
• M1 - August 17, 2006
  • Branding: Move to osaf.us placeholder
  • Community: Rollout osaf.us/server and osaf.us/client URLs
  • Ops: New admin/vm server purchased and set up with Xen
  • Ops: Promotion of single Server Bundle instance over cosmo-demo/scooby-demo split
• M2 - September 14, 2006
  • User: Customer self-service via ProductFAQ^? page
  • User: Customer self-service via forums
  • Community: Customer support ticket tracking system. RT 3.6 install, queue setup, scrips and templates customization, email gateways.
  • Community: Service home page
  • Community: Forums available to the public. phpbb
  • Community: Docs for Chandler, Scooby, Atom, iCal, Evolution usage as sticky posts in forums
  • Ops: cosmo-demo/scooby-demo services turned off
  • Ops: Switch to Hibernate backend. Set up of separate MySQL^? production database.
  • Upstream: Snarf 0.5-0.3 release and upgrade
  • Marketing: Development of metrics dashboard
  • Marketing: Development of metrics round #1
  • Email: Prototype email rounds
• M3 - October 19, 2006 - OSAF Alpha
  • Email: Send/receive account prototype based on top of OpenSRS^? Email API.
  • Community doc: iCal usage as anchor post in forums
  • Ops: Solid interactive quantitative scaling model
  • Ops: Nightly backups taken of server data. Via HTTP-based protocol.
  • Community: Customer support ticket tracking system available. Support queues configured. Visual design tweaked for better look. System documented and available for usage.
  • Ops: Monitoring and automation #1
  • Community: Ticket tracking #1
  • Community: Ticket tracking #2
• M4 - November 16, 2006 - OSAF Alpha 5
  • Email: Email submission final
  • Email: Chandler email usage
  • Upstream: Upgrade to Hibernate-backed released Cosmo
• M5 - December 14, 2006
  • Ops: Hardware capable of 3k target users
• M6 - January 18, 2007
  • Branding: Switch to domain name based upon OSAF solution brand produced by the BrandingExercise
  • 1 Google AdSense^? ad on 1 service page
• M7 - February 15, 2007
• M8 - March 15, 2007 - OSAF Beta
• M9 - July 19, 2007
• M10 - October 18, 2007
• 1.0 final - 2007
  • Nothing substantial not in Beta
  • Ops: Hardware capable of 15k target users

Sticky exercise

• M1: Admin server #1
• M2: Snarf 0.5-0.3 (milestone). Prototype email #1. Prototype email #2. Prototype email #3. Metrics #1.
• M3: Ticket tracking (PPD). Ticket tracking #1. Ticket tracking #2. Monitoring and automation #1 (contractor). Metrics #2.
• M4: Customer service forum (PPD). Customer service forums #1. Customer service forums #2.
• M5: Hibernate upgrade (Milestone). Hibernate upgrade. Email #1 (contractor). Big hardwre (15k). Metrics #3.
• M6: Email #2 (contractor). Backup #1. Backup #2. Backup #3.
• M7: Large server failover #1. Large server failover #2. Large server failover #3. Metrics #4. Monitoring and automation #2 (contractor). Email #3 (contractor)
• More: 24x7 support.

Milestones to-sort

• Email submission to office calendar
• Email receive of service-provided email account
• Email send of service-provided email account
• SMTP-based spam protection of service-provided email accounts
• Webmail for service-provided email accounts
• Throw away email addresses
• Cookie-protected submission of emails
• 1st admin/VM server
• 1st big app server
• Separate physical DB servers
• Deployment of relational database onto separate hosting layer
• Deployment of Scooby & Cosmo onto separate layers
• Hardware-based decoding of SSL
• IP sprayer appliance with session persistence and failover
• SSL-option access
• SSL-required access
• Group rendevous
• Service personalized homepage
• Ticket/cookie for group of calendars
• SMS submission of new events
• SMS notification of event alerts (and reminders, etc)
• URL redirection to appropriate network service for proper client (heuristic logic)
• OpenSRS^? email account API access