sorry for the slow response. The are still some uncertainties what the actual structure of the Mylyn project will end up being but I have pasted my suggestions below.
1) We would like to track our activities using Mylyn Reviews Bugzilla,
- Can we assume that the Bugs/ Tasks related to Mylyn Reviews framework can be raised under Eclipse.org bugzilla (Tools-> Mylyn Reviews -> core component) ?
Mario, should be able to create an R4E component in Bugzilla under Mylyn.Reviews. For now I would just tag them as [r4e] in the summary. Once the component is in place or a separate project is create you can easily move the bugs.
2) For the R4E open source related tasks, can we get R4E defined as a new component under Mylyn Reviews ?
See above :).
2.1) Is it the right time to re-define the component structure to include Framework, Task Base Reviews, R4E and Gerrit ?
+1
3) The proposed data model for the mylyn reviews framework and other code is currently stored in our own local Git repository, We would like to commit it under Mylyn Reivews repository under Eclipse.org, what would be the next steps to get this code committed ?
An existing committer would need to initiate a nomination. This can be done at any point, all that is required for the nominee is a Bugzilla account. Since the Reviews project already exists I think it makes sense to go ahead with that. The alternative would be to do this as part of the restructuring but I don't see a good reason to wait for that.
Steffen
