chore: add missing OSS compliance files @W-24528552@

CODEOWNERS

@@ -3,3 +3,5 @@
 
 # Comment line immediately above ownership line is reserved for related other information. Please be careful while editing.
 #ECCN:Open Source
+#GUSINFO:Platform CLI,Platform CLI
+* @salesforcecli/cli

CODE_OF_CONDUCT.md

@@ -0,0 +1,105 @@
+# Salesforce Open Source Community Code of Conduct
+
+## About the Code of Conduct
+
+Equality is a core value at Salesforce. We believe a diverse and inclusive
+community fosters innovation and creativity, and are committed to building a
+culture where everyone feels included.
+
+Salesforce open-source projects are committed to providing a friendly, safe, and
+welcoming environment for all, regardless of gender identity and expression,
+sexual orientation, disability, physical appearance, body size, ethnicity, nationality,
+race, age, religion, level of experience, education, socioeconomic status, or
+other similar personal characteristics.
+
+The goal of this code of conduct is to specify a baseline standard of behavior so
+that people with different social values and communication styles can work
+together effectively, productively, and respectfully in our open source community.
+It also establishes a mechanism for reporting issues and resolving conflicts.
+
+All questions and reports of abusive, harassing, or otherwise unacceptable behavior
+in a Salesforce open-source project may be reported by contacting the Salesforce
+Open Source Conduct Committee at [email protected].
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of gender
+identity and expression, sexual orientation, disability, physical appearance,
+body size, ethnicity, nationality, race, age, religion, level of experience, education,
+socioeconomic status, or other similar personal characteristics.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy toward other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Personal attacks, insulting/derogatory comments, or trolling
+- Public or private harassment
+- Publishing, or threatening to publish, others' private information—such as
+  a physical or electronic address—without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+- Advocating for or encouraging any of the above behaviors
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned with this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project email
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the Salesforce Open Source Conduct Committee
+at [email protected]. All complaints will be reviewed and investigated
+and will result in a response that is deemed necessary and appropriate to the
+circumstances. The committee is obligated to maintain confidentiality with
+regard to the reporter of an incident. Further details of specific enforcement
+policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership and the Salesforce Open Source Conduct
+Committee.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][contributor-covenant-home],
+version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html.
+It includes adaptions and additions from [Go Community Code of Conduct][golang-coc],
+[CNCF Code of Conduct][cncf-coc], and [Microsoft Open Source Code of Conduct][microsoft-coc].
+
+This Code of Conduct is licensed under the [Creative Commons Attribution 3.0 License][cc-by-3-us].
+
+[contributor-covenant-home]: https://www.contributor-covenant.org 'https://www.contributor-covenant.org/'
+[golang-coc]: https://golang.org/conduct
+[cncf-coc]: https://github.com/cncf/foundation/blob/master/code-of-conduct.md
+[microsoft-coc]: https://opensource.microsoft.com/codeofconduct/
+[cc-by-3-us]: https://creativecommons.org/licenses/by/3.0/us/

CONTRIBUTING.md

@@ -0,0 +1,42 @@
+## Contributing
+
+1. The [DEVELOPING](DEVELOPING.md) doc has details on how to set up your environment.
+1. Create a new issue before starting your project so that we can keep track of
+   what you are trying to add/fix. That way, we can also offer suggestions or
+   let you know if there is already an effort in progress.
+1. Fork this repository (external contributors) or branch off main (committers).
+1. Create a _topic_ branch in your fork based on the main branch. Note, this step is recommended but technically not required if contributing using a fork.
+1. Edit the code in your fork/branch.
+1. Write appropriate tests for your changes. Try to achieve at least 95% code coverage on any new code. No pull request will be accepted without associated tests.
+1. Sign CLA (see [CLA](#cla) below).
+1. Send us a pull request when you are done. We'll review your code, suggest any
+   needed changes, and merge it in.
+1. Upon merge, a new release of the `@salesforce/plugin-command-reference` plugin will be published to npmjs with a version bump corresponding to the [conventional commit spec](https://www.conventionalcommits.org/en/v1.0.0/).
+   - To increase the patch version, make sure that at least 1 commit message starts with "fix:"
+   - To increase the minor version, make sure that at least 1 commit message starts with "feat:"
+   - To bump the major version, please work with the CLI team.
+
+### CLA
+
+External contributors will be required to sign a Contributor's License
+Agreement. You can do so by going to https://cla.salesforce.com/sign-cla.
+
+## Branches
+
+- We work in branches off of `main`.
+- Our released (aka. _production_) branch is `main`.
+- Our work happens in _topic_ branches (feature and/or bug-fix).
+  - feature as well as bug-fix branches are based on `main`
+  - branches _should_ be kept up-to-date using `rebase`
+  - [commit messages are enforced](DEVELOPING.md#When-you-are-ready-to-commit)
+
+## Pull Requests
+
+- Develop features and bug fixes in _topic_ branches off main, or forks.
+- _Topic_ branches can live in forks (external contributors) or within this repository (committers).
+  \*\* When creating _topic_ branches in this repository please prefix with `<initials>/`.
+- PRs will be reviewed and merged by committers.
+
+## Releasing
+
+- A new version of this plugin (`@salesforce/plugin-command-reference`) will be published upon merging PRs to `main`, with the version number increment based on commitizen rules.

DEVELOPING.md

@@ -0,0 +1,112 @@
+# Developing
+
+## Table of Contents
+
+[One-time Setup](#one-time-setup)</br>
+[Quick Start](#quick-start)</br>
+[Testing](#testing)</br>
+[Debugging](#debugging)</br>
+[Running Commands](#running-commands)</br>
+[When you are ready to commit](#When-you-are-ready-to-commit)</br>
+[Useful Yarn Commands](#useful-yarn-commands)</br>
+
+<hr>
+
+## One-time Setup
+
+1.  Install NodeJS. If you need to work with multiple versions of Node, you
+    might consider using [nvm](https://github.com/creationix/nvm). </br>_Suggestion: use the current [LTS version of node](https://github.com/nodejs/release#release-schedule)._
+1.  Install [yarn](https://yarnpkg.com/) to manage node dependencies. </br>_Suggestion: install yarn globally using `npm install --global yarn`_
+1.  Clone this repository from git. E.g., (ssh): </br>`git clone [email protected]:salesforcecli/plugin-command-reference.git`
+1.  Configure [git commit signing](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits).
+
+## Quick Start
+
+1.  `cd` into the `plugin-command-reference` directory
+1.  Checkout the main branch: `git checkout main`
+1.  Get all latest changes: `git pull`
+1.  Download NPM dependencies: `yarn install`. If it's been a while since you last did this you may want to run `yarn clean-all` before this step.
+1.  Build and lint the code: `yarn build`
+1.  Create a branch off main for new work: `git checkout -b <branch_name>` _Suggestion: use branch_name format of initials/work-title_. For external contributors, please fork the main branch of the repo instead and PR the fork to the main branch.
+1.  Make code changes and build: `yarn build`
+1.  Run changed commands: e.g., `./bin/run.js <command> -h`
+1.  Write tests and run: `yarn test` (unit) and/or `yarn test:nuts` (NUTs)
+1.  Show all changed files: `git status`
+1.  Add all files to staging: `git add .`
+1.  Commit staged files with helpful commit message following the [conventional commit spec](https://www.conventionalcommits.org/en/v1.0.0/).: `git commit`
+    - See [When you are ready to commit](#When-you-are-ready-to-commit)
+1.  Push commit(s) to remote: `git push -u origin <branch_name>`
+1.  Create a pull request (PR) using the GitHub UI [here](https://github.com/salesforcecli/plugin-command-reference).
+
+## Testing
+
+All changes must have associated tests. This library uses a combination of unit testing and NUTs (non-unit tests).
+
+### Unit tests
+
+Unit tests are run with `yarn test` and use the mocha test framework. Tests are located in the test directory and are named with the pattern, `<test-file>.test.ts`. Reference the existing unit tests when writing and testing code changes.
+
+### NUTs (non-unit tests)
+
+Non-unit tests are run with `yarn test:nuts` and use the [cli-plugin-testkit](https://github.com/salesforcecli/cli-plugins-testkit) framework. These tests run using the default devhub in your environment. NUTs are a way to test the library code in a real environment versus a unit test environment where many things are stubbed.
+
+## Debugging
+
+If you need to debug plugin code or tests you should refer to the excellent documentation on this topic in the [Plugin Developer Guide](https://github.com/salesforcecli/cli/wiki/Debug-Your-Plugin).
+
+## Running Commands
+
+To run your modified plugin commands locally, use `./bin/run.js` or `./bin/run.cmd` (Windows). Note that you must compile any code changes (`yarn compile`) before seeing those changes with `./bin/run.js`.
+
+```bash
+# Run using local script.
+./bin/run.js <command> --help
+```
+
+There should be no differences when running via the Salesforce CLI or using the local scripts. However, it can be useful to link the plugin to do some additional testing or run your commands from anywhere on your machine.
+
+```bash
+# Link your plugin to the sf cli
+sf plugins:link .
+# To verify
+sf plugins
+```
+
+## When you are ready to commit
+
+If you want your changes to be published to npmjs, your commit messages must follow the [conventional commit spec](https://www.conventionalcommits.org/en/v1.0.0/).
+
+- To increase the patch version, make sure that at least 1 commit message starts with "fix:"
+- To increase the minor version, make sure that at least 1 commit message starts with "feat:"
+- To bump the major version, please work with the CLI team.
+  If you'd like a review from a CLI developer, please tag us in Slack or in the PR.
+
+## Useful yarn commands
+
+#### `yarn install`
+
+This downloads all NPM dependencies into the node_modules directory.
+
+#### `yarn compile`
+
+This compiles the typescript to javascript.
+
+#### `yarn lint`
+
+This lints all the typescript using eslint.
+
+#### `yarn build`
+
+This compiles and lints all the typescript (e.g., `yarn compile && yarn lint`).
+
+#### `yarn clean`
+
+This cleans all generated files and directories. Run `yarn clean-all` to also clean up the node_module directories.
+
+#### `yarn test`
+
+This runs unit tests (mocha) for the project using ts-node.
+
+#### `yarn test:nuts`
+
+This runs NUTs (non-unit tests) for the project using ts-node.