Skip to main content
Jump to: navigation, search

Difference between revisions of "Mylyn/Activity Tracing For Mylyn"

(Milestones)
Line 22: Line 22:
 
[[Image:Mookup.png]]
 
[[Image:Mookup.png]]
  
== Architecture ==
+
== ToDos  ==
 +
 
 +
*extend the comment stream by additional informations: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=355974 BUG 355974]
 +
*Commits, builds, reviews
 +
 
 +
 
 +
*get the additional informations from the workspace:
 +
*task list, builds data model, EGit repo model
 +
 
 +
 
 +
*integrate a tableviewer in the comment stream
 +
*show the commit informations in the tableviewer
 +
*extend the tableviewer for additional build and review data
 +
*embed the additional data in the comment stream (task editor)
  
 
== Milestones  ==
 
== Milestones  ==

Revision as of 16:07, 26 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 / BUG 355974

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:

  1. Show the commit informations in a TableViewer, which is embedded in the task editor.
  2. Extend the Tableviewer for the additional build and review data. The TableViewer displays now all needed data.
  3. Embed the additional data in the comment stream (task editor).
  4. Optional: Dashboard, which aggregates data about several tasks.

Mookup

Mookup.png

ToDos

  • extend the comment stream by additional informations: BUG 355974
  • Commits, builds, reviews


  • get the additional informations from the workspace:
  • task list, builds data model, EGit repo model


  • integrate a tableviewer in the comment stream
  • show the commit informations in the tableviewer
  • extend the tableviewer for additional build and review data
  • embed the additional data in the comment stream (task editor)

Milestones

Milestone Date Items Status Bugzilla Entry
M1 May 01, 2012 Studying the documentation and existing code and prepare toolchain In Progress BUG 196788 BUG 187698
BUG 197924 BUG 198004
BUG 336298 BUG 340794
BUG 355973 BUG 355015
M2 May 20, 2012 Create a design and mockup In Progress N/A
M3 July 15, 2012 Mid term: Show commit information in task editor TBD N/A
M4 July 30, 2012 Show builds and code reviews in the task editor TBD N/A
M5 August 13, 2012 Embed activity data in the comment stream TBD N/A
M6 August 20, 2012 Pencils down: Documentation complete TBD N/A

Related Links

[1] Mylyn Restructuring
[2] Mylyn Contributor Reference
[3] Mylyn User Guide
[4] Tasktop Blog

Back to the top