Re: [Audacity-manual] Tracking changes across pages

[Ed M. <edg...@wa...>]

> -----Original Message-----
> From: James Crook 
> 
> I think near to release,  a developer should review all of those commit
messages since
> last release, as part of getting a feel for what might be problem areas
[   --Ed   ] 
not just a "developer" a team programmer*



> Obviously developers shouldn't say which pages
> are affected, as it is the manual writers role to know where different
features are
> documented.
> 
[   --Ed   ] 
+1


> I would also like to put on the table automating the process of obtaining
updated
> screenshots.  I would like manual team to 'own' the process of updating
screenshots,
> and once it is automatic that could even trigger awareness that some pages
text where
> the images are used needs to change.
> 
[   --Ed   ] 
Automating seems a big job. There are a lot of screenshots; many have been
edited--cropped, annotated etc.. There [are | may be] places where multiple
OS versions exist (where there is an OS difference like the Mac menu
structure??). For the last few years I have been the go-to guy for
pictures**; having one person doing images seems to work well, that would
mean that that person would coordinate with that *programmer.

**Since the manual expects Windows 7 Basic themed images and I was the only
editor on Win7 I took on the job. Gale is now on Win7 too and can do the
job.


--Ed