Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Mylyn/Activity Tracing For Mylyn"
(→Related Links) |
(→Related Links) |
||
| Line 38: | Line 38: | ||
[2] [http://wiki.eclipse.org/Mylyn/Contributor_Reference Mylyn Contributor Reference]<br> | [2] [http://wiki.eclipse.org/Mylyn/Contributor_Reference Mylyn Contributor Reference]<br> | ||
[3] [http://wiki.eclipse.org/Mylyn/User_Guide MyLyn User Guide]<br> | [3] [http://wiki.eclipse.org/Mylyn/User_Guide MyLyn User Guide]<br> | ||
| − | [4] [http://tasktop.com/blog/ Tasktop]<br> | + | [4] [http://tasktop.com/blog/ Tasktop Blog]<br> |
Revision as of 17:12, 24 April 2012
This is the wiki page for the GSOC2012 project Activity Tracing for Mylyn.
Student: Timur Achmetow
Mentor: Steffen Pingel
Bug ID: BUG 376233
About
The Mylyn task editor is the hub for task-focused collaboration. Yet, there are many other artifacts and activities that are part of the development workflow that are visualized in different views in the IDE. A unified activity view that aggregates tasks, builds, reviews and commits either in a dashboard or embedded in the task editor would nicely enhance traceability and visibility.
This additional data could show for example in the task editor or in a dashboard (new view). The new view helps the user to trace the selected tasks. One use case for this view could be, show the files, which are changed with the last commit. So the user have later the possibility to see, which files with this task are changed. Similar use cases are the build and review traces, who the user want see, if the selected task have an association with the build server task or a finished review task. So can die developer see, which changes have broken the build. With these additional data the task editor gets more connection to other developer tools.
Details
Implementation steps:
- Show the commit informations in a TableViewer, which is embedded in the task editor.
- Extend the Tableviewer for the additional build and review data. The TableViewer displays now all needed data.
- Embed the additional data in the comment stream (task editor).
- Optional: Dashboard, which aggregates data about several tasks.
Mookup
Architecture
Milestones
- M1 / May 01: Studying the documentation and existing code and prepare toolchain
- M2 / May, 20: Create a design and mockup
- M3 / July, 15: Mid term: Show commit information in task editor
- M4 / July, 30: Show builds and code reviews in the task editor
- M5 / August, 13: Embed activity data in the comment stream
- M6 / August, 20: Pencils down: Documentation complete
Related Links
[1] Mylyn Restructuring
[2] Mylyn Contributor Reference
[3] MyLyn User Guide
[4] Tasktop Blog