Martin Hollmichel wrote:
Hi,
last year we initiated the bug bounty program ...
Are there any other ideas to make the Program more attractive ?
or should we stop this effort because it's hopeless ?
May I suggest that some of the bounty money, and/or equivalent time and
effort, might be better spent on lowering the entry barriers for newcomers?
Consider our target audience, those we're trying to attract. Are we
limiting our search to the pool of the Linux/SVN-capable? Or, do we want
to fish in the (much larger!) sea of Windows developers? The logic here
is, why are they developing under Windows? If we're offering money, we
should offer it to the money-hungry.
Windows developers would be expectably running Ms's latest-and-greatest,
Windows Vista (or W7 pre-releases). If they decide to take a look at
the code ("Do I want to get involved with this?"), they hit an immediate
barrier: the SVN folks only boast a client for WXP. A little of our
money here, or just a few friendly words, might help. (The developer
reaction we want to avoid is, "Oh, these kids are locked in their Linux
playpen. Forget it!")
Removing the next barrier -- allowing (and documenting!) OO.o
development under Windows -- involves significant (but not massive)
effort on our part. It should be readily doable (assuming a solution for
the SVN problem), since both the compilers and the product run under WV.
Resources expended on fixing particular bugs will fix those bugs, once.
Investing in process improvement should help us forever.
--
T. J. Frazier
Melbourne, FL
(TJFrazier on OO.o)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
