Sharing services strawman plan

---

Status: Outdated and inappropriate. This document is merely notes from another source.

---

Preface

This document explores issues related to the development of an OSAF-affiliated sharing service. It's a mix of top-down and bottom-up design and is incomplete on most dimensions. In this document, the term product will be used to refer to the whatever the offering actually is; in other words, we treat the service as a product, at least initially.

Product vision and mission

Vision

Making management of the PIM ecology easier.

Mission

We will build an Internet service which provides personal information coordination and collaboration services. We will provide services difficult to integrate into single applications, including publicly-available data storage and retrieval, synchronization services, browse-anywhere access, multi-client coordination, group coordination, directory services.

---

Marketing

Value proposition

(only notes)

events -> summary views -> coordination with other individuals -> grouping individuals into groups -> coordination as a group

People are willing to pay some money for good synchronization.

Competitive space

Brand

Creative brief

Naming

Marks

URLs, logos, audio marks, animated marks

Tenents

• Using a web-based user interface speeds development and deployment of the service.
• The service should help manage:
  • Multiple Chandler instances
  • Coordinating groups of people

Product phasing

• Prototype
• Scoping
• Plausible face
• Infrastructure buildout

Phase details

Prototype

Phase exit criteria

• Chandler can use Cosmo

Prototype

Phase exit criteria

Infrastructure buildout

Phase exit criteria

• In colocation with bandwidth sufficient for target volume
• In best-practices hosting environment colocation with bandwidth sufficient for target volume

Cosmo service
  Service definition
    Cosmo instance
      Only runs stable, released versions of Cosmo software
        ie, don't fork
    Scooby instance
      Only runs stable, released versions of Scooby software
        ie, don't fork
    Free storage
    Calendaring services
    service
      Branding
        Options
          Cosmo demo service
          Halua
      message
        data is not backed up
        welcome to use to experiment
        especially suited to Chandler use
        only Chandler supported
        Welcome to use for WebDAV
        Quota
        Reserve the rights
      support
        RT
      Prototype
        200 Gb shared
      General availability
  Marketing
    Brand
      Naming
      Marks
        Logos
          favicon.ico
          web small
          Vector
        hostnames
        Audio
          None
    Creative brief
      Helpful
      Experimental
      Available for use
      Hip
      Interoperable
      Sharing
      Community
    Resources
      Pieter Cosmo Marketing page
  Open issues
    service name
      Options
        Cosmo demo
          too generic
        halua
          too close to hula
        odie
  Operations
    People
    Network
      network
        ISC, Redwood City
        hostname
          halua
        Service name
          cosmo-demo-v2
    Storage
    Hardware
      hardware
        new hardware
          new egg. com. order rushed
        CPU
          Athlon 64 3000 512kb 90nm
        Memory
          4 Gb PC3200
        Disk
          2x 300Gb SATA 7200RPM 8Mb
        Case
          2U 400W 24+8 PS
    Software
      JVM 
      Servlet
      App
      software
        OS
          Debian sid
        JVM
          Sun SDK 1.4
          free-java in Debian
        admin scripts
          build-cosmo-instance
      Apache
        functionality
          SSL
          throttling
          RPAF
          mod_proxy (forward and reverse proxy)
          mod_rewrite (URL mapping)
      Cosmo
        functionality
          public account creation
            Email-confirmed
            Anonymous
            Web-based
            Links in Chandler
          WebDAV
          CalDAV
          storage
            virtualization
          Portals JSR-168
          Authentication / authorization
            LDAP integration
          Fully-qualified URL overriding
          RSS
          Homepage
        config
          tarball distro
            Tomcat
            Cosmo
            others?
          HTTP port
          Tomcat shutdown port
          Admin password
          URL prefix
        admin
          backups
            no time snapshots
            RAID 1 (mirroring)
          monitoring
            areas
              performance
              availability
            App-maintained
              HTTP + URL retrieval
            VM-maintained
              JMX
    transport
      SSL encrypted
        certificate
    monitoring
      Framework
        Nagios
          Custom HTTP-based check plugins
        Instrumented VM
          Txns/sec
            Subtopic
          Memory usage
          Object count
          GC stats
      Availability
        Quotas
      Performance
        Time per txn
      security
    accounts
      forgotten username/password
    policy
      Acceptable use
    Scaling model
    SLA
      Data is not backed-up
        You should arrange to backup your data remotely if its important
      It's a good machine, but not highly available.  We could be down up to a week a year; most likely is about a day.
      We'll try hard to preserve your data when we update the Cosmo version in production.
  Background
    Vision
      Anyone can share digital personal information easily with the world
    Mission
      To operate an efficient, reliable sharing service for the public
    Values
      Very quick to set up an account
      You can provide parts of your calendar securely with people you don't know well
      You can get all your data out of the service and import it into current and future systems
http://wiki.osafoundation.org/Projects/CosmoMarketing