[Ambassadors] Red Hat's investments (was Re: Going passive)

Michael Schwendt bugs.michael at gmx.net
Thu Nov 11 20:44:53 UTC 2010

On Thu, 11 Nov 2010 01:34:40 +0000, Jóhann wrote:

> create "proven $language coders" groups which maintainers sign up for
> Reverse the roles of testers and maintainers and host a "bug squash day!"
> QA decide which components needs addressing and contacts the relevant 
> "proven $language coders".
> Triagers run through the bugs list on the component the day(s) before 
> and create a tracker bug with all the valid reports
> "proven $language coders" run through tracker bug list

Whether a person is capable of fixing bugs depends mostly on the person's
familiarity with a specific application's source code and the used APIs
than with the used programming language. To become familiar (and to stay
familiar) with an app's code can take a significant amount of time.
A person may know C but not GTK+/GLib, C++ but not Qt or KDE, …

IOW, you would need to replace $language with $framework or $environment.
And once you've done that, you may as well replace it with $package_name. ;-)

More information about the advisory-board mailing list