Discussed during 24/08/05 KDE Sig meeting:
With the impending change for all updates to require +3 karma before being pushed, there is a focused need to gather karma for updates to push in a timely manner while still maintaining the quality that is expected of Fedora KDE. With this in mind, it was discussed that an internal KDE Sig quality group consisting primarily of end users that would test updates beforehand could be useful.
In order for this recruitment to take place, there would likely need to be Fedora KDE Marketing (cc: @radbirb @kellin ) push to go along with it.
Contributor documentation would also need to be improved so that people could easily onboard. This would be documentation geared at how to test. This also aligns with what is needed for #493 since additional application test cases need to be created anyway
The discussion centered around incentivizing users to be involved.
There's also an opportunity to align hardware testing (e.g. aarch64 hardware) with the Internal QA team so if there is a need for more targeted testing, separate incentives could be devised for that express purpose.
This ticket is meant primarily as a discussion starting point for a future rewards program to get greater involvement in the Fedora KDE project.
There are also other activities that could be incentivized: Bug Reporting Bug Fixing Test Case Writing
Also the incentives would need to strike a balance between valuable enough for people on the fence of contributing to jump onto the other side and not valuable enough to warrant gaming the system.
Very cool! Tshirts or not lol. Anyway Ive been trying to see if I can do more to help with testing providing karma and so on.
Is this a good place to start?
https://fedoraproject.org/wiki/Fedora_Project_Wiki
https://fedoraproject.org/wiki/QA:Updates_Testing#Using_the_updates-testing_repositories
Thanks!
Very cool! Tshirts or not lol. Anyway Ive been trying to see if I can do more to help with testing providing karma and so on. Is this a good place to start? https://fedoraproject.org/wiki/Fedora_Project_Wiki https://fedoraproject.org/wiki/QA:Updates_Testing#Using_the_updates-testing_repositories Thanks!
Any help helps, there are MANY parts of a distro that needs help all the time :)
I would like to assist in this. I'll switch to the testing repository once I come back from an event tomorrow. Just wanted to note that since I'm on Fedora Kinoite, layering packages to be tested is an extra step there and may also result in peculiarities not found in Fedora KDE Spin.
If anyone wants to test, KDE Frameworks update 6.5.0/Plasma 6.1.4 is out and needs karma: https://bodhi.fedoraproject.org/updates/FEDORA-2024-963139591c
Just checked for updates and it's not there yet. I assume it'll be there in= a few hours. Will test tomorrow morning.
Sent with Proton Mail secure email.
On Sunday, August 11th, 2024 at 7:54 PM, Steve Cossette pagure@pagure.io = wrote:
farchord added a new comment to an issue you are following: If anyone wants to test, KDE Frameworks update 6.5.0/Plasma 6.1.4 is out= and needs karma: https://bodhi.fedoraproject.org/updates/FEDORA-2024-96313= 9591c =20 To reply, visit the link below or just reply to this email https://pagure.io/fedora-kde/SIG/issue/551
If anyone wants to test, KDE Frameworks update 6.5.0/Plasma 6.1.4 is out= and needs karma: https://bodhi.fedoraproject.org/updates/FEDORA-2024-96313= 9591c
Just checked for updates and it's not there yet. I assume it'll be there in= a few hours. Will test tomorrow morning. Sent with Proton Mail secure email. On Sunday, August 11th, 2024 at 7:54 PM, Steve Cossette pagure@pagure.io = wrote: farchord added a new comment to an issue you are following: If anyone wants to test, KDE Frameworks update 6.5.0/Plasma 6.1.4 is out= and needs karma: https://bodhi.fedoraproject.org/updates/FEDORA-2024-96313= 9591c =20 To reply, visit the link below or just reply to this email https://pagure.io/fedora-kde/SIG/issue/551
If you want to test now, you can do so by running:
bodhi updates download --updateid FEDORA-2024-963139591c
and then, doing sudo dnf update ./*.rpm
sudo dnf update ./*.rpm
(I do recommend you do that in an empty folder)
Oh you might need to install bodhi-client (Not sure if that's installed by default)
It sounds like we would also need to know which hardware the Internal QA people would be testing on as there appear to be gaps in our architecture coverage
x86_64 is likely to be well covered but aarch64 has some large gaps
I believe QA folks use Raspberry Pi 4 series devices primarily, as they're the main ARM devices people want to use. @kparal has indicated that the Fedora QA team uses Raspberry Pi 400s, so that should be sufficient as a starting point.
Since aarch64 lacks automated testing, we really need people to test and give feedback.
We have both RPi4 and RPi 400. We have other devices as well, but RPis are the most important ones, I believe, yes. @lbrabec and @coremodule can provide more details.
https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org/thread/3WD5J33I7XJ2SERFCDZI3KQQEW2T2SHW/
Heads up that there's a call for support for this if anyone has the bandwidth to help this time around. cc: @derekenz @muelsyse @radbirb
I don't know which of the Sig members actually has viable aarch64 hardware, however. I know @siosm has the apple silicon but that's the only person I can think of. @farchord doesn't have viable aarch64 hardware. @ngompa did you have aarch64 hardware?
I backed the Tachyon 5G but it's not here yet, and may not be here for a few months. I also have an Apple Silicon Mac for Fedora Asahi Remix development. I might be able to resuscitate one of my RPis, but we'll see.
Unfortunately I don't have the hardware yet. Working on getting an M1 Mac system but no guarantees.
On Wed, Sep 18, 2024 at 9:13=E2=80=AFAM Timothy Arnold pagure@pagure.io w= rote:
timaeos added a new comment to an issue you are following: `` https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org= /thread/3WD5J33I7XJ2SERFCDZI3KQQEW2T2SHW/ Heads up that there's a call for support for this if anyone has the bandwidth to help this time around. cc: @derekenz @muelsyse @radbirb I don't know which of the Sig members actually has viable aarch64 hardware, however. I know @siosm has the apple silicon but that's the onl= y person I can think of. @farchord doesn't have viable aarch64 hardware. @ngompa did you have aarch64 hardware? `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-kde/SIG/issue/551
timaeos added a new comment to an issue you are following: ``
https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org= /thread/3WD5J33I7XJ2SERFCDZI3KQQEW2T2SHW/
I don't know which of the Sig members actually has viable aarch64 hardware, however. I know @siosm has the apple silicon but that's the onl= y person I can think of. @farchord doesn't have viable aarch64 hardware. @ngompa did you have aarch64 hardware?
``
To reply, visit the link below or just reply to this email https://pagure.io/fedora-kde/SIG/issue/551
I could go buy the rpi4b, but honestly, I already spent $2k on my new x1e laptop, I'm good XD Prolly gonna be able to help next release, this one might be a bit tight.
Log in to comment on this ticket.