Hey Folks!
I am proposing a QA classroom to cover the following topics:
Introduction to Fedora QA: This section could provide an overview of what Fedora QA is, what it does, and why it's important to the Fedora community.
Fedora QA Team Structure: This section could introduce the different roles within the Fedora QA team and explain how they work together to ensure the quality of Fedora releases.
Getting Started with Fedora QA: This section could provide practical information on how to get started with Fedora QA, including how to join the team, where to find relevant documentation and resources, and how to get in touch with other team members.
Fedora Release Process: This section could explain the Fedora release process, including the different stages of development, testing, and release, and how Fedora QA fits into this process.
Testing Tools and Techniques: This section could introduce the testing tools and techniques used by Fedora QA, including automation tools, manual testing procedures, and other testing methodologies.
Reporting Bugs and Issues: This section could explain how to report bugs and issues found during testing, including how to use Bugzilla, how to write good bug reports, and how to communicate effectively with developers and other team members.
Working with the Fedora Community: This section could provide guidance on how to work effectively with other Fedora community members, including developers, packagers, and other QA team members.
Conclusion and Next Steps: This section could summarize the key takeaways from the onboarding call and provide information on what to do next, including how to get involved in specific testing projects and how to continue learning and growing within the Fedora QA community.
I wanted to ask what will be a good time and date?
Hi Sumantro, Thanks for proposing this. I was looking for onboarding call. I have been here from 2020 but didn't get a chance to contribute. I am looking forward to this call to start my contribution. My vote will be for coming weekend i.e. 22 & 23 April.
Regards, Ravindra
On Tue, Apr 18, 2023, 9:48 AM Sumantro Mukherjee sumukher@redhat.com wrote:
Hey Folks!
I am proposing a QA classroom to cover the following topics:
Introduction to Fedora QA: This section could provide an overview of what Fedora QA is, what it does, and why it's important to the Fedora community.
Fedora QA Team Structure: This section could introduce the different roles within the Fedora QA team and explain how they work together to ensure the quality of Fedora releases.
Getting Started with Fedora QA: This section could provide practical information on how to get started with Fedora QA, including how to join the team, where to find relevant documentation and resources, and how to get in touch with other team members.
Fedora Release Process: This section could explain the Fedora release process, including the different stages of development, testing, and release, and how Fedora QA fits into this process.
Testing Tools and Techniques: This section could introduce the testing tools and techniques used by Fedora QA, including automation tools, manual testing procedures, and other testing methodologies.
Reporting Bugs and Issues: This section could explain how to report bugs and issues found during testing, including how to use Bugzilla, how to write good bug reports, and how to communicate effectively with developers and other team members.
Working with the Fedora Community: This section could provide guidance on how to work effectively with other Fedora community members, including developers, packagers, and other QA team members.
Conclusion and Next Steps: This section could summarize the key takeaways from the onboarding call and provide information on what to do next, including how to get involved in specific testing projects and how to continue learning and growing within the Fedora QA community.
I wanted to ask what will be a good time and date?
-- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Hi Sumatro, I haven't contributed in a while so hopefully a classroom call refresher would definitely help me get back on track. The coming weekend should be good.
Warm Regards, Ashish Kumar LinkedIn https://www.linkedin.com/in/ashishkumar99/
On Tue, Apr 18, 2023 at 9:48 AM Sumantro Mukherjee sumukher@redhat.com wrote:
Hey Folks!
I am proposing a QA classroom to cover the following topics:
Introduction to Fedora QA: This section could provide an overview of what Fedora QA is, what it does, and why it's important to the Fedora community.
Fedora QA Team Structure: This section could introduce the different roles within the Fedora QA team and explain how they work together to ensure the quality of Fedora releases.
Getting Started with Fedora QA: This section could provide practical information on how to get started with Fedora QA, including how to join the team, where to find relevant documentation and resources, and how to get in touch with other team members.
Fedora Release Process: This section could explain the Fedora release process, including the different stages of development, testing, and release, and how Fedora QA fits into this process.
Testing Tools and Techniques: This section could introduce the testing tools and techniques used by Fedora QA, including automation tools, manual testing procedures, and other testing methodologies.
Reporting Bugs and Issues: This section could explain how to report bugs and issues found during testing, including how to use Bugzilla, how to write good bug reports, and how to communicate effectively with developers and other team members.
Working with the Fedora Community: This section could provide guidance on how to work effectively with other Fedora community members, including developers, packagers, and other QA team members.
Conclusion and Next Steps: This section could summarize the key takeaways from the onboarding call and provide information on what to do next, including how to get involved in specific testing projects and how to continue learning and growing within the Fedora QA community.
I wanted to ask what will be a good time and date?
-- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
+1 for the proposal. Thank you for proposing, this looks like a wonderful idea .
On Tue, 18 Apr 2023 at 9:48 AM, Sumantro Mukherjee sumukher@redhat.com wrote:
Hey Folks!
I am proposing a QA classroom to cover the following topics:
Introduction to Fedora QA: This section could provide an overview of what Fedora QA is, what it does, and why it's important to the Fedora community.
Fedora QA Team Structure: This section could introduce the different roles within the Fedora QA team and explain how they work together to ensure the quality of Fedora releases.
Getting Started with Fedora QA: This section could provide practical information on how to get started with Fedora QA, including how to join the team, where to find relevant documentation and resources, and how to get in touch with other team members.
Fedora Release Process: This section could explain the Fedora release process, including the different stages of development, testing, and release, and how Fedora QA fits into this process.
Testing Tools and Techniques: This section could introduce the testing tools and techniques used by Fedora QA, including automation tools, manual testing procedures, and other testing methodologies.
Reporting Bugs and Issues: This section could explain how to report bugs and issues found during testing, including how to use Bugzilla, how to write good bug reports, and how to communicate effectively with developers and other team members.
Working with the Fedora Community: This section could provide guidance on how to work effectively with other Fedora community members, including developers, packagers, and other QA team members.
Conclusion and Next Steps: This section could summarize the key takeaways from the onboarding call and provide information on what to do next, including how to get involved in specific testing projects and how to continue learning and growing within the Fedora QA community.
I wanted to ask what will be a good time and date?
-- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Hi Sumatro,
Thanks for proposing. Brand new to Fedora QA, and ready to jump in and test away. The class would be extremely beneficial for me getting familiar with Fedora QA team. Looking forward to it!
On Mon, Apr 17, 2023, 23:18 Sumantro Mukherjee sumukher@redhat.com wrote:
Hey Folks!
I am proposing a QA classroom to cover the following topics:
Introduction to Fedora QA: This section could provide an overview of what Fedora QA is, what it does, and why it's important to the Fedora community.
Fedora QA Team Structure: This section could introduce the different roles within the Fedora QA team and explain how they work together to ensure the quality of Fedora releases.
Getting Started with Fedora QA: This section could provide practical information on how to get started with Fedora QA, including how to join the team, where to find relevant documentation and resources, and how to get in touch with other team members.
Fedora Release Process: This section could explain the Fedora release process, including the different stages of development, testing, and release, and how Fedora QA fits into this process.
Testing Tools and Techniques: This section could introduce the testing tools and techniques used by Fedora QA, including automation tools, manual testing procedures, and other testing methodologies.
Reporting Bugs and Issues: This section could explain how to report bugs and issues found during testing, including how to use Bugzilla, how to write good bug reports, and how to communicate effectively with developers and other team members.
Working with the Fedora Community: This section could provide guidance on how to work effectively with other Fedora community members, including developers, packagers, and other QA team members.
Conclusion and Next Steps: This section could summarize the key takeaways from the onboarding call and provide information on what to do next, including how to get involved in specific testing projects and how to continue learning and growing within the Fedora QA community.
I wanted to ask what will be a good time and date?
-- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Although I’ve been using Fedora for about 30 years, I’m a user, not a systems programmer, so, even though I often try out early releases on an old machine, I’ve never found the information I’d need to be comfortable with testing on my up-to-date machine.
So, yes, a class would be helpful.
Thanks! Fred
On Tue, Apr 18, 2023 at 12:18 AM Sumantro Mukherjee sumukher@redhat.com wrote:
Hey Folks!
I am proposing a QA classroom to cover the following topics:
Introduction to Fedora QA: This section could provide an overview of what Fedora QA is, what it does, and why it's important to the Fedora community.
Fedora QA Team Structure: This section could introduce the different roles within the Fedora QA team and explain how they work together to ensure the quality of Fedora releases.
Getting Started with Fedora QA: This section could provide practical information on how to get started with Fedora QA, including how to join the team, where to find relevant documentation and resources, and how to get in touch with other team members.
Fedora Release Process: This section could explain the Fedora release process, including the different stages of development, testing, and release, and how Fedora QA fits into this process.
Testing Tools and Techniques: This section could introduce the testing tools and techniques used by Fedora QA, including automation tools, manual testing procedures, and other testing methodologies.
Reporting Bugs and Issues: This section could explain how to report bugs and issues found during testing, including how to use Bugzilla, how to write good bug reports, and how to communicate effectively with developers and other team members.
Working with the Fedora Community: This section could provide guidance on how to work effectively with other Fedora community members, including developers, packagers, and other QA team members.
Conclusion and Next Steps: This section could summarize the key takeaways from the onboarding call and provide information on what to do next, including how to get involved in specific testing projects and how to continue learning and growing within the Fedora QA community.
I wanted to ask what will be a good time and date?
-- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-
Ashish Kumar -
Frederick Bartlett -
John P -
Ravindra Lakal -
Rohit vyas -
Sumantro Mukherjee