Skip to content

Commit 65b11b2

Browse files
jimmajimma
committed
[JBWS-4346]:Add community guideline files
1 parent baa13d3 commit 65b11b2

File tree

4 files changed

+193
-4
lines changed

4 files changed

+193
-4
lines changed

‎CODE_OF_CONDUCT.md

+132
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,132 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, caste, color, religion, or sexual
10+
identity and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the overall
26+
community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or advances of
31+
any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email address,
35+
without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement:
63+
at Jim Ma <[email protected]> or Rebecca Searls <[email protected]>
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series of
86+
actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or permanent
93+
ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within the
113+
community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.1, available at
119+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
120+
121+
Community Impact Guidelines were inspired by
122+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
123+
124+
For answers to common questions about this code of conduct, see the FAQ at
125+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
126+
[https://www.contributor-covenant.org/translations][translations].
127+
128+
[homepage]: https://www.contributor-covenant.org
129+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
130+
[Mozilla CoC]: https://github.com/mozilla/diversity
131+
[FAQ]: https://www.contributor-covenant.org/faq
132+
[translations]: https://www.contributor-covenant.org/translations

‎CONTRIBUTING.md

+50
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
Contributing Guide
2+
==================================
3+
4+
We welcome contributions from the community. This guide will walk you through the steps for getting started on our project.
5+
6+
- [Git Setup](#git-setup)
7+
- [Issues](#issues)
8+
- [Good First Issues](#good-first-issues)
9+
- [Code Style](#code-style)
10+
11+
12+
13+
## Git Setup
14+
To contribute, you first need to fork the [jbossws-common](https://github.com/jbossws/jbossws-common) repository.
15+
then clone your newly forked copy onto your local workspace.
16+
And make sure you have set up your Git authorship correctly:
17+
```
18+
git config --global user.name "Your Full Name"
19+
git config --global user.email [email protected]
20+
```
21+
To pull update from the jbossws-common upstream, the jbossws-common remote can be added to your local git repo :
22+
```
23+
git remote add upstream https://github.com/jbossws/jbossws-common.git
24+
```
25+
Before change/fix, always pull update from jbossws-common:
26+
```
27+
$ git checkout -f main
28+
$ git pull --rebase upstream main
29+
```
30+
31+
## Issues
32+
JBssWS project uses JIRA to manage issues. All issues can be found [here](https://issues.redhat.com/projects/JBWS/issues).
33+
34+
To create a new issue, comment on an existing issue, or assign an issue to yourself, you'll need to first [create a JIRA account](https://issues.redhat.com/).
35+
36+
37+
### Good First Issues
38+
39+
We added the project issues with `good-first-issue` label for good to start the contribution. These can be found [here](https://issues.redhat.com/issues/?filter=12406834).
40+
When you start the issue you'd like to contribute, please make sure it isn't assigned to someone else. To assign the selected issue to yourself, click the "Assign" and check the
41+
assignee name before finish.
42+
It is highly recommended creating a topic git branch for one JIRA issue. A commit message with JIRA number is always a good
43+
practice to track which commit resolve which JIRA issue. Later the commit or PR number will be automatically linked to JIRA system.
44+
After finish the JIRA issue task, creating a GitHub pull request based on main branch. We'll monitor the PR queus and
45+
get the PR reviewed and merged.
46+
If you encounter any problem during the contribution, please use [GitHub discussion](https://github.com/jbossws/jbossws-cxf/discussions) to let us know.
47+
48+
## Code Style
49+
If you are using Eclipse then set your code style to eclipse/jboss-style.xml and check style to eclipse/jboss-format.xml.
50+
And please make sure you're putting correct license headers to Java and XML files.

‎README-COMMITTERS

-4
This file was deleted.

‎SECURITY.md

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Security Policy
2+
3+
## Security Contacts and Procedures
4+
5+
JBossWS community takes security very seriously, and we aim to take immediate action to address serious security-related problems that involve our products or services.
6+
7+
Please report any suspected security vulnerability in this project to Red Hat Product Security at [email protected]. You can use our GPG key to communicate with us securely.
8+
9+
To report an issue in any Red Hat branded website or online service, please contact Red Hat Information Security at [email protected].
10+
11+
https://access.redhat.com/security/team/contact

0 commit comments

Comments
 (0)