flatcar · John15321 · Mar 30, 2026
@@ -1,71 +1,13 @@
-# How to Contribute
+Welcome! We're so glad you're here and interested in contributing to Flatcar! 💖
 
-CoreOS projects are [Apache 2.0 licensed](LICENSE) and accept contributions via
-GitHub pull requests.  This document outlines some of the conventions on
-development workflow, commit message formatting, contact points and other
-resources to make it easier to get your contribution accepted.
+Whether you're fixing a bug, adding a feature, or improving docs — we appreciate you!
 
-# Certificate of Origin
+For more detailed guidelines (finding issues, community meetings, PR lifecycle, commit message format, and more), check out the [main Flatcar CONTRIBUTING guide](https://github.com/flatcar/Flatcar/blob/main/CONTRIBUTING.md).
 
-By contributing to this project you agree to the Developer Certificate of
-Origin (DCO). This document was created by the Linux Kernel community and is a
-simple statement that you, as a contributor, have the legal right to make the
-contribution. See the [DCO](DCO) file for details.
+---
 
-# Email and Chat
+## Repository Specific Guidelines
 
-The project currently uses the general CoreOS email list and IRC channel:
-- Email: [coreos-dev](https://groups.google.com/forum/#!forum/coreos-dev)
-- IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org
+Any guidelines specific to this repository that are not covered in the main contribution guide will be listed here.
 
-Please avoid emailing maintainers found in the MAINTAINERS file directly. They
-are very busy and read the mailing lists.
-
-## Getting Started
-
-- Fork the repository on GitHub
-- Read the [README](README.md) for build and test instructions
-- Play with the project, submit bugs, submit patches!
-
-## Contribution Flow
-
-This is a rough outline of what a contributor's workflow looks like:
-
-- Create a topic branch from where you want to base your work (usually master).
-- Make commits of logical units.
-- Make sure your commit messages are in the proper format (see below).
-- Push your changes to a topic branch in your fork of the repository.
-- Make sure the tests pass, and add any new tests as appropriate.
-- Submit a pull request to the original repository.
-
-Thanks for your contributions!
-
-### Format of the Commit Message
-
-We follow a rough convention for commit messages that is designed to answer two
-questions: what changed and why. The subject line should feature the what and
-the body of the commit should describe the why.
-
-```
-scripts: add the test-cluster command
-
-this uses tmux to setup a test cluster that you can easily kill and
-start for debugging.
-
-Fixes #38
-```
-
-The format can be described more formally as follows:
-
-```
-<subsystem>: <what changed>
-<BLANK LINE>
-<why this change was made>
-<BLANK LINE>
-<footer>
-```
-
-The first line is the subject and should be no longer than 70 characters, the
-second line is always blank, and other lines should be wrapped at 80 characters.
-This allows the message to be easier to read on GitHub as well as in various
-git tools.
+<!-- Add repo-specific guidelines below this line -->
@@ -1 +1 @@
-ghcr.io/flatcar/mantle:git-0aa1b3f42f11db9c3d3053f54dbdc1b1136a02e0
+ghcr.io/flatcar/mantle:git-eee95857ce80d8740f8bb756ac2358a2b1dee73f
@@ -1,16 +1,12 @@
-From 8bf635277ccd8f0aeb3bb2e2c67f73dd4188e618 Mon Sep 17 00:00:00 2001
-From: James Le Cuirot <jlecuirot@microsoft.com>
-Date: Wed, 25 Mar 2026 10:55:24 +0000
-Subject: [PATCH 18/21] /usr/share/oem -> /oem
+From 12188bc2ac6220685b9a43132d0e85dce36c4ca5 Mon Sep 17 00:00:00 2001
+From: Krzesimir Nowak <knowak@microsoft.com>
+Date: Tue, 4 Apr 2023 12:12:42 +0200
+Subject: [PATCH 18/19] /usr/share/oem -> /oem
 
-Flatcar previously kept looking at the initrd's /usr/share/oem even
-after the migration for compatibility, but the minimal initrd now moves
-it to /oem before Ignition starts.
 ---
- config/util/translate.go    | 2 +-
- docs/supported-platforms.md | 2 +-
- internal/distro/distro.go   | 2 +-
- 3 files changed, 3 insertions(+), 3 deletions(-)
+ config/util/translate.go  | 2 +-
+ internal/distro/distro.go | 5 ++++-
+ 2 files changed, 5 insertions(+), 2 deletions(-)
 
 diff --git a/config/util/translate.go b/config/util/translate.go
 index 347d148c..d4c057b2 100644
@@ -25,32 +21,22 @@ index 347d148c..d4c057b2 100644
  		} else {
  			// generate a new path
  			fsMap[name] = "/tmp/" + name + "-ign" + strconv.FormatUint(addedSuffixCounter, 10)
-diff --git a/docs/supported-platforms.md b/docs/supported-platforms.md
-index 0a30664c..1522d0ef 100644
---- a/docs/supported-platforms.md
-+++ b/docs/supported-platforms.md
-@@ -12,7 +12,7 @@ Ignition is currently supported for the following platforms:
- * [Amazon Web Services] (`aws`) - Ignition will read its configuration from the instance userdata. Cloud SSH keys are handled separately.
- * [Microsoft Azure] (`azure`)- Ignition will read its configuration from the custom data provided to the instance. Cloud SSH keys are handled separately.
- * [Microsoft Azure Stack] (`azurestack`) - Ignition will read its configuration from the custom data provided to the instance. Cloud SSH keys are handled separately.
--* Bare Metal - Use the `ignition.config.url` kernel parameter to provide a URL to the configuration. The URL can use the `http://`, `https://`, `tftp://`, `s3://`, or `gs://` schemes to specify a remote config or the `oem://` scheme to specify a local config, rooted in `/usr/share/oem`.
-+* Bare Metal - Use the `ignition.config.url` kernel parameter to provide a URL to the configuration. The URL can use the `http://`, `https://`, `tftp://`, `s3://`, or `gs://` schemes to specify a remote config or the `oem://` scheme to specify a local config, rooted in `/oem`.
- * [Brightbox] (`brightbox`) - Ignition will read its configuration from the instance userdata. Cloud SSH keys are handled separately.
- * [CloudStack] (`cloudstack`) - Ignition will read its configuration from the instance userdata via either metadata service or config drive. Cloud SSH keys are handled separately.
- * `cloudsigma` - Ignition will read its configuration from the instance userdata. Cloud SSH keys are handled separately.
 diff --git a/internal/distro/distro.go b/internal/distro/distro.go
-index f3c32aaf..36bdf3f5 100644
+index f3c32aaf..7359eefe 100644
 --- a/internal/distro/distro.go
 +++ b/internal/distro/distro.go
-@@ -33,7 +33,7 @@ var (
+@@ -32,7 +32,10 @@ var (
+ 	bootIDPath        = "/proc/sys/kernel/random/boot_id"
  	// initramfs directory containing distro-provided base config
  	systemConfigDir = "/usr/lib/ignition"
- 	// initramfs directory to check before retrieving file from OEM partition
--	oemLookasideDir = "/usr/share/oem"
-+	oemLookasideDir = "/oem"
+-	// initramfs directory to check before retrieving file from OEM partition
++	// initramfs directory to check before retrieving file from
++	// OEM partition; note that OEM partition is mounted on /oem
++	// on the host, but initrds still use /usr/share/oem for
++	// backwards compatilibity
+ 	oemLookasideDir = "/usr/share/oem"
 
  	// Helper programs
- 	groupaddCmd  = "groupadd"
 -- 
-2.53.0
+2.51.0
 
@@ -35,8 +35,6 @@ else
 		"${FILESDIR}/0017-docs-Add-re-added-platforms-to-docs-to-pass-tests.patch"
 		"${FILESDIR}/0018-usr-share-oem-oem.patch"
 		"${FILESDIR}/0019-internal-exec-stages-mount-Mount-oem.patch"
-		"${FILESDIR}/0020-Create-mnt-directory-before-attempting-to-mount-OEM-.patch"
-		"${FILESDIR}/0021-Replace-deprecated-ioutil.TempDir-call-with-os.Mkdir.patch"
 	)
 fi
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		ghcr.io/flatcar/mantle:git-0aa1b3f42f11db9c3d3053f54dbdc1b1136a02e0
		ghcr.io/flatcar/mantle:git-eee95857ce80d8740f8bb756ac2358a2b1dee73f