From owner-freebsd-advocacy Tue Jan 28 13:30: 8 2003 Delivered-To: freebsd-advocacy@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CD6C37B401 for ; Tue, 28 Jan 2003 13:30:05 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2658E43FAF for ; Tue, 28 Jan 2003 13:30:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h0SLU3NS093478 for ; Tue, 28 Jan 2003 13:30:03 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h0SLU3A7093477; Tue, 28 Jan 2003 13:30:03 -0800 (PST) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B09B37B401 for ; Tue, 28 Jan 2003 13:27:17 -0800 (PST) Received: from digiflux.org (43.Red-80-59-151.pooles.rima-tde.net [80.59.151.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B76B43F85 for ; Tue, 28 Jan 2003 13:27:16 -0800 (PST) (envelope-from olivas@digiflux.org) Received: from digiflux.org (localhost [127.0.0.1]) by digiflux.org (8.12.7/8.12.7) with ESMTP id h0SLR7j7007250 for ; Tue, 28 Jan 2003 22:27:14 +0100 (CET) Received: (from root@localhost) by digiflux.org (8.12.7/8.12.3/Submit) id h0SLR7iO007249; Tue, 28 Jan 2003 22:27:07 +0100 (CET) Message-Id: <200301282127.h0SLR7iO007249@digiflux.org> Date: Tue, 28 Jan 2003 22:27:07 +0100 (CET) From: Stacy Olivas Reply-To: Stacy Olivas To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: advocacy/47606: The advocacy push continues.. FreeBSD PR team proposed... News at 11. Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Number: 47606 >Category: advocacy >Synopsis: The advocacy push continues.. FreeBSD PR team proposed... News at 11. >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-advocacy >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Tue Jan 28 13:30:02 PST 2003 >Closed-Date: >Last-Modified: >Originator: Stacy Olivas (olivas@digiflux.org) >Release: FreeBSD 4.7-STABLE i386 >Organization: >Environment: System: FreeBSD digiflux.org 4.7-STABLE FreeBSD 4.7-STABLE #7: Thu Dec 26 17:18:28 CET 2002 olivas@digiflux.org:/usr/src/sys/compile/Digiflux i386 >Description: 29 January 2003: In the span of just a few days, the newly rekindled spirit of the FreeBSD adovcates seems to be at the point of making a breakthrough. What is the breakthrough? The proposed formation of the FreeBSD PR team that has been officially sanctioned by the FreeBSD core team itself. Dicussions arose as to who would be the leader of this effort? Several people have stepped forward and tossed their "hats" into the ring. The "proposed" structure of this team (that has so far meet the approval of a few -advocacy mailing list participants) is as follows: The FreeBSD Advocacy group should be structured as follows: A core team consisting of not less than 4 people, with at least one person as the overall "head". The core team will be the ones who set the goals, coordinate press releases, etc.. (each member will have a vote on what direction things will go in). The "head" of the team will have an equal vote on issues, but they will also be able to take the initiative and have the ability to "push" things in a given direction (helps keep from forming a deadlock). Using the four person minimum as the base model, each member of the core team will have specific responsibilities to towards the adovcacy project. They are divided as follows (to borrow some stuff from Anthony's post on lead times, etc): Team head: Overall project management/Primary POC Primary advocacy responsibilities: Onlines/Slashdot Core team member #1: In charge of recruting/providing assistance (direction) to new advocates Primary advocacy responsibilities: Magazines Core team member #2: In charge of Primary advocacy responsibilities: Newspapers Core team member #3: In charge of Primary advocacy responsibilities: Trade rags Each core team member will have the authority to speak on behalf of the project itself and act as an official representative for the project (and FreeBSD). They will also have the authority to delegate responsibility to people volunteering to work on the advocacy project (but it does not alleviate them of being overall responsible for what they have delegated.. So, if someone drops the ball..) New core team members can be added ONLY if there is an unanimous vote from all current core team members. Q: Why are we even bothering forming another layer of bureacracy for FreeBSD? Isn't the project kinda bloated as it is with "team members"? A: This isn't official yet (not until the core team gives it's approval for such a thing. It's being formed so that there is a recognizable entity that can be put out as the PR dept for FreeBSD. Q: Who cares? I've been trolling these lists for years and people like you come and go everyday. A: I care. And you are wrong. *WE* will succeed where others have failed. Q: Why? A: Because we can. Q: How? A: Any way we can. Q: When A: Now... >How-To-Repeat: Subscribe to the freebsd-advocacy mailing list and join in! >Fix: Advocate FreeBSD until you are blue in the face! Go find someone who's building a new machine, introduce then to FreeBSD and go from there. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message