Daniel Gibbs
4 years ago
18 changed files with 1508 additions and 121 deletions
@ -1,4 +0,0 @@ |
|||||
# Configuration for top-issue-bot |
|
||||
labelName: ":thumbsup: Top Issue!" |
|
||||
labelColor: "f442c2" |
|
||||
numberOfIssuesToLabel: 5 |
|
||||
File diff suppressed because it is too large
@ -1,4 +0,0 @@ |
|||||
# .github/write-good.yml |
|
||||
writeGood: true |
|
||||
alex: true |
|
||||
spellchecker: true |
|
||||
@ -1,44 +0,0 @@ |
|||||
language: node_js |
|
||||
dist: bionic |
|
||||
node_js: |
|
||||
- "stable" |
|
||||
env: |
|
||||
global: |
|
||||
secure: VsS98cwJ5X/Ev3HEm7KEOPftYay+7jNTHepTS7d+gQNHcDR1UYKTmqlQNSIoUC52Ejs1cHq43jOfle4330zDPOYI0v5BMri6/iZKpmMxAw6KWNiUgSkziTP2kHC4NRLwEoU2WQTI3JZQjrBEfsPmD81+yR/eWXV3rph+YcSOxao= |
|
||||
|
|
||||
before_script: |
|
||||
- curl -L "https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/shunit2/shunit2-2.1.6.tgz" | tar zx |
|
||||
|
|
||||
install: |
|
||||
- npm install gamedig |
|
||||
|
|
||||
addons: |
|
||||
apt: |
|
||||
packages: |
|
||||
- mailutils |
|
||||
- postfix |
|
||||
- jq |
|
||||
- lib32gcc1 |
|
||||
- lib32stdc++6 |
|
||||
- shellcheck |
|
||||
- libcurl4-openssl-dev |
|
||||
- libdw-dev |
|
||||
- cmake |
|
||||
|
|
||||
jobs: |
|
||||
include: |
|
||||
- stage: "Jobs" |
|
||||
name: "code coverage" |
|
||||
script: bash tests/tests_kcov.sh; kcov --bash-method=DEBUG coverage tests/tests_mcserver.sh |
|
||||
- script: bash tests/tests_mcserver.sh |
|
||||
name: "Minecraft" |
|
||||
- script: bash tests/tests_jc2server.sh |
|
||||
name: "Just Cause 2" |
|
||||
- script: bash tests/tests_fctrserver.sh |
|
||||
name: "Factorio" |
|
||||
- script: bash tests/tests_ts3server.sh |
|
||||
name: "Teamspeak 3" |
|
||||
- script: bash tests/tests_defaultcfg/tests_defaultcfg.sh |
|
||||
name: "_default.cfg checks" |
|
||||
after_success: |
|
||||
- bash <(curl -Ls https://coverage.codacy.com/get.sh) |
|
||||
@ -1,73 +1,133 @@ |
|||||
|
|
||||
# Contributor Covenant Code of Conduct |
# Contributor Covenant Code of Conduct |
||||
|
|
||||
## Our Pledge |
## Our Pledge |
||||
|
|
||||
In the interest of fostering an open and welcoming environment, we as |
We as members, contributors, and leaders pledge to make participation in our |
||||
contributors and maintainers pledge to making participation in our project and |
community a harassment-free experience for everyone, regardless of age, body |
||||
our community a harassment-free experience for everyone, regardless of age, body |
size, visible or invisible disability, ethnicity, sex characteristics, gender |
||||
size, disability, ethnicity, sex characteristics, gender identity and expression, |
identity and expression, level of experience, education, socio-economic status, |
||||
level of experience, education, socio-economic status, nationality, personal |
nationality, personal appearance, race, caste, color, religion, or sexual identity |
||||
appearance, race, religion, or sexual identity and orientation. |
and orientation. |
||||
|
|
||||
|
We pledge to act and interact in ways that contribute to an open, welcoming, |
||||
|
diverse, inclusive, and healthy community. |
||||
|
|
||||
## Our Standards |
## Our Standards |
||||
|
|
||||
Examples of behavior that contributes to creating a positive environment |
Examples of behavior that contributes to a positive environment for our |
||||
include: |
community include: |
||||
|
|
||||
* Using welcoming and inclusive language |
* Demonstrating empathy and kindness toward other people |
||||
* Being respectful of differing viewpoints and experiences |
* Being respectful of differing opinions, viewpoints, and experiences |
||||
* Gracefully accepting constructive criticism |
* Giving and gracefully accepting constructive feedback |
||||
* Focusing on what is best for the community |
* Accepting responsibility and apologizing to those affected by our mistakes, |
||||
* Showing empathy towards other community members |
and learning from the experience |
||||
|
* Focusing on what is best not just for us as individuals, but for the |
||||
|
overall community |
||||
|
|
||||
Examples of unacceptable behavior by participants include: |
Examples of unacceptable behavior include: |
||||
|
|
||||
* The use of sexualized language or imagery and unwelcome sexual attention or advances |
* The use of sexualized language or imagery, and sexual attention or |
||||
* Trolling, insulting/derogatory comments, and personal or political attacks |
advances of any kind |
||||
|
* Trolling, insulting or derogatory comments, and personal or political attacks |
||||
* Public or private harassment |
* Public or private harassment |
||||
* Publishing others' private information, such as a physical or electronic address, without explicit permission |
* Publishing others' private information, such as a physical or email |
||||
* Other conduct which could reasonably be considered inappropriate in a professional setting |
address, without their explicit permission |
||||
|
* Other conduct which could reasonably be considered inappropriate in a |
||||
|
professional setting |
||||
|
|
||||
## Our Responsibilities |
## Enforcement Responsibilities |
||||
|
|
||||
Project maintainers are responsible for clarifying the standards of acceptable |
Community leaders are responsible for clarifying and enforcing our standards of |
||||
behavior and are expected to take appropriate and fair corrective action in |
acceptable behavior and will take appropriate and fair corrective action in |
||||
response to any instances of unacceptable behavior. |
response to any behavior that they deem inappropriate, threatening, offensive, |
||||
|
or harmful. |
||||
|
|
||||
Project maintainers have the right and responsibility to remove, edit, or |
Community leaders have the right and responsibility to remove, edit, or reject |
||||
reject comments, commits, code, wiki edits, issues, and other contributions |
comments, commits, code, wiki edits, issues, and other contributions that are |
||||
that are not aligned to this Code of Conduct, or to ban temporarily or |
not aligned to this Code of Conduct, and will communicate reasons for moderation |
||||
permanently any contributor for other behaviors that they deem inappropriate, |
decisions when appropriate. |
||||
threatening, offensive, or harmful. |
|
||||
|
|
||||
## Scope |
## Scope |
||||
|
|
||||
This Code of Conduct applies both within project spaces and in public spaces |
This Code of Conduct applies within all community spaces, and also applies when |
||||
when an individual is representing the project or its community. Examples of |
an individual is officially representing the community in public spaces. |
||||
representing a project or community include using an official project e-mail |
Examples of representing our community include using an official e-mail address, |
||||
address, posting via an official social media account, or acting as an appointed |
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 |
representative at an online or offline event. |
||||
further defined and clarified by project maintainers. |
|
||||
|
|
||||
## Enforcement |
## Enforcement |
||||
|
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be |
Instances of abusive, harassing, or otherwise unacceptable behavior may be |
||||
reported by contacting the project team at [email protected]. All |
reported to the community leaders responsible for enforcement at |
||||
complaints will be reviewed and investigated and will result in a response that |
[INSERT CONTACT METHOD]. |
||||
is deemed necessary and appropriate to the circumstances. The project team is |
All complaints will be reviewed and investigated promptly and fairly. |
||||
obligated to maintain confidentiality with regard to the reporter of an incident. |
|
||||
Further details of specific enforcement policies may be posted separately. |
All community leaders are obligated to respect the privacy and security of the |
||||
|
reporter of any incident. |
||||
|
|
||||
|
## Enforcement Guidelines |
||||
|
|
||||
|
Community leaders will follow these Community Impact Guidelines in determining |
||||
|
the consequences for any action they deem in violation of this Code of Conduct: |
||||
|
|
||||
|
### 1. Correction |
||||
|
|
||||
|
**Community Impact**: Use of inappropriate language or other behavior deemed |
||||
|
unprofessional or unwelcome in the community. |
||||
|
|
||||
|
**Consequence**: A private, written warning from community leaders, providing |
||||
|
clarity around the nature of the violation and an explanation of why the |
||||
|
behavior was inappropriate. A public apology may be requested. |
||||
|
|
||||
|
### 2. Warning |
||||
|
|
||||
|
**Community Impact**: A violation through a single incident or series |
||||
|
of actions. |
||||
|
|
||||
Project maintainers who do not follow or enforce the Code of Conduct in good |
**Consequence**: A warning with consequences for continued behavior. No |
||||
faith may face temporary or permanent repercussions as determined by other |
interaction with the people involved, including unsolicited interaction with |
||||
members of the project's leadership. |
those enforcing the Code of Conduct, for a specified period of time. This |
||||
|
includes avoiding interactions in community spaces as well as external channels |
||||
|
like social media. Violating these terms may lead to a temporary or |
||||
|
permanent ban. |
||||
|
|
||||
|
### 3. Temporary Ban |
||||
|
|
||||
|
**Community Impact**: A serious violation of community standards, including |
||||
|
sustained inappropriate behavior. |
||||
|
|
||||
|
**Consequence**: A temporary ban from any sort of interaction or public |
||||
|
communication with the community for a specified period of time. No public or |
||||
|
private interaction with the people involved, including unsolicited interaction |
||||
|
with those enforcing the Code of Conduct, is allowed during this period. |
||||
|
Violating these terms may lead to a permanent ban. |
||||
|
|
||||
|
### 4. Permanent Ban |
||||
|
|
||||
|
**Community Impact**: Demonstrating a pattern of violation of community |
||||
|
standards, including sustained inappropriate behavior, harassment of an |
||||
|
individual, or aggression toward or disparagement of classes of individuals. |
||||
|
|
||||
|
**Consequence**: A permanent ban from any sort of public interaction within |
||||
|
the community. |
||||
|
|
||||
## Attribution |
## Attribution |
||||
|
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, |
This Code of Conduct is adapted from the [Contributor Covenant][homepage], |
||||
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html |
version 2.1, available at |
||||
|
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. |
||||
|
|
||||
[homepage]: https://www.contributor-covenant.org |
Community Impact Guidelines were inspired by |
||||
|
[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. |
||||
|
|
||||
For answers to common questions about this code of conduct, see |
For answers to common questions about this code of conduct, see the FAQ at |
||||
https://www.contributor-covenant.org/faq |
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available |
||||
|
at [https://www.contributor-covenant.org/translations][translations]. |
||||
|
|
||||
|
[homepage]: https://www.contributor-covenant.org |
||||
|
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html |
||||
|
[Mozilla CoC]: https://github.com/mozilla/diversity |
||||
|
[FAQ]: https://www.contributor-covenant.org/faq |
||||
|
[translations]: https://www.contributor-covenant.org/translations |
||||
|
|||||
@ -35,7 +35,7 @@ The following is a set of guidelines for contributing to LinuxGSM, which are hos |
|||||
|
|
||||
## Code of Conduct |
## Code of Conduct |
||||
|
|
||||
This project and everyone participating in it are governed by the [LinuxGSM Code of Conduct](https://github.com/GameServerManagers/linuxgsm/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behaviour to [[email protected]](mailto:[email protected]). |
This project and everyone participating in it is governed by the [LinuxGSM Code of Conduct](https://github.com/GameServerManagers/linuxgsm/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behaviour to [[email protected]](mailto:[email protected]). |
||||
|
|
||||
## 🎉 Bug/Enhancement Contributions 🐛 |
## 🎉 Bug/Enhancement Contributions 🐛 |
||||
|
|
||||
@ -87,7 +87,7 @@ Features are tracked as [GitHub issues](https://guides.github.com/features/issue |
|||||
This section guides you through submitting a game server request for LinuxGSM, Following these guidelines help maintainers and the community understand your game server request 📝. |
This section guides you through submitting a game server request for LinuxGSM, Following these guidelines help maintainers and the community understand your game server request 📝. |
||||
#### Before Submitting a Game Server Request |
#### Before Submitting a Game Server Request |
||||
|
|
||||
* **Check for existing** [**game server requests**](https://github.com/GameServerManagers/LinuxGSM/labels/type%3A%20game%20server%20request) to see if the new game server has already been suggested. If it has **and if the new game server is still open**, give it a thumbs. |
* **Check for existing** [**game server requests**](https://github.com/GameServerManagers/LinuxGSM/labels/type%3A%20game%20server%20request) to see if the new game server has already been suggested. If it has **and if the new game server is still open**, give it a thumbs up. |
||||
* **Check the game server is supported on Linux**, this does not include Wine servers which we do not support. |
* **Check the game server is supported on Linux**, this does not include Wine servers which we do not support. |
||||
#### How Do I Submit A (Good) Game Server Request? |
#### How Do I Submit A (Good) Game Server Request? |
||||
* The title should be as follows: **[Server Request] Game Name** |
* The title should be as follows: **[Server Request] Game Name** |
||||
@ -98,9 +98,9 @@ This section guides you through submitting a game server request for LinuxGSM, F |
|||||
|
|
||||
LinuxGSM is a management script that acts as a wrapper around game servers. These game servers are developed by different game developers such as Valve, Epic and Facepunch to name a few. |
LinuxGSM is a management script that acts as a wrapper around game servers. These game servers are developed by different game developers such as Valve, Epic and Facepunch to name a few. |
||||
|
|
||||
LinuxGSM has no control over the development and limited knowledge of issues directly relating to the game servers themselves. The same also applies for any mods, add-ons, maps etc. |
LinuxGSM has no control over the development and limited knowledge of issues directly relating to the game servers themselves. The same also applies to any mods, add-ons, maps etc. |
||||
|
|
||||
If there is an issue with a specific game server or mod the best action may be to contact the game/mod developers on there support forums. If it is unclear some community members should be able to help. |
If there is an issue with a specific game server or mod the best action may be to contact the game/mod developers on their support forums. If it is unclear some community members should be able to help. |
||||
|
|
||||
A [list](https://docs.linuxgsm.com/support/game-server) of known game developer forums is available on the [LinuxGSM docs](https://docs.linuxgsm.com/support/game-server). |
A [list](https://docs.linuxgsm.com/support/game-server) of known game developer forums is available on the [LinuxGSM docs](https://docs.linuxgsm.com/support/game-server). |
||||
|
|
||||
@ -157,7 +157,7 @@ Below is an example of the subject line for a pull request: |
|||||
### Testing |
### Testing |
||||
|
|
||||
#### Pull Request Status Checks |
#### Pull Request Status Checks |
||||
When a Pull Request is submitted, a series of status check tests are conducted. These tests will asses the code quality, complete CI tests etc. To get your PR merged these status checks must pass. |
When a Pull Request is submitted, a series of status check tests are conducted. These tests will assess the code quality, complete CI tests etc. To get your PR merged these status checks must pass. |
||||
|
|
||||
#### Test Environment |
#### Test Environment |
||||
It is recommended that you have a testing environment available to test your code during development. To test your own code you must change some variables within the `linuxgsm.sh` file. This will force the use of your own code branch. |
It is recommended that you have a testing environment available to test your code during development. To test your own code you must change some variables within the `linuxgsm.sh` file. This will force the use of your own code branch. |
||||
@ -197,10 +197,10 @@ This section lists the labels we use to help us track and manage issues and pull |
|||||
[GitHub search](https://help.github.com/articles/searching-issues/) makes it easy to use labels for finding groups of issues or pull requests you're interested in. There are several categories of labels available: |
[GitHub search](https://help.github.com/articles/searching-issues/) makes it easy to use labels for finding groups of issues or pull requests you're interested in. There are several categories of labels available: |
||||
|
|
||||
**command** Labels |
**command** Labels |
||||
Highlights the LinuxGSM command the Issue/PR relates too. |
Highlights the LinuxGSM command the Issue/PR relates to. |
||||
|
|
||||
**info** Labels |
**info** Labels |
||||
Labels to help pinpoint what the issue or PR relates too. |
Labels to help pinpoint what the issue or PR relates to. |
||||
|
|
||||
variants: |
variants: |
||||
* _distro_ |
* _distro_ |
||||
|
|||||
Loading…
Reference in new issue