Merge branch 'main' into mailpit

.editorconfig

@@ -6,7 +6,7 @@ root = true
 
 [*]
 charset = utf-8
-indent_size = 2
+indent_size = 4
 indent_style = space
 end_of_line = lf
 insert_final_newline = true

.github/CODEOWNERS

@@ -0,0 +1 @@
+*	@N6REJ

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,134 @@
+
+# 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, caste, color, 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
+[Contact Us](mailto:abuse@bearsampp.com)
+
+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.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+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 the FAQ at
+[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

.github/CONTRIBUTING.md

@@ -0,0 +1,5 @@
+# Contributing guidelines
+
+Please read [the 'Contribute' official page](https://bearsampp.com/contribute).
+
+You are also bound by our [Contributors Code of Conduct](https://bearsampp.com/code-of-conduct).

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: N6REJ
+custom: https://www.paypal.me/BearLeeAble

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a report to help us improve
+---
+
+### Behaviour
+
+#### Steps to reproduce this issue
+
+1.
+2.
+3.
+
+#### Expected behaviour
+
+> Tell me what should happen
+
+#### Actual behaviour
+
+> Tell me what happens instead
+
+### Configuration
+
+* Bearsampp version and the previous version in case of upgrade: 
+* Operating system: 
+
+### Logs
+
+>* Close Bearsampp.
+>* Change the `logsVerbose` variable to the value `2` in the `bearsampp.conf` file.
+>* Launch Bearsampp and reproduce your issue.
+>* Close Bearsampp.
+>* Zip the `logs` folder and the `core/tmp` folder.
+>* [Drag and drop](https://help.github.com/en/github/managing-your-work-on-github/file-attachments-on-issues-and-pull-requests) the zip archive here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/module_request.md

@@ -0,0 +1,13 @@
+---
+name: Module request
+about: Do you want a new module to be added?
+labels: ":bulb: feature request, :package: module"
+---
+
+> Please follow this guide to file a proper request report : http://bearsampp.com/request
+
+* Name: 
+* Description: 
+* Website: 
+* License (e.g. Freeware, OSS, GPL, MIT, etc): 
+* Comment (anything else which might help): 

.github/SUPPORT.md

@@ -0,0 +1,20 @@
+<h1 class="intro-header text-center">Reporting an issue</h1>
+<h3 id="before-submitting-an-issue">Before submitting an issue</h3>
+<span>Please do a search in <a href="https://github.com/bearsampp/bearsampp/issues" target="_blank" class="docs-creator" rel="noopener">open issues</a> to see if the issue or feature request has already been filed and read the <a href="https://bearsampp.com/faq/" class="docs-creator">FAQ</a> page first.<br /></span><span>If you find your issue already exists, make relevant comments and add your <a href="https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments" target="_blank" class="docs-creator" rel="noopener">reaction</a>.<br />Use a reaction like </span> <span><img title="+1" alt="" src="https://github.githubassets.com/images/icons/emoji/unicode/1f44d.png" height="16" width="16" /> - upvote or </span> <span><img title="-1" alt="" src="https://github.githubassets.com/images/icons/emoji/unicode/1f44e.png" height="16" width="16" /> - downvote in place of a “+1” comment.<br /></span> <span>If you cannot find an existing issue that describes your bug or feature, submit an issue using the guidelines below.</span>
+<p></p>
+<h3 id="writing-good-bug-reports-and-feature-requests">Writing good bug reports and feature requests</h3>
+<span>File a single issue per problem and feature request.</span>
+<ul>
+<li>Do not enumerate multiple bugs or feature requests in the same issue.</li>
+<li>Do not add your issue as a comment to an existing issue unless it’s for the identical input. Many issues look similar, but have different causes.</li>
+<li>Do include images and/or video if it helps explain your issue better.</li>
+<li>Do not use any language other then english</li>
+</ul>
+<span>The more information you can provide, the more likely someone will be successful in reproducing the issue and finding a fix.</span>
+<span>You are now ready to <a href="https://github.com/bearsampp/bearsampp/issues/new/choose" target="_blank" class="docs-creator" rel="noopener">create a new issue</a>!</span>
+<p></p>
+<h3 id="closure-policy">Closure policy</h3>
+<ul>
+<li>Issues that don’t have the information requested above (when applicable) will be closed immediately and the poster directed to the support guidelines.</li>
+<li>Issues that go a week without a response from original poster are subject to closure at our discretion.</li>
+</ul>

.github/auto-comment.yml

@@ -0,0 +1,10 @@
+# Comment to a new issue.
+issueOpened: >
+  Thank your for raising a issue. We will try and get back to you as soon as possible.
+
+  Please make sure you have given us as much context as possible.
+
+pullRequestOpened: >
+  Thank your for raising your pull request.
+
+  Please make sure you have followed our contributing guidelines. We will review it as soon as possible

.github/auto-merge.yml

@@ -0,0 +1,11 @@
+- match:
+    dependency_type: development
+    update_type: semver:minor # includes patch updates!
+
+- match:
+    dependency_type: production
+    update_type: security:minor # includes patch updates!
+
+- match:
+    dependency_type: production
+    update_type: semver:patch

.github/dependabot.yml

@@ -0,0 +1,15 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "daily"
+      time: "08:00"
+      timezone: "America/Chicago"
+    labels:
+      - ":robot: bot"
+
+permissions:
+  pull-requests: write
+  issues: write
+  repository-projects: write

.github/labels.yml

@@ -0,0 +1,101 @@
+## more info https://github.com/crazy-max/ghaction-github-labeler
+- # bot
+  name: "bot :robot:"
+  color: "69cd00"
+  description: "Used by bots"
+- # bug
+  name: "bug :bug:"
+  color: "b60205"
+  description: "For known bugs"
+  from_name: "bug"
+- # Urgent
+  name: "Urgent :bomb:"
+  color: "ED7014"
+  description: "Urgent"
+- # dependencies
+  name: "dependencies :man_cook:"
+  color: "0366d6"
+  description: "Dependencies need fixed"
+- # documentation
+  name: "documentation :books:"
+  color: "c5def5"
+  description: ""
+  from_name: "documentation"
+- # duplicate
+  name: "duplicate :busts_in_silhouette:"
+  color: "cccccc"
+  description: "Duplicate"
+- # enhancement
+  name: "enhancement :sparkles:"
+  color: "0054ca"
+  description: "Improve program"
+- # feature request
+  name: "feature request :bulb:"
+  color: "0e8a16"
+  description: "Feature Request"
+- # feedback
+  name: "feedback :mega:"
+  color: "03a9f4"
+  description: ""
+  from: "question"
+- # future maybe
+  name: "future maybe :rocket:"
+  color: "fef2c0"
+  description: "Something to consider"
+- # good first issue
+  name: "good first issue :hatching_chick:"
+  color: "7057ff"
+  description: "Should be easy"
+  from: ":hatching_chick: good first issue"
+- # help wanted
+  name: "help wanted :pray:"
+  color: "4caf50"
+  description: "Need Help"
+  from: "help wanted"
+- # hold
+  name: "hold :hand:"
+  color: "24292f"
+  description: "Hold for later version"
+- # invalid
+  name: "invalid :no_entry_sign:"
+  color: "e6e6e6"
+  description: "Not a bug"
+- # needs more info
+  name: "needs more info :thinking:"
+  color: "795548"
+  description: "Need Info"
+- # Blocker
+  name: "Blocker :triangular_flag_on_post:"
+  color: "ff0000"
+  description: "Show Stopper"
+- # Website
+  name: "Website :technologist:"
+  color: "FFFFFF"
+  description: "Our website"
+- # Security
+  name: "Security :closed_lock_with_key:"
+  color: "CD5C5C"
+  description: "Security issue"
+- # Has PR
+  name: "PR :scientist:"
+  color: "FFFFFF"
+  description: "Has PR"
+- # RTC
+  name: "RTC :runner:"
+  color: "87ceeb"
+  description: "Ready to commit"
+- # Sync
+  name: "Sync :arrow_forward:"
+  color: "87ceeb"
+  description: "Sync Action"
+  from_name: "sync"
+- # Won't fix
+  name: "Wont_fix_it :man_mechanic:"
+  color: "b45f06"
+  description: "Won't fix"
+  from_name: "wontfix"
+- # Hacktoberfest
+  name: "Hacktoberfest-Accepted :mending_heart:"
+  description: "Accepted for Hacktoberfest"
+  from_name: "Hacktoberfest accepted"
+