My presentation at the lca2010 Googlewave miniconf

1. Building The Independent Wave

3. Status of the Independent Wave

4. Where the Independent Wave needs to be

6. Evolution happens in software as in life, mutations allow old forms to occupy new niches

7. Iwave allows for more rapid evolution of Wave through exposure to different environments

8. Iwave creates demand for Gwave

11. Released under Apache License (opportunity)

12. Implements full federation protocol

13. Not production ready

14. Under heavy development

15. Working Agents implementation

16. Console based client

18. Web based interface

19. Achieved federation with wavesandbox.com and FedOne servers

20. Character by character transmission

21. Last commit was 2 nd December

23. Started life as a Gadget testing framework for Gwave

24. Still being actively developed

25. Actively developing Client/Server Protocol

26. Not production ready

27. Actively developing non Web based client

28. Doesn't support federation yet

30. Announced Wave support (including Federation)

31. Is still awaiting release

32. Closed source

33. Initially SAAS, then possibly installable product

36. Works with FedOne Iwave server

37. Under development

38. QT Based

39. Not production ready

41. Proof of concept

42. Limited to Pygowave Servers only

44. Integration with existing systems

45. Agents

47. Demand for “Native Wave Applications” already exists

48. Independent protocols allowed for the development of any number of different email servers and clients

49. Open Protocol invites new players into the eco-system

51. Integration must happen in as seamless a way as possible

52. Iwave needs Agents. No Iwave server that doesn't support Agents will succeed

53. For an example of such integration see PlonieBot

59. Active developer community

60. Products and Services

61. Standards with backing

63. Developers with certainty tend to be more inclined to develop

65. Agents

67. Ruby on Sails

68. FedOne

71. Client/s

72. Agents

76. Commercial Confidentiality

80. Federation

81. WCSP (Wave Client-Server Protocol)

82. “Groupware”

83. WASP (Wave Agent-Server Protocol)

85. They are part of the greater ecology

86. The early work is being done

87. People are starting to take the first steps towards the Iwave

88. It's exciting, isn't it