User:Leam

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Initial thoughts on using Fedora to meet personal goals)
 
Line 8: Line 8:
 
  - Corporation needing low cost server solution
 
  - Corporation needing low cost server solution
 
  - RHC[T|E|A] Aspirant
 
  - RHC[T|E|A] Aspirant
  - Developer on Linux/Unix
+
  - Develop applications on Linux/Unix
 
  - Developer for Fedora
 
  - Developer for Fedora
 
  - Quality Engineer
 
  - Quality Engineer
Line 15: Line 15:
  
  
The en/join-fedora page is great but seems disjointed from the wiki/Main_Page. Some folks coming in will want to join Fedora and thus the Join Fedora link could be melded so that a bit more info was on en/join-fedoa and then linked to greater detail on wiki/Main_Page.
+
== Quality Engineer ==
  
Part of this is a desire to resonate with people's dreams of themselves. Not "what skills do you have?" but "how do you see your self, your future self?". Once we open their self-awareness we can tap into internal motivations to meet exteral goals. For example, is it better to tell someone they can be a QA person with no weekly time commitments or give them a list of things to consider like:
 
  
 +
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.
 
  - 1 Hour IRC meeting Wednesdays at 11:00 EST, useful to attend.
- Able to build linux box multiple times a week without interrupting personal or business computing needs.
 
- Some familiarity with RPM, Python, Kickstart useful. You can learn on the job and the more you know the wider your options.
 
 
  - Documentation and Communications skills are important but can be in your personal learning plan.
 
  - Documentation and Communications skills are important but can be in your personal learning plan.
- A mentor will facilitate your self-evaluation, provide feedback, and help find contributions within your time and skill constraints.
 
- Mentors also help structure your personal learning plan so that contributing to Fedora stays in line with your personal goals.
 
 
  - 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.
 
  - 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===
 +
 +
Bug-zapper
 +
 +
Bug-Triage
 +
 +
Tool Development
 +
 +
Feature Tester
 +
 +
Rawhide Tester
 +
 +
Installation Testing
 +
 +
Stream Liason (?)

Revision as of 15:31, 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

Bug-zapper

Bug-Triage

Tool Development

Feature Tester

Rawhide Tester

Installation Testing

Stream Liason (?)