Sharing source code across Project Areas with restricted access
If two project areas in RTC require source code to be shared, I understand one project area will 'own' the stream/component and the other can access it. If we want this code to have limited visibility due to it's IP, how can this be done? Do we setup user access groups and make them visible to the appropriate user groups?
When we are setting up these project areas/teams, is there best practiced to determine when a project area should have multiple teams (in order to share code) versus create separate project areas (and hopefully be able to use these user access groups).
|
One answer
Geoffrey Clemm (30.1k●3●30●35)
| answered May 09 '17, 4:49 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER From a technical perspective, it doesn't matter whether you use project areas, team areas, or access group lists to specify read access to a component/stream. The only difference is how much work it is to maintain the access information. If you have an existing project or team area whose membership determines "who should have read access to this component/stream", then it is easiest to just have that be the owner of the component/stream, and then whenever you modify the membership of the project/team area, it is immediately reflected in who has read access to the component/stream. But if there is no such existing project or team area, it is probably simplest to just create an access group list to define who should have read access.
|
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.