| /Zephyr-latest/doc/project/ |
| D | proposals.rst | 37 importance to the project. Often, the requester may have a readiness and
47 the project goals and other timeline considerations. The priority is
59 by any project member or the community. You should contact an assigned owner if
66 Project roadmaps and release plans are both important tools for the project, but
67 they have very different purposes and should not be confused. A project roadmap
68 communicates the high-level overview of a project's strategy, while a release
72 - The project roadmap communicates the why; a release plan details the what
77 Project Roadmap
80 The project roadmap should serve as a high-level, visual summary of the
81 project's strategic objectives and expectations.
[all …]
|
| D | tsc.rst | 7 The TSC role and its responsibilities is defined in the `Zephyr project charter`_.
13 Zephyr Project. TSC members work collaboratively with other TSC members,
14 contributors, and stakeholders to ensure the project's success and
18 the overall success and growth of the Zephyr Project, ensuring that it remains a
26 Participate in key decisions related to the project's technical direction,
34 Gain access to relevant project repositories, documentation, and communication
52 project goals, standards, and best practices through active participation as
57 compatibility with project standards.
64 Contribute to the development and maintenance of project documentation,
69 coordinate project releases, ensuring timely delivery and quality assurance.
[all …]
|
| D | index.rst | 3 Project and Governance
24 The Zephyr project defines a development process workflow using GitHub
35 project's :ref:`development processes and tools <dev-environment-and-tools>`
37 project's goals and guidelines for our active developer community.
39 :ref:`project_roles` describes in detail the Zephyr project roles and associated permissions
|
| /Zephyr-latest/doc/develop/west/ |
| D | built-in.rst | 13 Some commands take projects as arguments. These arguments can be project
15 on the local file system. Omitting project arguments to commands which
89 [--group-filter FILTER] [--stats] [PROJECT ...]
94 :file:`west.yml`, and updates each project specified there.
95 If your manifest uses :ref:`project groups <west-manifest-groups>`, then
98 To operate on a subset of projects only, give ``PROJECT`` argument(s). Each
99 ``PROJECT`` is either a project name as given in the manifest file, or a
100 path that points to the project within the workspace. If you specify
103 **Project update procedure:**
105 For each project that is updated, this command:
[all …]
|
| D | manifest.rst | 35 repositories in the workspace, with each project repository boxed in by a
42 project repositories. This relationship is shown using dotted line arrows in the
44 to a corresponding commit in a project repository.
52 - Project and manifest repository histories don't have to move
60 One use for moving backward in project history is to "revert" a regression by
63 - Project repository commits can be "skipped": ``P3`` moves forward
66 - In the above diagram, no project repository has two revisions "at
84 # short names for project URLs
88 # default project attributes
94 # a list of project groups to enable or disable
[all …]
|
| D | config.rst | 164 - String, default empty. A comma-separated list of project groups to
173 * - ``manifest.project-filter``
183 Project names are matched against each regular expression (``re1``,
184 ``re2``, ``re3``, ...) in the list, in order. If the entire project name
186 deactivates or activates the project. The project is deactivated if the
187 element begins with ``-``. The project is activated if the element
188 begins with ``+``. (Project names cannot contain ``,`` if this option is
192 If a project's name matches multiple regular expressions in the list,
194 if ``manifest.project-filter`` is:
200 Then a project named ``hal_bar`` is inactive, but a project named
[all …]
|
| D | release-notes.rst | 52 string, which prints the project's ``description:`` value.
75 - ``west.manifest.Project`` now has a ``description`` attribute,
89 - Support for a new ``manifest.project-filter`` configuration option.
94 - Project names which contain comma (``,``) or whitespace now generate
95 warnings. These warnings are errors if the new ``manifest.project-filter``
117 ``manifest.project-filter`` configuration option's value.
324 project. See :ref:`west-project-userdata` for details.
334 - The ``west.manifest.Project.userdata`` attribute was added to support
335 project user data.
347 - The manifest file parser was incorrectly allowing project names which contain
[all …]
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 006_nomination.md | 3 about: Nominate a GitHub user for additional rights on the Zephyr Project
12 The [TSC Project Roles] defines the main roles for the Zephyr Project, including
36 Add links to 3-5 GitHub pull requests, in the Zephyr project, authored or
38 Zephyr project.
41 [TSC Project Roles]: <https://docs.zephyrproject.org/latest/project/project_roles.html>
|
| /Zephyr-latest/tests/ztest/fail/ |
| D | CMakeLists.txt | 10 # Set the target binary for the 'core' external project. The path to this must match the one set
16 # Set the target binary for the 'core' external project. The path to this must match the one set
21 # Create the project and set the sources for the target
22 project(fail)
25 # Find which CONFIG_ZTEST_FAIL_TEST_* choice was set so we can pass it to the external project
27 # 'core' project as a cmake argument.
35 # Add the 'core' external project which will mirror the configs of this project.
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | manifest_projects_table.py | 74 for project in manifest.projects:
75 if project.name == "manifest":
79 and manifest.is_active(project)
81 and not manifest.is_active(project)
85 projects.append(project)
102 entry += nodes.paragraph(text="Project")
109 for project in projects:
114 entry += nodes.paragraph(text=project.name)
119 project.revision,
120 project.revision,
[all …]
|
| /Zephyr-latest/doc/develop/tools/ |
| D | stm32cubeide.rst | 11 A project must have already been created with Zephyr and west.
16 Project Setup
28 #. Open your already existing project by going to
29 :menuselection:`File --> New --> STM32 CMake Project`:
33 :alt: Create new CMake project
35 #. Select :guilabel:`Project with existing CMake sources`, then click :guilabel:`Next`.
41 Press :guilabel:`Finish` and your project should now be available.
44 #. Right-click on the newly created project in the workspace, and select
54 :alt: Properties dialog for project
57 out-of-tree project or not.
[all …]
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server/src/ |
| D | response_big.html.bin | 22 <h1>What is Zephyr™ Project?</h1>
27 …Project, is a Linux Foundation hosted Collaboration Project, an open source collaborative effort u…
31 …Project is perfect for building simple connected sensors, LED wearables, up to modems and small Io…
|
| /Zephyr-latest/samples/net/sockets/dumb_http_server_mt/src/ |
| D | response_big.html.bin | 22 <h1>What is Zephyr™ Project?</h1>
27 …Project, is a Linux Foundation hosted Collaboration Project, an open source collaborative effort u…
31 …Project is perfect for building simple connected sensors, LED wearables, up to modems and small Io…
|
| /Zephyr-latest/doc/contribute/ |
| D | external.rst | 31 Integrating code into the Zephyr Project from other projects that use a license
34 `Zephyr project charter`_. The board will automatically reject licenses that
41 .. _Zephyr project charter:
49 with the Zephyr Project without concerns over patent or copyright issues.
56 comes from an existing project, there are additional questions that must be
60 into the project:
62 - Is this the most optimal way to introduce the functionality to the project?
65 - Is the external project being actively maintained? This is particularly
68 Are there other open source project that implement the same functionality?
73 There are two ways of integrating external source code into the Zephyr Project,
[all …]
|
| D | index.rst | 6 Contributions from the community are the backbone of the project. Whether it is by submitting code,
23 Learn about the overall process and guidelines for contributing to the Zephyr project.
26 how to ensure your contribution can be considered for inclusion in the project and potentially
31 contributors to the project.
42 project.
47 The Zephyr project thrives on good documentation. Whether it is as part of a code contribution or
48 as a standalone effort, contributing documentation is particularly valuable to the project.
89 blobs <blobs-process>` to the project.
94 When your first contribution to the Zephyr project gets merged, you'll become eligible to claim your
96 profile, etc. It will allow you to showcase your involvement in the Zephyr project and help raise
|
| D | bin_blobs.rst | 39 The Zephyr Project does not host binary blobs in its Git repositories or
119 be unconditionally accepted by the project; any blob may be rejected for other
131 meets these requirements. The project may remove a blob from the upstream
151 APIs may change and such blobs cannot be modified by all project maintainers
162 can be linked by a toolchain supported by the Zephyr Project. This is required
176 project maintainers define an open source test suite that an upstream
188 At the discretion of the release team, the project may remove support for a
194 The Zephyr Project is not expected to be responsible for the maintenance and
196 Zephyr Project release team, and on a case-by-case basis:
200 - Such issues may be closed as out of scope of the Zephyr project
[all …]
|
| /Zephyr-latest/doc/_doxygen/ |
| D | mainpage.md | 9 information about the project and becoming a member, and this [summary
11 to help you find your way around the project.
23 in the [project's GitHub LICENSE
25 There are some imported or reused components of the Zephyr project that
26 use other licensing, as described in [Licensing of Zephyr Project
|
| /Zephyr-latest/scripts/utils/ |
| D | twister_to_list.py | 8 -p path/to/zephyr-based-project
47 def twister_to_list(project, dry_run): argument
52 for p in project.glob("**/*"):
76 "-p", "--project", type=Path, required=True, help="Zephyr-based project path"
81 twister_to_list(args.project, args.dry_run)
|
| D | migrate_includes.py | 12 -p path/to/zephyr-based-project
28 def update_includes(project, dry_run): argument
29 for p in project.glob("**/*"):
79 "-p", "--project", type=Path, required=True, help="Zephyr-based project path"
84 update_includes(args.project, args.dry_run)
|
| D | migrate_sys_init.py | 11 -p path/to/zephyr-based-project
22 def update_sys_init(project, dry_run): argument
23 for p in project.glob("**/*"):
85 "-p", "--project", type=Path, required=True, help="Zephyr-based project path"
90 update_sys_init(args.project, args.dry_run)
|
| /Zephyr-latest/doc/security/ |
| D | secure-coding.rst | 17 security is addressed within the Zephyr project. All code submitted
25 This document covers guidelines for the `Zephyr Project`_, from a
31 .. _Zephyr Project: https://www.zephyrproject.org/
36 gives basic requirements that a developer working on the project will
47 project.
68 of the Zephyr project, this can be realized, e.g., by modular code
84 of the Zephyr project, this could encompass split keys [PAUL09]_.
115 threshold of 80% is given in [MS12]_). For the Zephyr project, this can
137 The Zephyr project must have at least one primary developer who knows
187 A "primary developer" in a project is anyone who is familiar with the
[all …]
|
| D | reporting.rst | 9 Vulnerabilities to the Zephyr project may be reported via email to the
12 Each vulnerability will be entered into the Zephyr Project security
102 Zephyr project bug tracking system.
108 within the Zephyr project to fix the issues, and 60 days for external
115 project github. Developers shall make an attempt to not reveal the
141 The Zephyr project shall maintain a vulnerability-alerts mailing list.
142 This list will be seeded initially with a contact from each project
145 vetted by the project director to determine that they have a
153 status within the project. This information is intended to allow them
159 - The Zephyr Project security advisory link (GitHub).
[all …]
|
| /Zephyr-latest/tests/arch/arm/arm_irq_vector_table/ |
| D | README.txt | 5 Verify a project can install ISRs directly in the vector table. Only for
10 Building and Running Project:
12 This project outputs to the console. It can be built and executed on QEMU as
21 Problems caused by out-dated project information can be addressed by
22 issuing one of the following commands then rebuilding the project:
40 PROJECT EXECUTION SUCCESSFUL
|
| /Zephyr-latest/doc/ |
| D | index-tex.rst | 4 Zephyr Project documentation main file
8 Zephyr Project Documentation
24 project/index.rst
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | README_http_parser | 4 The http-parser library* from the nodejs project is a downstream of an
5 externally maintained open source project. The original upstream code
14 * "http-parser" is the project's name, "http_parser" is used in filenames.
|
