From owner-freebsd-advocacy Wed Jan 29 11: 3:22 2003 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 AA27B37B401 for ; Wed, 29 Jan 2003 11:03:15 -0800 (PST) Received: from otter3.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93FE743E4A for ; Wed, 29 Jan 2003 11:03:14 -0800 (PST) (envelope-from anderson@centtech.com) Received: (from root@localhost) by otter3.centtech.com (8.12.3/8.12.3) id h0TJ30L8022288; Wed, 29 Jan 2003 13:03:00 -0600 (CST) (envelope-from anderson@centtech.com) Received: from centtech.com (electron.centtech.com [204.177.173.173]) by otter3.centtech.com (8.12.3/8.12.3) with ESMTP id h0TJ2wNG022281; Wed, 29 Jan 2003 13:02:58 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <3E382558.8000508@centtech.com> Date: Wed, 29 Jan 2003 13:02:48 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stacy Olivas Cc: bsd-advocacy@daemonnews.org, advocacy@freebsd.org Subject: Re: [bsd-advocacy] Re: Draft: Proposed FreeBSD PubRel project Charter References: <002801c2c7c7$968abfd0$0502000a@sentinel> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-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 Before we go into getting this stamped for approval, please read my previous post to the bsd-advocacy list about some slight modifications to this team structure.. I think we should have 5, and only 5 (no less, no more) CORE MEMBERS that each have different angles/skillsets (that's the short version). Eric Stacy Olivas wrote: > The only thing is, if you look at 3.d.(3)(a) and 3.d.(4)(a), they are > currently blank. Something needs to > be put there first. Any ideas? > > -Stacy > >>That sounds great. Probably would get accepted. >> >>On Wed, 2003-01-29 at 10:33, Stacy Olivas wrote: >> >>>Ok, >>>Here is what I promised earlier.. Please look it over and >> >>rip it apart.. :) >> >>>Once this gets hammered out, we can ask someone (maybe >> >>Micahel Lucas) to >> >>>present this and >>>get this officially approved to be part of the project. >>> >>>-Stacy >>> >>> >> >>-------------------------------------------------------------- >>-------------- >> >>>------------- >>> >>>(Proposed) FreeBSD Public Relations Project Team Charter (Draft): >>> >>>The following document is a draft of the FreeBSD Public >> >>Relations project >> >>>charter. >>> >>>1. Purpose. The purpose of the FreeBSD Public Relations >> >>project (called >> >>>PubRel) is to >>>inform the world about the existance of the FreeBSD >> >>Operationg system. It >> >>>will be the >>>primary point of contact on all publicity matters for the >> >>FreeBSD OS. >> >>>2. Responsibilities. The FreeBSD PubRel team will be >> >>responsible for: >> >>> a. Coordination of all press releases for the FreeBSD >> >>project (on-line, >> >>>print, etc). >>> b. Maintain an up-to-date press kit on FreeBSD, which >> >>will allow any >> >>>technical or >>> non-technical person understand the advantages >> >>FreeBSD has over other >> >>>OS's. >>> c. Act as the primary point of contact on all FreeBSD advocating >>>activities, >>> to in include (but not limited to): organizing of >> >>booths or other >> >>>public >>> presentations, sponsoring presentations given by various >>>individuals/organizations, >>> etc. >>> d. Recruting new people as advocates for the FreeBSD OS. >>> e. Monitoring all media outlets (to their best of their >> >>abilities) and >> >>>collecting >>> any information found on FreeBSD for use in press >> >>releases, etc. >> >>> f. Promoting a positive image of FreeBSD to the world. >>> g. Act as the primary points of contact with all media >> >>outlets for the >> >>>FreeBSD project. >>> h. Work with the other parts of the FreeBSD project >> >>(core team, release >> >>>engineering team, etc) >>> and with the FreeBSD foundation in developing >> >>promotional materials >> >>>for distribution. >>> >>>3. Organization. >>> >>> a. The PubRel team will consist of not less than four >> >>(4) core team >> >>>members. >>> b. Each of these core team members will share an equal >> >>vote on all >> >>>matters >>> related to the project. >>> c. One member will be designated as the "head" of the >> >>PubRel project, >> >>>and as >>> such be able to push the project in a given >> >>direction to help keep >> >>>from >>> forming a deadlock. >>> d. Each core team member will have specific >> >>responsibilities assignem to >> >>>them. These responsibilities >>> are as follows: >>> >>> (1) Team Head >>> >>> (a) Overall project management and primary point >> >>of contact\ >> >>> (b) Responsible for press releases to on-line >> >>media outlets >> >>>(including Slashdot) >>> >>> (2) Team member #1 >>> >>> (a) Rrcruting new advocates and providing >> >>assistance to advocates >> >>> (b) Responsible for press releases to Magazines >> >>(print, exclusing >> >>>trade publications) >>> >>> (3) Team member #2 >>> >>> (a) >>> (b) Responsible for press releases to Newspapers >>> >>> (4) Team member #3 >>> >>> (a) >>> (b) Responsible for press releases to Trade Publications >>> >>> e. New core team members can be added only upon a >> >>unanimous vote from >> >>>all current team members. >>> f. Team members can only be removed upon a unanimous >> >>vote from all >> >>>current team members and >>> a minimum of 3 votes from the current FreeBSD >> >>project core team. >> >>>4. Reporting requirements. The PubRel team will be >> >>directly responsible to >> >>>the FreeBSD core team and, as such >>>will be required to provide the core team with quarterly >> >>updates on their >> >>>activities. Invluding (but >>>not limited to: >>> >>> a. Number of press releases that were released (and to >> >>what type of >> >>>media outlet) >>> b. Number of press releases that were used (who and when) >>> c. Progress on any current projects. >>> d. Submit copies of all press releases via send-pr >> >>with a copy posted >> >>>to the -advocacy list >>> >>> >>>To Unsubscribe: send mail to majordomo@FreeBSD.org >>>with "unsubscribe freebsd-advocacy" in the body of the message >> >>-- >>Peter Kieser >>pfak@telus.net >> >>() ascii ribbon campaign - against html e-mail >>/\ - against microsoft attachments >> >>_______________________________________________ >>bsd-advocacy mailing list >>bsd-advocacy@daemonnews.org >>https://secure.daemonnews.org/mailman/listinfo/bsd-advocacy >> > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-advocacy" in the body of the message -- ------------------------------------------------------------------ Eric Anderson Systems Administrator Centaur Technology Attitudes are contagious, is yours worth catching? ------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message