Hello Kyle it's like gdocs, but markdown I think we paste in the README with the features to start off with and then we can slice it and dice it people can comment etc

One of the neat things about Open Source is all the things you get to learn about teamwork and coordinating with others. This can lead to great things, but sometimes it's so easy to start off excited, and then pick a project and drown immediately. Bob Killen recently distilled his contributor lessons over years of contributing to Kubernetes and other Cloud Native projects. Consider this the blog version: The best tip we can recommend is to educate yourself about the project, its community and their contributor processes BEFORE asking questions. Look for a CONTRIBUTING.md file in the repository and start from there. People are much more willing to help you if you ask "Hey, I noticed this issue is still open. I’m interested in working on it, but couldn’t find info on <foo>, is there a good reference or person I can talk to about it?" vs "Hey, I’m new to <project> and want to contribute, where do I start"? Starting with good-first-issue labelled issues never hurts, and you can use tools like CLOtributor to aggregate good first issues across projects, so if you fancy a certain language or tech stack you can start from a knowledgeable place.

As part of our move to beta we've found a scaling issue that needs to be sorted; skip below if you just want the instructions. Initially the Nvidia images were signed by a key scoped only to the ublue-os/nvidia repository. At the time, we didn't expect to grow much past that, but now we want to add more akmods (like OBS loopback camera, XBox Wireless Controllers, etc.) which we are building in a seperate ublue-os/akmods repository as a "new layer" if you will. As part of our secrets management process, we are regenerating the keys used for Secure Boot signing our kernel modules. This means existing users must install a new key for all of Universal Blue akmods in addition to the key specific to Nvidia. On June 17th, we will switch Secure Boot signing to use the new key; from that time on only the new new key will be required. As of this morning the new key is on the images, so subsequent new installations will be fine.

Welcome new users! Today we're putting a 1.0 stamp on the uBlue Nvidia images. These are images of Fedora Silverblue (GNOME), Kinoite (KDE), Vauxite (XFCE), Sericea (Sway), LXQt, and MATE. Find them here (ISOs will be coming later, see below) What is this? Over the past few years, Fedora CoreOS has been working on making OCI containers the primary mechanism for delivering image-based updates to clients.

opensuse microOS With special guest star Richard Brown. (These are just notes, feel free to add/edit, move stuff, anything you think would be good to talk about) Vibe: "Comedians in Cars getting coffee but for linux". Two people just having a conversation about something they're passionate about. A tour of the OS with chitchat.