├── .gitignore ├── CONTRIBUTING.md ├── DCO ├── LICENSE ├── NOTICE ├── README.md ├── bash_completion ├── boot_nspawn ├── bootstrap_sdk ├── build_docker_aci ├── build_image ├── build_library ├── board_options.sh ├── build_image_util.sh ├── catalyst.sh ├── catalyst_default_stage4.sh ├── catalyst_toolchains.sh ├── check_root ├── configure_bootloaders.sh ├── dev_container_util.sh ├── disk_layout.json ├── disk_util ├── ebuild_aci_manifest.in ├── ebuild_aci_util.sh ├── gen_tmpfiles.py ├── generate_au_zip.py ├── generate_grub_hashes.py ├── generate_kernel_hash.sh ├── grub.cfg ├── grub_install.sh ├── menu.lst ├── modify_image_util.sh ├── niftycloud_ovf.sh ├── oem_aci_util.sh ├── parallels_pvs.sh ├── prod_image_util.sh ├── qemu_template.sh ├── release_util.sh ├── set_lsb_release ├── template_interoute.ovf ├── template_vmware.ovf ├── test_build_root ├── test_image_content.sh ├── test_oem_pkgs ├── toolchain_util.sh ├── torcx_manifest.sh ├── virtualbox_ovf.sh ├── vm_image_util.sh └── write_hdd.sh ├── build_oem_aci ├── build_packages ├── build_toolchains ├── build_torcx_store ├── check_out_of_date.py ├── clean_loopback_devices ├── code-of-conduct.md ├── common.sh ├── contrib ├── create-basic-configdrive └── create-coreos-vdi ├── core_date ├── core_dev_sign_update ├── core_pre_alpha ├── core_roller_upload ├── core_sign_update ├── cros_workon ├── find_overlay_dups ├── get_latest_image.sh ├── get_package_list ├── image_inject_bootchain ├── image_set_group ├── image_to_vm.sh ├── jenkins ├── README.md ├── formats-amd64-usr.txt ├── images.sh ├── packages.sh ├── sdk.sh ├── toolchains.sh └── vm.sh ├── lib ├── cros_build_lib.py ├── cros_build_lib_unittest.py ├── cros_vm_constants.sh ├── cros_vm_lib.sh └── shflags │ ├── README.chromium │ └── shflags ├── oem ├── azure │ └── update-gallery.sh ├── generic │ └── check_etag.sh └── openstack │ ├── README.md │ └── glance_load.sh ├── prune_images ├── rebuild_packages ├── sdk_lib ├── sdk_util.sh └── updates │ └── 0000.0.0.sh ├── set_official ├── set_shared_user_password.sh ├── setup_board ├── signing ├── devel.key.pem ├── devel.pub.pem ├── new_key.sh ├── print_key.sh ├── prod-2.pub.pem ├── sign.sh └── transfer.sh ├── tag_release ├── update_chroot ├── update_distfiles ├── update_ebuilds └── update_metadata /.gitignore: -------------------------------------------------------------------------------- 1 | # User files 2 | /.chromeos_dev 3 | /.default_board 4 | /.local_mounts 5 | /shared_user_passwd.txt 6 | 7 | # Generated files 8 | *.pyc 9 | *~ 10 | /cbuildbot_package.list 11 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # How to Contribute 2 | 3 | CoreOS projects are [Apache 2.0 licensed](LICENSE) and accept contributions via 4 | GitHub pull requests. This document outlines some of the conventions on 5 | development workflow, commit message formatting, contact points and other 6 | resources to make it easier to get your contribution accepted. 7 | 8 | # Certificate of Origin 9 | 10 | By contributing to this project you agree to the Developer Certificate of 11 | Origin (DCO). This document was created by the Linux Kernel community and is a 12 | simple statement that you, as a contributor, have the legal right to make the 13 | contribution. See the [DCO](DCO) file for details. 14 | 15 | # Email and Chat 16 | 17 | The project currently uses the general CoreOS email list and IRC channel: 18 | - Email: [coreos-dev](https://groups.google.com/forum/#!forum/coreos-dev) 19 | - IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org 20 | 21 | Please avoid emailing maintainers found in the MAINTAINERS file directly. They 22 | are very busy and read the mailing lists. 23 | 24 | ## Getting Started 25 | 26 | - Fork the repository on GitHub 27 | - Read the [README](README.md) for build and test instructions 28 | - Play with the project, submit bugs, submit patches! 29 | 30 | ## Contribution Flow 31 | 32 | This is a rough outline of what a contributor's workflow looks like: 33 | 34 | - Create a topic branch from where you want to base your work (usually master). 35 | - Make commits of logical units. 36 | - Make sure your commit messages are in the proper format (see below). 37 | - Push your changes to a topic branch in your fork of the repository. 38 | - Make sure the tests pass, and add any new tests as appropriate. 39 | - Submit a pull request to the original repository. 40 | 41 | Thanks for your contributions! 42 | 43 | ### Format of the Commit Message 44 | 45 | We follow a rough convention for commit messages that is designed to answer two 46 | questions: what changed and why. The subject line should feature the what and 47 | the body of the commit should describe the why. 48 | 49 | ``` 50 | scripts: add the test-cluster command 51 | 52 | this uses tmux to setup a test cluster that you can easily kill and 53 | start for debugging. 54 | 55 | Fixes #38 56 | ``` 57 | 58 | The format can be described more formally as follows: 59 | 60 | ``` 61 | : 62 | 63 | 64 | 65 |