I agree most strongly.

I signed up to help long ago, and since then I have found it just too
frustrating and too much overhead learning where everything is and how
it works.

I finally gave up.

When the experts agree this is "all better", please send some sort of

**** OBVIOUS ANNOUNCEMENT ****

inviting all us readers and non-contributors to try it (again).

Thanks to everyone who has contributed to a great product, and the
documentation, and the WWW sites.

Jim

Opinions I express are not necessarily MN DOT's.
James R. Harris, Information Architect, MS 240
MN Dept. of Transportation, Information Technology
395 John Ireland Blvd., St. Paul MN 55155-1899
Phone/Voice-Mail 651.297.3493  651.297.1473 Fax
Mgr.: [EMAIL PROTECTED] 651.297.7335
>>> [EMAIL PROTECTED] 02/20/05 1:19 PM >>>
Reading this long series of threads, I can summarise the main problem
this way.

All this setup hassle is just one more barrier getting in the way of
doing 
what I want to do, which is to help out on the Doc Project. Scott and
Gerry 
have asked for help, and I'd like to do so.

But if I have to spend a lot of time and hassle getting set up to help
out, 
I am very likely to say "it isn't worth the trouble" and go away and do 
something else.

In fact, I am *that close* (holds fingers about 1 mm apart) to chucking
it 
all in and giving up completely on anything to do with the OOo website.
I 
can work with Authors and help out at conferences, and that's more than 
enough to fill up my time.

I'm sure many other potential volunteers feel the same way.

If the system cannot be fixed (and I appreciate that it probably can't
be), 
then the instructions absolutely must be made easy enough for Jonathon's

"great aunt Martha" to understand, and/or tools must be provided to make

setup easy. Otherwise you won't get -- or keep -- the volunteers you
need, 
esp. in a place like Docs where our expertise is more likely to be in 
writing than in software use.

I hope that Scott's solution works out, but I suspect help is also
needed 
on making sure a key is produced and tested to be sure it works, or 
whatever is needed to remove that barrier. If I have to troubleshoot
every 
single step, and not know what factor (or combination of factors) might
be 
the problem, I am very likely to give up.

Regards, Jean 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to