Daniel Carrera wrote:
Peter Kupfer OOo wrote:
If anyone learns about the other feature on their own, and wants to
use it, that's cool. The writer will notice whe they are on the
"accept and reject changes" window.
I don't agree. Mostly just on the principle that I don't think we
should be keeping secrets and hiding features from people. I don't
think this is what you mean necessarily.
We have to find a balance. Each feature that we require/expect our
volunteers to use makes the project a little more daunting. We need to
decide whether the benefit from the feature is worth the higher barrier
for newcommers. In the case of using notes, I think it's definitely
worth doing. In the case of the notes vs comments distinction, I don't
think it's worth it.
I think we both agree, this is not a concept we want to push on
newcomers. My thinking, as you will see below, is that as a reviewer
becomes more advanced and shows signs of sticking with the project, we
start introducing them to new review techniques. Kind of a teaching process.
I wish there was a way to gradually warm users to new features. So, when
someone joins the only hear about Insert > Notes, but when they are very
confortable with the project we start talking about Edit > Changes >
Comments.
I thought about this some in the last 12 hours and I think that you
don't really appreciate the difference until you are an
author/maintainer and have to actually go through someone else's changes.
So, maybe the at the point where someone moves from being a reviewer to
a writer would be the first time we would suggest they try to do it the
other way. If we do implement some kind of mentoring thing, this would
be fairly simple. The persons mentor would just mention this to them
when they write their first chapter.
If we don't have a formalized mentoring process, then maybe we could
have a document somewhere for the "advanced members". I don't know what
the best way to do it, but as time goes on newbies, who are engrossed in
the project, will be able to handle more complex tasks and things, and I
think it is obligation (maybe that is strong, but I feel obliged) to
teach them better reviewing techniques. It benefits them and the project.
--
Peter Kupfer -- Using OOo since 'OO4 -- [EMAIL PROTECTED]
Want to help? http://www.oooauthors.org
For OOo tips: http://openoffice.peschtra.com/ooo_tips_tricks.html
To order OOo: http://openoffice.peschtra.com/distro/ooo_distro.html
