The component needs to be able to say who has read access to that
component. But any stream that has read access to component should be
able to decide/control whether that stream can create a branch of a
component (i.e. have "write access" to that component).

A "component" effectively is there to keep track of all the "copies"
(branches) of the component that have been made in different streams, so
that it can help you "merge" changes from one of those copies to
another. If you tried to control in a component who would create a
branch of that component, all you are doing is forcing someone to make a
copy of that component in some new component, which would mean that the
SCM system could no longer help you with merging changes between those
copies.

Cheers,
Geoff

eanderso wrote:

Is there a way to restrict component write when the component is owned
by a project but doesn't belong to a stream in that project* (the
component is used in a stream from a different project)?

* - this special purpose project is intended to manage source access
(compartments) and I control the process configuration. I don't
control the process configuration of the other project.

I haven't found a way to support read only access to components in
this project. Any ideas?