Skip to content

Commit 65332ba

Browse files
authored
Merge pull request #19 from github/ldennington/additional-os-release-files
open source release: add required files
2 parents 4ea09ed + 336deed commit 65332ba

File tree

6 files changed

+189
-1
lines changed

6 files changed

+189
-1
lines changed

CODEOWNERS

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# This repository is maintained by:
2+
* @vdye @derrickstolee @ldennington

CODE_OF_CONDUCT.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
[homepage]: http://contributor-covenant.org
4+
[version]: http://contributor-covenant.org/version/1/4/
5+
6+
## Our Pledge
7+
8+
In the interest of fostering an open and welcoming environment, we as
9+
contributors and maintainers pledge to making participation in our project and
10+
our community a harassment-free experience for everyone, regardless of age, body
11+
size, disability, ethnicity, gender identity and expression, level of experience,
12+
nationality, personal appearance, race, religion, or sexual identity and
13+
orientation.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to creating a positive environment
18+
include:
19+
20+
* Using welcoming and inclusive language.
21+
* Being respectful of differing viewpoints and experiences.
22+
* Gracefully accepting constructive criticism.
23+
* Focusing on what is best for the community.
24+
* Showing empathy towards other community members.
25+
26+
Examples of unacceptable behavior by participants include:
27+
28+
* The use of sexualized language or imagery and unwelcome sexual attention or
29+
advances.
30+
* Trolling, insulting/derogatory comments, and personal or political attacks.
31+
* Public or private harassment.
32+
* Publishing others' private information, such as a physical or electronic
33+
address, without explicit permission.
34+
* Other conduct which could reasonably be considered inappropriate in a
35+
professional setting.
36+
37+
## Our Responsibilities
38+
39+
Project maintainers are responsible for clarifying the standards of acceptable
40+
behavior and are expected to take appropriate and fair corrective action in
41+
response to any instances of unacceptable behavior.
42+
43+
Project maintainers have the right and responsibility to remove, edit, or
44+
reject comments, commits, code, wiki edits, issues, and other contributions
45+
that are not aligned to this Code of Conduct, or to ban temporarily or
46+
permanently any contributor for other behaviors that they deem inappropriate,
47+
threatening, offensive, or harmful.
48+
49+
## Scope
50+
51+
This Code of Conduct applies both within project spaces and in public spaces
52+
when an individual is representing the project or its community. Examples of
53+
representing a project or community include using an official project e-mail
54+
address, posting via an official social media account, or acting as an appointed
55+
representative at an online or offline event. Representation of a project may be
56+
further defined and clarified by project maintainers.
57+
58+
## Enforcement
59+
60+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
61+
reported by contacting the project team at [email protected]. All
62+
complaints will be reviewed and investigated and will result in a response that
63+
is deemed necessary and appropriate to the circumstances. The project team is
64+
obligated to maintain confidentiality with regard to the reporter of an incident.
65+
Further details of specific enforcement policies may be posted separately.
66+
67+
Project maintainers who do not follow or enforce the Code of Conduct in good
68+
faith may face temporary or permanent repercussions as determined by other
69+
members of the project's leadership.
70+
71+
## Attribution
72+
73+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
74+
version 1.4, available at [http://contributor-covenant.org/version/1/4][version]

CONTRIBUTING.md

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
## Contributing
2+
3+
[code-of-conduct]: CODE_OF_CONDUCT.md
4+
[commit-guidance]: https://github.blog/2022-06-30-write-better-commits-build-better-projects/
5+
[compare]: https://github.com/github/git-bundle-server/compare
6+
[contributions-under-license]: https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license
7+
[github-help]: https://help.github.com
8+
[license]: LICENSE
9+
[open-source-contributions]: https://opensource.guide/how-to-contribute/
10+
[pr-guidance]: https://help.github.com/articles/about-pull-requests/
11+
[readme]: README.md
12+
13+
Hi there! We're thrilled that you'd like to contribute to the `git-bundle-server`
14+
project. Your work is extremely appreciated :star:.
15+
16+
Contributions to this project are [released][contributions-under-license] to the public
17+
under the [project's open source license][license].
18+
19+
Please note that this project is released with a [Contributor Code of
20+
Conduct][code-of-conduct]. By participating in this project you agree to abide
21+
by its terms.
22+
23+
## Prerequisites for running and testing code
24+
25+
Check out the project's [`README`][README] for thorough guidance on how
26+
to hit the ground running :dash:.
27+
28+
## Submitting a pull request
29+
30+
1. Clone the repository.
31+
0. Reference the project's [`README`][README] to build, test, and lint.
32+
0. Create a new branch: `git checkout -b <my-branch-name>`
33+
0. Do some awesome work :sparkles:.
34+
0. Add tests and make sure the tests and linter still pass.
35+
0. Push your changes and [submit a pull request][compare].
36+
0. Pat yourself on the back and wait for your pull request to be reviewed
37+
and merged.
38+
39+
Here are a few things you can do that will increase the likelihood of your pull
40+
request being accepted:
41+
42+
- Write tests.
43+
- Keep your change as focused as possible. If there are multiple changes you
44+
would like to make that are not dependent upon each other, consider submitting
45+
them as separate pull requests.
46+
- Write a [good commit message][commit-guidance].
47+
48+
## Resources
49+
50+
- [How to Contribute to Open Source][open-source-contributions]
51+
- [Using Pull Requests][pr-guidance]
52+
- [GitHub Help][github-help]

README.md

Lines changed: 33 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,19 @@
11
# `git-bundle-server`: Manage a self-hosted bundle server
22

3+
[bundle-uris]: https://github.com/git/git/blob/next/Documentation/technical/bundle-uri.txt
4+
[codeowners]: CODEOWNERS
5+
[contributing]: CONTRIBUTING.md
6+
[license]: LICENSE
7+
[support]: SUPPORT.md
8+
9+
## Background
10+
311
By running this software, you can self-host a bundle server to work with Git's
412
[bundle URI feature][bundle-uris].
513

6-
[bundle-uris]: https://github.com/git/git/blob/next/Documentation/technical/bundle-uri.txt
14+
This repository is under active development, and loves contributions from the
15+
community :heart:. Check out [CONTRIBUTING][contributing] for details on getting
16+
started.
717

818
## Cloning and Building
919

@@ -16,6 +26,14 @@ executables with
1626
$ go build -o . ./...
1727
```
1828

29+
## Testing and Linting
30+
31+
To run the project's unit tests, navigate to the repository root directory and
32+
run `go test -v ./...`.
33+
34+
To run the project's linter, navigate to the repository root directory and run
35+
`go vet ./...`.
36+
1937
## Bundle Management through CLI
2038

2139
The following command-line interface allows you to manage which repositories are
@@ -66,3 +84,17 @@ server, you can manage the web server process itself using these commands:
6684

6785
Finally, if you want to run the web server process directly in your terminal,
6886
for debugging purposes, then you can run `git-bundle-web-server`.
87+
88+
## License
89+
90+
This project is licensed under the terms of the MIT open source license. Please
91+
refer to [LICENSE][license] for the full terms.
92+
93+
## Maintainers
94+
95+
See [CODEOWNERS][codeowners] for a list of current project maintainers.
96+
97+
## Support
98+
99+
See [SUPPORT][support] for instructions on how to file bugs, feature requests,
100+
and general questions/requests for help.

SECURITY.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# Security
2+
3+
[bug-bounty]: https://hackerone.com/github?type=team
4+
5+
If you discover a security issue in this repo, please submit it through the
6+
[GitHub Security Bug Bounty program][bug-bounty].
7+
8+
Thanks for helping make open source products on GitHub safe for everyone.

SUPPORT.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Support
2+
3+
[discussion]: https://github.com/github/git-bundle-server/discussions
4+
5+
## How to file issues and get help
6+
7+
This project uses GitHub issues to track bugs and feature requests. Please search
8+
the existing issues before filing new issues to avoid duplicates. For new
9+
issues, file your bug or feature request as a new issue.
10+
11+
For help or questions about using this project, please start a
12+
[Discussion][discussion].
13+
14+
- `git-bundle-server` is under active development and maintained by GitHub
15+
staff **AND THE COMMUNITY**. We will do our best to respond to support, feature
16+
requests, and community questions in a timely manner.
17+
18+
## GitHub Support Policy
19+
20+
Support for this project is limited to the resources listed above.

0 commit comments

Comments
 (0)