Hi
That is good to hear too.
So for this current version of the handbook Alan can choose between a
short-term patch or refer to a future version of the GS or something. No
choice is likely to be perfect but any choice is likely to be plenty "good
enough". Lets just stand by whichever choice is made.
I find flipping a coin is a good way of making such choices. When the coin
lands you often get a feeling that the coin is wrong, in which case go
against the coin's suggestion. If you know it's right then go with it. If
you are still unsure then either go with it or flip again for "best out of
3", whichever causes less panic. A "best of 3" kinda indicates that the
coin was probably wrong though.
The main thing is avoiding too much work on this 1 issue because it's a
temporary patch to deal with something that has already been fixed for the
next iteration.
Wrt Alan's concerns about;
1. "needs to be edited for consistency of style" = Proof-reading?
and
2. "checked carefully against the app for accuracy" = Reviewing?
So these are normal parts of the established policy. Apparently we don't
always do them, because it's not always necessary, but it's something the
team aims for.
3. screen-shots.
Would i be right in saying that 1 is probably best done by non-experts in
Base and that only 2 needs an expert? A non-expert might help "de-geekify"
so that would give them an advantage? I guess 3 can be done by either but
might be best done by someone who has done screen-shots for other guides or
likes working with images?
Regards from
Tom