Mylyn Project Restructuring Proposal
This document describes a proposed restructuring of the Eclipse Mylyn
project. We solicit
additional participation and input from the Eclipse community.
Please send all feedback and requests for participation, by April
5th, to the
mylyn-dev mailing list or indicate interest in
participation by
submitting a Bugzilla report.
Background
Since its 1.0 release in
December of 2006, Mylyn has grown to become the task and
application lifecycle management (ALM) integration framework for
Eclipse. Mylyn provides:
- A task management
tool for developers
- A broad ecosystem of
Agile and ALM integrations
- The revolutionary
task-focused interface
Due to the growing adoption
of Mylyn’s frameworks, we are planning to restructure the project
around its API boundaries for key components such as Tasks and
Context. The goal of the proposed sub-projects is to address the
growth of Mylyn by creating sub-projects for the components, and to
solicit additional participation from ISVs and other stakeholders in
the new sub-projects.
Overview
We expect the following
structure and participation to evolve while the restructuring is in
the proposal phase. "Reference Tools" are open source ALM tools
used for reference implementations of the corresponding Mylyn
sub-project APIs. The "Reference Standard" implementation is
for the Open Services for Lifecycle Collaboration (OSLC)
REST APIs for ALM.
|
Project |
Summary |
Reference Tools |
Reference Standards |
|
Tasks |
Change, issue, defect and user story
management |
Bugzilla, Trac
|
OSLC-CM |
|
Context |
Context management and task focus |
JDT, CDT |
|
|
SCM |
Source code and configuration management |
CVS, EGit
|
OSLC-SCM |
|
Build |
Build, release and continuous integration |
Hudson |
OSLC-Automation |
|
Review |
Collaborative code review |
n/a |
|
|
Docs |
Documentation and requirements |
WikiText |
|
|
Commons |
Rich client, REST and WS utilities |
n/a |
|
Compatibility
Binary compatibility with existing Mylyn
3.x releases will be retained under the restructuring.
Projects
Mylyn
Mylyn project and
committers remain unchanged (see
Mylyn Contributors), with Mik Kersten as the project lead. This project
will no longer contain source code, all of which will move into sub-projects. The proposed sub-projects and their committers are listed
below. Committers not currently on the Eclipse Mylyn project are
described. The sub-projects will
actively support interested parties earning commit rights.
Mylyn/Tasks
The scope of this project is integration with Agile, issue,
bug and defect tracking servers. The project provides rich task editing, task
list management and offline synchronization for ALM servers. The Tasks project
is the central portion of the ALM integration framework used by Mylyn.
Individuals listed as "New Contributors" have stated their intersted in
contributing to the project.
Existing Committers
- Steffen Pingel, Lead (Tasktop)
- Shawn Minto (Tasktop)
- Robert Elves (Tasktop)
- Mik Kersten (Tasktop)
- Frank Becker (individual)
New Contributors
-
Mark
Ringer (Rally Software, goal is to help drive support for
Agile in Mylyn and server side interoperability)
Mylyn/Context
The scope of this project is the implementation of usage
monitoring, degree-of-interested modeling and the
task-focused interface
implementation for Eclipse, which re-aligns the IDE
user interface around tasks and provides features such as workspace focusing and
one-click multitasking.
Existing Committers
- Shawn Minto, Lead (Tasktop)
- Steffen Pingel (Tasktop)
- Robert Elves (Tasktop)
- Mik Kersten (Tasktop)
Mylyn/SCM
The scope of this project is Eclipse integration for source
code and configuration management tools and bi-directional linking to change
management tools. This project and APIs it provides builds on the existing
Eclipse "Team" APIs.
Existing Committers
- Robert Elves (Tasktop)
- Steffen Pingel (Tasktop)
- Mik Kersten (Tasktop)
New Contributors
- Kevin Sawicki (Perforce, goal is to help drive Mylyn framework changes for support of
advanced SCM features)
Mylyn/Build
The scope of this project is Eclipse integration of
continuous integration and build systems. This is a new project that includes
existing Eclipse.org committers who will collaborate on extending Mylyn’s build
system APIs.
Existing Committers
- Steffen Pingel (Tasktop)
- David Green, Lead (individual)
New Contributors
- Henrik Lindberg (Cloudsmith,
Eclipse B3 committer)
- Thomas Hallgren (Cloudsmith,
Eclipse B3 committer)
- Michal Ruzicka (Cloudsmith,
Eclipse B3 committer)
- David Shepherd (Tasktop, created Tasktop’s existing build and CI system APIs)
Mylyn/Review (Incubation)
The scope of this project is to provide Eclipse-based code
review functionality that’s seamlessly integrated with the Tasks and SCM systems
supported by Mylyn.
Committers
- Mario Bernhart, Lead (INSO)
- Christoph Mayerhofer (INSO)
- Kilian Matt (INSO)
- Stefan Strobl (INSO)
Mylyn/Docs
The scope of this project is Eclipse-based access to
documentation systems such as Wikis and other portals. This builds on the Mylyn
WikiText framework.
Committers
- David Green, Lead (individual)
- Robert Elves (Tasktop)
Mylyn/Commons
The scope of this project is to provide a framework of
common UI, web service, REST and test utilities to be used by the
rest of Mylyn and by other Eclipse-based tools.
Committers
- Steffen Pingel, Lead (Tasktop)
- Shawn Minto (Tasktop)
- Mik Kersten (Tasktop)
- Robert Elves (Tasktop)
Mylyn/Incubator (Incubation)
The scope of this
project is to provide an place for experimentation. This will subsume the
existing
Mylyn Sandbox. All
committers granted commit rights.
Interested Parties
-
AccuRev
-
Atlassian
-
Cloudsmith
-
CollabNet
-
HP
-
IBM
-
Microsoft
-
Perforce
-
Polarion
-
Rally Software
-
SpringSource, a division of VMware
-
Tasktop
-
ThoughtWorks
Studios
-
VersionOne
-
Zend