Community
Participate
Working Groups
Proposed structure, in alphabetical order. Note that our approach has been to make the feature naming as complete (ie, redundant) as possible so that users don't get confused when uninstalling a single feature. The only name prefix that we skip is "Eclipse". h3. Mylyn Features * Mylyn Builds (Incubation) * Mylyn EGit (Incubation) * Mylyn Reviews (Incubation) * Mylyn Task List * Mylyn Task-Focused Interface * Mylyn WikiText h3. Mylyn Connectors * Mylyn Builds Connector: Hudson (Incubation) * Mylyn Context Connector: C/C++ Development * Mylyn Context Connector: Eclipse IDE * Mylyn Context Connector: Java Development * Mylyn Context Connector: Plug-in Development * Mylyn Reviews Connector: Gerrit (Incubation) * Mylyn Tasks Connector: Bugzilla * Mylyn Tasks Connector: Trac * Mylyn Versions Connector: CVS * Mylyn Versions Connector: Git (Incubation) h3. Mylyn Frameworks & SDKs (formerly Mylyn Plug-in Development) * Mylyn Builds SDK * Mylyn Commons SDK * Mylyn Docs SDK * Mylyn EGit SDK (Incubation) * Mylyn JGit SDK (Incubation) * Mylyn Reviews SDK * Mylyn Tasks SDK * Mylyn Versions SDK h3. Mylyn Incubator * Mylyn Reviews: R4E (Incubation) * Mylyn Reviews: Task-Based Reviews(Incubation)
*** Bug 336285 has been marked as a duplicate of this bug. ***
This looks good to me. Additionally, Frameworks & SDK would end up with Mylyn Context SDK. The only thing that I find a bit confusing is the name of the "Mylyn Incubator" category. The listed features are not part of the Mylyn Incubator project and other Incubating features are listed in categories not marked Incubation so it's hard to see where the split is. How about "Mylyn Extra Connectors"? As outlined in bug 317913#c7 I would like to keep the actual Mylyn Incubator features on an entirely separate update site like we have done in the past.
The other thing we need to be think through is the names of "Eclipse EGit" changing to "Mylyn EGit". I'm happy with whatever the EGit/JGit teams want here, I don't think it needs to be perfectly consistent, but I wrote it up that way and think that the list under "Mylyn Features" makes it clear what Mylyn has become.
Created attachment 189771 [details] screen shot
I have updated the categories and feature names as shown in the screenshot. I made some adjustments to the original proposal to maintain the current sort order of categories: Mylyn Features, Mylyn Integrations, Mylyn SDKs and Frameworks. For now the Builds and Reviews framework features are listed in the SDK category. These features are not useful unless a connector is installed and I don't want users to easily get into a scenario where they have an empty Builds view and no easy way to get the Hudson integration. I would suggest that we move the features to the top category once we have a proper discovery integration that supports simple installation of connectors. R4E and TBR are not yet included (see http://dev.eclipse.org/mhonarc/lists/mylyn-reviews-dev/msg00357.html).
One more thing: The Commons, Context and Tasks SDKs are not yet available as separate features but all combined in the Mylyn SDK.
Steffen: Looks good. I wonder if we should take off the "(Required)" and "(Recommended)" tags.
Thanks for the feedback. I have removed the "Required" and "Recommended" qualifiers. We can reconsider if this turns out to confuse users.
