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/Restructuring/2015"
< Mylyn | Restructuring
m (→Proposed Structure) |
(→Proposed Structure) |
||
| Line 9: | Line 9: | ||
* Model Focusing Tools (move out of sub-structure) | * Model Focusing Tools (move out of sub-structure) | ||
| − | + | ==== Candidates for archival ==== | |
* R4E | * R4E | ||
* ePub (from Docs) | * ePub (from Docs) | ||
* HTMLText (from Docs) | * HTMLText (from Docs) | ||
| − | The most significant simplification is the merge of a lot projects into TFI. This should greatly reduce the release overhead. They are all developed and released together today anyway. However, separate documentation must be prepared given the old structure. | + | |
| + | == Discussion == | ||
| + | '''Task Focused Interface'''<br> | ||
| + | The most significant simplification is the merge of a lot projects into TFI. This should greatly reduce the release overhead. They are all developed and released together today anyway. There is a significant However, separate documentation must be prepared given the old structure. | ||
Revision as of 06:48, 10 December 2013
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).
Proposed Structure
- Task Focused Interface (unifies Builds, Commons, Context, Reviews, Tasks, and Versions)
- Wikitext (extracted from Docs)
- Intent (move out of docs)
- VEX (move out of docs)
- Incubator (as it is today)
- Model Focusing Tools (move out of sub-structure)
Candidates for archival
- R4E
- ePub (from Docs)
- HTMLText (from Docs)
Discussion
Task Focused Interface
The most significant simplification is the merge of a lot projects into TFI. This should greatly reduce the release overhead. They are all developed and released together today anyway. There is a significant However, separate documentation must be prepared given the old structure.