From owner-freebsd-advocacy@FreeBSD.ORG Fri Feb 18 02:44:57 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 B8B5816A4CE for ; Fri, 18 Feb 2005 02:44:57 +0000 (GMT) Received: from salvador.pacific.net.sg (salvador.pacific.net.sg [203.120.90.219]) by mx1.FreeBSD.org (Postfix) with SMTP id 5AD1A43D49 for ; Fri, 18 Feb 2005 02:44:56 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 23772 invoked from network); 18 Feb 2005 02:44:52 -0000 Received: from unknown (HELO maxwell6.pacific.net.sg) (203.120.90.212) by salvador with SMTP; 18 Feb 2005 02:44:52 -0000 Received: from [192.168.0.109] ([210.24.246.133]) by maxwell6.pacific.net.sg with ESMTP <20050218024451.ZMRV1233.maxwell6.pacific.net.sg@[192.168.0.109]>; Fri, 18 Feb 2005 10:44:51 +0800 Message-ID: <42155724.1040209@pacific.net.sg> Date: Fri, 18 Feb 2005 10:47:00 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Astrodog References: <200502152327.j1FNRBQL041297@fire.jhs.private> <4212F72B.2020201@nbritton.org> <2fd864e050217072412ef0b18@mail.gmail.com> In-Reply-To: <2fd864e050217072412ef0b18@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-advocacy@freebsd.org cc: Julian Stacey Subject: Re: 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: Fri, 18 Feb 2005 02:44:57 -0000 Hi, Astrodog wrote: >> >>Now that you got me thinking about it... There is no reason why a group >>of us (I'll help) couldn't fork the entire FreeBSD website, doc, etc. >>projects and redo or create everything thats needed for a better >>Image/PR etc. Then just point the download links to the freebsd servers. >>This way we can just side step all the bullshit and resistance where >>getting. We could then merge the projects when they finally see the >>light. If we really wanted to we could just rebrand the entire FreeBSD >>project, having are own core/committers of web designers, >>writes/editors, marketing and business people :-). > > > I suspect that would not play really well with most FreeBSD users. > I think that it is good idea to create a new project concentrating on the other things without affecting FreeBSD as it is. DragonFly or even Darwin are doing the same thing on different levels. When FreeBSD sees things in their projects which are considered good those things are ported into FreeBSD without disturbing the current development. This will be the same with a different "marketing" project. The only difference would be that the "marketing" project continues to use the FreeBSD code base without any changes. FreeBSD would keep the "old" user base and will gain new shares in areas never attracted. Erich