Making the New Notes - Community, Cooperation, Concepts
?Download as ODP, PDF?
0 likes?501 views
The document discusses the Notes2 project in OpenOffice.org, which aimed to improve the notes functionality. It describes how the implementation team was formed through community involvement, analyzed requirements by gathering use cases and comparing competitors, and collaborated remotely using tools like IRC, phone calls, email and wikis. The project was successful in developing new notes features for OpenOffice.org 3.0 while demonstrating that open source communities can effectively work together on technical improvements.
Making the New Notes - Community, Cooperation, Concepts
- 1. ?
- 2. Making the New Notes Christoph Noack OpenOffice.org User Experience Max Odendahl OpenOffice.org Development Christian Jansen Sun Microsystems Community Concepts ³ Cooperation ³
- 3. Making the New Notes Community Concepts Cooperation
- 4. Making the New Notes Community Concepts Cooperation
- 5. Introduction to Notes2 Notes2 is an activity to improve the existing notes functionality in OpenOffice.org Writer
- 6. Notes2 has been developed with major community involvement
- 7. Notes2 solved about 100 issue tracker entries
- 8. Notes2 has been rewarded in the ¡°OpenOffice.org Community Innovation Program Awards¡± (Technical, Core)
- 9. First results are contained in OpenOffice.org 3.0 Question: Do you remember the past?
- 10. Notes in Previous Versions Result:
- 11. Notes in OpenOffice.org 3.0 Result:
- 12. Start of the Activity 06/2002 Issue 6193 requests improvements for the notes handling in Writer 03/2007 Mathias Bauer proposes to start an activity within Google Summer of Code Max Odendahl applies for the GSOC and gets accepted (Student of Computer Sciences) 04/2007 Christoph Noack joins the team after being asked by the User Experience project lead (UX community member) 05/2007 An implementation team is made up (i-Team ¡°Notes2¡±)
- 13. The Implementation Team ¡ supported by the whole OpenOffice.org community! Christoph Noack Community Max Odendahl Community Mathias Bauer Sun Microsystems Christian Jansen Sun Microsystems ?ric Savary Sun Microsystems Uwe Fischer Sun Microsystems Mentor Mentor
- 14. Making the New Notes Community Concepts Cooperation
- 15. Working Steps Cooperation does mean: ¡°come together, clarify what to do, work on it, realize something useful¡±
- 16. The ¡°working steps¡± show one classic approach Sounds easy? Let's look at the first step... Problem Concepts Design Requirements Engineering Test and Feedback Code Development
- 17. Understanding the Problem An IRC chat was the first ¡°official¡± team meeting. Oh dear... We did not know each other (personal goals, previous work in the community, skills, ...)
- 18. We knew the single issues of the notes, but lacked understanding for the common goal
- 19. We had no agenda, we just started to discuss Experience: A face-to-face kick-off meeting or phone conference in the first phase may be helpful
- 20. Formulating a project goal helps to keep the focus
- 21. Requirements Engineering Roadmap and design concepts are based on requirements (collection of information, prioritization, definition of terms)
- 22. Information sources: Use cases (¡°brainstorming¡±)
- 23. Competitor analysis (different office applications)
- 24. Requests for enhancements (issue tracker entries, feedback on community mailing lists)
- 25. Experience of the implementation team Question: Do we have some examples for that?
- 26. Requirements Engineering Working with Use Cases High-level requirements: Identify the stakeholders
- 27. Collect use cases in the document life cycle Experience: Judges facts, not preferences
- 29. Effort may be high, you need to convince others Example Requirement StR 49: If the user exports a document, he wishes to be informed if notes are not visible. Use Case: User A edited a document and filtered some notes. Then, he sends the document via e-mail. Thus, he wishes to be informed of information which is not visible. Comments: Alternative is to change the default; deactivate the export of notes. Source: http://wiki.services.openoffice.org/wiki/Notes2 Hint: It also helps to look at the competition.
- 30. Requirements Engineering Competitor Analysis Word processor ¡°Softmaker TextMaker 2006¡± Notes similar to Microsoft Word 2003
- 31. Example: Page contains many notes -> notes not really usable (overlay, cut-off)
- 32. Similar behavior in first Apple Pages Finding: Robust and scalable functionality required Notes.tmd - Textmaker Status Bar Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Comment [2007-10-27]: Nunc ac erat vel nisi mollis vestibulum. Donec purus tellus, eleifend non, pulvinar et, porttitor eu, lacus. Nam dictum arcu at justo. Proin semper tempus nisl. Morbi a arcu ac metus interdum consequat. Praesent aliquet imperdiet est. Nunc quis risus id nunc posuere blandit. Aliquam cursus, ante ac interdum convallis, leo felis congue nulla, sed faucibus lacus dui tempus ante. Duis viverra augue sit amet turpis. Donec ac lacus vel massa sollicitudin aliquet. Etiam aliquet dolor quis elit. Pellentesque adipiscing tellus sed sem. Quisque sit amet quam non dui viverra ornare. Integer nec risus ut risus lobortis vestibulum. Proin hendrerit, pede vel commodo cursus, felis enim egestas mi, ut aliquet enim nisi sit amet elit. Nulla facilisi. In auctor volutpat leo. Nam vitae nibh a arcu dapibus aliquet. Maecenas turpis. Donec quam. Sed ipsum libero, viverra eget, fringilla vel, auctor eget, ipsum. Curabitur egestas facilisis lectus. Duis dignissim lectus vel velit. Fusce congue velit eget neque. Integer consequat. Fusce nec purus ut justo consequat commodo. Menu and Toolbar
- 33. Requirements Engineering Competitor Analysis Presentation program ¡°Microsoft Powerpoint 2003¡± Notes are handled like small graphic objects
- 34. Example: Click on anchor to open note window
- 35. Select text -> text looks being editable
- 36. Pressing 'Del' removes the note! Finding: Be clear in communicating different states to the user Nunc ac erat vel nisi mollis vestibulum. Donec purus tadolom. Joe User 2007-10-27 mollis vestibulum Nunc ac erat vel nisi mollis vestibulum. Donec purus tadolom. Joe User 2007-10-27
- 37. Communication Channels Face-to-face Very positive, although it was a bit too late... Phone Calls Good for the discussion of single topics (better if we had an online-whiteboard) Chat Rated good if used between few members
- 38. Never used again by the whole team E-Mail Very good for discussion of single topics
- 39. Decisions shold be officially published Issue Tracker Good to manage mid-term to long-term issues Wiki Very good! Remote collaboration can work well!
- 40. The tools are not that important (but we re-think their use)
- 41. Communication Wiki Store common knowledge, e.g.: Project details
- 44. Proposals, concepts, mockups Experience: Great for getting feedback
- 45. Use it as soon as possible
- 46. Care about the structure Source: http://wiki.services.openoffice.org/wiki/Notes2
- 47. Communication Discussions and Decisions Examples: procedure, roadmap planning, design decisions Experience: Decisions should not be made by the whole team in general -> establish guidelines accepted by the team
- 48. Planning for a certain release didn't work well -> define minimum feature and quality requirements
- 49. The foundation provides a certain set of capabilities -> identify technical constraints as soon as possible
- 50. Making the New Notes Community Concepts Cooperation
- 51. Design Proposals ¡°Notes Window¡± Visual evolution of the note window and the options buttons /+------------+ / | notes text | ----/ | notes text | | notes text | : : | Author/Dat | +------------+
- 52. Design Proposals ¡°Advanced Text Editing¡± Much text inside note window Many notes on one document page Deleted notes for change tracking
- 53. Implemented Design ¡°Colors¡± Definition of Colors Accessibility Check Display Check Notes author colors are based on other OpenOffice.org colors Result: New colors are consistent, fresh, accessibility tested
- 54. Features Being Worked On The framework is now ready for advanced functionality. Grouping of notes belonging together
- 55. ¡°Reply-To-Note¡± to answer existing notes
- 56. Better integration with change tracking comments
- 57. Improved anchors, e.g. new anchors for text areas (e.g. referring to words)
- 58. Ideas for Future Versions ¡°Printing¡± Printing has still room for improvement
- 59. Specification drafts available for: Printing notes windows next to document
- 60. Printing notes text only There are still many other ideas... Help is appreciated.
- 61. Making the New Notes Community Concepts Cooperation
- 62. Summary Community Success? A feature improvement at least...
- 63. We think, the community does have impact! Collaboration Remote collaboration does work!
- 64. Working has been much fun and sometimes exhausting! Concepts Not everything is perfect, yet. There will be improvements!
- 65. Many ideas still flying around. And now? Start your project and share your experience!
- 66. OpenOffice.org User Experience Team ux.openoffice.org
Editor's Notes
- ID : StR 49 If the user saves a document in a non-standard document format and the document contains notes information which is suppressed in the current view, the user wishes, that OOo informs him that there is suppressed information UseCase : The user A filtered some of the notes information during the editing of the document. At the end, he exports the document to a PDF file to send it via e-mail. The original document contains some private information in the notes he does not want to export. Therefore user A wishes to be informed about that if he exports the document. Comments: Alternative: Deactivate the export of notes information per default, if it is exported. Refer also to StR 44