Jean Hollis Weber wrote:(1) Do you think we should keep the little illustrations in the "What does OOo include?" section.
I like the illustrations. They are at the beginning of the whole book where we don't want to scare people off with too much text. I think they break things up nicely (Carol made the same comment to me about the earlier draft of the chapter).
The half-size thing is a concern, but I would hope it won't be a problem *because* the illustrations don't convey any information, if you see what I mean.
Thanks for saying what I had been thinking, on both those subjects.
(2) I'm still considering moving the "short history" section and the info on open source to an appendix in the book, instead of keeping them in this chapter. What do you think?
What you've done here is cut down these sections to the bare bones. I think that works well if the sections are included at the end of the chapter. Putting them in an appendix is still an option, but I would think we would want to beef them up (or return to one of Rick's earlier versions) if they were having their own appendix.
Again, I was thinking much the same thing: if I move them from the chapter to an appendix, they should be re-expanded for the new location. I'm still undecided which is the best way to go.
(3) The licensing info could become one of the FAQs, instead of having its own section. What do you think?I would think about what information we trying to convey in the licensing section. Currently it is just a pointer to more information (Rick's FAQ in the doc. already expands well on licensing without explicitely talking about licenses). I think it works fine as it is now. A FAQ might go into more detail and be useful for developers, resellers and corporates, but is the user guide really the place for that sort of detail?
I definitely wasn't thinking of expanding the licensing info if it went into the FAQ section, just a way of concatenating that info with the other FAQ info. Something else for me to think about some more!
Regards, Jean
