User:Leam

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(QE Teams)
Line 31: Line 31:
 
===QE Teams===
 
===QE Teams===
  
[[Bug Zappers]]
+
[[BugZappers]]
  
 
Fedora BugZappers can start with Triage skills and assume greater responsibility as C and Python skills grow. Minimal knowledge of Bugzilla is required for initial work, as well as the ability to communicate via e-mail lists and IRC. This would be a great place to develop your understanding of the Linux kernel and application development.  
 
Fedora BugZappers can start with Triage skills and assume greater responsibility as C and Python skills grow. Minimal knowledge of Bugzilla is required for initial work, as well as the ability to communicate via e-mail lists and IRC. This would be a great place to develop your understanding of the Linux kernel and application development.  

Revision as of 20:15, 2 February 2009

This is a DRAFT, it is only a draft.


How do you see your self?

- Desktop User
- Heterogenous System Administrator
- Operating Systems Student
- Corporation needing low cost server solution
- RHC[T|E|A] Aspirant
- Develop applications on Linux/Unix
- Developer for Fedora
- Quality Engineer
- Project Manager wanting more Linux
- INCOSE Systems Engineer (CSEP) developing real world skills


Quality Engineer

Our Quality Engineering teams let you contribute with your current skills and learn more as you work with us. Take our quick self-assessment (need to write this) and think about what skills you want to develop. That will help you find the right entry point and ensure you're getting the right amount of challenge and development. Once you're comitted to a team one of the members will help guide you through the initial learning curve. They will also seek your feedback on how the team's communications are and what sorts of improvments you might suggest.

When you consider the Quality Engineer path, here are some things to be aware that you're committing to:

- Current languages tools are in Python and C. 
- Fedora/Linux technologies like Kickstart, RPM, Yum, and Git are key.
- 1 Hour IRC meeting Wednesdays at 11:00 EST, useful to attend.
- Documentation and Communications skills are important but can be in your personal learning plan.
- Long term goals may include moving to Kernel hacking, RHC[T|E|A], Quality Software Testing Certification (ISTQB Foundation level), INCOSE CSEP experience, or other industry standard certifications.


QE Teams

BugZappers

Fedora BugZappers can start with Triage skills and assume greater responsibility as C and Python skills grow. Minimal knowledge of Bugzilla is required for initial work, as well as the ability to communicate via e-mail lists and IRC. This would be a great place to develop your understanding of the Linux kernel and application development.


Tool Development

Our tool sets are primarily written in Python 2.5. Besides work on Anaconda, Snake, various Kickstart tests, Cobbler, and whatever else we can think up to make life easier for users, we'll push your Python and Linux automation skills up a notch.


Feature Tester

Care to take on a sub-set of the distrobution and make sure it's component parts work well? Find the right scope for your time and interests and then invest in working with the related teams to make sure things still work after each upgrade.


Rawhide Tester

When the bleeding edge gets a bit staid for you, help the Rawhide spin maintainers check the frequent builds. There is no promise anything will work, but your trouble-shooting and pre-boot environment expertise will be put to the test.


Installation Testing

Once Rawhide has gotten something close to stable it's time to make sure the installation process works on all current architectures. For this you need to have a build box that can be worked on and rebuilt without impacting your business or personal computing needs.


Stream Liasion

Fedora provides for a wide variety of users who have an even wider variety of tool needs. As a Stream Liasion you'll keep yourself aware of what your user community needs and wants while staying abreast of changes in upcoming releases. For example, if the Ham Radio community uses Tools X and Y on Desktop Z 90% of the time you know what needs to be tested first.