Skip to content

Commit 19b5d44

Browse files
graysonguarinograysonguarino
authored
Merge pull request #6 from geico/add-contribution-files
Add AUTHORS, CODE_OF_CONDUCT, and CONTRIBUTING
2 parents c7dc718 + 9a77163 commit 19b5d44

3 files changed

Lines changed: 167 additions & 0 deletions

File tree

‎AUTHORS‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
Unless mentioned otherwise in a specific file's header, all code in this
2+
project is released under the Apache 2.0 license.
3+
4+
The list of authors and contributors can be retrieved from the git
5+
commit history and in some cases, the file headers.
6+

‎CODE_OF_CONDUCT.md‎

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
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, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and 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 advances
26+
* Trolling, insulting/derogatory comments, and personal or political attacks
27+
* Public or private harassment
28+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
29+
* Other conduct which could reasonably be considered inappropriate in a professional setting
30+
31+
## Our Responsibilities
32+
33+
Project maintainers are responsible for clarifying the standards of acceptable
34+
behavior and are expected to take appropriate and fair corrective action in
35+
response to any instances of unacceptable behavior.
36+
37+
Project maintainers have the right and responsibility to remove, edit, or
38+
reject comments, commits, code, wiki edits, issues, and other contributions
39+
that are not aligned to this Code of Conduct, or to ban temporarily or
40+
permanently any contributor for other behaviors that they deem inappropriate,
41+
threatening, offensive, or harmful.
42+
43+
## Scope
44+
45+
This Code of Conduct applies both within project spaces and in public spaces
46+
when an individual is representing the project or its community. Examples of
47+
representing a project or community include using an official project e-mail
48+
address, posting via an official social media account, or acting as an appointed
49+
representative at an online or offline event. Representation of a project may be
50+
further defined and clarified by project maintainers.
51+
52+
## Enforcement
53+
54+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
55+
reported by contacting the project team at tuxtape@geico.com. All
56+
complaints will be reviewed and investigated and will result in a response that
57+
is deemed necessary and appropriate to the circumstances. The project team is
58+
obligated to maintain confidentiality with regard to the reporter of an incident.
59+
Further details of specific enforcement policies may be posted separately.
60+
61+
Project maintainers who do not follow or enforce the Code of Conduct in good
62+
faith may face temporary or permanent repercussions as determined by other
63+
members of the project's leadership.
64+
65+
## Attribution
66+
67+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
68+
available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
69+
70+
[homepage]: https://www.contributor-covenant.org
71+
72+
For answers to common questions about this code of conduct, see <https://www.contributor-covenant.org/faq>
73+

‎CONTRIBUTING.md‎

Lines changed: 88 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,88 @@
1+
# Contributing
2+
3+
<!-- Include start contributing -->
4+
5+
The TuxTape team appreciates contributions to the project through pull requests and issues on the GitHub repository.
6+
7+
Check the following guidelines before contributing to the project.
8+
9+
## Code of Conduct
10+
11+
When contributing, you must adhere to the Code of Conduct.
12+
13+
## License and copyright
14+
15+
By default, any contribution to this project is made under the Apache
16+
2.0 license.
17+
18+
The author of a change remains the copyright holder of their code
19+
(no copyright assignment).
20+
21+
## Pull requests
22+
23+
Changes to this project should be proposed as pull requests on GitHub.
24+
25+
Proposed changes will then go through review there and once approved,
26+
be merged in the main branch.
27+
28+
### Developer Certificate of Origin
29+
30+
To improve tracking of contributions to this project we use the DCO 1.1
31+
and use a "sign-off" procedure for all changes going into the branch.
32+
33+
The sign-off is a simple line at the end of the explanation for the
34+
commit which certifies that you wrote it or otherwise have the right
35+
to pass it on as an open-source contribution.
36+
37+
```
38+
Developer Certificate of Origin
39+
Version 1.1
40+
41+
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
42+
660 York Street, Suite 102,
43+
San Francisco, CA 94110 USA
44+
45+
Everyone is permitted to copy and distribute verbatim copies of this
46+
license document, but changing it is not allowed.
47+
48+
Developer's Certificate of Origin 1.1
49+
50+
By making a contribution to this project, I certify that:
51+
52+
(a) The contribution was created in whole or in part by me and I
53+
have the right to submit it under the open source license
54+
indicated in the file; or
55+
56+
(b) The contribution is based upon previous work that, to the best
57+
of my knowledge, is covered under an appropriate open source
58+
license and I have the right under that license to submit that
59+
work with modifications, whether created in whole or in part
60+
by me, under the same open source license (unless I am
61+
permitted to submit under a different license), as indicated
62+
in the file; or
63+
64+
(c) The contribution was provided directly to me by some other
65+
person who certified (a), (b) or (c) and I have not modified
66+
it.
67+
68+
(d) I understand and agree that this project and the contribution
69+
are public and that a record of the contribution (including all
70+
personal information I submit with it, including my sign-off) is
71+
maintained indefinitely and may be redistributed consistent with
72+
this project or the open source license(s) involved.
73+
```
74+
75+
An example of a valid sign-off line is:
76+
77+
```
78+
Signed-off-by: Random J Developer <random@developer.org>
79+
```
80+
81+
Use a known identity and a valid e-mail address.
82+
Sorry, no anonymous contributions are allowed.
83+
84+
We also require each commit be individually signed-off by their author,
85+
even when part of a larger set. You may find `git commit -s` useful.
86+
87+
<!-- Include end contributing -->
88+

0 commit comments

Comments
 (0)