en: translate open_mic_27_03_2026

Translate open_mic_27_03_2026 page into English.

Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>

1 files changed, 86 insertions, 0 deletions

diff --git a/content/en/open_mic_27_03_2026/_index.md b/content/en/open_mic_27_03_2026/_index.md
new file mode 100644
index 0000000..3542396
--- /dev/null
+++ b/content/en/open_mic_27_03_2026/_index.md
@@ -0,0 +1,86 @@
+# 🎙️ Open Mic #001
+
+## “Forking the Kernel. Engineers for Engineers, or What Does LANDAU Have to Do with It?”
+
+---
+
+📅 **Date:** March 27, 2026
+⏰ **Time:** 20:00
+📍 **Format:** In‑person / Online (hybrid)
+👥 **Organiser:** [RULKC](https://rulkc.org) (Russian Linux Kernel Community)
+
+---
+
+## 🧭 About the meeting
+
+We are launching a series of practical discussions focused on the challenges of maintaining Linux kernel technical work in the current environment. The topic of the first meeting is intentionally broad in order to gather as many engineering opinions as possible.
+
+**👋 We invite the following to take part in the conversation:**
+*   🐧 Linux kernel developers and maintainers from Russian companies
+*   🔌 Embedded systems engineers and hardware developers
+*   💡 Anyone interested in the future of the Linux platform in Russia
+
+---
+
+## ❓ Key discussion questions
+
+During the discussion, we will address the creation of a unified Linux kernel fork by Russian engineers, maintainers, and hardware vendors.
+We will talk about needs and goals, risks, architecture, and the support model for such a project.
+
+The meeting will be held as an open‑mic discussion with moderators:
+
+1.  **🤔 Do we need a unified fork?**
+    *   Does the engineering community need one?
+    *   How does each company currently maintain its own forks?
+    *   What practical problems could it solve (code duplication, maintenance difficulties, sanctions‑related risks when collaborating)?
+
+2.  **🖧 Hardware support**
+    *   How can we effectively organise joint work on drivers for Baikal, Elbrus, RISC‑V, and other processors, as well as peripheral devices?
+    *   Is there a critical mass to unify code from various vendors?
+    *   Do users need accessible, discussable, and cross‑validated code?
+    *   Do we need a common “sandbox” for experiments?
+    *   In which products and releases could LANDAU be used? For embedded systems, desktops, servers?
+
+3.  **🏗️ Development model**
+    *   Should the fork be only the kernel itself, or should it include a minimal test environment?
+    *   How often should we rebase to new upstream versions?
+    *   Should the fork have LTS branches? If so, how often should they be released?
+
+4.  **⚙️ Infrastructure**
+    *   How can we build a distributed CI lab for testing (based on Kernel‑CI and LAVA) on real hardware?
+    *   Who is ready to share resources?
+
+---
+
+## 🎯 Expected outcomes
+
+By the end of the meeting, we plan to:
+
+*   📊 **Identify market needs** for a unified kernel fork
+*   🗣️ **Hear participants’ opinions** on their readiness to invest resources into supporting the fork
+*   🎯 **Prioritise areas** for further work
+*   👣 **Discuss next steps** — holding additional meetings with different participants, creating a working group, possible legal formalisation of the activity
+
+---
+
+## 💡 Why is this important?
+
+The goal of this meeting is **to hear each other**.
+To understand the pain points of different teams, where we can join forces right now, and which issues require deeper discussion with lawyers and managers.
+
+📊 The outcome will be a **list of engineering community needs** that will form the basis for the next steps of the ⚛️ LANDAU project.
+
+---
+
+## 📝 Registration and contacts
+
+To participate (especially in the in‑person format), please follow the link:
+🔗 [https://tabs.mts.ru/share/shrjzSDNCwDjT3kp6VNWE](https://tabs.mts.ru/share/shrjzSDNCwDjT3kp6VNWE)
+
+---
+
+**Contact person:** RULKC
+📧 [rulkc@rulkc.org](mailto:rulkc@rulkc.org)
+💬 [t.me/linux_kernel_O](https://t.me/linux_kernel_O)
+
+[⬅️ Back to LANDAU main page](../)
\ No newline at end of file