Thank you for your patient answers, André.
I would like to help out in this regard. But I must say that in
spite of the wealth of text on the "How Can I Help?" type of pages
on the OOo site, it is not very easy to figure out where someone
like me - who is NOT a programmer (but I am long-time veteran
software tester) - fits into this testing process.
*sigh* we know, that our web pages are not perfect. But at least you
did the right thing, ask at the list ;-)
That's OK! It is obvious to the non-progammer that the entire OOo
site has been geared towards participating programmers for years. You
don't need an extra Project: "revise site to be intelligible to, and
navigable by, end-users". At the same time, because (I hope and
believe) more and more end-users will start visiting OO.org looking
for ways to join this exciting OS project, it is important to
leverage any and all help coming in.
So I'll do an "even more right thing" and make the time to write up
some specific suggestions for a revised page at
http://qa.openoffice.org/helping.html. I'll send them directly to you
unless anyone else here voices a wish to have a look and contribute
ideas for making that page as user-friendly as possible.
1. What skill level of "testers" is being sought?
<snip>
"end users who know ..." is the level to start with doing QA. I
think most of us belong to this category.
great, I'll try to recruit a few more for OS X specifically, or for
any platform. My colleagues are skilled pros in 4GL db development,
not C programmers, but any of them who have the time and inclination
would make great testers. (They are also located in many countries,
so could help test localized versions.)
In general, "latest builds for testing" are the developer snapshots:
http://download.openoffice.org/680/index.html
thank you. Has been duly bookmarked, and I signed up for every QA
list & will start Observing qa for announcements.
You are at the right list, when speaking about QA web pages. One of
the problem is, that long term members often don't see the need for
more easy information and rather focus on doing the "real job".
I understand completely. Like I said, I'm a veteran software tester.
When good testers start sending back really good bug reports that
save hours of time and result in a much better-quality end result,
that tends to change :-) and the wisdom of making it easier for
testers to feel welcome and to participate becomes very apparent.
But you are welocme to send your suggestions.
I will!
kazar
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
