/openbmc/docs/designs/ |
H A D | ci-authorization.md | 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 42 openbmc/general-developers GitHub team, the contributor must first be a member 47 openbmc/general-developers group membership administrative capability. 58 The proposal is to simply migrate the current openbmc/general-developers GitHub
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/libfido2/ |
H A D | libfido2_1.16.0.bb | 5 HOMEPAGE = "https://developers.yubico.com/libfido2" 12 SRC_URI = "https://developers.yubico.com/${BPN}/Releases/${BPN}-${PV}.tar.gz"
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | NRL | 5 …ibution from the US Naval Research Laboratory (NRL) are copyrighted by their respective developers. 7 …nt is binding on those portions of the software. In all cases, the NRL developers have retained th… 9 …tware and documentation were developed at NRL by various people. Those developers have each copyri…
|
H A D | LZMA-SDK-9.11-to-9.20 | 6 Some code in LZMA is based on public domain code from another developers:
|
H A D | LZMA-SDK-9.22 | 6 Some code in LZMA SDK is based on public domain code from another developers:
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/bitwise/ |
H A D | bitwise_0.50.bb | 5 kernel developers and device drivers developers."
|
/openbmc/qemu/docs/devel/ |
H A D | index.rst | 14 documentation for future developers. 16 All developers will want to familiarise themselves with
|
/openbmc/qemu/docs/system/devices/ |
H A D | canokey.rst | 33 * libcanokey-qemu supports debugging output thus developers can 39 Then for developers: 41 * For developers on software with secure key support (e.g. FIDO2, OpenPGP), 43 * For secure key developers, USB packets between guest OS and CanoKey
|
/openbmc/sdbusplus/ |
H A D | .gitignore | 6 # Created by https://www.toptal.com/developers/gitignore/api/python 7 # Edit at https://www.toptal.com/developers/gitignore?templates=python 171 # End of https://www.toptal.com/developers/gitignore/api/python
|
/openbmc/docs/tof/ |
H A D | membership-and-voting.md | 45 | Jan 30th | July 30th | Developers disputing membership eligibility must submit a petition … 68 contributions to the project. By contributing to the project, developers gain a 87 cycle, normal developers are given a vote weight of 1 and highly-productive 88 developers are given a vote weight of 3.
|
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libconfig/ |
H A D | libconfig-autoconf-perl_0.319.bb | 6 developers as GNU Autoconf <http://www.gnu.org/software/autoconf/> does for \ 7 Shell developers."
|
/openbmc/openbmc/poky/meta/classes/ |
H A D | extrausers.bbclass | 14 # groupadd developers; \ 17 # groupmod -g 1020 developers; \
|
/openbmc/telemetry/ |
H A D | .gitignore | 8 # Created by https://www.toptal.com/developers/gitignore/api/vim,intellij,meson,visualstudiocode 9 # Edit at https://www.toptal.com/developers/gitignore?templates=vim,intellij,meson,visualstudiocode 177 # End of https://www.toptal.com/developers/gitignore/api/vim,intellij,meson,visualstudiocode
|
/openbmc/docs/ |
H A D | kernel-development.md | 39 welcome to cc the OpenBMC list when sending upstream, so other kernel developers 44 this is useful for developers who are not familiar with writing kernel code, it 68 email to the OpenBMC list to get the opinion of the kernel developers. Patches
|
/openbmc/openbmc/poky/meta-selftest/recipes-devtools/python/ |
H A D | python-async-test.inc | 2 HOMEPAGE = "http://github.com/gitpython-developers/async"
|
/openbmc/openbmc/poky/meta/recipes-devtools/python/ |
H A D | python3-gitdb_4.0.12.bb | 2 HOMEPAGE = "http://github.com/gitpython-developers/gitdb"
|
H A D | python3-smmap_6.0.0.bb | 5 HOMEPAGE = "http://github.com/gitpython-developers/GitPython"
|
/openbmc/qemu/include/qemu/ |
H A D | help-texts.h | 6 "Fabrice Bellard and the QEMU Project developers"
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-sqlalchemy_2.0.41.bb | 2 application developers the full power and flexibility of SQL"
|
/openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/libdvbpsi/ |
H A D | libdvbpsi_1.3.3.bb | 4 HOMEPAGE = "http://www.videolan.org/developers/libdvbpsi.html"
|
/openbmc/bmcweb/ |
H A D | .gitignore | 17 # Created by https://www.toptal.com/developers/gitignore/api/osx,linux,clion,meson,eclipse,windows 18 # Edit at https://www.toptal.com/developers/gitignore?templates=osx,linux,clion,meson,eclipse,windo… 292 # End of https://www.toptal.com/developers/gitignore/api/osx,linux,clion,meson,eclipse,windows
|
/openbmc/openbmc/poky/documentation/overview-manual/ |
H A D | development-environment.rst | 21 developers. Contrast this to the more standard centralized development 23 developers produces a product for sale using a defined set of procedures 235 responsible for accepting changes from other developers and for 256 Developers (including contributing community members) create and 263 Developers are responsible for keeping their local repository up-to-date 270 There is a somewhat formal method by which developers commit changes and 280 project's maintainer. A set of developers independently 319 two different developers. 330 of developers "pushing" local commits to a remote repository, which 332 developers "pulling" known states of the project down into their [all …]
|
/openbmc/qemu/docs/ |
H A D | conf.py | 97 copyright = u'2025, The QEMU Project Developers' 98 author = u'The QEMU Project Developers' 295 u'The QEMU Project Developers', 'manual'), 319 ['Fabrice Bellard and the QEMU Project developers'], 7), 322 ['The QEMU Project developers'], 7),
|
/openbmc/openbmc/poky/meta/recipes-extended/libmnl/ |
H A D | libmnl_1.0.5.bb | 2 DESCRIPTION = "Minimalistic user-space library oriented to Netlink developers, providing \
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-test/cukinia/ |
H A D | cukinia_0.7.0.bb | 3 developers run simple system-level validation tests on their firmware."
|