How to participate?


I’m relatively new to Linux and completely new to openSUSE. I’m experimenting with openSUSE on an old ASUS Netbook. In reading the openSUSE documentation I see that participation in the community is encouraged so I thought I’d post here. I am interested in learning the more technical aspects of Linux - be it coding, testing or proper documentation (or anything else really). Reading the documentation, it sounds like talking to folks is a good place to start so here I am.

Are there any beginner friendly aspects to the openSUSE project that I may be of use on, and where I could learn a thing or two?

Welcome aboard! I hope you will enjoy openSUSE like we do here and I think this is the right place to start if you want to learn a bit or two.
Start by using openSUSE and experimenting with it; should you need help don’t be afraid to ask here, you will be amazed at how responsive the community is, especially to people willing to learn.
Maybe in a short time you will be able to help others sort out problems you already encountered, but this is not essential.
Then you can help a lot by testing new releases (Leap 15.2 has just been released a few weeks ago…) and reporting bugs to (same username and password as here, but maybe new members have to setup a new account there…).
Again, ask here if you are unsure if something odd is really a bug or just something you don’t understand yet.
You can contribute to the Wiki at with anything interesting, or to the “HowTo” section of the Forums at
Then if support is not enough for you, you may contribute by becoming a maintainer/packager of a package or two in need of help or, if you have coding skills, contribute to the never ending development of Tumbleweed, for instance.
If this is the case a good place to start are the Factory mailing lists, browse and possibly subscribe to a couple of them at
There is also the openSUSE Build System at where you will be able to build your own version of packages (see “home projects”) or even your tailor made distribution.

If you write about your preferences or skills I’m sure that members here will guide you to what you are looking for, as you can see there are lots of opportunities!

Welcome. Just start by reading the forums to pick up an idea of the culture and then join in if you think you have something helpful to add. You can help by reporting bugs in openSUSE or in specific programs. If you find the documentation for something inadequate offer your suggestions. A lot will depend on what you are interested in and what you try out.

I have found people incredibly helpful and respectful over the twenty years I have been contributing in my limited way.

The way to learn is to speak up and ask questions, and we’re pretty relaxed about topics around here…
If your question has to do with something other than fixing a problem, as you’ve already noticed there are Forums for Development and more generally “almost anything” although I suspect that you’ll know people who aren’t into computing won’t likely find your posts in an openSUSE forum.

Just one weird restriction I’m aware of…
There’s a policy about being non-political which I can understand but I very, very strongly disagree with when it has to do with supporting FOSS unflinchingly and rarely with exception.
I cannot believe that a project and company based so much on FOSS should not be willing to defend FOSS without reservation, but that’s the way things are interpreted. Principles like FOSS should be instinctively supported, not questioned.
Don’t ask me for particulars because I have no interest in arguing for a change…
I only mention the policy and will not discuss anything in detail.


I think it is quite clear in the Forum Terms and Conditions re ‘Board Content’ we are focused on Technical Support here, plenty of other area’s in the openSUSE Infrastructure eg Mailing Lists and IRC that can be discussed AFAIK and probably glean a wider audience…

The Terms and Conditions are quite clear.


Thanks for the messages folks! I look forward to diving in and learning more about openSUSE! I’ll post as things come up. Cheers!

Alright, I have a question. I was browsing the system settings and noticed the kernel settings options. Not knowing about this I checked the openSUSE wiki and saw that there wasn’t a page discussing it. I’ve since found my answers on a combination of wikipedia/linux sites/reddit but I thought it might be useful to have an openSUSE wiki page on the subject.

Being a rookie I’m unsure of what is useful - would writing up a short wiki page and providing the references I have found be something useful to the community?

Both are useful. Don’t duplicate content. Be concise. Be precise, especially with the preconditions.

In my early days, it was all about practice, practice, practice.
Having a separate (sandbox) machine is always a good starter
If you mess things up, just start over.
Eventually, you can make Linux your daily driver.
I used to carve up my HD so I could multi-boot different Distros.
Eventually I ended up writing for major Linux magazines. I don’t do that now as normal work dictates.
I have Tumbleweed KDE as my system and recently (after a very long break from windows) I installed windows 10 pro on a nvme drive, just because circumstances required it.
There are a lot of strong opinions and it’s often best just to ignore anything that is aimed at inflating egos or passions in a particular direction. Play it cool and enjoy.

Writing it up is a good practice, so go for it.

If you mean the Kernel Settings in YaST, SysRq, which is disabled by default, would be a good thing to have it documented, its purpose and how to use it after enabling it. The “Global I/O Scheduler” setting I’m unsure how relevant it still is. Maybe you have these references to back it up. OTOH it might be something that should be removed from the GUI, so a bugzilla report is a better way to move forward. You’ll find that reporting bugs is also a good way to contribute.

Also, for each wiki article you write I’ll suggest you put every relevant info about it, so users can, but don’t need to follow the references. Especially if those references aren’t maintained (reddit, forum posts, etc.)

Are you also new to UNIX®?

If you’re into coding and testing then, what are your coding skills?

  • Are you into system programming or more oriented to application programming?

The “proper” Linux documentation, apart from the openSUSE documentation which is also “proper” but more relevant to system administration, is available from the Linux Documentation Project: <>.

My primary source at the moment is a book I found online on kernel development. I’ve used the reddit and forum posts to help find some plain language interpretations of the more technical jargon. I’ve got about a page of notes that I’m going to turn into something presentable.

And yes, I was referring to the Global I/O Scheduler in the Kernel Settings in YaST.

My thinking for the wiki page was to be a 411 as to what the menu items mean (i.e. what is an I/O Scheduler, Deadline, CFQ, and NOOP).

Do you think a bugzilla report would be more useful?

Most definitely new to UNIX

If you’re into coding and testing then, what are your coding skills?

  • Are you into system programming or more oriented to application programming?

The “proper” Linux documentation, apart from the openSUSE documentation which is also “proper” but more relevant to system administration, is available from the Linux Documentation Project: <>.

I’m interesting in learning programming but I’m a complete rookie in that regard. A long time ago I took some java courses but I didn’t go down that route. What is the difference between system programming and application programming? Presumably system programming is something akin to kernel development?

I’d say double check if those options are still valid. There’s the new mq-deadline/kyber/bfq/none options available on kernel v.5x for both TW and Leap. Maybe the sources you checked explain older kernels. Then after confirmation bugzilla would be the best place to go (if there’s no report yet).

“System Programming” is the gentle art of using the Operating System’s API – the system library calls – directly.
“Application Programming” is the gentle art of producing applications for users – mostly with the help of frameworks which avoid the need to have to come to grips with the Operating System’s system library …

And therefore, possibly, also Linux.

  • With respect to your experience to date, which Operating Systems were being targeted for the applications being developed?