My WineHQ menu structure proposal
igor at mlug.missouri.edu
Sun Nov 3 12:03:19 CST 2002
On Sunday 03 November 2002 11:41 am, 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!
A stable release is years in the future. When it happens, many people will
offer to redesign the website. Until them, let's focus on what Wine is now
and not what it will become in 5 years.
> > Hmm, could someone yell "me!" when it comes to finding someone to
> > mail a "this is it so far" status report to wine-devel ?
> > I think it'd be good to have a mail describing the current agreement.
> It will get done, give people a day, or two to comment on it. I'll
> do it if need be, don't worry. But the point is well taken: summarizing
> the results of such threads is very imporantant, as otherwise we loose
> a lot of the good stuff hidden in the middle of long emails. This is
> the very reason I sent in my proposal for the menu, as it was a kind
> of summarization of the discussions we had around here.
Ummm... the whole patch idea seems pretty stupid. Let's agree on a plan and
let one person do everything. Website development by committee is not going
to work well, especially since we are in need of a new design (and not simply
I wouldn't mind working on a redesigned version, as long as I don't have to do
it in small incremental patches that get endlessly discussed on wine-devel.
Does anyone really know how the website is structured currently? Does it run
out of a database? If not, what does it use PHP for? Can we make it
mostly-static or is it some weird system that requires tons of scripting? I
know php, but it should be easy to maintain for someone who doesn't.
More information about the wine-devel