Tool Reduces information overload Makes multi-tasking easy Framework How it works

1. Mylyn • Tool • Reduces information overload • Makes multi-tasking easy • Framework • How it works • Integrating and extending • Integration • Showcase of extensions • Task-Focused Desktop Task-Focused Toolkit • Mik Kersten Last updated June 2007, made available under the EPL v1.0

3. Informationoverload Context loss when multi-tasking

4. With Mylyn Tasks are integrated See only what you are working on

5. Overview • Task-Focused UI • Demos of key features • Integrated task management • Automated context management • Collaboration and planning • The framework • How the task context model works • How to build on Mylyn • Integration showcase • Extensions and ecosystem • Task-Focused Desktop

6. Task management • Before Mylyn • Scattered throughout web apps, code and pieces of paper • No integration with IDE workflow • One task list • Manage all your tasks in a single personalized view • Eclipse’s rich searching, linking and editing facilities • Repository connectors • Integrate web-based task repositories • Offline editing and access • Integrated change notifications • Demo

7. Task-focused UI • Information overload • Time wasted scrolling, browsing and searching, tagging, filtering • Constant multi-tasking causes context loss • Task context • Mylyn monitors your interaction • Creates degree-of-interest model • What you touch is in your context • Actively managed as you work • Task-focused UI • View filtering, element decoration • Automatic folding, content assist ranking • Editor and perspective management • One-click task switching • Demo

8. Collaboration • Before Mylyn • Manual management of change sets • Email overload, interruption, difficulty sharing expertise • Change set management • Changes are automatically grouped by task • Commit messages are automatic • Everything is linked • Task context sharing • Expertise is captured and can be shared via repository • Tasks are easy to recall, knowledge easy to share • Demo

9. Planning • With Mylyn • Too many tasks end up in your Task List • Personal planning • Meshes with team planning activities • Can monitor components and collaborations • Focused workweek • See only the tasks you need to work on • Demo

10. Mylyn 2.0 • Schedule • 2.0M3 May 11 • 2.0RC1 June 15 • 2.0 final June 29 with Europa • Even deeper integration • Debugging, XML, relationship navigation • More automation • Workflow, content assist, streamlining • Easier organization • Personal and team planning

11. Mylyn Framework

12. Mylyn Framework • Status • Mylyn 1.0 provided APIs that supported a core set of connectors • Mylyn 2.0 is evolving based on integrator feedback • APIs • Tasks: task management • Context: context management • Team: team provider integration • Monitor: workbench interaction monitoring

13. Tasks API • Goal • Bring your repositories’ tasks into Eclipse • Streamline task management user experience across repositories • Provide customizable behavior with consistent integration • Task repository connectors • Core facilities: lifecycle, persistence, synchronization • UI facilities: queries and task editing • Decide on level of integration: queries only, rich editing • Reference implementation is Bugzilla

14. Context API • Goal • Connect task context model to domain-specific artifacts • Task context bridges • Structure bridges: map context to existing models: e.g. JavaModel • UI bridges: selection/edit/refactoring capture, map to UI • Reference implementation is Java

15. Team & Monitor APIs • Team API • Provides change set integration, automatic commit messages • Reference implementation is CVS • Monitor API • Captures user’s workbench interaction history • Monitors views, editors, commands, preferences • Provides privacy, obfuscation, reporting • Reference implementation is user study example

16. Usage Reporting

17. Framework

18. Model • Interaction • Task context • Degree-of-interest (DOI) weighting • Frequency and recency of interaction with element • Both direct and indirect interaction interest

19. Topology • Task context graph • Edges added for relations between elements • Scaling factors determine shape, e.g. decay rate • Thresholds define interest levels • [l, ∞] Landmark • (0, ∞] Interesting • [-∞, 0] Uninteresting

20. Integration Showcase

21. Status IssueZilla CodeBeamer Tasks Context Team XPlanner Ruby JIRA Ant SVN Trac Java Bugzilla Files CVS Eclipse Mylyn

22. XPlannerConnector License: com.(JBuilder)Available: now

23. Project TrackerIssueZillaConnectors License: com. (free)Available: Q3

24. Agile Project Manager License: com. (free)Available: Q3

25. ChrisHane MantisConnector License: EPL(alpha)Available: now

26. Lubos Pochman CodeBeamerConnector License: free(alpha)Available: now

27. SubclipseTeam SVN TeamIntegration License: EPL(mature)Available: now

28. SubversiveSVN TeamIntegration License: EPL(mature)Available: now

29. DLTKStructure Bridge License: EPL(alpha)Available: Q3

30. Community needs … … ScrumWorks Tasks Context Team Tasktop Spring CodeBeamer … XPlanner Ruby ClearCase Email Perforce JIRA Ant SVN Web Trac Java Bugzilla Files CVS Desktop Eclipse Mylyn

31. Changing the way we work • Once tasks are explicit • Dramatic reduction in information overload • Information you need to get work done is at your finger tips • Multitasking and recalling old tasks become effortless • UI automation (e.g. working sets, search, commit messages) • Keeps you in Eclipse and out of your browser and inbox • Validated technology • Statistically significant increase in programmer productivity • Task context model supports generic knowledge work • The framework is open and growing • Mylyn is all about integration

32. Mylyn • Committers • Mik Kersten, Rob Elves, Steffen Pingel and Eugene Kuleshov • Key contributions by • Gail Murphy, Shawn Minto, Willian Mitsuda, Brock Janiczak, Meghan Allen, Nathan Hapke, Raphael Ackermann, Ken Sueda, Jeff Pound, Wesley Coelho and Leah Findlater The Task-Focused UI