The proposal looks good to me in general. I have some specific comments on the components, but those can wait until were finalizing the details on a Bugzilla bug.
High level, Im wondering whether the key framework projects should be their own products, rather than being components of things like Mylyn Versions. Specifically, at the outset, it seems that at least EGit and JGit should remain independent products in Bugzilla, as per our differentiation in branding between Framework Projects (eg, Mylyn Versions) and Tools Projects (eg, JGit) which, unlike the framework projects, dont need to be prefixed by Mylyn for their branding.
Mik
--
Dr. Mik Kersten Tasktop CEO, Mylyn Lead, http://twitter.com/mik_kersten
Assistant: zoe.jong@xxxxxxxxxxx, +1-778-588-6896, Skype: zoe.e.jong
To follow up on the discussion on the call today, here is my proposal for restructuring the Bugzilla components and product to reflect the new Mylyn top-level project structure as outlined in http://wiki.eclipse.org/Mylyn/Restructuring .
I propose that each sub-project gets its own product in Bugzilla. This allows each project to define its own components and versions and evolve and plan separately from other sub-projects. It should also work well in terms of using the automatic IP log to track contributions.
The Mylyn product would provide an inbox for users who are unsure where to file a specific bug and a place to track administrative tasks. I suggest that we create the following products and components :
Mylyn * Inbox, Releng, Website
Mylyn Commons * Identity, Monitor, Repositories, Notifications, UI
Mylyn Context * Java, C/C++, Framework, PDE, Resources
Mylyn Docs * WikiText, HtmlText
Mylyn Incubator * Usage Monitor, UI Experiments, Web Templates, WikiText Sandbox
Mylyn Reviews * Framework, Gerrit, R4E, SCM, Tasks
Mylyn Tasks * Bugzilla, Framework, OSLC, Trac
Mylyn Versions * CVS, Framework, EGit, OSLC
|