• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Building The Independent Wave

Building The Independent Wave



My presentation at the lca2010 Googlewave miniconf

My presentation at the lca2010 Googlewave miniconf



Total Views
Views on SlideShare
Embed Views



1 Embed 10

http://www.slideshare.net 10



Upload Details

Uploaded via as OpenOffice

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Building The Independent Wave Building The Independent Wave Presentation Transcript

    • Building The Independent Wave
    • What is the Independent Wave
      • In a nutshell, the independent wave is all things wavey built outside of Google Wave.
    • Status of the Independent Wave
    • Where the Independent Wave needs to be
    • Why do we need the Independent Wave
      • Every system evolves
      • Evolution happens in software as in life, mutations allow old forms to occupy new niches
      • Iwave allows for more rapid evolution of Wave through exposure to different environments
      • Iwave creates demand for Gwave
    • What's happening in the Iwave now
      • Servers
        • FedOne
          • http://code.google.com/p/wave-protocol/
        • Ruby On Sails
          • http://github.com/danopia/ruby-on-sails
        • Pygowave
          • http://pygowave.net/
        • Novell Pulse
          • http://www.novell.com/products/pulse/
    • Iwave Servers
      • FedOne
        • Googles Open Source Reference Server
        • Released under Apache License (opportunity)
        • Implements full federation protocol
        • Not production ready
        • Under heavy development
        • Working Agents implementation
        • Console based client
    • Iwave Servers
      • Ruby On Sails
        • Ruby based system
        • Web based interface
        • Achieved federation with wavesandbox.com and FedOne servers
        • Character by character transmission
        • Last commit was 2 nd December
    • Iwave Servers
      • Pygowave
        • Python/Django based system
        • Started life as a Gadget testing framework for Gwave
        • Still being actively developed
        • Actively developing Client/Server Protocol
        • Not production ready
        • Actively developing non Web based client
        • Doesn't support federation yet
    • Iwave Servers
      • Novell Pulse
        • “Social Web Aggregator”
        • Announced Wave support (including Federation)
        • Is still awaiting release
        • Closed source
        • Initially SAAS, then possibly installable product
    • What's happening in the Iwave now
      • Clients
        • Qwave
          • http://code.google.com/p/qwaveclient/
        • Pygowave-qt
          • http://github.com/p2k/pygowave-qt/
    • Iwave Clients
      • QwaveClient
        • Cross platform client
        • Works with FedOne Iwave server
        • Under development
        • QT Based
        • Not production ready
    • Iwave Clients
      • Pygowave-QT
        • Utilises Pygowave Client/Server Protocol
        • Proof of concept
        • Limited to Pygowave Servers only
    • Evolution is driven by challenges
      • Structural Challenges
        • Protocols
        • Integration with existing systems
        • Agents
    • Structural Challenges - Protocols
      • Client / Server Protocol
        • A defined and agreed upon Client/Server protocol is essential to the growth of the Iwave
        • Demand for “Native Wave Applications” already exists
        • Independent protocols allowed for the development of any number of different email servers and clients
        • Open Protocol invites new players into the eco-system
    • Structural Challenges - Integration
      • Integration with existing systems
        • Iwave needs to be able to plug in to existing infrastructure
        • Integration must happen in as seamless a way as possible
        • Iwave needs Agents. No Iwave server that doesn't support Agents will succeed
        • For an example of such integration see PlonieBot
    • Structural Challenges - Agents
      • Agents offer both challenges and opportunities
      • #1 Challenge: How do you prevent malicious Agents from screwing things up?
        • Agents not only hosted locally but remotely
        • Determining whether a remote participant is an Agent or not
      • Agents can make or break the Iwave
    • Building the Iwave - Foundations
      • Even the most impressive building needs a solid foundation
      • Iwave foundation requires
        • Gwave/Google
        • Active developer community
        • Products and Services
        • Standards with backing
    • Building the Iwave - Standards
      • There is currently one defined Standard
        • Federation
      • Standards give developers certainty
      • Developers with certainty tend to be more inclined to develop
      • New standards required:
        • Client/Server Protocol
        • Agents
    • Building the Iwave - Ecologies
      • Remember these:
        • Pygowave
        • Ruby on Sails
        • FedOne
        • Pulse
      • Each of these represents a potential Iwave ecology
    • Building the Iwave - Ecologies
      • An Iwave Ecology is made up of the following
        • Server
        • Client/s
        • Agents
        • Users
      • All of which opportunities for developers to become involved in that ecology
    • Building the Iwave – Opportunities
      • Many organisations are interested in Wave
      • However for many reasons, they can't use Gwave
        • Privacy Legislation
        • Commercial Confidentiality
        • Infrastructure Requirements
      • Each of these organisations is an opportunity for the Iwave
    • Building the Iwave – My Ideal
      • The following is my own Iwave Server Ideal
      • This server needs to bridge the divide between Email and Wave:
        • SMTP, POP3, IMAP as native rather than Agent
        • Federation
        • WCSP (Wave Client-Server Protocol)
        • “Groupware”
        • WASP (Wave Agent-Server Protocol)
    • Building the Iwave – Final Thoughts
      • Gwave and Iwave need each other
      • They are part of the greater ecology
      • The early work is being done
      • People are starting to take the first steps towards the Iwave
      • It's exciting, isn't it