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. ;-) _______________________________________________ advisory-board mailing list advisory-board@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/advisory-board
