So to have some starting point and in order to organize ourselves, those who are willing to make part of the testers group please drop a comment here.
Probably useful also to share your knowledge level.
Don’t be shy, there is no wrong level.
We need both advanced users, and common users provided they are good willing to learn and have some kind of initiative instinct 
Thanks to anyone who will step up.
Looking forward to read you.
@WilsonPhillips steps forward.
I have never had the need to build packages, but I am learning now. I am way more of an expert on Windows Server and Active Directory, but I know my way around Linux pretty well. I am a team player. This is my new home and I am ready to do my part, however small that might be.
I raise my hand.
I can’t say how much time I’ll have in the near future as I am just changing jobs, but I will try and see what’s possible.
I am mid-level. New to OM and kinda new to linux, although I have played around with docker containers and some distributions for some time, but never had linux on my main machine for long periods.
I would love to help out with testing. I have moved both of my installs over to the cooker repos. I have been on linux for about three years, not much beyond gaming, web browsing, video editing, simple networking for my samba and jellyfin. I have tried learning how to build packages and made no headway so far, still reading and learning.
While my prefence is writing code and packaging, I’m more than willing to do some testing too.
I’ve used Linux on and off since the last century startign with Slackware, then RedHad, and … Up until my switch to OpenMandriva I was mainly an Arch user, but I’m really enjoying OpenMandriva.
I’ve been programming since I was 12 or 13 starting with GW Basic, then Pascal, C, C++, various assembly languages, and so on. Professionally I’m an electrical engineer and the programming I do is mainly embedded control systems which are microcontroller or FPGA based.
The PC in the kitchen is just there to play political YouTube videos while I am cooking. It is not easy enough to reach to do any serious testing. That leaves this one, my main machine.
Do I change my Update Channel to Cooker or do I just tick the box to Enable Testing Repos? How risky is this?
I do have my first backup of my ~/home folder, so I can reinstall if needed and only be down for a day or so in an emergency, and I do have Timeshift up and running. I would just have to remember to get a snapshot before upgrading any packages.
@WilsonPhillips and @all
It’s up to you.
For ROME (rolling branch) we’ll mainly need test the major upgrades, and the existing packages;
Yes you can enable the /testing repo on ROME.
It’s as risky as if you run cooker. Testing repo packages are backports from cooker so by design ‘untested yet’ in ROME system
The workflow is: the new builds go first in /testing and after a while we publish them in main repo. Often we move the deemed safe packages in main straight away.
Cooker is way more exciting because of new builds every day. That probably requires an advanced user who can sort the issues if any and/or can recognize and avoid them and promptly report, better if in the cooker channel.
I will throw my hat in. I can test and help try to find bugs.
I have assigned you all to the @Testers group 
This post of @ben79 even if originally not stricly addressed to the @Testers group, may provide some food for thoughts.
Regardless if you run ROME or Cooker, as om-welcome is one of our jewels ( 
) you may want to test it and check all the modules of all the pages/tabs.
They should properly install the relevant application or open the relevant systemsetting or web page.
I should have mentioned earlier, but I do right now, that you can test the system/s also in virtual machines.
Unless the purpose will be to test hardware and hardware related stuff, of course.
They have some sort of limitation, however virtual machines are good to install packages that you normally would not use in your daily driver box.
Since we are testing om-welcome, should we start a new thread for that, or is there something else we are supposed to do? I did look at the old one and it was locked. I have not been through orientation yet. 
@WilsonPhillips feel free to start a new thread if you find something wrong.
Please add if in ROME or Cooker and the usual info you believe are useful.
I’m up for helping out with testing. I’m a fairly advanced user who can do a moderate level of stack tracing and some debugging. Most of my experience is in malware analysis and figuring out what something is actually doing but it does transfer to figuring out where something is breaking and potential fixes.
I just turned on the QA packages as well. I’m having some trouble with certain testing mirrors, though.
@Sniper061 Cool!
I add you to @Testers team
@P_J I’m publishing a package in rolling /extra and /restricted. Let’s see if it will help to refresh the repository metadata.
Please clean the dnf cache before try again
sudo dnf clean all;dnf clean all;dnf repolist
Good! 
Haha, nice. I went ahead and migrated both OMLx systems to QA packages. 
