My WineHQ menu structure proposal
andi at rhlx01.fht-esslingen.de
Sun Nov 3 11:51:08 CST 2002
On Sun, Nov 03, 2002 at 12:41:29PM -0500, Dimitrie O. Paun wrote:
> On November 3, 2002 12:26 pm, Andreas Mohr wrote:
> > IMHO the CVS stuff should *only* be mentioned in the Wine User Guide (and
> > the Developers Guide would explain the more advanced usage patterns).
> > Then it'd be pretty easy to simply add a small "For CVS download of Wine
> > source, see <Wine Users Guide link>".
> Why in Wine User Guide? Ideally, users should not have to deal with CVS
> at all. The *only* reason this is so it's that Wine is very immature,
> and changes quickly. But once we reach a stable release, this should
> hopefully change a little. When I open the user guide, I want it to small,
> and to the point -- it has to tell me the absolute minimum that I need to
> know to run the thing. Note: ideally, it should be so easy, and intuitive
> to run Wine, that we should not need a Wine User Guide!
Hmm, I guess you're right.
How about we throw away CVS in User Guide and document *all* CVS management
issues in the Devel Guide and simply have a reference to the Devel Guide
in the Users Guide when it comes to CVS ?
WineHQ would then use a link to the Devel Guide only, of course.
I think that makes quite some sense.
More information about the wine-devel