Skip to content
p2k edited this page Sep 13, 2010 · 1 revision

PyGoWave Server Roadmap

The up-to-date todo list can be viewed at the Issues tab.

Alpha 0.1

Quick-and-dirty Gadget wrapper

  • Create data models for basic server operation – done
  • Think of an event sending/dispatching engine – done
  • Experiment with robot client libraries – done
  • Find appropriate tools – done
  • Create a basic design for webpages – done
  • Implement registration form for PyGoWave – done
  • Create a basic settings page – done
  • Add a Gadget registration form – done
  • Add a Wave creation form – done
  • Build a small Wave Gadget environment emulator – done
  • Implement simple client script for Gadget communication – done

Alpha 0.2

Bugfixed alpha release

  • Fix upcoming bugs

Alpha 0.3

Improved PyGoWave client, basic Wave communication working

  • Look for a better JavaScript toolkit – done
  • Port existing non-client code to the new toolkit – done
  • Read and understand Operational Transformation – done
  • Design and implement a client object model and OT – done
  • Implement RPC server back-end for the client object model – done
  • Implement a serialization for the server Wave model – done

Alpha 0.4

Robot support, bugfixed Wave communication

  • Add a contact list with authorization system
  • Implement text formatting and cursor positions
  • Multiple Blips i.e. answers and inline
  • Add a Robots tab and create a Robot registration form
  • Implement an event handler for robots into the RPC server
  • Try to run an example robot with the server via the Google App Engine
  • Decouple the Robot API from the Google App Engine to allow non-GAE Robots on Django

Beta 0.5

Ready for daily use, Embed API ready

Beta 0.6

Bugfixes, advanced Wave communication

  • Implement image upload
  • Implement playback feature
  • Show differences between Wavelet versions

Beta 0.7

Federation Protocol implemented

  • Implement Google Wave Federation Protocol

Beta 0.8

More bugfixes

Beta 0.9

Last beta release

  • Use distutils (and others) to create an installable version

Release 1.0

Production-ready system