It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,856

question asked: Apr 17 '12, 12:01 p.m.
question was seen: 5,506 times
last updated: Apr 17 '12, 12:01 p.m.

Related questions

RTC - EGL Development, source managment question

0
Ivan Bogovic (93●1●14●11) | asked Apr 17 '12, 12:01 p.m.
Hello,

we have issue with migrating one project (EGL) in RTC, project proprieties is like this:

- in RBD workspace its single project that is referenced by other projects
- it contains 40 packages
- on project simultaneity work 7 teams on different packages
- all packages under project have to be visible to everyone
- some packages can be changed only by certain teams

Its should be one single project area with 7 teams in RTC.
Is there a way we can implement this structure using RTC (using streams, components, ownership and visibility)
or can we somehow load different RTC components in same RBD project (loading packages not project), or we just have to create 7 RBD projects (last solution)?

Any suggestion is good.

Thanks, Ivan

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Kim Soederhamn (1.5k●3●43●48) | answered May 01 '12, 5:24 a.m.
Hello,

we have issue with migrating one project (EGL) in RTC, project proprieties is like this:

- in RBD workspace its single project that is referenced by other projects
- it contains 40 packages
- on project simultaneity work 7 teams on different packages
- all packages under project have to be visible to everyone
- some packages can be changed only by certain teams

Its should be one single project area with 7 teams in RTC.
Is there a way we can implement this structure using RTC (using streams, components, ownership and visibility)
or can we somehow load different RTC components in same RBD project (loading packages not project), or we just have to create 7 RBD projects (last solution)?

Any suggestion is good.

Thanks, Ivan


Hi Ivan, You are definitely on the right track. Create you 7 teams to keep their tasks separated. split your packages in 40 component or possibly fewer now you have the chance to clean up. Make specific teams owners of the components. The components is added to a stream everyone can see. Now the single components can only be modified by the owning team but everyone can see them and the content.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.