Merge branch 'add-evaluating-open-source' into 'master'

Add evaluating open source software to product

Closes Product#639

See merge request gitlab-com/www-gitlab-com!36940

source/handbook/product/index.html.md.erb

@@ -1474,6 +1474,7 @@ Buyer
 - [Chorus transcriptions](/handbook/business-ops/tech-stack/#chorus) of sales calls and demos
 - Reviewing Customer Success [designated top issues](/handbook/customer-success/tam/cs-top-10)
 - Maintaining [competitive](/handbook/marketing/product-marketing/competitive/) and [market assessments](#analyst-engagement) as well as missing [features](/features/) in your category epics (competitive landscape section). Subscribing to your competitor's blogs to be aware of what they are releasing will help you here.
+- Tracking open source projects in the same space as part of your competitive analysis is important as well. You can [evaluate these open source options](#evaluating-open-source-software) not just for interesting features and ideas, but potentially to integrate them in our product.
 Internal
 - Leadership [OKRs](/company/okrs) set the direction for the company
@@ -2352,7 +2353,7 @@ As a result, the [Ops](/handbook/product/categories/#ops-section) and [CI/CD](/h
 As a Product Manager you may need to make a decision on whether GitLab should engineer a solution to a particular problem, or use off the shelf software to address the need.
 First, consider whether our users share a similar need and if it's part of GitLab's scope. If so, strongly consider [building as a feature in GitLab](/handbook/product/#dogfood-everything):
-* Evaluate if there is [compatible open source software](https://docs.gitlab.com/ee/development/licensing.html#acceptable-licenses) which could accelerate delivery.
+* [Evaluate open source options](#evaluating-open-source-software) to utilize.
 * If time to market is an issue, a [global optimization issue](/handbook/product/#prioritize-global) may also be opened to assist with prioritization.
 * For a potential acquisition, follow the [acquisition process](/handbook/acquisitions/acquisition-process/).
@@ -2366,6 +2367,14 @@ If after evaluating these considerations buying a commercial solution is the bes
 1. Consider [who owns the outcome](/handbook/finance/#how-spend-is-allocated-to-departments), as the spend will be allocated to their department. Get their approval on the proposed plan.
 1. Have the owning party [open a finance issue](https://gitlab.com/gitlab-com/finance/issues/new) using the `vendor_contracts` template, ensure the justification above is included in the request.
+#### Evaluating Open Source Software
+
+When considering open source software in build vs. "buy" decisions we utilize the following general criteria to decide whether to integrate a piece of software:
+* **Compatibility** - Does the software utilize a [compatible open source license](https://docs.gitlab.com/ee/development/licensing.html#acceptable-licenses)?
+* **Viability** - Is the software, in its current state, viable for the use case in question? 
+* **Velocity** - Is there a high rate of iteration with the software? Are new features or enhancements proposed and completed quickly? Are security patches applied regularly?
+* **Community** - Is there a diverse community contributing to the software? Is the software governed by broader communities or by a singular corporate entity? Do maintainers regularly address feedback from the community?
+
 ## GitLab as a Product
 ### Single application