I always recommend to start with the simplest structure, and then extend
it only when you have a specific reason to do so.

So this would suggest starting with a single project area, and then
create team areas within that project area for each group of people for
whom you'd like a separate "plan".

For importing your MKS source, the simplest is to just copy the tip of
your main branch into the file system, and then put that under RTC
source control. If you want history, or if you have multiple branches,
then you'll probably want to use an MKS->Subversion importer, and then
use the RTC Subversion importer.

Cheers,
Geoff

On 2/16/2011 4:38 AM, praveennilam wrote:

Hi all,

Please suggest a way to manage the exisiting MKS structure to RTC.

MKS Structure:
-->We have more than hundred projects
in MKS and these are categorized w.r.t groups. For Ex, Group A is
responsibel for some projects, group B is responsible for another set
of projects and so on.

-->We treat all these projects as a
single product and we maintaind releases for that product. For this
we build each project when neccessary, and release that product.

RTC Structure:

Now, we want to migrate all source of all projects into RTC and we
have two options like

First, Having all the projects under
one stream. And create different streams with some of the
projects from above stream and
allow the responsible group to manage the stream. This is for one
group and do the same for other project groups. Finally in this
scenario, we will have atleast 6 streams, one for all projects and 5
for each group.

Second, Having different project areas
for each group and each group has a stream with responsible
projects.

Questions:

1. Which one is the better approach to migrate?
2. Is there another way of migrating source, in this scenario?
3. are there any issues while building so many components?

Any suggestions or ideas..plz share with me.

Thanks in advance.