| /openbmc/docs/ |
| H A D | meta-layer-guidelines.md | 1 # OpenBMC meta layer guidelines
6 the rules exist, then can be understood and managed by the project. In general,
10 ## Meta layers should not patch projects that exist within the openBMC tree
27 Discuss with the project maintainers and the community about whether or not the
31 If it needs to be per-project or per-machine configurable, check it in under a
39 Yocto itself is an open source project that accepts contributions. The more
40 changes that OpenBMC stacks against Yocto recipes, the more unmaintainable it
42 the Yocto community is as responsive (sometimes much faster) than the OpenBMC
49 cherry-pick the commit into the OpenBMC tree, with a pointer to the review in
59 There are some OpenBMC projects that are utilized outside of OpenBMC. As such,
[all …]
|
| H A D | community-membership.md | 3 This doc outlines the various expectations of contributor roles in OpenBMC. The
4 OpenBMC project is subdivided into subrepositories. Responsibilities for most
8 …------------------- | ------------------------------------------------------ | -------------------…
11 … | [OWNERS] entry within the meta-\* subfolder for the …
14 | TOF Member | Set direction and priorities for the project | Elected via [TOF e…
25 principles in this document, familiarity with project organization, roles,
27 Role-specific expectations, responsibilities, and requirements are enumerated
34 Gerrit, and pre-submit tests are automatically run for their reviews. Members
41 - Have made multiple contributions to the project or community. Contribution may
43 - Authoring or reviewing code reviews on Gerrit
[all …]
|
| H A D | README.md | 1 # OpenBMC documentation
3 The [OpenBMC project](https://www.openbmc.org/) is a Linux Foundation project
4 whose goal is to produce a customizable, open-source firmware stack for
6 for OpenBMC as a whole. There may be component-specific documentation in the
9 The [features](features.md) document lists the project's major features with
14 - Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc
15 - List Archive: https://lore.kernel.org/openbmc/
16 - Discord: https://discord.gg/69Km47zH98
18 ## OpenBMC Development
20 These documents contain details on developing OpenBMC code itself
[all …]
|
| H A D | hw-vendor-repos-policy.md | 13 OpenBMC Github project is made. It starts with the requirements and then some
19 OpenBMC architecture (bitbake, d-bus, phosphor-dbus-interfaces, ...).
22 guidelines to be used by the OpenBMC TOF in their decision to approve or not
25 Both hardware-specific and vendor-specific repositories should meet the
26 following requirements to be eligible for a repository under OpenBMC:
34 5. It is a feature that is believed to be generally useful to the OpenBMC
36 - Determination made by the TOF
37 - Reference: "Create a new repository" TOF [process][tof]
38 6. It has an active OpenBMC community member that is willing to be a maintainer
41 under OpenBMC (vs. a recipe in OpenBMC that points to an external repository).
[all …]
|
| H A D | CONTRIBUTING.md | 1 # Contributing to OpenBMC
4 guidelines for contributing to an OpenBMC repository which are hosted in the
5 [OpenBMC Organization](https://github.com/openbmc) on GitHub. Feel free to
11 [Code of Conduct](https://github.com/openbmc/docs/blob/master/code-of-conduct.md).
17 OpenBMC relies on the Open Compute Project to provide guidelines on inclusive
20 https://www.opencompute.org/documents/ocp-terminology-guidelines-for-inclusion-and-openness
24 OpenBMC has quite a modular structure, consisting of small daemons with a
25 limited set of responsibilities. These communicate over D-Bus with other
29 daemon, which then translates those requests to D-Bus messages.
32 'openbmc' build infrastructure.
[all …]
|
| H A D | code-of-conduct.md | 6 standards projects (each a “Project”) and undertakes such other activities as is
13 - support the collaborative development, availability and adoption of open
17 - host various projects pursuing the development of Open Technology and other
18 technical assets, materials and processes (each such project, which itself may
19 include any number of projects, a “Project”);
20 - provide enablement and support to Projects to assist their development
22 - undertake such other lawful activity as permitted by law and as consistent
23 with the mission, purpose and tax status of LFP, Inc., a Delaware non-profit
24 non-stock corporation and the sole member of LF Projects.
35 provides a benchmark for self-evaluation and acts as a vehicle for better
[all …]
|
| H A D | maintainer-workflow.md | 1 # OpenBMC Maintainer/CLA Workflow
3 OpenBMC contributors are required to execute an OpenBMC CLA (Contributor License
5 for sub-project maintainers to follow before approving patches.
7 - Manually verify the contributor has signed the ICLA (individual) or is listed
9 - Executed CLAs can be found [in the CLA repository][1].
10 - If you were not added to the appropriate CLA repository ACL send an email to
11 openbmc@lists.ozlabs.org with a request to be added.
12 - If a CLA for the contributor is found, accept the patch(1).
13 - If a CLA is not found, request that the contributor execute one and send it to
15 - Do not accept the patch(1) until a signed CLA (individual _or_ corporate)
[all …]
|
| H A D | kernel-development.md | 1 # OpenBMC kernel development
3 The OpenBMC project maintains a kernel tree for use by the project. The tree's
6 case-by-case basis. If in doubt, start a discussion on the mailing list.
8 The OpenBMC kernel tree is hosted at https://github.com/openbmc/linux and
12 Your code will make it into the OpenBMC tree in these ways, from most to least
15 1. When the OpenBMC kernel moves to a new upstream release
16 2. By backporting upstream commits from a newer kernel version to the OpenBMC
18 3. Patches included in the OpenBMC tree temporarily
27 …`git format-patch --subject-prefix="PATCH linux dev-4.7" --to=openbmc@lists.ozlabs.org --to=joel@j…
34 hardware you wish to support. Check the OpenBMC `-dev` tree, check upstream, and
[all …]
|
| /openbmc/webui-vue/ |
| H A D | CONTRIBUTING.md | 1 Contributing to WebUI-Vue
5 The following is a set of guidelines for contributing to the OpenBMC Web UI.
9 - [Project Setup](#project-setup)
10 - [Code of Conduct](#code-of-conduct)
11 - [Asking Questions](#asking-questions)
12 - [Submitting Bugs](#submitting-bugs)
13 - [Request a New Feature](#request-a-new-feature)
14 - [User Research](#user-research)
15 - [Design Reviews](#design-reviews)
16 - [Help Wanted](#help-wanted)
[all …]
|
| H A D | README.md | 1 # webui-vue
3 webui-vue is a web-based user interface for the OpenBMC firmware stack built on
6 ## Hold on... What happened to phosphor-webui?
8 [phosphor-webui](https://github.com/openbmc/phosphor-webui) was built on
10 [AngularJS went End of Life](https://www.convective.com/angularjs-end-of-life/)
13 ## When will this new Vue.js application reach feature parity with phosphor-webui?
16 …s label:phosphor-webui-feature-parity](https://github.com/openbmc/webui-vue/issues?q=is%3Aissue+is…
19 ## What improvements does webui-vue have?
21 As mentioned, this application is built using Vue.js, a modern open-source
22 Model-View-ViewModel JavaScript framework supported by an active community and
[all …]
|
| /openbmc/docs/designs/ |
| H A D | ci-authorization.md | 1 # Continuous integration and authorization for OpenBMC
7 Created: 2019-01-30
11 The OpenBMC project maintains a number of Jenkins CI jobs to ensure incoming
12 contributions to the project source code meet a level of quality. Incoming
13 contributions can be made by the general public - anyone with a GitHub account.
15 attempt to compromise project resources, e.g. build systems, and as such some
19 The project already has contributor authorization for CI. This proposal serves
26 openbmc/general-developers GitHub team. If the contributor is a member of the
27 team (or a general-developers sub-team), the automated CI processes are
29 the general-developers team, manual intervention (ok-to-test) is required by a
[all …]
|
| H A D | phosphor-hwmon-io-uring.md | 7 - Brandon Kim ([brandonkim@google.com](mailto:brandonkim@google.com), brandonk)
8 - William A. Kennington III ([wak@google.com](mailto:wak@google.com), wak)
14 Currently, OpenBMC has code that performs I2C reads for sensors that may take
16 therefore may block other functions such as IPMI. This project will involve
17 going through OpenBMC repositories (specifically
18 [phosphor-hwmon](https://github.com/openbmc/phosphor-hwmon)) that may have this
27 sensor reads for OpenBMC.
30 method for preventing sensors from blocking all other sensor reads and D-Bus if
31 they do not report failures quickly enough in the phosphor-hwmon repository
32 ([link to change](https://gerrit.openbmc.org/c/openbmc/phosphor-hwmon/+/24337)).
[all …]
|
| H A D | ecc-dbus-sel.md | 5 Created: 2019-02-26
23 OpenBMC currently support for generating SEL entries based on parsing the D-Bus
24 event log. It does not yet support the BMC ECC SEL feature in OpenBMC project.
25 Therefore, the memory ECC information will be registered to D-Bus and generate
28 …](https://www.intel.com/content/www/us/en/servers/ipmi/ipmi-second-gen-interface-spec-v2-rev1-1.ht…
32 Currently, the OpenBMC project does not support ECC event logs in D-Bus because
33 there is no relevant ECC information in the OpenBMC D-Bus architecture. The new
34 ECC D-Bus information will be added to the OpenBMC project and an ECC monitor
41 ECC-enabled memory controllers can detect and correct errors in operating
55 …](https://www.intel.com/content/www/us/en/servers/ipmi/ipmi-second-gen-interface-spec-v2-rev1-1.ht…
[all …]
|
| /openbmc/openbmc-tools/tof-voters/libvoters/subcmd/ |
| H A D | analyze-reviews.py | 16 def __init__(self, parser: argparse._SubParsersAction) -> None:
18 "analyze-reviews", help="Determine points for reviews"
22 "--before",
23 "-b",
24 help="Before timestamp (YYYY-MM-DD)",
28 "--after",
29 "-a",
30 help="After timestamp (YYYY-MM-DD)",
36 def run(self, args: argparse.Namespace) -> int:
47 if not re.match(r"[0-9]*\.json", f):
[all …]
|
| /openbmc/docs/security/ |
| H A D | how-to-report-a-security-vulnerability.md | 3 This describes how you can report an OpenBMC security vulnerability privately to
4 give the project time to address the problem before public disclosure.
8 - You have information about a security problem or vulnerability which is not
10 - You want the problem fixed before public disclosure and you are willing to
12 - You understand the problem will eventually be publicly disclosed.
14 To begin the process: Privately contact the OpenBMC security response team and
15 (if known) the project maintainer:
17 - Suggest sending an email. Use `openbmc-security at lists.ozlabs.org`.
18 - If you know which source code repository is affected, find the repository
21 - Include details about the security problem such as:
[all …]
|
| H A D | obmc-security-response-team-guidelines.md | 3 These are the guidelines for OpenBMC security responders, including the security
4 response team, project owners, and community members who are responding to
7 Each project within OpenBMC works independently to resolve security
9 consistency within the OpenBMC project, and helps to get CVEs assigned.
13 - Keep problems private until announce.
14 - Work with diligence.
15 - Keep stakeholders informed.
21 - Within a day, acknowledge you received the report. Note that reports are
23 - Communicate by opening the GitHub draft security advistory as soon as the
27 and OpenBMC).
[all …]
|
| /openbmc/docs/process/ |
| H A D | subproject-maintainership.md | 3 <!--toc:start-->
5 - [Subproject Maintainership and Forward Progress](#subproject-maintainership-and-forward-progress)
6 - [Process](#process)
7 - [Problem Description](#problem-description)
8 - [Scope](#scope)
9 - [Considerations](#considerations)
10 - [Social](#social)
11 - [Technical](#technical)
12 - [Security](#security)
13 - [Synthesis of Considerations](#synthesis-of-considerations)
[all …]
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | code_standards_check.md | 10 Project [codespell](https://github.com/codespell-project/codespell) designed
24 ### 2. robotframework-lint
26 Project [robotframework-lint](https://pypi.org/project/robotframework-lint/) for
30 $ pip install –upgrade robotframework-lint
42 [custom rules](https://github.com/openbmc/openbmc-test-automation/blob/master/robot_custom_rules.py)
46 Project [check_robot_tags](https://github.com/generatz/check_robot_tags) Checks
55 $ awk -f check_robot_tags.awk ~/openbmc-test-automation/redfish/test_xit.robot
56 --- /home/openbmc-test-automation/redfish/test_xit.robot:
|
| /openbmc/bmcweb/ |
| H A D | OEM_SCHEMAS.md | 13 and can be maintained forever. Within OpenBMC, we have no such group of
15 entire project.
17 Because of that, OEM properties in an open-source project pose many problems
20 OpenBMC's external Redfish API aims to be as compatible between systems as
21 possible. Adding machine-specific resources, properties, and types defeats a
22 large amount of reuse, as clients must implement machine-specific APIs, some of
23 which are likely to overlap, which increases the amount of code overall. OpenBMC
25 and therefore needs to take care when adding new, non-standard APIs, given the
28 In the experience of the project, OEM resources trend toward a lower level of
29 quality and testing than their spec-driven alternatives, given the lack of
[all …]
|
| /openbmc/openbmc-tools/openbmc-autobump/ |
| H A D | openbmc-autobump.py | 3 # Contributors Listed Below - COPYRIGHT 2018
11 # http://www.apache.org/licenses/LICENSE-2.0
25 git = sh.git.bake("--no-pager")
40 git.reset("--hard", "FETCH_HEAD", _cwd=local_name)
47 if "github.com/openbmc" not in uri:
62 # the project is the right-most path segment
63 return (uri.split("/")[-1].replace(".git", ""), branch)
71 project = None
78 sha = line.split("=")[-1].replace('"', "").strip()
79 elif not project and uris or "_URI" in line:
[all …]
|
| /openbmc/docs/tof/ |
| H A D | contract.md | 1 # OpenBMC Technical Oversight Forum (TOF)
5 The OpenBMC TOF or Technical Oversight Forum represents the technical leadership
6 of the OpenBMC project.
8 The TOF handles the processes around accepting new features into OpenBMC,
11 technical leadership concerns related to OpenBMC. This source of this document
12 is in the [OpenBMC documentation repository](https://github.com/openbmc/docs).
19 - Decision making is a spectrum between building broad consensus, in which
21 strongly differing view-points. This group should intend to work towards broad
24 - Members within this forum are representatives of the development community as
28 - Encouraging progress, experimentation, and decision making within the project
[all …]
|
| H A D | membership-and-voting.md | 7 The TOF body shall consist of between 5 and 9 members selected by the OpenBMC
12 TOF members must themselves be members of the OpenBMC Development Community.
20 - The entity is the Linux Foundation.
21 - The TOF members have been unopposed in an election.
25 Members are elected by Ranked Choice Voting of the OpenBMC Development Community
27 before their seat is up for re-election; members have no term limits.
30 months in which half (+/- 1) of the seats are re-elected. Due to additions or
41 | :----------: | :----------: | :------------------------------------------------------------------…
42 | Jan 1st | July 1st | Developer contributions close for OpenBMC Development Community mem…
56 | :----------------- | :-------------: |
[all …]
|
| /openbmc/openbmc/ |
| H A D | .gitreview | 2 host=gerrit.openbmc-project.xyz
4 project=openbmc/openbmc.git
|
| H A D | README.md | 1 # OpenBMC chapter
3 …](https://jenkins.o…
5 OpenBMC is a Linux distribution for management controllers used in devices such
10 [D-Bus](https://www.freedesktop.org/wiki/Software/dbus/) to allow easy
13 ## Setting up your OpenBMC project
18 …mentation](https://docs.yoctoproject.org/ref-manual/system-requirements.html#required-packages-for…
24 sudo apt install git python3-distutils gcc g++ make file wget \
38 git clone https://github.com/openbmc/openbmc
39 cd openbmc
49 The script needs to be sourced while in the top directory of the OpenBMC
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Led/ |
| H A D | README.md | 68 …https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Led/Group…
73 are un-done.
75 - Henceforth, the term **asserted** would mean writing boolean **true** onto
76 `assert` property of the group. Term **de-assert** would mean writing
116 …https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Led/Physi…
128 `/xyz/openbmc/project/led/physical/id_front` and
129 `/xyz/openbmc/project/led/physical/id_rear`
132 `/xyz/openbmc/project/led/physical/id_front` and
133 `/xyz/openbmc/project/led/physical/id_rear`
|