RFC: Wine Documentation

2000-09-15 Thread Jeremy White
As part of the Wine 1.0 effort, we've been working on improving the Wine documentation. We have a proposal for a way to overhaul the documentation system, and we'd like some feedback. We start with the following goals: 1. Documentation should be easy to find 2. Documentation should be

Re: RFC: Wine Documentation

2000-09-15 Thread Alexandre Julliard
Jeremy White [EMAIL PROTECTED] writes: 3. If it's a separate tree, multiple developers be given commit access to the new tree. I think commit access would be basically granted to any developer who requests it, so long as they have some standing in the

Re: RFC: Wine Documentation

2000-09-15 Thread Gerald Pfeifer
On Fri, 15 Sep 2000, Jeremy White wrote: 2. Documentation should be clear (the user should quickly see the thing that he or she wants, and there should be no confusion as to which document is 'right') Sounds good! 4. Switch the FAQ to use a FAQ-O-MATIC, to

Re: RFC: Wine Documentation

2000-09-15 Thread James Juran
Gerald Pfeifer wrote: On Fri, 15 Sep 2000, Jeremy White wrote: 2. Documentation should be clear (the user should quickly see the thing that he or she wants, and there should be no confusion as to which document is 'right') Sounds good! 4. Switch the FAQ

Re: [Re: RFC: Wine Documentation]

2000-09-15 Thread Andreas Mohr
On Fri, Sep 15, 2000 at 08:41:37PM -0400, Douglas J. Hunley wrote: James Juran wrote: But a manually edited FAQ requires rather constant (or at least consistent) attention, which it is not receiving now. Unless someone is willing to be a more regular FAQ editor than the current WineHQ