open source release: add CONTRIBUTING.md

A CONTRIBUTING.md file is one of the requirements for releasing projects
as open source. Add CONTRIBUTING.md file with instructions on expected
workflows accordingly.

Signed-off-by: Lessley Dennington <[email protected]>

Author: Lessley Dennington

CONTRIBUTING.md

@@ -0,0 +1,52 @@
+## Contributing
+
+[code-of-conduct]: CODE_OF_CONDUCT.md
+[commit-guidance]: https://github.blog/2022-06-30-write-better-commits-build-better-projects/
+[compare]: https://github.com/github/git-bundle-server/compare
+[contributions-under-license]: https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license
+[github-help]: https://help.github.com
+[license]: LICENSE
+[open-source-contributions]: https://opensource.guide/how-to-contribute/
+[pr-guidance]: https://help.github.com/articles/about-pull-requests/
+[readme]: README.md
+
+Hi there! We're thrilled that you'd like to contribute to the `git-bundle-server`
+project. Your work is extremely appreciated :star:.
+
+Contributions to this project are [released][contributions-under-license] to the public
+under the [project's open source license][license].
+
+Please note that this project is released with a [Contributor Code of
+Conduct][code-of-conduct]. By participating in this project you agree to abide
+by its terms.
+
+## Prerequisites for running and testing code
+
+Check out the project's [`README`][README] for thorough guidance on how
+to hit the ground running :dash:.
+
+## Submitting a pull request
+
+1. Clone the repository.
+0. Reference the project's [`README`][README] to build, test, and lint.
+0. Create a new branch: `git checkout -b <my-branch-name>`
+0. Do some awesome work :sparkles:.
+0. Add tests and make sure the tests and linter still pass.
+0. Push your changes and [submit a pull request][compare].
+0. Pat yourself on the back and wait for your pull request to be reviewed
+and merged.
+
+Here are a few things you can do that will increase the likelihood of your pull
+request being accepted:
+
+- Write tests.
+- Keep your change as focused as possible. If there are multiple changes you
+would like to make that are not dependent upon each other, consider submitting
+them as separate pull requests.
+- Write a [good commit message][commit-guidance].
+
+## Resources
+
+- [How to Contribute to Open Source][open-source-contributions]
+- [Using Pull Requests][pr-guidance]
+- [GitHub Help][github-help]

README.md

@@ -1,13 +1,18 @@
 # `git-bundle-server`: Manage a self-hosted bundle server
 
 [bundle-uris]: https://github.com/git/git/blob/next/Documentation/technical/bundle-uri.txt
+[contributing]: CONTRIBUTING.md
 [license]: LICENSE
 
 ## Background
 
 By running this software, you can self-host a bundle server to work with Git's
 [bundle URI feature][bundle-uris].
 
+This repository is under active development, and loves contributions from the
+community :heart:. Check out [CONTRIBUTING][contributing] for details on getting
+started.
+
 ## Cloning and Building
 
 Be sure to clone inside the `src` directory of your `GOROOT`.
@@ -19,6 +24,14 @@ executables with
 $ go build -o . ./...
 ```
 
+## Testing and Linting
+
+To run the project's unit tests, navigate to the `git-bundle-server` directory
+and run `go test -v ./...`.
+
+To run the project's linter, navigate to the `git-bundle-server` directory
+and run `go vet ./...`.
+
 ## Bundle Management through CLI
 
 The following command-line interface allows you to manage which repositories are