Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Mylyn/Restructuring/2015"

Line 42: Line 42:
 
== Plan of Actions ==
 
== Plan of Actions ==
  
=== 1. TFI ===
+
=== TFI ===
 
{|{{BMTableStyle}}
 
{|{{BMTableStyle}}
 
!Projects
 
!Projects
Line 90: Line 90:
  
  
=== 2. R4E ===
+
=== R4E ===
 
* The project will be archived
 
* The project will be archived
  
  
=== 3. Intent ===
+
=== Intent ===
 
{|{{BMTableStyle}}
 
{|{{BMTableStyle}}
 
!Projects
 
!Projects
Line 118: Line 118:
 
!Websites
 
!Websites
 
|
 
|
* eclipse.org/intent
+
* No change
 
|}
 
|}
  
=== 5. Wikitext ===
+
 
 +
=== VEX ===
 +
{|{{BMTableStyle}}
 +
!Projects
 +
|
 +
* Move from Mylyn Docs project into Mylyn Top Level project
 +
|-
 +
!Committer
 +
|
 +
* No changes
 +
|-
 +
!Git
 +
|
 +
* No changes
 +
|-
 +
!Bugzilla
 +
|
 +
* Rename "Mylyn Docs VEX" into "VEX"
 +
|-
 +
!Newsgroups & Forums
 +
|
 +
* No changes
 +
|-
 +
!Websites
 +
|
 +
* No change
 +
|}
 +
 
 +
 
 +
=== Wikitext ===
 
{|{{BMTableStyle}}
 
{|{{BMTableStyle}}
 
!Projects
 
!Projects

Revision as of 09:46, 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)


Explanations

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.

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 Mylyn 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.


Open Questions

  • Difference between Mylyn Top Level project and the "Mylyn" project?
    • Can the new Task Focused Interface project use the "Mylyn" Bugzilla product?
    • Can the new Task Focused Interface project use the /mylyn URL and namespace?

Plan of Actions

TFI

Projects
  • The following projects will be merged into the TFI project
    • Mylyn Builds
    • Mylyn Commons
    • Mylyn Context
    • Mylyn Reviews
    • Mylyn Tasks
    • Mylyn Versions
  • Scope: TBD
Committer
  • All committers will become committers of TFI
Git
  • All Git repositories will be made available under git.eclipse.org/c/mylyn
    • Actually, no relocation of any Git repo necessary.
  • Direct push will be disabled for all Git repositories, i.e. every commit has to go through Gerrit
  • Direct push will be granted to project leads
Bugzilla
  • The following separate products will be merged into the "Mylyn" product:
    • Mylyn Builds
    • Mylyn Commons
    • Mylyn Context
    • Mylyn Reviews
    • Mylyn Tasks
    • Mylyn Versions
Newsgroups & Forums
  • eclipse.tools.mylyn
    • Can eclipse.tools.mylyn be renamed to eclipse.mylyn?
  • Archive eclipse.builds
  • Archive eclipse.versions
Websites
  • All web content should go into eclipse.org/mylyn
  • Individual project websites will be deleted.


R4E

  • The project will be archived


Intent

Projects
  • Move from Mylyn Docs project into Mylyn Top Level project
Committer
  • No changes
Git
  • No changes
Bugzilla
  • Rename "Mylyn Docs Intent" into "Mylyn Intent"
Newsgroups & Forums
  • No changes
Websites
  • No change


VEX

Projects
  • Move from Mylyn Docs project into Mylyn Top Level project
Committer
  • No changes
Git
  • No changes
Bugzilla
  • Rename "Mylyn Docs VEX" into "VEX"
Newsgroups & Forums
  • No changes
Websites
  • No change


Wikitext

Projects
  • The Mylyn Docs project will be renamed to Wikitext
Committer
  • All committers stay the same
Git
Bugzilla
  • Rename Mylyn Docs into Wikitext
Newsgroups & Forums
  • eclipse.wikitext
Websites
  • eclipse.org/wikitext

Back to the top