From owner-freebsd-advocacy Wed May 13 21:17:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00988 for freebsd-advocacy-outgoing; Wed, 13 May 1998 21:17:38 -0700 (PDT) (envelope-from owner-freebsd-advocacy@FreeBSD.ORG) Received: from mail1.realtime.net (mail1.realtime.net [205.238.128.217]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA00933 for ; Wed, 13 May 1998 21:17:26 -0700 (PDT) (envelope-from jktheowl@bga.com) Received: (qmail 16558 invoked from network); 14 May 1998 04:16:11 -0000 Received: from zoom.realtime.net (HELO zoom.bga.com) (root@205.238.128.40) by mail1.realtime.net with SMTP; 14 May 1998 04:16:11 -0000 Received: from barnowl (apm5-164.realtime.net [205.238.146.164]) by zoom.bga.com (8.6.12/8.6.12) with SMTP id XAA26997; Wed, 13 May 1998 23:16:00 -0500 Date: Wed, 13 May 1998 23:22:59 -0500 (CDT) From: John Kenagy X-Sender: jktheowl@barnowl To: "Jason C. Wells" cc: FreeBSD-advocacy Subject: Re: Preliminary Tenets In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good start, But, watch out for two areas; 1. Having a position of general "free software" advocacy is at some level in conflict with the active promotion of a particular "free" product. That needs to be thought out a bit. 2. Veto? I don't like that word - Why have and advocacy group at all? The core group could just do it. I think the core group's opinion should carry weight but veto? Keep going! John On Wed, 13 May 1998, Jason C. Wells wrote: > Many yesses, no nos. So here we go. > > OBTW, this is not intended to be a mailing list charter. This is intended > to be a charter for an organization. > > This is _my_ vision of a charter. This is proposed to get discussion > started. (Thanks for the advice Greg.) It is very much subject to debate, > addition, or truncation. > > I will not discuss my ideas yet. I will just state them. > > ***** > > - Duties > > The FreeBSD Advocacy Group shall have the duty to spread the word and > improve the user base. > > The Group shall be able to answer this question, asked by a perspective > user, "Why should I choose FreeBSD?" > > - The Group's Position (if not that of each and every member) > > The Group shall support freely available software and other free software > communities including the Free Software Foundation, Mozilla.org, Linux, > and the BSD variants. All free software communities have a vested interest > in cooperation. > > The Group supports software licensing that makes source code available. > The Group is not formed for the purpose of advocating BSD over GPL. The > Group supports the FREEDOM of free software. > > The Group shall advocate the porting of applications to the FreeBSD > platform to provide a compelling reason to use FreeBSD and improve our > user base. > > The Group shall advocate the release of driver source code to enhance > hardware compatibility and improve our user base. > > The Group is formed to advance the FreeBSD user base. The Group shall not > officially engage in activities that detract from other communities. The > Group shall present FreeBSD as an alternative to FooSoft. The Group shall > not engage in "FooSoft Sucks!" > > - Powers > > Current members of the core group shall have veto power until such time > the the Advocacy Group has matured and can handle its own affairs. This is > to ensure that the Advocacy Group performs in a manner which is beneficial > to FreeBSD, Inc and the FreeBSD community at large. > > The FreeBSD advocacy group shall be ruled by "oral vote". In the event > that a clear consensus has not been reached, talk some more and reach one! > :) > > - Moderation. > > Discussion on the FreeBSD-advocacy shall not be moderated. Let rhetoric > stand by its own merit. > > - Sanctioned Advocacy > > All sanctioned advocacy should be perfomed in accordance with the above > duties and positions. > > The FreeBSD Advocacy Group shall sanction certain advocacy actions. The > actions that the Group will sanction will be of the corporate nature. If > FreeBSD is to form a cooperative advocacy alliance with an organization, > that alliance should be sanctioned. > > This is done to provide other organizations with a coherent and consistent > representation of FreeBSD, Inc. > > - Unsanctioned Advocacy > > All members are invited to advocate FreeBSD in their daily affairs. The > opinions of members who engage in unsanctioned advocacy represent their > personal views and not necessarily those views of FreeBSD, Inc. To > represent an unsanctioned position as one that is sanctioned will be > considered inappropriate. > > ***** > > Your turn. > > Thank you, | Try some of this. It will show you where you're at. > Jason Wells | http://www.freebsd.org/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-advocacy" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message