James will discuss the considerations that go into onboarding a new open source component into a software product, including evaluating: the license and other legal considerations; the health and sustainability of the open source community around the project; and what support options are available (and desirable) depending on the use case.

• Compliance
• Context: what is the code going to be used for (internal use, distribution,..)
• Health-assessment of an OS Project:
  • Look at bug tracker. The more issues, the better.
  • Responsiveness to issues. The faster, the better.
  • Code release frequency. The higher, the better
• Support plan. Understanding whether your project can support the plan you've defined in your procurement steps.

Meeting minute review: the meeting minutes for 7/24, 6/19, 6/5 OSR meetings were approved.