Henri Yandell <[EMAIL PROTECTED]> wrote on 31/01/2003 02:28:59 PM: [snip] > However, a consistent skin might actually be the best way to get a > consistently labelled and functional site together. > > Now I get to disagree with Dion :) His list of important things, the ones > Maven produce, are by and large not important. The important things are > the ones the user cares about: They're important to me as a developer. As a user, yeah it's a different list.
How about we give these items some names: > 1) Where do I download? Downloads > 2) Has their been a release? Release Notes > 3) Where are the tutorials/documentation? Documentation > 4) How do I complain about a bug? Bugs > 5) Where do I ask a question? Mailing Lists > and then more minor questions like: > > 6) So who is behind Project X? Team Members > 7) What Apache community does Project X belong to? What's an Apache community? Do you mean 'top-level project'? [snippage] > Those who can't do, complain. But I'm happy to be a member of both sets. I > believe the first step is to actually try to cross-manage the site. Tbh, I What's cross-management? > Once a site-wide contract for labelling and minimum functionality is > ironed out, each particular look and feel, project and generational tool > are free to enhance it as much as they want, as long as they: > > eg) Provide a link called 'Download nightly build' or whatever. Cool. Let's take a stab at it then. -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
