Reading an earlier question I asked about restricting developers from delivering to a stream :
Stop changes being delivered to a stream – RTC source control
I think a solution to this is to create a new team area with just the developers that are required ownership of the stream. Change the ownership of the stream to this newly created team area. The developers of the newly created team area will then be only developers that can deliver to this stream. Will the developers that are no longer members of the team ownded by stream still be able to view the stream and its change sets ?
Is this good practice ?
Will the developers that are no longer members of the team ownded by stream still be able to view the stream and its change sets ?
Yes. (unless, with RTC4, you set read access preventing others to read the content of your stream).
Is this good practice ?
Yes, although I am using it on an “integration” stream in order for an “integration” team to accept changes from other stream.
See for example “Restrict user access at component level within a stream“.
In other word, I don’t restrict deliver team by team, for every stream.
I restrict deliver only for certain key stream, and make sure only the team in charge of that stream can accept changes from any other stream, allowing said team to control exactly what is landing in their stream.