From owner-freebsd-advocacy@FreeBSD.ORG Tue Feb 15 23:26:28 2005 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 984D316A4CE for ; Tue, 15 Feb 2005 23:26:28 +0000 (GMT) Received: from tower.berklix.org (bsd.bsn.com [194.221.32.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7A1C43D1F for ; Tue, 15 Feb 2005 23:26:27 +0000 (GMT) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A706D.dip.t-dialin.net [84.154.112.109]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j1FNQOYS069851; Wed, 16 Feb 2005 00:26:25 +0100 (CET) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j1FNRBix013140; Wed, 16 Feb 2005 00:27:16 +0100 (CET) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j1FNRBQL041297; Wed, 16 Feb 2005 00:27:11 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200502152327.j1FNRBQL041297@fire.jhs.private> To: freebsd-advocacy@freebsd.org From: "Julian Stacey" Organization: http://berklix.com/~jhs/ Munich Unix, BSD, Internet User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org Date: Wed, 16 Feb 2005 00:27:11 +0100 Sender: jhs@berklix.org Subject: Can FreeBSD Grow Large? 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: Tue, 15 Feb 2005 23:26:28 -0000 > From: Shawn Harrison > Message-id: <421258EE.2000605@tbc.net> > only those who are trusted hackers (committers) have any structural > voice whatsoever in the community. Presumably that includes some who hold commit privs mainly for the freebsd.org web site. It's tedious though, how much irrelevant hot air has been dumped onto advocacy@ Re. logo preferences, considering we won't get to vote ! - Apparently commiters will vote; Presumably advocacy@ will not. - Commiters are on the commit list, & current@, I guess just a low percentage of advocacy@ are committers. - Most commiters will probably ignore advocacy@ when they vote. Deduction: people with logo preferences should contact commiters who will vote, not this advocacy@ list that likely includes few voters. Readers of advocacy@ have limited choices: - Face reality, realise logo preference on advocacy@ is hot air, Or ... - Do a load of send-pr's & be individually invited to be a commiter to src/ ports/ doc/ or www/ who can vote, Or ... - Agitate for votes for advocacy@ members (little chance I guess), Or ... - Wait for commiters (who will ignore advocacy@) to choose Their logo, then advocacy@ individuals can ignore or include logo on non freebsd.org controlled BSD advocacy sites & events that advocacy@ readers organise. Best skip the irrelevant logo debates where our views are Not wanted. Best be more constructive, & discuss what we Can do: eg collecting content for web sites to promote business adopting BSD etc. Harvesting facts such as (paraphrasing) ... From: Johnson David To: ... freebsd-advocacy@freebsd.org Message-id: <9C4E897FB284BF4DBC9C0DC42FB34617641AFA@mvaexch01.acuson.com> 1200 employees ... & Five Solaris IT guys then ... V ... 900 employees using MS need 20 MCSEs now. Julian Stacey Net & Sys Eng Consultant, Munich http://berklix.com Mail in Ascii (Html=Spam). Ihr Rauch = mein allergischer Kopfschmerz.