I can provide a basic description of how things work, but I would
appreciate it if someone could clean it up and make it more
intelligible. I'm not a very good writer.
On Fri, 2002-06-14 at 10:22, dpeterso@... wrote:
> On Fri, 14 Jun 2002, James A. Treacy had this to say:
> >On Fri, Jun 14, 2002 at 06:52:57AM -0600, Don Allingham wrote:
> >> Well, not necessarily contemplating a change. I've had a few comments
> >> that the current model is too confusing. This leads to one of two
> >> problems:
> >> 1) The model is not correct or difficult to use.
> >> 2) The interface is confusing.
> >My opinion is that there is simply insufficient documentation. It took
> >a while before it dawned on me that a base + specific reference model
> This happened to me as well. I think it would definitely be good to add
> more information about sourcing to the documentation.
> >In fact, insufficient documentation is probably the biggest problem in
> This, IMHO, is the biggest problem with open source projects in general.
> Nobody likes to write documentation...it's thankless, unglorious work.
> Having said that, though, I must say that I am generally pleased
> with the completeness of Gramps' documentation. Does it need more depth?
> yes. Could it be more thorough? yes. Feel free to help us out! :-)
> >general. Sure, it's not that difficult to figure out how to get going
> >in gramps, but a tutorial showing how to implement good genealogical
> >practices in gramps would be very welcome.
> Are you speaking about *teaching* good genealogical practices, or how to
> use them in Gramps? I think these could be two separate pieces of work...
> >Specific areas that newbies would really find useful:
> [list snipped]
> These are really good ideas. If I may follow this notion with another
> question to the developers at-large: Should this be a separate tutorial
> document, or should the present documentation be expanded? I would lean a
> little on the side of simply enhancing the present documentation by adding
> examples or "deeper" explanations of how and why things are done the way
> the are.
> >Why don't I start such a beast? Frankly, because I am a lone
> >genealogist (no connection to any local genealogy groups I could ask
> >for suggestions) who is just getting started and don't know enough
> >yet. If someone starts a tutorial, I would definitely help.
> Well, some of your ideas regarding data-entry were certainly within your
> grasp. I would suggest reading the current documentation, and seeing
> where it falls short in your opinion, and add in things that you have
> discovered beneficial through personal experience. The gramps-manual.sgml
> file is what you want to edit; sgml is a simple markup language, that can
> essentially be treated as plain text.
> Let me know if you need further guidance,
> Donald A. Peterson | dpeterso@...
> Ph.D. Research Associate |
> Dept. of Chemistry | PH: (541) 737-7079
> Oregon St. University | FAX: (541) 737-0480
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
> Gramps-devel mailing list