We need help with this project. Contributions are very welcome. See the roadmap, open issues, and join us in Slack to talk about your cool ideas for the project.
For purposes of tracking code-origination, we follow a simple sign-off process. If you can attest to the Developer Certificate of Origin then you append in each git commit text a line such as:
Signed-off-by: Your Name <[email protected]>
Conduct collaboration in accordance to the Code of Conduct.
- Please submit issues to https://github.com/u-root/webboot/issues
The webboot project aims to follow the standard formatting recommendations
and language idioms set out in the Effective Go
guide, for example formatting
and names.
gofmt and golint are law, although this is not automatically enforced
yet and some housecleaning needs done to achieve that.
We have a few rules not covered by these tools:
- Standard imports are separated from other imports. Example:
import ( "regexp" "time" dhcp "github.com/krolaw/dhcp4" )
Well formatted patches aide code review pre-merge and code archaeology in the future. The abstract form should be:
<component>: Change summary
More detailed explanation of your changes: Why and how.
Wrap it to 72 characters.
See [here] (http://chris.beams.io/posts/git-commit/)
for some more good advices.
Signed-off-by: <[email protected]>
An example from this repo:
tcz: quiet it down
It had a spurious print that was both annoying and making
boot just a tad slower.
Signed-off-by: Ronald G. Minnich <[email protected]>
Webboot aims to be able to boot (optionally) signed distros from URLs.
We accept GitHub pull requests.
Fork the project on GitHub, work in your fork and in branches, push these to your GitHub fork, and when ready, do a GitHub pull requests against https://github.com/u-root/webboot.
webboot uses go modules. Do not clone webboot into your GOPATH.
If you add new dependencies, use the appropriate go modules command
to update things.
Every commit in your pull request needs to be able to build and pass the CI tests.
If the pull request closes an issue please note it as: "Fixes #NNN".
Look at the area of code you're modifying, its history, and consider tagging some of the maintainers when doing a pull request in order to instigate some code review.
We use Azure pipelines for our CI.