Merge pull request #418 from Nordix/lentzi90/metal3-at-kubeconf

Post: Metal3 at KubeCon EU 2024

.cspell-config.json

@@ -69,6 +69,7 @@
     "com",
     "ConfigMap",
     "contrib",
+    "contribfest",
     "Controlplane",
     "CoreOS",
     "Cormier",
@@ -107,6 +108,7 @@
     "failovers",
     "faqs",
     "firewalld",
+    "Flickr",
     "foo",
     "fubarhouse",
     "Garima",

_posts/2024-04-10-Metal3_at_KubeCon_EU_2024.md

@@ -0,0 +1,60 @@
+---
+title: "Metal3 at KubeCon EU 2024"
+date: 2024-04-10
+draft: false
+categories: ["metal3", "talk", "conference", "kubecon"]
+author: Lennart Jern
+---
+
+The Metal3 project was present at KubeCon EU 2024 with multiple maintainers,
+contributors and users! For many of us, this was the first time we met in the
+physical world, despite working together for years already. This was very
+valuable and appreciated by many of us, I am sure. We had time to casually
+discuss ideas and proposals, hack together on the
+[ironic-standalone-operator](https://github.com/metal3-io/ironic-standalone-operator)
+and simply get to know each other.
+
+![Lightning
+talk](/assets/2024-04-10-Metal3_at_KubeCon_EU_2024/lightningtalk.jpg)
+
+*Photo by Michael Captain.*
+
+As a project, we had the opportunity to give an update through a [lightning
+talk](https://www.youtube.com/watch?v=6QsOQsQZQS8) on Tuesday!
+
+<!-- markdownlint-disable no-inline-html -->
+<iframe width="560" height="315" src="https://www.youtube.com/embed/6QsOQsQZQS8?si=bH5w9svPxM1NE8Le" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
+<!-- markdownlint-enable no-inline-html -->
+
+On Wednesday we continued with a [contribfest session](https://sched.co/1YheY)
+where we gave an introduction to the project for potential new contributors. We
+had prepared a number of good-first-issue's that people could choose from if
+they wanted. Perhaps more important though, was that we had time to answer
+questions, discuss use-cases, issues and features with the attendees. The new
+[quick-start](https://book.metal3.io/quick-start) page was also launched just in
+time for the contribfest. It should hopefully make it easier to get started with
+the project and we encourage everyone to run through it and report or fix any
+issues found.
+
+![Contribfest](/assets/2024-04-10-Metal3_at_KubeCon_EU_2024/contribfest.jpg)
+
+*Photo from the official CNCF Flickr. More photos
+[here](https://www.flickr.com/photos/143247548@N03/53609847541/in/album-72177720315561784/).*
+
+Finally, just like previous, we had a table in the Project Pavilion. There was a
+lot of interest in Metal3, more than last year I would say. Even with five
+maintainers working in parallel, we still had a hard time keeping up with the
+amount of people stopping by to ask questions! My takeaway from this event is
+that we still have work to do on explaining what Metal3 is and how it works. It
+is quite uncommon that people know about baseboard management controllers (BMCs)
+and this of course makes it harder to grasp what Metal3 is all about. However,
+the interest is there, so we just need to get the information out there so that
+people can learn! Another takeaway is that Cluster API in general seems to
+really take off. Many people that came by our kiosk knew about Cluster API and
+were interested in Metal3 because of the integration with have with it.
+
+For those of you who couldn't attend, I hope this post gives an idea about what
+happened at KubeCon related to Metal3. Did you miss the contribfest? Maybe you
+would like to contribute but don't know where to start? Check out the
+[good-first-issue's](https://github.com/issues?page=1&q=archived%3Afalse+user%3Ametal3-io+label%3A%22good+first+issue%22+is%3Aissue+sort%3Acreated-asc+is%3Aopen)!
+There are still plenty to choose from, and we will keep adding more.

_sass/_reset.scss

@@ -63,7 +63,7 @@
     audio,
     video {
       max-width: 100%;
-      height: auto;
+      // height: auto;
     }
 
     iframe {