Open Ticket v4 Beta
This commit is contained in:
@@ -0,0 +1,128 @@
|
||||
# Contributor Covenant Code of Conduct
|
||||
|
||||
## Our Pledge
|
||||
|
||||
We as members, contributors, and leaders pledge to make participation in our
|
||||
community a harassment-free experience for everyone, regardless of age, body
|
||||
size, visible or invisible disability, ethnicity, sex characteristics, gender
|
||||
identity and expression, level of experience, education, socio-economic status,
|
||||
nationality, personal appearance, race, religion, or sexual identity
|
||||
and orientation.
|
||||
|
||||
We pledge to act and interact in ways that contribute to an open, welcoming,
|
||||
diverse, inclusive, and healthy community.
|
||||
|
||||
## Our Standards
|
||||
|
||||
Examples of behavior that contributes to a positive environment for our
|
||||
community include:
|
||||
|
||||
* Demonstrating empathy and kindness toward other people
|
||||
* Being respectful of differing opinions, viewpoints, and experiences
|
||||
* Giving and gracefully accepting constructive feedback
|
||||
* Accepting responsibility and apologizing to those affected by our mistakes,
|
||||
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 include:
|
||||
|
||||
* The use of sexualized language or imagery, and sexual attention or
|
||||
advances of any kind
|
||||
* Trolling, insulting or derogatory comments, and personal or political attacks
|
||||
* Public or private harassment
|
||||
* Publishing others' private information, such as a physical or email
|
||||
address, without their explicit permission
|
||||
* Other conduct which could reasonably be considered inappropriate in a
|
||||
professional setting
|
||||
|
||||
## Enforcement Responsibilities
|
||||
|
||||
Community leaders are responsible for clarifying and enforcing our standards of
|
||||
acceptable behavior and will take appropriate and fair corrective action in
|
||||
response to any behavior that they deem inappropriate, threatening, offensive,
|
||||
or harmful.
|
||||
|
||||
Community leaders 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, and will communicate reasons for moderation
|
||||
decisions when appropriate.
|
||||
|
||||
## Scope
|
||||
|
||||
This Code of Conduct applies within all community spaces, and also applies when
|
||||
an individual is officially representing the community in public spaces.
|
||||
Examples of representing our community include using an official e-mail address,
|
||||
posting via an official social media account, or acting as an appointed
|
||||
representative at an online or offline event.
|
||||
|
||||
## Enforcement
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
||||
reported to the community leaders responsible for enforcement at
|
||||
support@dj-dj.be.
|
||||
All complaints will be reviewed and investigated promptly and fairly.
|
||||
|
||||
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.
|
||||
|
||||
**Consequence**: A warning with consequences for continued behavior. No
|
||||
interaction with the people involved, including unsolicited interaction with
|
||||
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
|
||||
|
||||
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
|
||||
version 2.0, available at
|
||||
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
|
||||
|
||||
Community Impact Guidelines were inspired by [Mozilla's code of conduct
|
||||
enforcement ladder](https://github.com/mozilla/diversity).
|
||||
|
||||
[homepage]: https://www.contributor-covenant.org
|
||||
|
||||
For answers to common questions about this code of conduct, see the FAQ at
|
||||
https://www.contributor-covenant.org/faq. Translations are available at
|
||||
https://www.contributor-covenant.org/translations.
|
||||
@@ -0,0 +1,41 @@
|
||||
# 🎥 Content Creators
|
||||
Hi there! We're searching for content creators to create tutorials & setup guides for Open Ticket.
|
||||
You can get many great rewards from helpin us!
|
||||
|
||||
You can choose which type of tutorial you want to make. You can create a quick setup, full setup, plugin tutorial or something else!
|
||||
You are not required to talk in the video, but make sure it has some kind of subtitles instead.
|
||||
|
||||
### 📄 Requirements
|
||||
- 📌 At least 2k subscribers!
|
||||
- 📌 A little bit of channel activity! *(minimum 2 uploads/month)*
|
||||
- 📌 Video length of at least 3 minutes!
|
||||
- 📌 Provide a clear link to the Open Ticket repository!
|
||||
- 📌 Recommended language is English!
|
||||
- 📌 Recommended platform is YouTube!
|
||||
- 📌 Must be for the latest version of Open Ticket!
|
||||
- 📌 **(OPTIONAL)** Speech in the video *(AI is allowed)*
|
||||
|
||||
|
||||
### 🎁 Rewards
|
||||
We won't give out any compensation in money, but we will give you some advantages!
|
||||
- ✅ Advertisement of tutorial in the [README.md](../README.md)!
|
||||
- ✅ Advertisement of channel in our [discord server](https://discord.dj-dj.be)!
|
||||
- ✅ `Content Creator` role in our [discord server](https://discord.dj-dj.be)!
|
||||
- ✅ Advertisement of tutorial & channel in documentation!
|
||||
- ✅ Lot's of of views generated from GitHub traffic!
|
||||
- ✅ A completely free 24/7 hosted Open Ticket bot!
|
||||
- ✅ We will advertise the video to all our socials!
|
||||
|
||||
### 💤 Outdated Content
|
||||
When a tutorial or setup guide is outdated or no longer applicable,
|
||||
we will remove it from the `README.md` & documentation.
|
||||
Your channel will still stay in the list of contributors, so don't worry about that!
|
||||
|
||||
You will be noticed at least a month before removal.
|
||||
This way you can take time to create an updated tutorial if you want.
|
||||
|
||||
### 💬 Contact Us
|
||||
If you've read all these guidelines, requirements & rewards,
|
||||
you can create a ticket in our [discord server](https://discord.dj-dj.be) to start working on it!
|
||||
|
||||
We will try to help you as fast as possible!
|
||||
@@ -0,0 +1,69 @@
|
||||
# Contributing Guidelines
|
||||
<img src="https://apis.dj-dj.be/cdn/openticket/logo.png" alt="Open Ticket Logo" width="500px">
|
||||
|
||||
[](https://discord.com/invite/26vT9wt3n3) [](https://github.com/DJj123dj/open-ticket/releases/tag/v4.0.0)
|
||||
|
||||
These are the Contributing Guidelines of Open Ticket!<br>
|
||||
Here you can find everything you need to know about contributing to Open Ticket.<br>
|
||||
This includes new features, translations & bug fixes.
|
||||
|
||||
### 💬 Translations
|
||||
#### Step 1: View & Check
|
||||
1. Check the [`./languages/`](./languages/) folder for existing translations.
|
||||
2. When it doesn't exist yet, visit **[step 2](#step-2-translation)**.
|
||||
3. When it does exist, check if it is outdated, incorrect or incomplete.
|
||||
4. If you match one of these requirements, you can also visit **[step 2](#step-2-translating)**.
|
||||
|
||||
#### Step 2: Translation
|
||||
1. If your language doesn't exist yet, copy the [`english.json`](./../languages/english.json) file and rename it to your language.
|
||||
2. You are allowed to use a little bit of `Google Translate` or `DeepL` when mentioned in the upload. (❌ Not Recommended)
|
||||
3. Only translate existing values in the json file. Don't add or remove any values from the file.
|
||||
4. If you are unable to translate something, leave it in `English`.
|
||||
|
||||
#### Step 3: Metadata
|
||||
Metadata can be found in the `_TRANSLATION` variable.
|
||||
|Value |Notes |
|
||||
|-------------|-------------------------------------------------------------------------------------------------|
|
||||
|`otversion` |The Open Ticket version of this translation. Don't edit this! |
|
||||
|`translator` |The translator discord username. When improving existing translation, add your name to the list. |
|
||||
|`lastedited` |The last edited date in the `DD/MM/YYYY` format. |
|
||||
|`language` |The full name of the language with capital letter. |
|
||||
|
||||
> #### ✅ You are also allowed to add your username to the [`README.md`](./../README.md) translator list!
|
||||
|
||||
#### Step 4: Uploading
|
||||
1. When adding a new language, please mention @DJj123dj. He will add the code required for the language to work.
|
||||
2. There are currently 3 ways of uploading translations:
|
||||
- Create a pull request to the [__`dev` branch!__](https://github.com/DJj123dj/open-ticket/tree/dev)
|
||||
- Create a ticket in our [discord server](https://discord.dj-dj.be)!
|
||||
- Send a DM to @DJj123dj on discord!
|
||||
3. Now you'll need to wait until the next Open Ticket version for it to be added.
|
||||
|
||||
#### Step 5: Rewards
|
||||
Translators get some rewards for translating Open Ticket!
|
||||
- ✅ Credits in the [`README.md`](./../README.md) translator list!
|
||||
- ✅ Credits in the changelog!
|
||||
- ✅ Credits in the documentation!
|
||||
- ✅ Credits in the translation JSON file!
|
||||
- ✅ A special role in our [discord server](https://discord.dj-dj.be)!
|
||||
|
||||
### 🧩 Plugins (temporary)
|
||||
Currently plugins can only be added to the list via our [discord server](https://discord.dj-dj.be)!
|
||||
|
||||
### 📦 Features (temporary)
|
||||
Currently features can only be suggested in our [discord server](https://discord.dj-dj.be)!
|
||||
|
||||
### 🕷️ Bug Fixes (temporary)
|
||||
Currently bug fixes can only be reported in the following ways:
|
||||
- Create an issue in the repository!
|
||||
- Create a ticket in our [discord server](https://discord.dj-dj.be)!
|
||||
|
||||
#### Please try to always include the `otdebug.txt` file!
|
||||
|
||||
---
|
||||
<img src="https://apis.dj-dj.be/cdn/openticket/logo.png" alt="Open Ticket Logo" width="170px">
|
||||
|
||||
**Contributing Guidelines**<br>
|
||||
[changelog](https://otgithub.dj-dj.be/releases) - [documentation](https://otdocs.dj-dj.be) - [tutorial](https://www.youtube.com/watch?v=2jK9kAf6ASU) - [website](https://openticket.dj-dj.be) - [discord](https://discord.dj-dj.be)<br>
|
||||
|
||||
© 2024 - [DJdj Development](https://www.dj-dj.be) - [Terms](https://www.dj-dj.be/terms#terms) - [Privacy Policy](https://www.dj-dj.be/terms#privacy)
|
||||
@@ -0,0 +1 @@
|
||||
github: DJj123dj
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
name: Bug Report
|
||||
about: Report bugs to help us improve Open Ticket!
|
||||
title: "[BUG] Your Bug"
|
||||
labels: bug
|
||||
assignees: DJj123dj
|
||||
---
|
||||
|
||||
### Bug Description:
|
||||
A clear and concise description of what the bug is.
|
||||
|
||||
### Steps To Reproduce:
|
||||
Steps to reproduce the behavior:
|
||||
1. Go to '...'
|
||||
2. Click on '....'
|
||||
3. Scroll down to '....'
|
||||
4. See error
|
||||
|
||||
> Leave empty when you are unable to reproduce the bug!
|
||||
|
||||
### Expected Behaviour:
|
||||
A clear and concise description of what you expected to happen.
|
||||
|
||||
### Screenshots:
|
||||
If applicable, add screenshots to help explain your problem.
|
||||
|
||||
### Files:
|
||||
Please include the `otdebug.txt` file in your report! With this file, we can take a deep-dive in to the error that happend.
|
||||
> This file doesn't contain any credentials or sensitive information!
|
||||
|
||||
### Additional Notes:
|
||||
Add any other context about the problem here.
|
||||
@@ -0,0 +1,49 @@
|
||||
# Security Policy
|
||||
<img src="https://apis.dj-dj.be/cdn/openticket/logo.png" alt="Open Ticket Logo" width="500px">
|
||||
|
||||
[](https://discord.com/invite/26vT9wt3n3) [](https://github.com/DJj123dj/open-ticket/releases/tag/v4.0.0)
|
||||
|
||||
This is the Security Policy of Open Ticket!<br>
|
||||
Here you can find a list of all supported & deprecated versions of the bot.<br>
|
||||
You will also find some guidelines about how to report vulnerabilities, bugs & errors.
|
||||
|
||||
### 📦 Supported Versions
|
||||
Below, you can find a list with the status of every Open Ticket version.<br>
|
||||
This list will be updated on every release.
|
||||
|
||||
- 🟦 Early Access **(ideas, bugs, support, html transcripts)**
|
||||
- ✅ Supported **(features, bugs, support, docs, html transcripts)**
|
||||
- 🚧 Maintenance **(support, docs, html transcripts)**
|
||||
- 🟧 Deprecated **(docs)**
|
||||
- ❌ Fully Deprecated
|
||||
|
||||
| Version | Supported | Notes |
|
||||
|------------|-----------|--------------------------------|
|
||||
| 4.0.0-beta | 🟦 | For v4.0.0 Full Release |
|
||||
| 3.5.8 | ✅ | Supported until October 2024 |
|
||||
| 3.5.7 | ✅ | Supported until September 2024 |
|
||||
| 3.5.6 | 🟧 | Documentation Only |
|
||||
| < 3.5.6 | 🟧 | Documentation Only |
|
||||
| < 3.5.0 | ❌ | |
|
||||
|
||||
### 🕷️ Reporting Vulnerabilities
|
||||
You can report vulnerabilities, errors & bugs using one of the following methods:
|
||||
- Create an issue on GitHub!
|
||||
- Create a ticket in our [discord server](https://discord.dj-dj.be)!
|
||||
- Message @DJj123dj in DM on discord!
|
||||
- Send an E-mail to [support@dj-dj.be](mailto:support@dj-dj.be)!
|
||||
|
||||
When you report a problem, please **give a small description** about what & how it happend.<br>
|
||||
Try to explain the issue in as much detail as possible.
|
||||
|
||||
If possible, try to provide screenshots!
|
||||
|
||||
### Please upload the `otdebug.txt` file together with your bug report!
|
||||
|
||||
---
|
||||
<img src="https://apis.dj-dj.be/cdn/openticket/logo.png" alt="Open Ticket Logo" width="170px">
|
||||
|
||||
**Security Policy**<br>
|
||||
[changelog](https://otgithub.dj-dj.be/releases) - [documentation](https://otdocs.dj-dj.be) - [tutorial](https://www.youtube.com/watch?v=2jK9kAf6ASU) - [website](https://openticket.dj-dj.be) - [discord](https://discord.dj-dj.be)<br>
|
||||
|
||||
© 2024 - [DJdj Development](https://www.dj-dj.be) - [Terms](https://www.dj-dj.be/terms#terms) - [Privacy Policy](https://www.dj-dj.be/terms#privacy)
|
||||
Reference in New Issue
Block a user