I'm not sure if this question makes sense here although in my point of view it does. Otherwise I would be happy to post it in the right SO.
I would like to rise a few scenarios concerning licensing obligations under the perspective of components and libraries usages. I will not talk about code language or package management but how would be the best (or close enough to it) approach to fulfill the component licensing obligations.
Below I will describe a few usage scenarios and I would like to get your feedback/answer how to deal with the obligations.
1) An internal team XPTO developed a component using an open-source component who obligates who use it to open their code publicly. Other teams from this same company are using this component in final projects that will be published in online stores. Question: Who must to open their source code? The internal component from XPTO team or the projects from other teams?
2) An internal team XYZ developed a back-end REST API based on an open-source framework who demands the usage projects to make a quote about this framework in the about view. This REST API has no friendly interface once is consume exclusively by a project who will be publish in an online store. Question: How to properly quote this framework? In an static land-page for the REST API if accessed by browser? In the about of the project consumer?
In short I would like to know how far the responsibility of the obligations would be scaled to the usage projects.