join/WelcomeToFedora
10
2
Fork 1
Code Issues 149 Pull requests Projects 1 Wiki Activity Actions

Welcome to Fedora: @willwic #182

New issue
Open
opened 2026-06-25 16:22:33 +00:00 by ankursinha · 9 comments
ankursinha commented 2026-06-25 16:22:33 +00:00
Owner
Copy link

Welcome Message & Introduction

Welcome

Hello @willwic(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 `@willwic`([FAS profile](https://accounts.fedoraproject.org/user/willwic/))! 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. :).
willwic commented 2026-06-26 04:21:50 +00:00
Copy link

Hi, my name is William. A computer science major from Malaysia. My main area of interest are in computer and gaming. I had finish my internship last april and since then I want to explore more about os development. During my internship, I had an opportunity to learn about software development and quality assurance. This internship help me gain exposure about how tech really works in real-world. So after my internship, I tried to learn C as my new programming language and found out that I had fun while learning. Furthermre, I tried to build a C project which currently is still in planning status, but I realized it maybe too ambitious for me to feast it once for all. Then, I did some research using LLM (gemini) and google, found out that I can join a open source community to able to learn more about C.

Here are the answers that is requested in the top comment:

  1. Experience with Free/Open Source Software (FOSS) communities/ecosystems:
  • This is my first experience in a FOSS community and I want to try and contribute to upskill myself as an software engineer.
  1. Background/skills:
  • Language Proficiency: Chinese, English, Malay
  • Programming: Python, Java, C
  • DevOps: Docker, Kubernetes, Git, Github, Jira/Bitbucket
  • Web Programming: TypeScript, React, Angular
  • Database: Postgresql
  • Operating Systems: Linux Mint, Ubuntu, Fedora, Windows (Current OS), Arch (Failed on Installing Network Driver) 😢
  • DE: KDE Plasma, Cinnamon, Gnome (I like this the most), Windows
  • Software Testing: RobotFramework (A Testing Language based on Python)
  1. Experience in communication platforms
  • Mailing List: Outlook, Gmail
  • I dont have a preferred chat platform but in Malaysia we mostly use WhatsApp, Discord, Facebook Messenger and Instagram for messaging.
  • I haven't helped with moderating/administering forums before
  1. How much time are you looking to/are you able to spend on volunteering (approximate hours per week)?
    As for now, I have finished my studies and currently looking for work. Right now, I able to spend on volunteering about 12 hours per week depending on the task and learning curve. Not sure if I able to commit on volunteering after I found a designated role, but I will try atleast 4 hours per week.

tl:dr I want to learn more about os development/programming 😁

Hi, my name is William. A computer science major from Malaysia. My main area of interest are in computer and gaming. I had finish my internship last april and since then I want to explore more about os development. During my internship, I had an opportunity to learn about software development and quality assurance. This internship help me gain exposure about how tech really works in real-world. So after my internship, I tried to learn C as my new programming language and found out that I had fun while learning. Furthermre, I tried to build a C project which currently is still in planning status, but I realized it maybe too ambitious for me to feast it once for all. Then, I did some research using LLM (gemini) and google, found out that I can join a open source community to able to learn more about C. Here are the answers that is requested in the top comment: 1. Experience with Free/Open Source Software (FOSS) communities/ecosystems: - This is my first experience in a FOSS community and I want to try and contribute to upskill myself as an software engineer. 2. Background/skills: - Language Proficiency: Chinese, English, Malay - Programming: Python, Java, C - DevOps: Docker, Kubernetes, Git, Github, Jira/Bitbucket - Web Programming: TypeScript, React, Angular - Database: Postgresql - Operating Systems: Linux Mint, Ubuntu, Fedora, Windows (Current OS), Arch (Failed on Installing Network Driver) 😢 - DE: KDE Plasma, Cinnamon, Gnome (I like this the most), Windows - Software Testing: RobotFramework (A Testing Language based on Python) 3. Experience in communication platforms - Mailing List: Outlook, Gmail - I dont have a preferred chat platform but in Malaysia we mostly use WhatsApp, Discord, Facebook Messenger and Instagram for messaging. - I haven't helped with moderating/administering forums before 4. How much time are you looking to/are you able to spend on volunteering (approximate hours per week)? As for now, I have finished my studies and currently looking for work. Right now, I able to spend on volunteering about 12 hours per week depending on the task and learning curve. Not sure if I able to commit on volunteering after I found a designated role, but I will try atleast 4 hours per week. tl:dr I want to learn more about os development/programming 😁
niknikovsky commented 2026-06-30 08:15:07 +00:00
Member
Copy link

Did I get your interests correctly?

Did I get your interests correctly?
willwic commented 2026-07-01 03:48:31 +00:00
Copy link

Yes, thank u so much! Where do I start learning/contributing on software development?

Yes, thank u so much! Where do I start learning/contributing on software development?
theprogram commented 2026-07-01 04:12:00 +00:00
Owner
Copy link

Most software development is done upstream. If you have some software you would like to contribute to you will have to find their git repo and contact them there.

In Fedora, we package software, and we need help with that. You can learn packaginf from the fine folks in the Matrix #devel:fedoraproject.org channel and you can check out our Fedora Copr system to make your first packages.

As for learning software development, how advanced are you at this time? There are so many languages, you can find a number on out Matrix, such as Python and Go, and the newly started Java room.

Most software development is done upstream. If you have some software you would like to contribute to you will have to find their git repo and contact them there. In Fedora, we package software, and we need help with that. You can learn packaginf from the fine folks in the Matrix #devel:fedoraproject.org channel and you can check out our Fedora Copr system to make your first packages. As for learning software development, how advanced are you at this time? There are so many languages, you can find a number on out Matrix, such as Python and Go, and the newly started Java room.
ankursinha commented 2026-07-01 12:50:09 +00:00
Author
Owner
Copy link

Here's the link for the package maintainers:

https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/

Basically:

  • we take software
  • we build it from source, run all tests, check that it's useful (works, licensed, etc..)
  • we build "rpms" from it (just zip files with the software files and additional metadata)
  • we publish them in repositories so that users can install them using dnf and other package managers.

So, we dont develop most of the software, but we package maintainers do spend a lot of time going through it, fixing bugs, supplying patches to upstream developers. We are the link between users and the developers (because users shouldnt be expected to learn how to debug software, fix bugs, submit patches).

So, while we dont do the main development, we do a LOT of software development as package maintainers. One can also help develop the software---lots of us do---but it's not a necessary part of package maintainer duties.

So, if you are interested in learning the complete software development lifecycle, package maintenance is a great place. You will learn lots of build systems, testing, CI, QA, debugging, patching, dealing with multiple bug trackers etc. etc. etc.

The community does develop some software---this is all the infrastructure that we use. For example, there's a team working with upstream forgejo to implement the features we need in this instance. Koji/Bodhi/ all the stuff we use to create all the Fedora images etc., is all heavily developed by the community.

So, plenty of technical work to do and learn.

How does that sound? Please ask for clarifications etc., happy to provide them.

Here's the link for the package maintainers: https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ Basically: - we take software - we build it from source, run all tests, check that it's useful (works, licensed, etc..) - we build "rpms" from it (just zip files with the software files and additional metadata) - we publish them in repositories so that users can install them using `dnf` and other package managers. So, we dont develop most of the software, but we package maintainers do spend a lot of time going through it, fixing bugs, supplying patches to upstream developers. We are the link between users and the developers (because users shouldnt be expected to learn how to debug software, fix bugs, submit patches). So, while we dont do the main development, we do a LOT of software development as package maintainers. One can also help develop the software---lots of us do---but it's not a necessary part of package maintainer duties. So, if you are interested in learning the complete software development lifecycle, package maintenance is a great place. You will learn lots of build systems, testing, CI, QA, debugging, patching, dealing with multiple bug trackers etc. etc. etc. ---- The community does develop some software---this is all the infrastructure that we use. For example, there's a team working with upstream forgejo to implement the features we need in this instance. Koji/Bodhi/ all the stuff we use to create all the Fedora images etc., is all heavily developed by the community. So, plenty of technical work to do and learn. How does that sound? Please ask for clarifications etc., happy to provide them.
willwic commented 2026-07-02 01:05:17 +00:00
Copy link

@theprogram wrote in #182 (comment):

Most software development is done upstream. If you have some software you would like to contribute to you will have to find their git repo and contact them there.

In Fedora, we package software, and we need help with that. You can learn packaginf from the fine folks in the Matrix #devel:fedoraproject.org channel and you can check out our Fedora Copr system to make your first packages.

As for learning software development, how advanced are you at this time? There are so many languages, you can find a number on out Matrix, such as Python and Go, and the newly started Java room.

Not that advanced, more like a beginner who is trying to explore. I been lately learning about how to use codex for ai development. As for core skills, I try to solve python leetcode problem daily and also learning C as a fun side-project hustle.

@theprogram wrote in https://forge.fedoraproject.org/join/WelcomeToFedora/issues/182#issuecomment-875268: > Most software development is done upstream. If you have some software you would like to contribute to you will have to find their git repo and contact them there. > > In Fedora, we package software, and we need help with that. You can learn packaginf from the fine folks in the Matrix #devel:fedoraproject.org channel and you can check out our Fedora Copr system to make your first packages. > > As for learning software development, how advanced are you at this time? There are so many languages, you can find a number on out Matrix, such as Python and Go, and the newly started Java room. Not that advanced, more like a beginner who is trying to explore. I been lately learning about how to use codex for ai development. As for core skills, I try to solve python leetcode problem daily and also learning C as a fun side-project hustle.
willwic commented 2026-07-02 01:06:57 +00:00
Copy link

@ankursinha wrote in #182 (comment):

Here's the link for the package maintainers:

https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/

Basically:

  • we take software
  • we build it from source, run all tests, check that it's useful (works, licensed, etc..)
  • we build "rpms" from it (just zip files with the software files and additional metadata)
  • we publish them in repositories so that users can install them using dnf and other package managers.

So, we dont develop most of the software, but we package maintainers do spend a lot of time going through it, fixing bugs, supplying patches to upstream developers. We are the link between users and the developers (because users shouldnt be expected to learn how to debug software, fix bugs, submit patches).

So, while we dont do the main development, we do a LOT of software development as package maintainers. One can also help develop the software---lots of us do---but it's not a necessary part of package maintainer duties.

So, if you are interested in learning the complete software development lifecycle, package maintenance is a great place. You will learn lots of build systems, testing, CI, QA, debugging, patching, dealing with multiple bug trackers etc. etc. etc.

The community does develop some software---this is all the infrastructure that we use. For example, there's a team working with upstream forgejo to implement the features we need in this instance. Koji/Bodhi/ all the stuff we use to create all the Fedora images etc., is all heavily developed by the community.

So, plenty of technical work to do and learn.

How does that sound? Please ask for clarifications etc., happy to provide them.

It looks very interesting. I will take a look into the docs on the package maintenance. Looks like a great place to learning new skills.

@ankursinha wrote in https://forge.fedoraproject.org/join/WelcomeToFedora/issues/182#issuecomment-875491: > Here's the link for the package maintainers: > > https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/ > > Basically: > > * we take software > * we build it from source, run all tests, check that it's useful (works, licensed, etc..) > * we build "rpms" from it (just zip files with the software files and additional metadata) > * we publish them in repositories so that users can install them using `dnf` and other package managers. > > So, we dont develop most of the software, but we package maintainers do spend a lot of time going through it, fixing bugs, supplying patches to upstream developers. We are the link between users and the developers (because users shouldnt be expected to learn how to debug software, fix bugs, submit patches). > > So, while we dont do the main development, we do a LOT of software development as package maintainers. One can also help develop the software---lots of us do---but it's not a necessary part of package maintainer duties. > > So, if you are interested in learning the complete software development lifecycle, package maintenance is a great place. You will learn lots of build systems, testing, CI, QA, debugging, patching, dealing with multiple bug trackers etc. etc. etc. > > The community does develop some software---this is all the infrastructure that we use. For example, there's a team working with upstream forgejo to implement the features we need in this instance. Koji/Bodhi/ all the stuff we use to create all the Fedora images etc., is all heavily developed by the community. > > So, plenty of technical work to do and learn. > > How does that sound? Please ask for clarifications etc., happy to provide them. It looks very interesting. I will take a look into the docs on the package maintenance. Looks like a great place to learning new skills.
ankursinha commented 2026-07-02 12:34:13 +00:00
Author
Owner
Copy link

@willwic wrote in #182 (comment):

Not that advanced, more like a beginner who is trying to explore. I been lately learning about how to use codex for ai development. As for core skills, I try to solve python leetcode problem daily and also learning C as a fun side-project hustle.

The best way to learn to code/develop software is to read others code. leet code etc are great, but they often focus on algorithms (and tricks in the questions). Most people never hand-write these algorithms---we use libraries that are optimised.

AI is great, but if the idea is to learn, I'd discuss with it and then write code myself. Otherwise, one doesnt train themselves to do it. It's still being researched, but this just came out in Nature (a well known, respected academic journal), for example:

Is AI ruining our skills? Early results are in — and they’re not good

@willwic wrote in https://forge.fedoraproject.org/join/WelcomeToFedora/issues/182#issuecomment-876952: > Not that advanced, more like a beginner who is trying to explore. I been lately learning about how to use codex for ai development. As for core skills, I try to solve python leetcode problem daily and also learning C as a fun side-project hustle. The best way to learn to code/develop software is to read others code. leet code etc are great, but they often focus on algorithms (and tricks in the questions). Most people never hand-write these algorithms---we use libraries that are optimised. AI is great, but if the idea is to learn, I'd discuss with it and then *write code myself*. Otherwise, one doesnt train themselves to do it. It's still being researched, but this just came out in Nature (a well known, respected academic journal), for example: [Is AI ruining our skills? Early results are in — and they’re not good](https://www.nature.com/articles/d41586-026-01947-1)
niknikovsky commented 2026-07-31 19:56:53 +00:00
Member
Copy link

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!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
C: Introduction requested

   
C: Needs response

   
C: Progress check 1

   
C: Progress check 2

   
C: Progress check 3 - Final

   
C: Temporary membership approved

   
C: Temporary membership needed

   
I: AI ML

   
I: Atomic

   
I: CI-CD
Gitlab CI/CD, Github Actions, jenkins (pipelines)

  
I: Cloud

   
I: CommOps

   
I: Data Science
AI/ML/etc...

  
I: Design

   
I: DevOps
Docker, Kubernetes, Ansible

  
I: Documentation

   
I: EDI

   
I: Fonts

   
I: Games

   
I: Go

   
I: Infrastructure

   
I: IoT

   
I: Marketing

   
I: Mentoring

   
I: Mobility

   
I: Music

   
I: Outreach

   
I: Package maintenance

   
I: Python

   
I: Quality assurance

   
I: Robotics

   
I: Rust

   
I: Science

   
I: Security

   
I: Server

   
I: Software development

   
I: Translation
Internationalization/Localization

  
I: Web development

   
S: Feedback

   
S: Getting to know Fedora

   
S: GSoC

   
S: Hello Fedora World

   
S: I am Fedora

   
S: Introduced myself

   
S: Invalid
Invalid ticket

  
S: Outreachy

   
S: Subscribed

   
S: User closed

   
S: User unresponsive
No labels
C: Introduction requested
C: Needs response
C: Progress check 1
C: Progress check 2
C: Progress check 3 - Final
C: Temporary membership approved
C: Temporary membership needed
I: AI ML
I: Atomic
I: CI-CD
I: Cloud
I: CommOps
I: Data Science
I: Design
I: DevOps
I: Documentation
I: EDI
I: Fonts
I: Games
I: Go
I: Infrastructure
I: IoT
I: Marketing
I: Mentoring
I: Mobility
I: Music
I: Outreach
I: Package maintenance
I: Python
I: Quality assurance
I: Robotics
I: Rust
I: Science
I: Security
I: Server
I: Software development
I: Translation
I: Web development
S: Feedback
S: Getting to know Fedora
S: GSoC
S: Hello Fedora World
S: I am Fedora
S: Introduced myself
S: Invalid
S: Outreachy
S: Subscribed
S: User closed
S: User unresponsive
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Welcome to Fedora ticket board
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
join/WelcomeToFedora#182
No description provided.