Home
last modified time | relevance | path

Searched +full:zephyr +full:- +full:main +full:- +full:ci +full:- +full:weekly +full:- +full:1 (Results 1 – 3 of 3) sorted by relevance

/Zephyr-latest/.github/workflows/
Dtwister-publish.yaml7 - main
9 - completed
12 upload-to-elasticsearch:
14 github.repository == 'zephyrproject-rtos/zephyr' &&
19 runs-on: ubuntu-22.04
22 - name: Checkout
25 fetch-depth: 0
26 persist-credentials: false
28 - name: Download Artifacts
29 id: download-artifacts
[all …]
/Zephyr-latest/doc/contribute/
Dguidelines.rst6 As an open-source project, we welcome and encourage the community to submit
24 https://github.com/zephyrproject-rtos/zephyr/blob/main/LICENSE
26 .. _GitHub repo: https://github.com/zephyrproject-rtos/zephyr
28 Zephyr uses the `Apache 2.0 license`_ (as found in the LICENSE file in
38 https://www.zephyrproject.org/faqs/#1571346989065-9216c551-f523
41 https://www.whitesourcesoftware.com/whitesource-blog/top-10-apache-license-questions-answered/
52 There are some imported or reused components of the Zephyr project that
55 Importing code into the Zephyr OS from other projects that use a license
57 context and approved by the Zephyr governing board.
61 the Zephyr community can develop products with the Zephyr Project
[all …]
Dcontributor_expectations.rst1 .. _contributor-expectations:
6 The Zephyr project encourages :ref:`contributors <contributor>` to submit
10 - Reviewed more quickly and reviewed more thoroughly. It's easier for reviewers
14 - Less wasted work if reviewers or maintainers reject the direction of the
17 - Easier to rebase and merge. Smaller PRs are less likely to conflict with other
20 - Easier to revert if the PR breaks functionality.
32 - Smaller PRs should encompass one self-contained logical change.
34 - When adding a new large feature or API, the PR should address only one part of
38 - PRs should include tests or samples under the following conditions:
40 - Adding new features or functionality.
[all …]