Merge branch 'master' into pywin32

.github/workflows/ci_ubuntu.yml

@@ -47,7 +47,7 @@ jobs:
         tests
 
     - name: Upload Coverage
-      if: github.event_name == 'push' && github.ref == 'refs/head/master'
+      if: github.event_name == 'push' && github.ref == 'refs/heads/master'
       env:
           COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }}
       run: |

.github/workflows/no-response.yml

@@ -0,0 +1,30 @@
+name: No Response
+
+# Both `issue_comment` and `scheduled` event types are required for this Action
+# to work properly.
+on:
+  issue_comment:
+    types: [created]
+  schedule:
+    # Schedule for five minutes after the hour, every hour
+    - cron: '5 * * * *'
+
+jobs:
+  noResponse:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: lee-dohm/no-response@9bb0a4b5e6a45046f00353d5de7d90fb8bd773bb
+        # This commit hash targets release v0.5.0 of lee-dohm/no-response.
+        # Targeting a commit hash instead of a tag has been done for security reasons.
+        # Please be aware that the commit hash specifically targets the "Automatic compilation"
+        # done by `github-actions[bot]` as the `no-response` Action needs to be compiled.
+        with:
+          token: ${{ github.token }}
+          daysUntilClose: 42
+          responseRequiredLabel: 'awaiting-reply'
+          closeComment: >
+                This issue has been automatically closed because there has been no response
+                to our request for more information from the original author. With only the
+                information that is currently in the issue, we don't have the means
+                to take action. Please reach out if you have or find the answers we need so
+                that we can investigate further.

.github/workflows/support.yml

@@ -0,0 +1,27 @@
+name: 'Support Requests'
+
+on:
+  issues:
+    types: [labeled, unlabeled, reopened]
+
+permissions:
+  issues: write
+
+jobs:
+  action:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: dessant/support-requests@v4
+        with:
+          github-token: ${{ github.token }}
+          support-label: 'support'
+          issue-comment: >
+            👋 We use the issue tracker exclusively for bug reports and feature requests.
+            However, this issue appears to be a support request. Please use our
+            [support channels](https://github.com/kivy/plyer/blob/master/CONTACT.md)
+            to get help with the project.
+            
+            Let us know if this comment was made in error, and we'll be happy
+            to reopen the issue.
+          close-issue: true
+          lock-issue: false

.readthedocs.yaml

@@ -0,0 +1,16 @@
+# Read the Docs configuration file for Sphinx projects
+# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
+
+version: 2
+
+build:
+  os: ubuntu-22.04
+  tools:
+    python: "3"
+
+python:
+  install:
+    - requirements: docs/requirements.txt
+
+sphinx:
+  configuration: docs/source/conf.py

CODE_OF_CONDUCT.md

@@ -0,0 +1,8 @@
+In the interest of fostering an open and welcoming community, we as 
+contributors and maintainers need to ensure participation in our project and 
+our sister projects is a harassment-free and positive experience for everyone. 
+It is vital that all interaction is conducted in a manner conveying respect, 
+open-mindedness and gratitude.
+
+Please consult the [latest Kivy Code of Conduct](https://github.com/kivy/kivy/blob/master/CODE_OF_CONDUCT.md).
+

CONTACT.md

@@ -0,0 +1,8 @@
+.. _contact:
+
+Contact Us
+==========
+
+If you are looking to contact the Kivy Team (who are responsible for managing the
+Plyer project), including looking for support, please see our
+`latest contact details <https://github.com/kivy/kivy/blob/master/CONTACT.md>`_.

CONTRIBUTING.md

@@ -0,0 +1,10 @@
+# Contribution Guidelines
+
+Plyer is part of the [Kivy](https://kivy.org) ecosystem - a large group of
+products used by many thousands of developers for free, but it
+is built entirely by the contributions of volunteers. We welcome (and rely on) 
+users who want to give back to the community by contributing to the project.
+
+Contributions can come in many forms. See the latest 
+[Contribution Guidelines](https://github.com/kivy/kivy/blob/master/CONTRIBUTING.md)
+for how you can help us.

FAQ.md

@@ -0,0 +1,13 @@
+# FAQ for Plyer
+
+## Introduction
+
+Plyer is a platform-independent Python API for accessing hardware features
+of various platforms (Android, iOS, macOS, Linux and Windows).
+
+Plyer is managed by the [Kivy Team](https://kivy.org/about.html). It is suitable for
+use with Kivy apps, but can be used independently.
+
+## No questions yet
+
+No Frequently Asked Questions have been identified yet. Please contribute some.

LICENSE

@@ -1,4 +1,6 @@
-Copyright (c) 2010-2017 Kivy Team and other contributors
+MIT License
+
+Copyright (c) 2010-2023 Kivy Team and other contributors
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal