You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
+
7
+
## Our Standards
8
+
9
+
Examples of behavior that contributes to creating a positive environment include:
10
+
11
+
* Using welcoming and inclusive language
12
+
* Being respectful of differing viewpoints and experiences
13
+
* Gracefully accepting constructive criticism
14
+
* Focusing on what is best for the community
15
+
* Showing empathy towards other community members
16
+
17
+
Examples of unacceptable behavior by participants include:
18
+
19
+
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20
+
* Trolling, insulting/derogatory comments, and personal or political attacks
21
+
* Public or private harassment
22
+
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23
+
* Other conduct which could reasonably be considered inappropriate in a professional setting
24
+
25
+
## Our Responsibilities
26
+
27
+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28
+
29
+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30
+
31
+
## Scope
32
+
33
+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
+
35
+
## Enforcement
36
+
37
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [switcher.project@gmail.com](mailto:switcher.project@gmail.com). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
+
39
+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40
+
41
+
## Attribution
42
+
43
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [https://contributor-covenant.org/version/1/4][version]
The following is a set of guidelines for contributing to Switcher Project. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
*[Your First Code Contribution](#your-first-code-contribution)
13
+
*[Pull Requests](#pull-requests)
14
+
15
+
## Code of Conduct
16
+
17
+
This project and everyone participating in it is governed by the [Switcher Project Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [switcher.project@gmail.com](mailto:switcher.project@gmail.com).
18
+
19
+
You can join the Switcher-HQ Slack team:
20
+
21
+
*[Join the Slack Team](https://switcher-hq.slack.com/)
22
+
* Even though Slack is a chat service, sometimes it takes several hours for community members to respond — please be patient!
23
+
* Use the `#random` channel for general questions or discussion about Switcher Project
24
+
25
+
## How Can I Contribute?
26
+
27
+
### Reporting Bugs
28
+
29
+
This section guides you through submitting a bug report. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
30
+
31
+
1. Use the GitHub issue search — check if the issue has already been reported.
32
+
2. Check if the issue has been fixed — try to reproduce it using the latest master or development branch in the repository.
33
+
34
+
Example:
35
+
36
+
> Short and descriptive example bug report title
37
+
>
38
+
> A summary of the issue. If suitable, include the steps required to reproduce the bug.
39
+
>
40
+
> 1. This is the first step
41
+
> 2. This is the second step
42
+
> 3. Further steps, etc.
43
+
>
44
+
> Any other information you want to share that is relevant to the issue being
45
+
> reported. This might include the lines of code that you have identified as
46
+
> causing the bug, and potential solutions (and your opinions on their
47
+
> merits).
48
+
49
+
> **Note:** If you find a **Closed** issue that seems like it is the same thing that you're experiencing, open a new issue and include a link to the original issue in the body of your new one.
50
+
51
+
### Suggesting Enhancements
52
+
53
+
This section guides you through submitting an enhancement suggestion for Switcher Project, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.
54
+
55
+
Simply create an issue and provide the following information:
56
+
57
+
***Use a clear and descriptive title** for the issue to identify the suggestion.
58
+
***Provide a step-by-step description of the suggested enhancement** in as much detail as possible. This additional context helps the maintainers to understand the enhancement from your perspective
59
+
***Explain why this enhancement would be useful**
60
+
61
+
### Your First Code Contribution
62
+
63
+
Unsure where to begin contributing to Switcher? You can start by looking through these `minor-issue` and `bug` issues:
64
+
65
+
* Minor issue - issues which should only require a few lines of code, and a test or two.
66
+
* Bug - issues which should be a bit more involved than `minor` issues.
67
+
68
+
### Pull Requests
69
+
70
+
The process described here has several goals:
71
+
72
+
- Maintain Switcher's Project quality
73
+
- Fix problems that are important to users
74
+
- Engage the community in working toward the best possible Switcher
75
+
- Enable a sustainable system for Switcher's maintainers to review contributions
76
+
77
+
Please follow these steps to have your contribution considered by the maintainers:
78
+
79
+
1. Fork the repository
80
+
2. Clone the repository
81
+
3. Create a branch
82
+
4. Make necessary changes and commit those changes
0 commit comments