| commit | feb3ba2933089561b3c99dbc020b9ddd7560816e | [log] [tgz] |
|---|---|---|
| author | Emily Shaffer <emilyshaffer@google.com> | Fri Sep 21 13:48:32 2018 -0700 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Sat Sep 22 04:05:11 2018 +0000 |
| tree | 3ff0aa01906e165d5e29c327fc7f10e8fff8cca9 | |
| parent | c33bca0d408e5714008c07dc8086b1348047a688 [diff] |
Update cla-signers with latest Intel Schedule A Change-Id: Id406e2978b7b561609701224bd3110f5812303cd Signed-off-by: Emily Shaffer <emilyshaffer@google.com>
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!
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.
openbmc-events: Query error events on the target serveropenbmc-sensors: Query sensors on the target serveropenbmc-sfw: Manage host and BMC firmware images on the target serveropenbmctool: A general purpose tool for user interactions with OpenBMCpretty-journal: Convert journalctl's 'pretty' output to regular outputupload_and_update: Upload a tarball to TFTP server and update BMC with itnetboot: Painless netboot of BMC kernelsobmc-gerrit: Automagically add reviewers to changes pushed to Gerritreboot: Endlessly reboot OpenPOWER hoststracing: Enable and clean up kernel tracepoints remotelywitherspoon-debug: Deploy the debug tools tarball to Witherspoon BMCscla-signers: Check if a contributor has signed the OpenBMC CLAopenbmc-autobump.py: Update commit IDs in bitbake recipes to bring in new changesHowever you want to send patches, we will probably cope:
Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted.
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.
We don't ask for much, but you need to give us at least a Signed-off-by, and put your work under the Apache 2.0 license. Licensing everything under Apache 2.0 will just hurt our heads less. Lets keep the lawyers off our backs. ^
^Any exceptions must be accompanied by a LICENSE file in the relevant subdirectory, and be compatible with Apache 2.0. You thought you would get away without any fine print?
There's no standard way to install the scripts housed in the here, so 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.