Skip to content

Commit a048710

Browse files
Snap-ASnap-A
authored
Merge branch 'main' into add_ti_x311_driver
2 parents a7802d0 + e85c5b6 commit a048710

File tree

6,983 files changed

+268318
-72871
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

6,983 files changed

+268318
-72871
lines changed

‎.clang-format‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,7 @@ ForEachMacros:
8282
- 'HTTP_SERVICE_FOREACH_RESOURCE'
8383
- 'I3C_BUS_FOR_EACH_I3CDEV'
8484
- 'I3C_BUS_FOR_EACH_I2CDEV'
85+
- 'MIN_HEAP_FOREACH'
8586
IfMacros:
8687
- 'CHECKIF'
8788
# Disabled for now, see bug https://github.com/zephyrproject-rtos/zephyr/issues/48520

‎.github/ISSUE_TEMPLATE/002_enhancement.md‎

Lines changed: 0 additions & 28 deletions
This file was deleted.

‎.github/ISSUE_TEMPLATE/002_enhancement.yml‎

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
name: Enhancement
2+
description: Submit an Enhancement
3+
labels: ["Enhancement"]
4+
type: "Enhancement"
5+
assignees: []
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
Thanks for taking the time to fill out this enhancement proposal.
11+
- type: textarea
12+
id: description
13+
attributes:
14+
label: Summary
15+
description: |
16+
Is your enhancement proposal related to a problem? Please describe.
17+
placeholder: |
18+
A clear and concise description of what the problem is.
19+
validations:
20+
required: true
21+
- type: textarea
22+
id: solution
23+
attributes:
24+
label: Describe the solution you'd like
25+
description: |
26+
Describe the solution you'd like
27+
placeholder: |
28+
A clear and concise description of what you want to happen.
29+
validations:
30+
required: true
31+
- type: textarea
32+
id: alternatives
33+
attributes:
34+
label: Alternatives
35+
description: Describe alternatives you've considered
36+
placeholder: |
37+
A clear and concise description of any alternative solutions or features you've considered.
38+
- type: textarea
39+
id: context
40+
attributes:
41+
label: Additional Context
42+
description: Add any other context or graphics (drag-and-drop an image) about the enhancement here.

‎.github/ISSUE_TEMPLATE/003_rfc-proposal.md‎

Lines changed: 0 additions & 60 deletions
This file was deleted.

‎.github/ISSUE_TEMPLATE/003_rfc-proposal.yml‎

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
name: RFC / Proposal
2+
description: Submit a Proposal (RFC)
3+
labels: ["RFC"]
4+
type: RFC
5+
assignees: []
6+
body:
7+
- type: markdown
8+
attributes:
9+
value: |
10+
## Introduction
11+
12+
This section targets end users, TSC members, maintainers and anyone else
13+
that might need a quick explanation of your proposed change.
14+
15+
- type: textarea
16+
id: problem-description
17+
attributes:
18+
label: Problem Description
19+
description: Why do we want this change and what problem are we trying to address?
20+
placeholder: Explain the problem or limitation this RFC is meant to resolve.
21+
validations:
22+
required: true
23+
24+
- type: textarea
25+
id: proposed-change-summary
26+
attributes:
27+
label: Proposed Change (Summary)
28+
description: A high-level summary of the proposed change.
29+
placeholder: Brief summary of what will change if this RFC is implemented.
30+
validations:
31+
required: true
32+
33+
- type: markdown
34+
attributes:
35+
value: |
36+
## Detailed RFC
37+
38+
This section targets the development team. Upon reading it, each engineer
39+
should understand what must be done to implement the proposed feature.
40+
41+
- type: textarea
42+
id: detailed-change
43+
attributes:
44+
label: Proposed Change (Detailed)
45+
description: Describe the change in as much detail as possible. Include context or background info, and reuse of existing components if applicable.
46+
placeholder: Explain exactly what you’re planning to change and how.
47+
validations:
48+
required: true
49+
50+
- type: textarea
51+
id: dependencies
52+
attributes:
53+
label: Dependencies
54+
description: Highlight how this change may affect the rest of the project or other teams/components.
55+
placeholder: List components, modules, or teams affected.
56+
validations:
57+
required: false
58+
59+
- type: textarea
60+
id: concerns
61+
attributes:
62+
label: Concerns and Unresolved Questions
63+
description: List any concerns, unknowns, or unresolved questions related to this proposal.
64+
placeholder: Any areas of uncertainty?
65+
validations:
66+
required: false
67+
68+
- type: textarea
69+
id: alternatives
70+
attributes:
71+
label: Alternatives Considered
72+
description: What alternative solutions were considered? Why was this proposal chosen?
73+
placeholder: List alternatives and explain the rationale behind your choice.
74+
validations:
75+
required: false

‎.github/ISSUE_TEMPLATE/004_feature_request.md‎

Lines changed: 0 additions & 28 deletions
This file was deleted.

‎.github/ISSUE_TEMPLATE/004_feature_request.yml‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
name: Feature Request
2+
description: Suggest a new feature or enhancement
3+
labels: ["Feature Request"]
4+
type: Feature
5+
assignees: []
6+
body:
7+
- type: textarea
8+
id: problem
9+
attributes:
10+
label: Is your feature request related to a problem? Please describe.
11+
description: A clear and concise description of what the problem is.
12+
placeholder: e.g., I'm frustrated when I need to do X manually because Y is missing.
13+
validations:
14+
required: true
15+
16+
- type: textarea
17+
id: solution
18+
attributes:
19+
label: Describe the solution you'd like
20+
description: A clear and concise description of what you want to happen.
21+
placeholder: e.g., It would be great if the system could automatically handle X by doing Y.
22+
validations:
23+
required: true
24+
25+
- type: textarea
26+
id: alternatives
27+
attributes:
28+
label: Describe alternatives you've considered
29+
description: Include any alternative solutions or features

‎.github/ISSUE_TEMPLATE/006_nomination.md‎

Lines changed: 0 additions & 42 deletions
This file was deleted.

‎.github/ISSUE_TEMPLATE/006_nomination.yml‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
name: Contributor Nomination
2+
description: Nominate a GitHub user for the Contributor role with triage permissions
3+
labels: [Role Nomination]
4+
assignees: ['nashif']
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
## Background
10+
11+
The [TSC Project Roles](https://docs.zephyrproject.org/latest/project/project_roles.html) defines the main roles for the Zephyr Project, including Maintainer, Collaborator, and Contributor.
12+
13+
By default, anyone who contributes code or documentation is a Contributor, but with the lowest [GitHub Permission Level](https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization) of **Read**.
14+
15+
Use this form to nominate a user for the **Contributor** role with **Triage** permission, which allows the user to:
16+
- Add reviewers to pull requests
17+
- Be added as a reviewer by others
18+
19+
- type: input
20+
id: full-name
21+
attributes:
22+
label: Full Name
23+
description: Full name of the nominated contributor.
24+
placeholder: e.g., Jane Doe
25+
validations:
26+
required: true
27+
28+
- type: input
29+
id: github-username
30+
attributes:
31+
label: GitHub Username
32+
description: GitHub handle of the nominated contributor.
33+
placeholder: e.g., @janedoe
34+
validations:
35+
required: true
36+
37+
- type: input
38+
id: organization
39+
attributes:
40+
label: Organization
41+
description: Organization the nominee is affiliated with (optional).
42+
placeholder: e.g., Acme Corp
43+
validations:
44+
required: false
45+
46+
- type: textarea
47+
id: supporting-documents
48+
attributes:
49+
label: Supporting Documents
50+
description: Provide links to 3–5 pull requests authored or reviewed by the nominee that demonstrate their dedication to the Zephyr project.
51+
placeholder: |
52+
e.g.,
53+
- https://github.com/zephyrproject-rtos/zephyr/pull/12345
54+
- https://github.com/zephyrproject-rtos/zephyr/pull/23456
55+
- https://github.com/zephyrproject-rtos/zephyr/pull/34567
56+
validations:
57+
required: true

0 commit comments

Comments
 (0)