Earlier quoted context omitted.
There is no compliance reason why OP couldn't have read access to look at the source. If there is a compliance issue with someone looking at source, then either (a) their source control is misconfigured, (b) their source control is being misused, or (c) they have no policy to guarantee appropriate use and detect improper use. Any organization that uses compliance as an excuse for opaqueness, creating silos, and guard…
> * There is no compliance reason why OP couldn't have read access to look at the source.* At a guess, I would say you have never worked with DRM integration. Getting access even to the binary SDK's can take months, and if you ever need the special license to work with the thing on source code level, prepare for a delay of several quarters. Long time ago, Nokia was integrating Microsoft's DRM. I got to witness first…
Thankfully, it was an optional side project at work, so I was able to step away and make more progress elsewhere.
But it also substantially reinforced my opinion that... if you need to keep a codebase secret... it's probably not a good thing.
And yes, I realize it is sadly endemic in the embedded world, for reasons both good (firmware secrets) and bad (artificial moats and controlling integration and compatibility).