GoogleWave presentation from Opensource Days 2010
•Télécharger en tant que PPTX, PDF•
1 j'aime•626 vues
My presentation on Google Wave at the opensourcedays in copenhagen march 5 2010.
Recommandé
Contenu connexe
En vedette
En vedette (20)
Similaire à GoogleWave presentation from Opensource Days 2010
Similaire à GoogleWave presentation from Opensource Days 2010 (20)
Dernier
Dernier (20)
GoogleWave presentation from Opensource Days 2010
- 1. Google Wave Open source days 2010 March 5 2010 Daniel Graversen Masteringwave.com Daniel Graversen dgr@masteringwave.com
- 2. Daniel Graversen Daniel Graversen dgr@masteringwave.com
- 3. Agenda Why Open source and Wave Use Cases Development options Daniel Graversen dgr@masteringwave.com
- 4. Why opensource and Wave Lesson in why Opensource targets business More buzz around the product More partcipation and help from the community First movers still can make money or get market share Creates an eco system More innovation Must help with adoption Daniel Graversen dgr@masteringwave.com
- 5. E-mail resembles the conventional post system Challenges of e-mail Collaborating on a piece of text Adding new people Attachingfiles Multiple conversation branches Smallcorrections E-mail to IM to e-mail Security Audit trail No business context Input to challenges: http://danieltenner.com/posts/0012-google-wave.html
- 7. A Wave is both conversation and document
- 8. A Wave is live
- 9. A Wave can be extended to provide business contextBy design solves most of e-mail’s problems
- 10. Wave in organisations No emails back and forth. Clarity A lot of processes in organisations can leverage from the use of Wave. A lot of unstructured processes cannot be fitted into a box. 80/20 rule One place to have communication Platform for developing applications Daniel Graversen dgr@masteringwave.com
- 11. Daniel Graversen dgr@masteringwave.com
- 12. Wave inbox Daniel Graversen dgr@masteringwave.com
- 13. Google WaveNot Your Grandmothers Email... Daniel Graversen dgr@masteringwave.com
- 14. Context Time Relations The new way to communicate Daniel Graversen dgr@masteringwave.com
- 15. Wavelets og Blips Daniel Graversen dgr@masteringwave.com
- 16. My Usecases with Wave Status meetings Scrum planning, backlog and status Blog writting Company procedures instead of Google sites Messaging with peers Design documents Status reports Daniel Graversen dgr@masteringwave.com
- 17. Daniel Graversen dgr@masteringwave.com
- 19. Extensions
- 20. Robots
- 21. Gadgets
- 22. Extensions
- 23. Open source componentsDaniel Graversen dgr@masteringwave.com
- 24. Protocol XMPP to communication between servers Wave Fed. Protocol on the server RPC to client Daniel Graversen dgr@masteringwave.com
- 26. e.g. insert character "a" at position x
- 27. As long as there is a function transform() with the following behaviour, it is always possible to have all the clients come to an convergent state.
- 28. S = Server OperationC = Client OperationS' = Transformed Server OperationC' = Transformed Client Operation(S', C') = transform(S, C)where C'⋅S = S'⋅C
- 29. Client and server must have the same transform() function
- 30. Soren Lassen http://www.waveprotocol.org/presentationsDaniel Graversen dgr@masteringwave.com
- 31. Operations compose Daniel Graversen dgr@masteringwave.com
- 32. Alternative Wave servers Ruby on Sails http://github.com/danopia/ruby-on-sails FedOne http://code.google.com/p/wave-protocol/ PyGoWave http://pygowave.net/ Novel Pulse http://www.novell.com/products/pulse/ 12sprints http://beta.12sprints.com Daniel Graversen dgr@masteringwave.com
- 33. Alternative Clients Waveboarder Novell Pulse Daniel Graversen dgr@masteringwave.com
- 35. Wave adds
- 36. Buildin real time updates
- 38. Playback – like everything else on wave
- 39. Can be hosted on webservers
- 40. Code in Javascript or Flash
- 41. HTML formattingDaniel Graversen dgr@masteringwave.com
- 42. Gadget Screenshots Daniel Graversen dgr@masteringwave.com
- 43. Gadget Demo Scrum taskboard gadget for google wave Strategy Planning Tool Daniel Graversen dgr@masteringwave.com
- 45. New partcipants
- 46. Changes in the document
- 47. Keystrokes
- 48. Document Submit
- 50. Can create new waves
- 51. Exists on Google AppEngine
- 52. Can create form and manage workflowsDaniel Graversen dgr@masteringwave.com
- 53. Robots Screenshots Daniel Graversen dgr@masteringwave.com
- 54. Robot Demo SAP ES Demo, Creating Service Requests Demo showing integration to SAP is possible to extract data and interact with backed Google Wave workflows Simple workflow engine in Wave, to have different aprovallers Daniel Graversen dgr@masteringwave.com
- 56. Extensions for Wordpress, Drupal, Joomla, SAP portal exists.
- 57. Just 10 lines of codeDaniel Graversen dgr@masteringwave.com
- 58. Screenshots Daniel Graversen dgr@masteringwave.com
- 59. Embeds Demo Daniel Graversen dgr@masteringwave.com
- 61. Adds the extensions to your toolbar
- 62. Easy to install and remove again
- 63. May be distributed via Wave app store..
- 64. A SETTINGS WAVE to manage your extensionsDaniel Graversen dgr@masteringwave.com
- 68. Consulting for Wave developmentDaniel Graversen dgr@masteringwave.com
Notes de l'éditeur
- Letuslook at howe-mailworks and whatthechallengeswiththis is.The design ofe-mailresemblesthetraditional post system. An e-mail is like a letter; it has a recipientwhich is used by to routethemessage and it has contentswhichopenedonce it reachestherecipientIfyou have severalrecipients to an e-mail, thee-mailwithcontents is copied and sent to eachrecipientseparately.Iftherecipientwant to respond, thee-mail is typicallycopied, modified and sent to the original sender. There is no link betweenthise-mail and the original one; onlywhatcan be readoutofthecontents.Becauseofthis, there is no single versionofthetruth for theconversation and this is theroot for most ofthe problems withe-mail.Collaborating on a piece of text - Different versions of the truth cause a high overhead for each iterationAdding new people – People can be added by anyone, but the next e-mail could reverse it. Forwarding e-mail. Etiquette around when to add people like your boss. Also, new people have a tough job understanding what has discussed earlierAttaching files – Files are only available in the e-mail it was sent. All subsequent e-mails have not access it and cause lost time due to searching etc.Multiple conversation branches – Typically use case where 4 questions are asked, but only last one is responded to.Small corrections – High overhead for each mail iteration, means that small corrections, for example in meeting minutes, are not performedEmail to IM to Email – Often a conversation changes to IM due to need for realtime communication. This looses all contextSecurity – Security of e-mails is in general poor. Any technical savvy person can send an e-mail that to most users appear to be from another personAudit trail – How said what is difficult to get based on the last e-mail since there is no one version of the truth and important points may be lostNo business context – Perhaps the most important, there is no relation to business context the e-mail was sent as part of. Which customer, which process. Also any data that are input to the conversation are pulled from business systems and copied to the e-mail
- Google Wave is an online tool for real-time communication and collaboration, which strives to be as good as face-to-face communication.It uses what progress and knowledge we’ve gained in the last 40 years, and applies it to the problem domain e-mail covers. In the same way as e-mail, it is based on a set of well-defined protocols which Google encourages others also to contribute to. (more of that later)A wave is shared. Any participant can reply anywhere in the message, edit the content and add participants at any point in the processA wave is equal parts conversation and document. People can communicate and work together with richly formatted text, photos, videos, maps, and more.A wave is live With live transmission as you type, participants on a wave can have faster conversations, see edits and interact with extensions in real-time.Do live demo of wave after explaining first imageDemonstrate:Offline sendTagsAttach fileMultiple branchesReal-time updateInvite new personsBy design solves most of e-mail’s problemsNo business context – Can, as we will see, be extended to provide business contextHowever, it does create need for new etiquetteCollaborating on a piece of text – same shared view of the conversaitonAdding new people – People are added permanently. New users can through the replay function see step by step the progressAttaching files – Files are added to the wave and available for participantsMultiple conversation branches – Structure allows multiple concurrent conversationsSmall corrections – Anyone can correct the text of others. Collective meeting minutesEmail to IM to Email – Wave provides real-time collaboration. No need to switchSecurity – Security model part of waveAudit trail – Replay of all messagesLive demo (copy paste text)Project Assignment: World Class Shared Services Portal Scope:-Implement alternative channels for enquiriesNot in scope:-Content modifications (line responsibility)Resources:-Product Owner-Scrum master-Web developer