diff options
author | Rutger Broekhoff | 2023-12-29 21:31:53 +0100 |
---|---|---|
committer | Rutger Broekhoff | 2023-12-29 21:31:53 +0100 |
commit | 404aeae4545d2426c089a5f8d5e82dae56f5212b (patch) | |
tree | 2d84e00af272b39fc04f3795ae06bc48970e57b5 /vendor/github.com/minio/minio-go/v7/code_of_conduct.md | |
parent | 209d8b0187ed025dec9ac149ebcced3462877bff (diff) | |
download | gitolfs3-404aeae4545d2426c089a5f8d5e82dae56f5212b.tar.gz gitolfs3-404aeae4545d2426c089a5f8d5e82dae56f5212b.zip |
Make Nix builds work
Diffstat (limited to 'vendor/github.com/minio/minio-go/v7/code_of_conduct.md')
-rw-r--r-- | vendor/github.com/minio/minio-go/v7/code_of_conduct.md | 80 |
1 files changed, 80 insertions, 0 deletions
diff --git a/vendor/github.com/minio/minio-go/v7/code_of_conduct.md b/vendor/github.com/minio/minio-go/v7/code_of_conduct.md new file mode 100644 index 0000000..cb232c3 --- /dev/null +++ b/vendor/github.com/minio/minio-go/v7/code_of_conduct.md | |||
@@ -0,0 +1,80 @@ | |||
1 | # Contributor Covenant Code of Conduct | ||
2 | |||
3 | ## Our Pledge | ||
4 | |||
5 | In the interest of fostering an open and welcoming environment, we as | ||
6 | contributors and maintainers pledge to making participation in our project and | ||
7 | our community a harassment-free experience for everyone, regardless of age, body | ||
8 | size, disability, ethnicity, gender identity and expression, level of experience, | ||
9 | nationality, personal appearance, race, religion, or sexual identity and | ||
10 | orientation. | ||
11 | |||
12 | ## Our Standards | ||
13 | |||
14 | Examples of behavior that contributes to creating a positive environment | ||
15 | include: | ||
16 | |||
17 | * Using welcoming and inclusive language | ||
18 | * Being respectful of differing viewpoints and experiences | ||
19 | * Gracefully accepting constructive criticism | ||
20 | * Focusing on what is best for the community | ||
21 | * Showing empathy towards other community members | ||
22 | |||
23 | Examples of unacceptable behavior by participants include: | ||
24 | |||
25 | * The use of sexualized language or imagery and unwelcome sexual attention or | ||
26 | advances | ||
27 | * Trolling, insulting/derogatory comments, and personal or political attacks | ||
28 | * Public or private harassment | ||
29 | * Publishing others' private information, such as a physical or electronic | ||
30 | address, without explicit permission | ||
31 | * Other conduct which could reasonably be considered inappropriate in a | ||
32 | professional setting | ||
33 | |||
34 | ## Our Responsibilities | ||
35 | |||
36 | Project maintainers are responsible for clarifying the standards of acceptable | ||
37 | behavior and are expected to take appropriate and fair corrective action in | ||
38 | response to any instances of unacceptable behavior, in compliance with the | ||
39 | licensing terms applying to the Project developments. | ||
40 | |||
41 | Project maintainers have the right and responsibility to remove, edit, or | ||
42 | reject comments, commits, code, wiki edits, issues, and other contributions | ||
43 | that are not aligned to this Code of Conduct, or to ban temporarily or | ||
44 | permanently any contributor for other behaviors that they deem inappropriate, | ||
45 | threatening, offensive, or harmful. However, these actions shall respect the | ||
46 | licensing terms of the Project Developments that will always supersede such | ||
47 | Code of Conduct. | ||
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]. The project team | ||
62 | will review and investigate all complaints, and will respond in a way that it deems | ||
63 | appropriate to the circumstances. The project team is obligated to maintain | ||
64 | 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], version 1.4, | ||
74 | available at [http://contributor-covenant.org/version/1/4][version] | ||
75 | |||
76 | This version includes a clarification to ensure that the code of conduct is in | ||
77 | compliance with the free software licensing terms of the project. | ||
78 | |||
79 | [homepage]: http://contributor-covenant.org | ||
80 | [version]: http://contributor-covenant.org/version/1/4/ | ||