Stage new submodule locations

submodules/ModernZ/.github/CODE_OF_CONDUCT.md

@@ -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
+ModernZ Github Issues.
+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.

submodules/ModernZ/.github/CONTRIBUTING.md

@@ -0,0 +1,99 @@
+How to contribute
+=================
+
+General
+-------
+
+All contributions are generally welcomed. We always appreciate the effort and time taken by others to improve or fix ModernZ.
+
+If you're hesitant or not sure about a specific contribution, you can always open an issue to ask a question or discuss something in detail to see if your contribution goes with ModernZ plans or not.
+
+Main project goals
+------------------
+
+- Revive and maintain the modern osc origin, as it is either abandoned or partially maintained by adding new code without fixing the old.
+- Apply common features that are missing and most users would want (ie: customization, button functions, lists and so on)
+
+ModernZ is trying to be in a middle area between stock OSC and a project like uosc. One is too simple, the other is too complicated.
+
+One of the first things that happened in ModernZ was to re-base on stock osc and integrate features that mpv already has, which eliminated a ton of bloat from the code.
+
+In essence, we want to be better than stock OSC, but we don't want to do everything. That is why for example we integrated locale as extras, and the same thing was done for the pause indicator. 
+
+If it's useful, but not necessary to the OSC, it should be in extras or an independent script. Modular methodology.
+
+Sending patches
+---------------
+
+- Make a GitHub pull request.
+- Plain diffs posted as pastebins are not acceptable. They only cause extra work for everyone, because they lack
+  commit message and authorship information.
+- Be sure to test your changes. If you didn't, please say so in the commit
+  message and the pull request text.
+
+Write good commit messages
+--------------------------
+
+- Write informative commit messages. Use present tense to describe the
+  situation with the patch applied, and past tense for the situation before
+  the change.
+- The subject line (the first line in a commit message) must contain an
+  identifying prefix, followed by a short description what
+  impact this commit has on ModernZ osc.
+
+Split changes into multiple commits
+-----------------------------------
+
+- Follow git good practices, and split independent changes into several commits.
+  It's usually OK to put them into a single pull request.
+- Try to separate cosmetic and functional changes. It's ok to make a few
+  additional cosmetic changes in the same file you're working on. However, don't do
+  something like reformatting a whole file, and hiding an actual functional
+  change in the same commit.
+- Splitting changes does _not_ mean that you should make them as fine-grained
+  as possible. Commits should form logical steps in development. The way you
+  split changes is important for code review and analyzing bugs.
+- We prefer to have pull requests in a merge
+  ready state.
+
+Touching user-visible elements may require updating the docs
+-------------------------------------------------------------
+
+- Most user-visible elements are normally documented in docs/. If your commit
+  touches documented behavior, list of options, etc., you need to adjust the
+  documentation.
+- These changes usually go into the same commit that changes the code.
+
+Code of Conduct
+---------------
+
+Please note that this project is released with a Contributor Code of Conduct.
+By participating in this project you agree to abide by its terms.
+The Contributor Code of Conduct can be found here:
+https://www.contributor-covenant.org/version/2/0/code_of_conduct/
+
+Copyright of contributions
+--------------------------
+
+- The copyright belongs to contributors. The project is a collaborative work. By
+  sending your changes, you agree to license your contributions according to the
+  requirements of this project.
+- All new code must be LGPLv2.1+ licensed, or come with the implicit agreement
+  that it will be relicensed to LGPLv2.1+ later.
+- 100% compatible licenses are allowed too.
+- Changes in files with more liberal licenses (such as BSD, MIT, or ISC) are
+  assumed to be dual-licensed under LGPLv2.1+ and the license indicated in the
+  file header.
+- You must be either the exclusive author of the patch, or acknowledge all
+  authors involved in the commit message. If you take 3rd party code, authorship
+  and copyright must be properly acknowledged. If you're making changes on
+  behalf of your employer, and the employer owns the copyright, you must mention
+  this. If the license of the code is not LGPLv2.1+, you must mention this.
+- These license statements are legally binding.
+- Don't use fake names (something that looks like an actual name, and may be
+  someone else's name, but is not your legal name). Using a pseudonym is
+  allowed if it can be used to identify or contact you, even if whatever
+  account you used to submit the patch dies.
+- Do not add your name to the license header. This convention is not used by
+  this project, and neither copyright law nor any of the used licenses require
+  it.

submodules/ModernZ/.github/ISSUE_TEMPLATE/1_feature_request.yml

@@ -0,0 +1,15 @@
+name: "Request a new Feature"
+description: "Create a request for a new feature"
+labels: ["feature request"]
+body:
+- type: textarea
+  attributes:
+      label: "Expected behavior of the wanted feature"
+      description: >
+          Before requesting a new feature, make sure it hasn't been
+          [requested yet](https://github.com/Samillion/ModernZ/labels/feature%20request).
+
+          If you are not sure about this, please read 
+          [FAQ and guidelines](https://github.com/Samillion/ModernZ/blob/main/docs/FAQ.md) first.
+  validations:
+      required: true

submodules/ModernZ/.github/ISSUE_TEMPLATE/2_bug_report.yml

@@ -0,0 +1,74 @@
+name: "Report an issue or a bug"
+description: "Create a report for an issue or a bug"
+labels: ["bug"]
+body:
+- type: textarea
+  attributes:
+      label: "mpv Information"
+      placeholder: |
+          mpv v0.39.0-300-g42ff6f92 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
+           built on Nov  3 2024 00:06:03
+          libplacebo version: v7.349.0 (v7.349.0-19-g118d810-dirty)
+          FFmpeg version: N-117698-gc325f9c61
+          FFmpeg library versions:
+             libavcodec      61.23.100
+             libavdevice     61.4.100
+             libavfilter     10.6.101
+             libavformat     61.9.100
+             libavutil       59.46.100
+             libswscale      8.9.101
+      description: |
+          Provide the output of `mpv --version`.
+      render: bash
+  validations:
+      required: false
+- type: textarea
+  attributes:
+      label: "Reproduction Steps"
+      description: >
+          Try to reproduce your issue with `--no-config` and mpv's stock osc first. If it is reproducible
+          even then, try to find out which option or script causes your issue.
+
+
+          Describe the reproduction steps as precise as possible. It's very likely that
+          the bug you experience wasn't reproduced by the developer because the workflow
+          differs from your own.
+  validations:
+      required: true
+- type: textarea
+  attributes:
+      label: "Expected Behavior"
+      placeholder: "What were you expecting?"
+  validations:
+      required: true
+- type: textarea
+  attributes:
+      label: "Actual Behavior"
+      placeholder: "What happened instead?"
+  validations:
+      required: true
+- type: textarea
+  attributes:
+      label: "Log File"
+      placeholder: "Drag and drop log file here (Don't paste content directly)"
+      description: >
+          Make a log file with `--log-file=output.txt` and
+          attach it to the issue. [[details](https://mpv.io/manual/master/#options-log-file)]
+
+
+          If you have trouble producing a log file, you can alternatively use `-v -v`,
+          save the terminal output to a file, and attach it to the issue.
+
+
+          Disclaimer: The log file may contain identifiable information, such as your username.
+          Review the log file before sharing and redact any sensitive data if necessary.
+  validations:
+      required: false
+- type: checkboxes
+  attributes:
+      label: "I carefully read all instructions and confirm that I did the following:"
+      options:
+          - label: "I tested with the latest mpv version to validate that the issue is not already fixed."
+            required: true
+          - label: "I provided all required information."
+            required: true

submodules/ModernZ/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: FAQ and guidelines (Important)
+    url: https://github.com/Samillion/ModernZ/blob/main/docs/FAQ.md
+    about: Frequent questions are answered there, also includes useful guidelines
+  - name: Discussions and Questions
+    url: https://github.com/Samillion/ModernZ/discussions
+    about: A place to discuss or ask a general question regarding ModernZ osc

submodules/ModernZ/.github/PULL_REQUEST_TEMPLATE

@@ -0,0 +1,7 @@
+Read this before you submit a pull request please:
+https://github.com/Samillion/ModernZ/blob/main/.github/CONTRIBUTING.md
+
+Reading this link and following the rules will get your pull request reviewed
+and merged faster.
+
+Delete this message after reading the link