> Oh, sure, you say that just as soon as I change the last occurrence of > "Apache HTTP Server (httpd)" to "Apache HTTPD". ;-) > > I honestly can't say that I feel strongly about this one way or > another, but I would like to know what the consensus is so that we can > be consistent. It doesn't flow well to call it "Apache HTTP Server" > every time we mention it in the main body of the docs. So we need to > agree on a full name variation, and an abbreviated variation: > > Full: > [ ] - Apache HTTP Server > [ ] - Apache HTTPD > > Abbreviated: > [ ] - httpd > [ ] - HTTPD > [ ] - Apache httpd > > Are there other options here? Is this something that needs to go to > the PMC, or can we arrive at consensus here? > > --Rich
I think you're going to be fighting a similar battle to the "GNU/Linux" vs "Linux" vs "linux" folks. Joe Public says "Apache" when he means "httpd". Similarly, he doesn't say "Apache Tomcat", merely "Tomcat". Granted, the documentation needs to be consistent with whatever is chosen here but I suspect this will pass un-noticed to most of our user-base. Mark. -- Mark Watts BSc RHCE MBCS Senior Systems Engineer, Managed Services Manpower www.QinetiQ.com QinetiQ - Delivering customer-focused solutions GPG Key: http://www.linux-corner.info/mwatts.gpg
signature.asc
Description: This is a digitally signed message part
