# how can MySQL involve the users in earlier bug finding?
Release Alpha/Nightly Builds for users interested in the bug finding.
# how can MySQL involve the users in its testing process?
Setup a page similar to sourceforge's project bug page. Where bugs can
be submitted, reviewed, etc. Once a bug is detected and fixed, it goes
into the new Nightly Build.
# what else can community members do for QA? (hints: bugs verification,
performance testing, standard compliance testing)
Have different levels of QA for the public, where one group verifies
bugs, another group looks for workarounds, another group tries to
further identify the problem, etc. Performance testing is good to,
especially in different environments, under specific conditions.
# What kind of incentive would make you (more) willing to cooperate?
(hints: public recognition, free services, discount on services,
contests with prizes)
Access to special builds, with "beta" features that are not available
to the public. When the public release comes out, in the credits there
is a Public QA section, and put the person's name in there. Discounts
on services for higher level public QA (see above).
Giuseppe Maxia wrote: