Hey All,
It's been some time, the QA team met for a workweek and we want to request to sit down for a week after Flock at Brno office where we would like to work on :
QA manager had a word with internal management and has been granted $2000 and the approximate delta is about $3000. This is important for the QA team 1. To decide goals and keeping aligned with the objectives 2. Understanding and knowledge sharing and exploring how to get aligned with the upcoming core OS testing process 3. Collaborate on completing the next generation QA onboarding dashboard which is currently in prod https://taskotron.fedoraproject.org/landing_page/. We are planning to add more onboarding resources like videos and pre-recorded classroom sessions
Mostly all the QA folks will be at Flock and it will be a great time to utilize the opportunity.
Metadata Update from @sumantrom: - Issue private status set to: False (was: True)
How much of this is funding the ability for community QA contributors to attend versus covering Red Hat employees?
The meeting is specifically targetted towards Fedora QA team which are RHT employees. Much of the work is something we need to get done and has been pending for some time now. This hackfest will mostly be Fedora QA team hashing out stuffs which are on priority and some of the backlogs.
We can't keep solving "Red Hat's QA team for Fedora is underfunded" with money meant for community. Of course a lot of the stuff that team is doing is for community, but it also naturally represents Red Hat priorities. We've got to figure out a better way, here.
I really thing we can't in good conscience spend Fedora community money on an entirely Red Hat-internal meeting. I support all of the goals of this meeting and think Red Hat should fund it, but I don't think the Fedora community budget is the right way for RH to do that.
If it can be re-drawn to include a Fedora QA community angle and to include some non-RH members, then we can revisit.
Thanks @mattdm @bcotton for valuable feedback. Sudhir is parallelly looking into funding options. I think this ticket has served its purpose.
Metadata Update from @sumantrom: - Issue close_status updated to: no action needed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.