From: Doug Blank <email@example.com>
To: Greg Lamberson <firstname.lastname@example.org>
Sent: Thu, March 24, 2011 5:33:29 AM
Subject: Re: [Gramps-devel] Questions related to working on the 3.3 Manual
On Wed, Mar 23, 2011 at 10:45 PM, Greg Lamberson <email@example.com
> As part of my self-indoctrination process, I'm going through the 3.3 English
> manual carefully to improve its readability, make sure it's reflective of
> what the user actually sees, and to generally make sure I'm thoroughly
> familiar with things.
Excellent way to contribute, and learn! Very useful at this point, too.
> The following questions have come up so far during
> this process:
> 1. Screen Shots: Should I redo all the screenshots to maintain uniformity in
> the manual or continue my practice of merely
replacing the ones which have
> changed? It's starting to look rather inconsistent. Is there a naming
> convention for screenshots? I could not find one and have been making my
Others that contribute to the manual will have to weigh in on this.
The manual has been evolving from a hardcopy version, to what we have
today. So it is probably time for a step in that evolution. What is
your naming scheme?
> 2. Backup, Archive, Export: Was the manual written before "Make Backup" was
> a menu item? This option is not mentioned in the manual (at least in the
> obvious places), and instead the export to xml/pkg option is mentioned as
> the preferred method to secure data before upgrading. If "Make Backup is
> still not the preferred option, it should at least be mentioned. Right now
> the absence of this option within the documentation is confusing, especially
> with the export
and archive methods also being mentioned.
This one I can answer: yes, the Make Backup is new, and should now be
highlighted as the preferred method of backing up. People should also
test this functionality as well. (I noticed that it didn't seem to
give feedback on status, and didn't warn on overwrite... just reported
That is another function one could perform: make sure things work, and
feel free to suggest refinements on new (and old) features.
> 3. Name Editor: I did my best regarding the changes in the Name Editor, but
> this section needs to be looked at by someone with more familiarity with
> these options just to make sure it's correct and complete.
> If I'm jumping the gun here on someone, I apologize. I'm just trying to jump
> in here and learn and get up to speed the best I can.
Yes, needs to be looked at from the technology viewpoint, and also the
> Greg Lamberson
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> Gramps-devel mailing list