Browse Source
Convert all templates to use forms. Signed-off-by: Anas Nashif <anas.nashif@intel.com>pull/90959/head
Anas Nashif
1 month ago
committed by
Benjamin Cabé
10 changed files with 309 additions and 235 deletions
@ -1,28 +0,0 @@
@@ -1,28 +0,0 @@
|
||||
--- |
||||
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. |
||||
--> |
||||
@ -0,0 +1,42 @@
@@ -0,0 +1,42 @@
|
||||
name: Enhancement |
||||
description: Submit an Enhancement |
||||
labels: ["Enhancement"] |
||||
type: "Enhancement" |
||||
assignees: [] |
||||
body: |
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
Thanks for taking the time to fill out this enhancement proposal. |
||||
- type: textarea |
||||
id: description |
||||
attributes: |
||||
label: Summary |
||||
description: | |
||||
Is your enhancement proposal related to a problem? Please describe. |
||||
placeholder: | |
||||
A clear and concise description of what the problem is. |
||||
validations: |
||||
required: true |
||||
- type: textarea |
||||
id: solution |
||||
attributes: |
||||
label: Describe the solution you'd like |
||||
description: | |
||||
Describe the solution you'd like |
||||
placeholder: | |
||||
A clear and concise description of what you want to happen. |
||||
validations: |
||||
required: true |
||||
- type: textarea |
||||
id: alternatives |
||||
attributes: |
||||
label: Alternatives |
||||
description: Describe alternatives you've considered |
||||
placeholder: | |
||||
A clear and concise description of any alternative solutions or features you've considered. |
||||
- type: textarea |
||||
id: context |
||||
attributes: |
||||
label: Additional Context |
||||
description: Add any other context or graphics (drag-and-drop an image) about the enhancement here. |
||||
@ -1,60 +0,0 @@
@@ -1,60 +0,0 @@
|
||||
--- |
||||
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. |
||||
--> |
||||
@ -0,0 +1,75 @@
@@ -0,0 +1,75 @@
|
||||
name: RFC / Proposal |
||||
description: Submit a Proposal (RFC) |
||||
labels: ["RFC"] |
||||
type: RFC |
||||
assignees: [] |
||||
body: |
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
## Introduction |
||||
|
||||
This section targets end users, TSC members, maintainers and anyone else |
||||
that might need a quick explanation of your proposed change. |
||||
|
||||
- type: textarea |
||||
id: problem-description |
||||
attributes: |
||||
label: Problem Description |
||||
description: Why do we want this change and what problem are we trying to address? |
||||
placeholder: Explain the problem or limitation this RFC is meant to resolve. |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: proposed-change-summary |
||||
attributes: |
||||
label: Proposed Change (Summary) |
||||
description: A high-level summary of the proposed change. |
||||
placeholder: Brief summary of what will change if this RFC is implemented. |
||||
validations: |
||||
required: true |
||||
|
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
## Detailed RFC |
||||
|
||||
This section targets the development team. Upon reading it, each engineer |
||||
should understand what must be done to implement the proposed feature. |
||||
|
||||
- type: textarea |
||||
id: detailed-change |
||||
attributes: |
||||
label: Proposed Change (Detailed) |
||||
description: Describe the change in as much detail as possible. Include context or background info, and reuse of existing components if applicable. |
||||
placeholder: Explain exactly what you’re planning to change and how. |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: dependencies |
||||
attributes: |
||||
label: Dependencies |
||||
description: Highlight how this change may affect the rest of the project or other teams/components. |
||||
placeholder: List components, modules, or teams affected. |
||||
validations: |
||||
required: false |
||||
|
||||
- type: textarea |
||||
id: concerns |
||||
attributes: |
||||
label: Concerns and Unresolved Questions |
||||
description: List any concerns, unknowns, or unresolved questions related to this proposal. |
||||
placeholder: Any areas of uncertainty? |
||||
validations: |
||||
required: false |
||||
|
||||
- type: textarea |
||||
id: alternatives |
||||
attributes: |
||||
label: Alternatives Considered |
||||
description: What alternative solutions were considered? Why was this proposal chosen? |
||||
placeholder: List alternatives and explain the rationale behind your choice. |
||||
validations: |
||||
required: false |
||||
@ -1,28 +0,0 @@
@@ -1,28 +0,0 @@
|
||||
--- |
||||
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. |
||||
--> |
||||
@ -0,0 +1,29 @@
@@ -0,0 +1,29 @@
|
||||
name: Feature Request |
||||
description: Suggest a new feature or enhancement |
||||
labels: ["Feature Request"] |
||||
type: Feature |
||||
assignees: [] |
||||
body: |
||||
- type: textarea |
||||
id: problem |
||||
attributes: |
||||
label: Is your feature request related to a problem? Please describe. |
||||
description: A clear and concise description of what the problem is. |
||||
placeholder: e.g., I'm frustrated when I need to do X manually because Y is missing. |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: solution |
||||
attributes: |
||||
label: Describe the solution you'd like |
||||
description: A clear and concise description of what you want to happen. |
||||
placeholder: e.g., It would be great if the system could automatically handle X by doing Y. |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: alternatives |
||||
attributes: |
||||
label: Describe alternatives you've considered |
||||
description: Include any alternative solutions or features |
||||
@ -1,42 +0,0 @@
@@ -1,42 +0,0 @@
|
||||
--- |
||||
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> |
||||
@ -0,0 +1,57 @@
@@ -0,0 +1,57 @@
|
||||
name: Contributor Nomination |
||||
description: Nominate a GitHub user for the Contributor role with triage permissions |
||||
labels: [Role Nomination] |
||||
assignees: ['nashif'] |
||||
body: |
||||
- type: markdown |
||||
attributes: |
||||
value: | |
||||
## Background |
||||
|
||||
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. |
||||
|
||||
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**. |
||||
|
||||
Use this form to nominate a user for the **Contributor** role with **Triage** permission, which allows the user to: |
||||
- Add reviewers to pull requests |
||||
- Be added as a reviewer by others |
||||
|
||||
- type: input |
||||
id: full-name |
||||
attributes: |
||||
label: Full Name |
||||
description: Full name of the nominated contributor. |
||||
placeholder: e.g., Jane Doe |
||||
validations: |
||||
required: true |
||||
|
||||
- type: input |
||||
id: github-username |
||||
attributes: |
||||
label: GitHub Username |
||||
description: GitHub handle of the nominated contributor. |
||||
placeholder: e.g., @janedoe |
||||
validations: |
||||
required: true |
||||
|
||||
- type: input |
||||
id: organization |
||||
attributes: |
||||
label: Organization |
||||
description: Organization the nominee is affiliated with (optional). |
||||
placeholder: e.g., Acme Corp |
||||
validations: |
||||
required: false |
||||
|
||||
- type: textarea |
||||
id: supporting-documents |
||||
attributes: |
||||
label: Supporting Documents |
||||
description: Provide links to 3–5 pull requests authored or reviewed by the nominee that demonstrate their dedication to the Zephyr project. |
||||
placeholder: | |
||||
e.g., |
||||
- https://github.com/zephyrproject-rtos/zephyr/pull/12345 |
||||
- https://github.com/zephyrproject-rtos/zephyr/pull/23456 |
||||
- https://github.com/zephyrproject-rtos/zephyr/pull/34567 |
||||
validations: |
||||
required: true |
||||
@ -1,77 +0,0 @@
@@ -1,77 +0,0 @@
|
||||
--- |
||||
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.) |
||||
|
||||
## Security |
||||
|
||||
Does this component include any cryptographic functionality? |
||||
If so, please describe the cryptographic algorithms and protocols used. |
||||
|
||||
How does this component handle security vulnerabilities and updates? |
||||
Are there any known vulnerabilities in this component? If so, please |
||||
provide details and references to any CVEs or security advisories. |
||||
|
||||
## 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`` |
||||
|
||||
@ -0,0 +1,106 @@
@@ -0,0 +1,106 @@
|
||||
name: External Component Integration |
||||
description: Propose integration of an external open source component |
||||
labels: ["TSC"] |
||||
assignees: [] |
||||
body: |
||||
- type: textarea |
||||
id: origin |
||||
attributes: |
||||
label: Origin |
||||
description: Name of project hosting the original open source code. Provide a link to the source. |
||||
placeholder: e.g., SQLite - https://sqlite.org |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: purpose |
||||
attributes: |
||||
label: Purpose |
||||
description: Brief description of what this software does. |
||||
placeholder: | |
||||
e.g., A small, fast, self-contained SQL database engine. |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: integration-mode |
||||
attributes: |
||||
label: Mode of Integration |
||||
description: Should this be integrated in the main tree or as a module? Explain your choice and suggest a module repo name if applicable. |
||||
placeholder: | |
||||
e.g., As a module - proposed repo name: zephyr-sqlite |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: maintainership |
||||
attributes: |
||||
label: Maintainership |
||||
description: List maintainers (GitHub IDs) for this integration. Include at least one primary maintainer. |
||||
placeholder: | |
||||
e.g., @username1 (primary), @username2 (collaborator) |
||||
validations: |
||||
required: true |
||||
|
||||
- type: input |
||||
id: pull-request |
||||
attributes: |
||||
label: Pull Request |
||||
description: Link to the pull request (if any) for this integration. Must be labeled "DNM" (Do Not Merge). |
||||
placeholder: | |
||||
e.g., https://github.com/zephyrproject-rtos/zephyr/pull/12345 |
||||
validations: |
||||
required: false |
||||
|
||||
- type: textarea |
||||
id: description |
||||
attributes: |
||||
label: Description |
||||
description: Long-form description to justify suitability of this component. |
||||
placeholder: | |
||||
- What is its primary functionality? |
||||
- What problem does it solve? |
||||
- Why is this the right component? |
||||
validations: |
||||
required: true |
||||
|
||||
- type: textarea |
||||
id: security |
||||
attributes: |
||||
label: Security |
||||
description: Security-related aspects of this component, including cryptographic functions and known vulnerabilities. |
||||
placeholder: | |
||||
- Does it use cryptography? |
||||
- How are vulnerabilities handled? |
||||
- Any known CVEs? |
||||
validations: |
||||
required: false |
||||
|
||||
- type: textarea |
||||
id: dependencies |
||||
attributes: |
||||
label: Dependencies |
||||
description: What does this component depend on, and how will it be integrated (directly or via abstraction)? |
||||
placeholder: | |
||||
- Other external packages? |
||||
- Direct or abstracted use in Zephyr? |
||||
validations: |
||||
required: false |
||||
|
||||
- type: input |
||||
id: revision |
||||
attributes: |
||||
label: Version or SHA |
||||
description: Which version or specific commit should be initially integrated? |
||||
placeholder: e.g., v3.45.0 or 79cc94d |
||||
validations: |
||||
required: true |
||||
|
||||
- type: input |
||||
id: license |
||||
attributes: |
||||
label: License (SPDX) |
||||
description: Provide the license using a valid SPDX identifier (e.g., BSD-3-Clause). |
||||
placeholder: e.g., MIT or BSD-3-Clause |
||||
validations: |
||||
required: true |
||||
Loading…
Reference in new issue