join/WelcomeToFedora

Fork 1

Welcome to Fedora: @flrnd #187

New issue

Open

opened 2026-07-09 13:58:52 +00:00 by niknikovsky · 5 comments

niknikovsky commented

2026-07-09 13:58:52 +00:00

Member

Welcome Message & Introduction

Welcome

Hello @flrnd(FAS profile)! Welcome to Fedora!

Before we begin, please subscribe to the Fedora join mailing list at fedora-join@lists.fedoraproject.org. We use this list for general discussion, and it is also where the community shares tasks that need help.

These links are a good read to begin with. They tell you what the Free/Open Source community is about, and then they'll introduce you to Fedora: what Fedora is all about, and what we do, and of course, how we do it:

Next, when you're ready, could you please introduce yourself (preferably on the list) so that the community can get to know you? (Interests, skills, anything you wish to say about yourself really).

Finally, could you let us know how you learned about the Fedora project? Was it from a colleague, or social media, for example?

If you have any questions at all, please ask! We'll use this ticket to keep in touch! :)

Get to know each other better

In addition, could you provide some information to understand your requirements better? (You can write them in the introduction, or answer here if you feel more comfortable).

For example:

your experience with Free/Open Source Software (FOSS) communities/ecosystems:
- have you participated in FOSS before, or is this the first time?
- how do you imagine your place in a FOSS community?
your background/skills, for example:
- community development and outreach, campaigning, journalism
- Operating System (Do you use GNU/Linux as your main OS? Is Fedora Linux your main distribution?)
- non-software development: design (Inkscape/Gimp/?), music/video/podcasting, marketing, language proficiency
- software development related: command line, version control: git/hg/svn/?, rpm/packaging, programming languages/frameworks/utilities, testing, infrastructure/sysadmin
your experience in communication platforms:
- have you used mailing lists before?
- what is your preferred real time chat platform?
- have you helped with moderating/administering forums?
how much time are you looking to/are you able to spend on volunteering (approximate hours per week)?

Remember that this is not a job interview at all. This is just an icebreaker to help all your new friends get to know you quicker. The better we know you, the better we can support you in identifying Fedora activities that promise to be relevant for you.

Please write how much/whatever you wish. :).

### Welcome Message & Introduction # Welcome Hello `@flrnd`([FAS profile](https://accounts.fedoraproject.org/user/flrnd/))! Welcome to Fedora! Before we begin, please subscribe to the [Fedora join mailing list at fedora-join@lists.fedoraproject.org](https://lists.fedoraproject.org/admin/lists/fedora-join.lists.fedoraproject.org/). We use this list for general discussion, and it is also where the community shares tasks that need help. These links are a good read to begin with. They tell you what the Free/Open Source community is about, and then they'll introduce you to Fedora: what Fedora is all about, and what we do, and of course, how we do it: - [What is Free Software: a quick video!](https://www.fsf.org/blogs/community/user-liberation-watch-and-share-our-new-video) - [Fedora's Mission and Foundations](https://docs.fedoraproject.org/en-US/project/) - [Fedora's Code of Conduct](https://docs.fedoraproject.org/en-US/project/code-of-conduct/) - [How is Fedora Organized?](https://docs.fedoraproject.org/en-US/project/orgchart/) - [Fedora's Current 12-18 Month Community Objectives](https://docs.fedoraproject.org/en-US/project/objectives/) - [Get started with badges!](https://docs.fedoraproject.org/en-US/fedora-join/welcome/badges/) - [How to be a successful contributor](https://docs.fedoraproject.org/en-US/fedora-join/contribute/successful-contributor/) Next, when you're ready, could you please introduce yourself (preferably on the list) so that the community can get to know you? (Interests, skills, anything you wish to say about yourself really). Finally, could you let us know how you learned about the Fedora project? Was it from a colleague, or social media, for example? If you have any questions at all, please ask! We'll use this ticket to keep in touch! :) ## Get to know each other better In addition, could you provide some information to understand your requirements better? (You can write them in the introduction, or answer here if you feel more comfortable). For example: - your experience with Free/Open Source Software (FOSS) communities/ecosystems: - have you participated in FOSS before, or is this the first time? - how do you imagine your place in a FOSS community? - your background/skills, for example: - community development and outreach, campaigning, journalism - Operating System (Do you use GNU/Linux as your main OS? Is Fedora Linux your main distribution?) - non-software development: design (Inkscape/Gimp/?), music/video/podcasting, marketing, language proficiency - software development related: command line, version control: git/hg/svn/?, rpm/packaging, programming languages/frameworks/utilities, testing, infrastructure/sysadmin - your experience in communication platforms: - have you used mailing lists before? - what is your preferred real time chat platform? - have you helped with moderating/administering forums? - how much time are you looking to/are you able to spend on volunteering (approximate hours per week)? Remember that this is not a job interview at all. This is just an icebreaker to help all your new friends get to know you quicker. The better we know you, the better we can support you in identifying Fedora activities that promise to be relevant for you. Please write how much/whatever you wish. :).

niknikovsky added the

C: Introduction requested

S: Hello Fedora World

labels

2026-07-09 13:58:52 +00:00

flrnd commented

2026-07-09 18:01:55 +00:00

Hi everyone! Wall of text incoming!

I'm Raúl (or my personal brand that I use for all things engineering Florian Rand, long story), a software engineer from Spain, and I'm excited to finally become part of the Fedora community.

I've been using Linux for almost twenty years. I first discovered it in high school with Slackware, and it completely changed how I looked at computers. I remember buying a book about C programming on Unix systems just so I could better understand what was happening under the hood. I spent countless hours experimenting with things like libpcap, rebuilding tools such as tcpdump, and generally taking things apart to see how they worked.

Since then Linux has been my primary operating system. Over the years I've used Debian, Ubuntu, Fedora and openSUSE, and although Ubuntu is currently my daily workstation, I still use Fedora extensively for my development containers and have spent quite a bit of time running Silverblue. Somewhere at home I even have a couple of old Red Hat CDs that I've never been able to throw away.

Although I've relied on open source software for most of my career, my contributions have mostly been small and practical: reporting bugs, helping with translations, documentation improvements, and submitting patches that solved problems I encountered mysel.

Professionally, I started as a Linux systems administrator. One of my first self-appointed projects was converting a nearly 100-page handwritten notebook of operational procedures into reusable shell scripts. Nobody asked me to do it—I simply got tired of repeatedly looking things up and wanted to make the work easier for everyone. Looking back, that probably says a lot about how I approach engineering.

After several years in systems administration I took an unexpected detour into graphic design and digital production, working in the automotive industry. Even then I found myself gravitating back toward technical problems: helping with render farms, improving automation scripts, and solving infrastructure issues. Eventually I returned to software engineering full time.

Today I've worked across frontend and backend development, internal tooling, application modernization, CI/CD, containers, and developer experience. I've come to realize that what I enjoy most isn't any particular language or framework—it's understanding systems, removing unnecessary complexity, and making other people's work a little easier. The problems that attract me most are usually the ones everyone has learned to work around until someone finally decides to fix them properly.

Technically I'm comfortable with Linux, Git, shell scripting, containers (especially Podman), JavaScript/TypeScript, Java, C, Go, Ansible, CI/CD, and general software engineering. I've also done RPM and DEB packaging in the past, although I'd definitely appreciate a refresher.

Outside of work I spend far too much time tinkering with my homelab. I recently simplified it from a fairly involved Proxmox setup to a much simpler Podman + systemd Quadlets + Cockpit setup, and I'm irrationally happy with that decision. Away from the keyboard I enjoy running, science fiction, classical singing, and spending time with my cats.

As for Fedora, it feels like a natural place to contribute. I've admired the engineering culture around Fedora and Red Hat for many years—particularly the emphasis on building in the open and contributing work upstream—and I'd like to become part of that ecosystem. My plan is to start with small contributions, learn how the community works, and hopefully grow into taking on larger responsibilities over time.

I'm looking forward to meeting you all and learning where I can best contribute.

PSA: I will try to send a copy to the mailing list.

Hi everyone! Wall of text incoming! I'm Raúl (or my personal brand that I use for all things engineering Florian Rand, long story), a software engineer from Spain, and I'm excited to finally become part of the Fedora community. I've been using Linux for almost twenty years. I first discovered it in high school with Slackware, and it completely changed how I looked at computers. I remember buying a book about C programming on Unix systems just so I could better understand what was happening under the hood. I spent countless hours experimenting with things like libpcap, rebuilding tools such as tcpdump, and generally taking things apart to see how they worked. Since then Linux has been my primary operating system. Over the years I've used Debian, Ubuntu, Fedora and openSUSE, and although Ubuntu is currently my daily workstation, I still use Fedora extensively for my development containers and have spent quite a bit of time running Silverblue. Somewhere at home I even have a couple of old Red Hat CDs that I've never been able to throw away. Although I've relied on open source software for most of my career, my contributions have mostly been small and practical: reporting bugs, helping with translations, documentation improvements, and submitting patches that solved problems I encountered mysel. Professionally, I started as a Linux systems administrator. One of my first self-appointed projects was converting a nearly 100-page handwritten notebook of operational procedures into reusable shell scripts. Nobody asked me to do it—I simply got tired of repeatedly looking things up and wanted to make the work easier for everyone. Looking back, that probably says a lot about how I approach engineering. After several years in systems administration I took an unexpected detour into graphic design and digital production, working in the automotive industry. Even then I found myself gravitating back toward technical problems: helping with render farms, improving automation scripts, and solving infrastructure issues. Eventually I returned to software engineering full time. Today I've worked across frontend and backend development, internal tooling, application modernization, CI/CD, containers, and developer experience. I've come to realize that what I enjoy most isn't any particular language or framework—it's understanding systems, removing unnecessary complexity, and making other people's work a little easier. The problems that attract me most are usually the ones everyone has learned to work around until someone finally decides to fix them properly. Technically I'm comfortable with Linux, Git, shell scripting, containers (especially Podman), JavaScript/TypeScript, Java, C, Go, Ansible, CI/CD, and general software engineering. I've also done RPM and DEB packaging in the past, although I'd definitely appreciate a refresher. Outside of work I spend far too much time tinkering with my homelab. I recently simplified it from a fairly involved Proxmox setup to a much simpler Podman + systemd Quadlets + Cockpit setup, and I'm irrationally happy with that decision. Away from the keyboard I enjoy running, science fiction, classical singing, and spending time with my cats. As for Fedora, it feels like a natural place to contribute. I've admired the engineering culture around Fedora and Red Hat for many years—particularly the emphasis on building in the open and contributing work upstream—and I'd like to become part of that ecosystem. My plan is to start with small contributions, learn how the community works, and hopefully grow into taking on larger responsibilities over time. I'm looking forward to meeting you all and learning where I can best contribute. PSA: I will try to send a copy to the mailing list.

niknikovsky added

S: Introduced myself

and removed

C: Introduction requested

labels

2026-07-09 18:07:01 +00:00

niknikovsky commented

2026-07-31 19:55:53 +00:00

Author

Member

Hello!
Just doing a quick check-in to see how you're settling in.
Are you stuck anywhere, or would you like some guidance on finding a team to join? Feel free to ask any questions!

Hello! Just doing a quick check-in to see how you're settling in. Are you stuck anywhere, or would you like some guidance on finding a team to join? Feel free to ask any questions!

niknikovsky added the

C: Progress check 1

label

2026-07-31 19:55:58 +00:00

niknikovsky added this to the Welcome to Fedora ticket board project

2026-07-31 20:47:20 +00:00

flrnd commented

2026-08-01 10:50:33 +00:00

Hello, thanks for reaching out!

To be honest, not much progress. Over the past few weeks I've taken a look at a few projects and SIGs to get a better feel for the ecosystem.

I've realized that most of my open source contributions tend to come from problems I encounter during day-to-day use rather than from picking up predefined tasks. Right now I'm familiarising myself with the Websites project codebase.

I'm still interested in contributing, though.

Hello, thanks for reaching out! To be honest, not much progress. Over the past few weeks I've taken a look at a few projects and SIGs to get a better feel for the ecosystem. I've realized that most of my open source contributions tend to come from problems I encounter during day-to-day use rather than from picking up predefined tasks. Right now I'm familiarising myself with the Websites project codebase. I'm still interested in contributing, though.

niknikovsky removed the

C: Progress check 1

label

2026-08-01 11:50:45 +00:00

niknikovsky commented

2026-08-01 13:31:08 +00:00

Author

Member

I just realized that no one replied to you, so I generated some recommendations on which teams to join based on your introduction:

Recommended Teams & Areas

Fedora Atomic Desktops & Container SIG:
Since you spend time with Silverblue, Podman, and Quadlets, the Atomic Desktops team (Silverblue, Kinoite, Sericea, Onyx) and Container SIG are prime choices. You can help improve host/container workflows, build Quadlet integrations, or contribute to containerized image tooling.
Package Maintenance & Papercuts:
If you want to refresh your RPM packaging skills, getting started with co-maintaining packages or picking up orphaned packages is a great entry point. It's also the best way to directly fix those annoying bugs and papercuts you encounter in software.
Fedora Infrastructure & DevEx Tooling:
Your background in CI/CD, Ansible, C, Go, and internal tooling fits perfectly with the Fedora Infra team. They maintain the backend pipelines, build system tooling, and services that keep the distribution running.
Fedora Design Team (Bonus!):
Since you spent time in graphic design and digital production, if you ever want to scratch that creative itch, the Fedora Design team is always looking for folks who understand both technical workflows and visual design.

Next Steps

Say Hello on Matrix: Pop into the Matrix channels that catch your eye:

Fedora Join (General Onboarding): #join:fedoraproject.org
Atomic Desktops: #atomic:fedoraproject.org
Infrastructure: #infrastructure:fedoraproject.org
Packaging: #fedora-devel:fedoraproject.org
Design: #design:fedoraproject.org
Most of this content was generated with the use of Artificial Intelligence

I just realized that no one replied to you, so I generated some recommendations on which teams to join based on your introduction: ### Recommended Teams & Areas * **Fedora Atomic Desktops & Container SIG:** Since you spend time with Silverblue, Podman, and Quadlets, the Atomic Desktops team (Silverblue, Kinoite, Sericea, Onyx) and Container SIG are prime choices. You can help improve host/container workflows, build Quadlet integrations, or contribute to containerized image tooling. * **Package Maintenance & Papercuts:** If you want to refresh your RPM packaging skills, getting started with co-maintaining packages or picking up orphaned packages is a great entry point. It's also the best way to directly fix those annoying bugs and papercuts you encounter in software. * **Fedora Infrastructure & DevEx Tooling:** Your background in CI/CD, Ansible, C, Go, and internal tooling fits perfectly with the Fedora Infra team. They maintain the backend pipelines, build system tooling, and services that keep the distribution running. * **Fedora Design Team (Bonus!):** Since you spent time in graphic design and digital production, if you ever want to scratch that creative itch, the Fedora Design team is always looking for folks who understand both technical workflows and visual design. ### Next Steps **Say Hello on Matrix:** Pop into the Matrix channels that catch your eye: * **Fedora Join (General Onboarding):** `#join:fedoraproject.org` * **Atomic Desktops:** `#atomic:fedoraproject.org` * **Infrastructure:** `#infrastructure:fedoraproject.org` * **Packaging:** `#fedora-devel:fedoraproject.org` * **Design:** `#design:fedoraproject.org` *Most of this content was generated with the use of Artificial Intelligence*

flrnd commented

2026-08-02 09:24:13 +00:00

Thanks for the pointers!

I've joined the Infrastructure Matrix room, and I'll take a look at the other suggestions too.

Thanks for the pointers! I've joined the Infrastructure Matrix room, and I'll take a look at the other suggestions too.