Create ADOPTERS.md (#126)

ADOPTERS.md

@@ -0,0 +1,18 @@
+# Score Adopters
+
+This is the list of organizations and users that have publicly shared how they are using Score.
+
+💡 **Want to add your organization? Please [create a PR to add your organization in the list below](https://github.com/score-spec/spec/edit/main/ADOPTERS.md).**
+
+_Note: There are several other organizations and users that are unable to publicly share their stories yet but are active in the Score community. We appreciate all our users and their contributions to make Score a successful CNCF project._
+
+The list of organizations that have publicly shared the usage of Score:
+
+| Organization                        | Success Story |
+|:------------------------------------|---------------|
+| [Bechtle](https://www.bechtle.com/) | Internal and external Developers use the Score `spec` to define the containerized workloads and their dependencies, and deploy them to Bechtle's IDP via the [Humanitec's Score implementation (`humctl`)](https://humanitec.com/products/score). |
+| [Convera](https://convera.com/)     | Enable Developers to choose their preferred level of abstractions for optimal developer self-service and productivity by using the Score `spec` for all their microservices, and deploy them via the [Humanitec's Score implementation (`humctl`)](https://humanitec.com/products/score). |
+| [Humanitec](https://humanitec.com)  | Use the Score `spec` to define all the containerized workloads and their dependencies of the SaaS product. [`score-compose`](https://docs.score.dev/docs/score-implementation/score-compose/) is used to run integration tests locally and in the CI pipelines with Docker Compose. Score files are deployed via the [Humanitec's Score implementation (`humctl`)](https://humanitec.com/products/score). |
+<!-- append the line below to the table
+| [name](URL) | brief description of how you are using Score |
+-->