From Fedora Project Wiki

(Updated links)
m (Add Beta bug trackers)
Line 39: Line 39:
=== Links ===
=== Links ===
* F15 Alpha tracker bugs
* F15 Alpha tracker bugs
** [ Proposed Blockers]
** Blockers - [ proposed], [ accepted]
** [ Accepted Blockers]
** Nice-to-have - [ proposed], [ accepted]
** [ Proposed NTH]
* F15 Beta tracker bugs
** [ Accepted NTH]
** Blockers - [ proposed], [ accepted]
** Nice-to-have - [ proposed], [ accepted]

Latest revision as of 18:54, 9 March 2011

James Laska
James Laska
Personal Information
Birthday: {{{birthday}}}
Birthplace: {{{birthplace}}}
Fedora Information
FAS name: jlaska
Fedora email:
IRC nick: jlaska
IRC channels: #fedora-qa, #fedora-test-days, #fedora-bugzappers
Fedorapeople page:
Miscellaneous Information
Private email: {{{pmail}}}
GPG key: ADEA5276
Homepage: [{{{homepage}}} {{{homepage}}}]
Jabber: {{{jabber}}}
RHCE Certificate: 805008170534050
RHCT Certificate: {{{rhct-cert}}}
Gtalk: {{{gtalk}}}
Badges ({{ #fedorabadgescount: jlaska }})
{{ #fedorabadges: jlaska }}


I have been involved with release testing Red Hat Enterprise Linux products starting with Red Hat Enterprise Linux 2.1. Currently, I manage a dedicated team of Fedora QA engineers. Among many things, we are responsible for expanding/sustaining/supporting a Fedora QA community, maintaining and providing status on Fedora release criteria, and identifying/building tools or process to streamline our work. I've been called many things, but the funniest is an officer of bureaucracy.

Oh, and how could I forget ... I like chicken!

Activities within Fedora

Quality Assurance