Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Mylyn/Restructuring/2015
This page described the process of simplifying the Mylyn project structure. Basically, all projects will be grouped below the Mylyn top-level project. The new structure becomes flat. Projects with overlapping committers should be merged into one (where possible).
Contents
Proposed Structure
- Mylyn (unifies Builds, Commons, Context, Reviews, Tasks, and Versions)
- Mylyn Incubator (as it is today)
- EPUB (extracted from Docs)
- Wikitext (renamed Docs)
- VEX (move out of Docs)
Candidates for archival
- R4E
- HTMLText (from Docs)
- Model Focusing Tools (move out of sub-structure)
- Intent (from Docs)?
Explanations
Mylyn
The most significant simplification is the merge of a lot sub-projects projects into Mylyn. This should greatly reduce the release overhead. They are all developed and released together today anyway.
Docs
Although being declared as the "home" for documentation related projects at Eclipse.org, it currently servers two purposes: 1) parent for documentation related projects and 2) home for Wikitext, Htmltext and ePub. The overhead of maintaining a separate project just for having a "home" for documentation related projects feels wrong. The Lifecycle Tools project is about ALM and any software documentation related project is welcome in there. We really shouldn't maintain a separate parent project. There is no need for sub-projects to hide behind such an umbrella project.
Wikitext
Wikitext demonstrated that it's a successful project on its own with a vibrant community. It's used as a separate library and tool. Thus, it really should be a separate project that can produce releases on it's own.
R4E
It seems that R4E didn't manage to build an active and vibrant community. Code reviews are really successful at GitHub or in Gerrit. Mylyn Reviews integrates very well with Gerrit. R4E should be archived.
ePub
It's actually not a project but a component within Docs. However, it's not really clear who uses it actively. We should either archive it or discuss with the committers where to put it best.
Htmltext
Also a component within Docs. It's not mature enough to be a separate project. We should either move it back to the Incubator or archive it.
Model Focusing Tool
It seems that MFT is not actively maintained anymore. MFT should be archived.
Plan of Actions
Mylyn
Projects |
|
---|---|
Committer |
|
Git |
|
Bugzilla |
|
Newsgroups & Forums |
|
Websites |
|
R4E
- Archive the R4E project.
Intent
- Archive the Intent project? (https://dev.eclipse.org/mhonarc/lists/mylyn-intent-dev/msg00024.html)
Projects |
|
---|---|
Committer |
|
Git |
|
Bugzilla |
|
Newsgroups & Forums |
|
Websites |
|
VEX
Projects |
|
---|---|
Committer |
|
Git |
|
Bugzilla |
|
Newsgroups & Forums |
|
Websites |
|
EPUB
Projects |
|
---|---|
Committer |
|
Git |
|
Bugzilla |
|
Newsgroups & Forums |
|
Websites |
|
Wikitext
Projects |
|
---|---|
Committer |
(obtained via git shortlog --since=1.year) |
Git |
|
Bugzilla |
|
Newsgroups & Forums |
|
Websites |
|
MFT
- Archive the MFT project.