Ask HN: How does your company manage OSS use and licensing?
My company is currently forcing all developers across multiple teams to submit new open source components to the OSS "committee" which yays or nays requests and adds approved OSS to internal repository. The obvious issues here is that while it benefits Legal, it's too bureaucratic and intrusive and nobody has the time to make sure the repository stays up-to-date. A simple request can take up to a week to approve and adding a new open source component feels like committing a sin.
What process do you have in place to manage open source bits used in your code base so that each product release ships with appropriate licensing terms?
This post does not have any comments yet