Merge branch 'main' into tmo-main

Author: nightly-merge

.github/ISSUE_TEMPLATE/001_bug_report.md

@@ -0,0 +1,57 @@
+---
+name: Bug report
+about: Create a report to help us improve Zephyr
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Notes (delete this)**
+Github Discussions (https://github.com/zephyrproject-rtos/zephyr/discussions)
+are available to first verify that the issue is a genuine Zephyr bug and not a
+consequence of Zephyr services misuse.
+
+This issue list is only for bugs in the main Zephyr code base
+(https://github.com/zephyrproject-rtos/zephyr/). If the bug is for a project
+fork (such as NCS) specific feature, please open an issue in the fork project
+instead.
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+Please also mention any information which could help others to understand
+the problem you're facing:
+ - What target platform are you using?
+ - What have you tried to diagnose or workaround this issue?
+ - Is this a regression? If yes, have you been able to "git bisect" it to a
+   specific commit?
+ - ...
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. mkdir build; cd build
+2. cmake -DBOARD=board\_xyz
+3. make
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Impact**
+What impact does this issue have on your progress (e.g., annoyance, showstopper)
+
+**Logs and console output**
+If applicable, add console logs or other types of debug information
+e.g Wireshark capture or Logic analyzer capture (upload in zip archive).
+copy-and-paste text and put a code fence (\`\`\`) before and after, to help
+explain the issue. (if unable to obtain text log, add a screenshot)
+
+**Environment (please complete the following information):**
+ - OS: (e.g. Linux, MacOS, Windows)
+ - Toolchain (e.g Zephyr SDK, ...)
+ - Commit SHA or Version used
+
+**Additional context**
+Add any other context that could be relevant to your issue, such as pin setting,
+target configuration, ...

.github/ISSUE_TEMPLATE/002_enhancement.md

@@ -0,0 +1,20 @@
+---
+name: Enhancement
+about: Suggest enhancements to existing features
+title: ''
+labels: Enhancement
+assignees: ''
+
+---
+
+**Is your enhancement proposal related to a problem? Please describe.**
+A clear and concise description of what the problem is.
+
+**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 graphics (drag-and-drop an image) about the feature request here.

.github/ISSUE_TEMPLATE/003_rfc-proposal.md

@@ -0,0 +1,51 @@
+---
+name: RFC / Proposal
+about: Submit an RFC / Proposal
+title: ''
+labels: RFC
+assignees: ''
+
+---
+
+## Introduction
+
+This section targets end users, TSC members, maintainers and anyone else that might
+need a quick explanation of your proposed change.
+
+### Problem description
+
+Why do we want this change and what problem are we trying to address?
+
+### Proposed change
+
+A brief summary of the proposed change - the 10,000 ft view on what it will
+change once this change is implemented.
+
+## Detailed RFC
+
+In this section of the document the target audience is the dev team. Upon
+reading this section each engineer should have a rather clear picture of what
+needs to be done in order to implement the described feature.
+
+### Proposed change (Detailed)
+
+This section is freeform - you should describe your change in as much detail
+as possible. Please also ensure to include any context or background info here.
+For example, do we have existing components which can be reused or altered.
+
+By reading this section, each team member should be able to know what exactly
+you're planning to change and how.
+
+### Dependencies
+
+Highlight how the change may affect the rest of the project (new components,
+modifications in other areas), or other teams/projects.
+
+### Concerns and Unresolved Questions
+
+List any concerns, unknowns, and generally unresolved questions etc.
+
+## Alternatives
+
+List any alternatives considered, and the reasons for choosing this option
+over them.

.github/ISSUE_TEMPLATE/004_feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: Feature Request
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is.
+
+**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 graphics (drag-and-drop an image) about the feature request here.

.github/ISSUE_TEMPLATE/005_hardware_support.md

@@ -0,0 +1,19 @@
+---
+name: Hardware Support
+about: Suggest adding hardware support
+title: ''
+labels: Hardware Support
+assignees: ''
+
+---
+
+**Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.**
+Describe in details the hardware support being requested and why this support benefits Zephyr.
+
+**Describe why you are asking for this support?**
+Describe why you are asking for this support instead of contributing it directly to the tree
+
+If this is a new board or SoC, please state whether you are willing to maintain the Zephyr support for it if it is included in the main tree
+
+**Additional context**
+Add any other context or graphics (drag-and-drop an image) about the hardware here.

.github/ISSUE_TEMPLATE/006_nomination.md

@@ -0,0 +1,42 @@
+---
+name: Contributor Nomination
+about: Nominate a GitHub user for additional rights on the Zephyr Project
+title: ''
+labels: Role Nomination
+assignees: ''
+
+---
+
+# Background
+
+The [TSC Project Roles] defines the main roles for the Zephyr Project, including
+Maintainer, Collaborator, and Contributor.
+
+By default anyone that contributes code or documentation is a Contributor, but
+with the lowest [GitHub Permission Level] of Read. For example, Contributors
+with Read permission do not have the permission to add reviewers to a pull
+request.
+
+Use this template to nominate a GitHub user for the Contributor role with
+Triage permission level, which allows the user to add reviewers to a pull
+request and be added as a reviewer by other users.
+
+# Nomination
+
+## GitHub User
+
+Provide the following information about the GitHub user:
+
+1. Full Name
+1. GitHub username
+1. Organization (optional)
+
+## Supporting Documents
+
+Add links to 3-5 GitHub pull requests, in the Zephyr project, authored or
+reviewed by the GitHub user that demonstrate the user's dedication to the
+Zephyr project.
+
+
+[TSC Project Roles]: <https://docs.zephyrproject.org/latest/project/project_roles.html>
+[GitHub Permission Level]: <https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization>

.github/ISSUE_TEMPLATE/007_ext-source.md

@@ -0,0 +1,68 @@
+---
+name: External Source Code
+about: Submit a proposal to integrate external source code
+title: ''
+labels: TSC
+assignees: ''
+
+---
+
+## Origin
+
+Name of project hosting the original open source code
+Provide a link to the source
+
+## Purpose
+
+Brief description of what this software does
+
+## Mode of integration
+
+Describe whether you'd like to integrate this external component in the main tree
+or as a module, and why. If the mode of integration is a module, suggest a
+repository name for the module
+
+## Maintainership
+
+List the person(s) that will be maintaining the integration of this external code
+for the foreseeable future. Please use GitHub IDs to identify them. You can
+choose to identify a single maintainer only or add collaborators as well
+
+## Pull Request
+
+Pull request (if any) with the actual implementation of the integration, be it
+in the main tree or as a module (pointing to your own fork for now). Make sure
+the PR is correctly labeled as "DNM"
+
+## Description
+
+Long description that will help reviewers discuss suitability of the
+component to solve the problem at hand (there may be a better options
+available.)
+
+What is its primary functionality (e.g., SQLLite is a lightweight
+database)?
+
+What problem are you trying to solve? (e.g., a state store is
+required to maintain ...)
+
+Why is this the right component to solve it (e.g., SQLite is small,
+easy to use, and has a very liberal license.)
+
+## Dependencies
+
+What other components does this package depend on?
+
+Will the Zephyr project have a direct dependency on the component, or
+will it be included via an abstraction layer with this component as a
+replaceable implementation?
+
+## Revision
+
+Version or SHA you would like to integrate initially
+
+## License
+
+Please use an SPDX identifier (https://spdx.org/licenses/), such as
+``BSD-3-Clause``
+

.github/ISSUE_TEMPLATE/008_bin-blobs.md

@@ -0,0 +1,41 @@
+---
+name: Binary blobs
+about: Submit a proposal to integrate binary blob(s)
+title: ''
+labels: TSC
+assignees: ''
+
+---
+
+## Origin
+
+Describe where the binary blob(s) originate from
+
+## Type
+
+- [ ] Precompiled library
+- [ ] Firmware image
+
+## Module
+
+The Zephyr module that this blob(s) will be referenced from
+
+## Purpose
+
+Brief description of what the blob(s) do. It is especially important to describe
+the functionality that the blob(s) provide, to the largest extent possible
+
+## Pull Request
+
+Link to the Pull request with the actual implementation of the integration. If
+you are submitting this as part of a new module you may link to the same Pull
+Request that introduced the new module.
+
+## Dependencies
+
+What other components do the blob(s) depend on, if any?
+
+## License
+
+Document the license the blob(s) are distributed under
+

.github/workflows/assigner.yml

@@ -0,0 +1,38 @@
+name: Pull Request Assigner
+
+on:
+  pull_request_target:
+    types:
+    - opened
+    - synchronize
+    - reopened
+    - ready_for_review
+    branches:
+    - main
+    - v*-branch
+
+jobs:
+  assignment:
+    name: Pull Request Assignment
+    if: github.event.pull_request.draft == false
+    runs-on: ubuntu-22.04
+
+    steps:
+    - name: Install Python dependencies
+      run: |
+        sudo pip3 install -U setuptools wheel pip
+        pip3 install -U PyGithub>=1.55
+
+    - name: Check out source code
+      uses: actions/checkout@v3
+
+    - name: Run assignment script
+      env:
+        GITHUB_TOKEN: ${{ secrets.ZB_GITHUB_TOKEN }}
+      run: |
+        python3 scripts/set_assignees.py \
+          -v \
+          -o ${{ github.event.repository.owner.login }} \
+          -r ${{ github.event.repository.name }} \
+          -M MAINTAINERS.yml \
+          -P ${{ github.event.pull_request.number }}

.github/workflows/backport.yml

@@ -0,0 +1,31 @@
+name: Backport
+on:
+  pull_request_target:
+    types:
+      - closed
+      - labeled
+    branches:
+      - main
+
+jobs:
+  backport:
+    name: Backport
+    runs-on: ubuntu-22.04
+    # Only react to merged PRs for security reasons.
+    # See https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target.
+    if: >
+      github.event.pull_request.merged &&
+      (
+        github.event.action == 'closed' ||
+        (
+          github.event.action == 'labeled' &&
+          contains(github.event.label.name, 'backport')
+        )
+      )
+    steps:
+      - name: Backport
+        uses: zephyrproject-rtos/[email protected]
+        with:
+          github_token: ${{ secrets.ZB_GITHUB_TOKEN }}
+          issue_labels: Backport
+          labels_template: '["Backport"]'