From owner-freebsd-advocacy@FreeBSD.ORG Wed Dec 29 19:17:51 2004 Return-Path: Delivered-To: freebsd-advocacy@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77CDA16A4CE; Wed, 29 Dec 2004 19:17:51 +0000 (GMT) Received: from sccimhc91.asp.att.net (sccimhc91.asp.att.net [63.240.76.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C53B43D60; Wed, 29 Dec 2004 19:17:50 +0000 (GMT) (envelope-from freebsd@nbritton.org) Received: from [192.168.1.10] (12-223-129-46.client.insightbb.com[12.223.129.46]) by sccimhc91.asp.att.net (sccimhc91) with ESMTP id <20041229191744i9100rftlee>; Wed, 29 Dec 2004 19:17:49 +0000 Message-ID: <41D302D3.1090600@nbritton.org> Date: Wed, 29 Dec 2004 13:17:39 -0600 From: Nikolas Britton User-Agent: Mozilla Thunderbird 1.0 (X11/20041219) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Simon L. Nielsen" References: <20041224000041.GD22614@eddie.nitro.dk> <7B69B4ED-5842-11D9-BA41-000A95C969C6@zumbrunn.com> <20041229182306.GD69078@eddie.nitro.dk> In-Reply-To: <20041229182306.GD69078@eddie.nitro.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-www@freebsd.org cc: freebsd-advocacy@freebsd.org Subject: Re: Rework of the FreeBSD website [was: FreeBSD's Visual Identity:Outdated?] X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 19:17:51 -0000 Simon L. Nielsen wrote: >On 2004.12.27 21:04:14 +0100, Chris Zumbrunn wrote: > > >>In the spirit of... >> >>On Dec 24, 2004, at 1:00 AM, Simon L. Nielsen wrote: >> >> >> >>>If somebody seriously want to do something for an improved website, I >>>think people should come up with a mockup of what they think a better >>>website would look like and post it to the www@ (and perhaps the >>>advocacy@) list. Just talking about it won't change anything (as the >>>mail archives shows plenty of examples of)... >>> >>> >>First Page: >>http://top.ch/sitedata/freebsd/freebsdweb1.gif >> >>On other pages, where appropriate: >>http://top.ch/sitedata/freebsd/freebsdweb2.gif >> >>An even more minimalist approach could be taken by just changing two >>existing images and adding two lines to the current CSS styles, >>yielding 95% of what the above screenshots show. >> >> > > > Excellent!, This is a step in the right direction. >First, I think it's great you actually did some work on this. I >actually hadn't expected anything to come out of this thread :-). > >I think the "More Power To Serve" text should just be removed, but >other than that I really like the look-and-feel of that grey bar. > > Or something like that, I think changing the slogan is a whole project in an of itself ;-) The slogan came from beatie and that fact that he was a "daemon" daemon: [Middle English, from Late Latin daemn, from Latin, spirit, from Greek daimn, divine power. See d- in Indo-European Roots.] 1. (in ancient Greek belief) a divinity or supernatural being of a nature between gods and humans. 1. mythology demigod: mythological being that is part-god and part-human 2. mythology guardian spirit: a guardian spirit 2. A spirit which guards a place or takes care of or helps a person. n. inward spirit; personality; genius. daemonic, a. Computer Science. A program or process that sits idly in the background until it is invoked to perform its task. /day'mn/ or /dee'mn/ n. [from the mythological meaning, later rationalized as the acronym `Disk And Execution MONitor'] A program that is not invoked explicitly, but lies dormant waiting for some condition(s) to occur. The idea is that the perpetrator of the condition need not be aware that a daemon is lurking (though often a program will commit an action only because it knows that it will implicitly invoke a daemon). For example, under ITS writing a file on the LPT spooler's directory would invoke the spooling daemon, which would then print the file. The advantage is that programs wanting (in this example) files printed need neither compete for access to nor understand any idiosyncrasies of the LPT. They simply enter their implicit requests and let the daemon decide what to do with them. Daemons are usually spawned automatically by the system, and may either live forever or be regenerated at intervals. Daemon and demon are often used interchangeably, but seem to have distinct connotations. The term `daemon' was introduced to computing by CTSS people (who pronounced it /dee'mon/) and used it to refer to what ITS called a dragon; the prototype was a program called DAEMON that automatically made tape backups of the file system. Although the meaning and the pronunciation have drifted, we think this glossary reflects current (2000) usage. - http://www.onelook.com/