Date: 29 Jan 2003 11:11:51 -0800 From: Peter <pfak@telus.net> To: Eric Anderson <anderson@centtech.com> Cc: Stacy Olivas <olivas@digiflux.org>, bsd-advocacy@daemonnews.org, advocacy@freebsd.org Subject: Re: [bsd-advocacy] Re: Draft: Proposed FreeBSD PubRel project Charter Message-ID: <1043867511.677.3.camel@sharpie> In-Reply-To: <3E382558.8000508@centtech.com> References: <002801c2c7c7$968abfd0$0502000a@sentinel> <3E382558.8000508@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
That sounds like a good idea, we should have like 2 core members per version of BSD, or something. The BSD's that I can think of are FreeBSD, MicroBSD, NetBSD and OpenBSD. That would make a total of 8 core members, or should we do it some other way? We really need to get together in a central meeting place, and discuss this out. (In real time). I recommend IRC as the central medium for this to take place. Try irc.striked.org #bsd-advocacy -- We'll work things out, figure out how we're going to do it. Then post a final revision to the mailing lists. On Wed, 2003-01-29 at 11:02, Eric Anderson wrote: > 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 -- Peter Kieser pfak@telus.net () ascii ribbon campaign - against html e-mail /\ - against microsoft attachments To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1043867511.677.3.camel>