Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc-tools / 97985148e84b969add2eba71a3f49c43f511b34f
commit97985148e84b969add2eba71a3f49c43f511b34f[log] [tgz]
authorAndrew Jeffery <andrew@aj.id.au>Fri Dec 22 15:33:07 2023 +1030
committerAndrew Jeffery <andrew@aj.id.au>Fri Dec 22 15:35:24 2023 +1030
treecf01595836fdedd2c07d476046ed07d1d29abc27
parentcff0bfa003d9f8a2f12f13c9b80646315c6f6b8c [diff]
OWNERS: Update Andrew's preferred email

We're having some grief with non-preferred emails in Gerrit[1]. I now
prefer project-related content goes to my work email address, so use my
non-preferred email to implement the switch.

[1]: https://issues.gerritcodereview.com/issues/317345953

Change-Id: Ice7e87bbe7d08640818e50d967d97c48ab73fcc9
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
1 file changed
tree: cf01595836fdedd2c07d476046ed07d1d29abc27
  1. adcapp/
  2. altitude/
  3. autojson/
  4. bbdbg/
  5. bi2cp/
  6. cla-signers/
  7. dbus-pcap/
  8. dbus-vis/
  9. dbus_sensor_tester/
  10. dbusView/
  11. ddconvnotrunc/
  12. expectedJsonChecker/
  13. format-yaml/
  14. ipkdbg/
  15. netboot/
  16. openbmc-autobump/
  17. openbmctool/
  18. overlay/
  19. pldm/
  20. prepare-emmc-qemu/
  21. pretty-journal/
  22. pwmtachtool/
  23. reboot/
  24. reboot-ping-pong/
  25. rootfs_size/
  26. sensor_yaml_config/
  27. tof-voters/
  28. tracing/
  29. witherspoon-debug/
  30. .linter-ignore
  31. .shellcheck-ignore
  32. LICENSE
  33. OWNERS
  34. README.md
README.md

The OpenBMC Tools Collection

The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.

It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!

Repository Rules

  • Always inspect what you will be executing
  • Some hacking on your part is to be expected

If you're still with us

Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.

Sending patches

Please use gerrit for all patches to this repository:

Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.

What we will do once we have your patches

So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.

What you must have in your patches

We don't ask for much, but you need to give us at least a Signed-off-by, use SPDX markers in your source files and put your work under an Apache 2.0 compatible license.

How you consume the repository

There's no standard way to install the scripts housed here, and adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.