Return-Path: 
 <ooo-dev-return-7093-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EA5AD7499
	for <apmail-incubator-ooo-dev-archive@minotaur.apache.org>;
 Fri, 14 Oct 2011 19:28:15 +0000 (UTC)
Received: (qmail 98288 invoked by uid 500); 14 Oct 2011 19:28:15 -0000
Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org
Received: (qmail 98250 invoked by uid 500); 14 Oct 2011 19:28:15 -0000
Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ooo-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:ooo-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:ooo-dev@incubator.apache.org>
List-Id: <ooo-dev.incubator.apache.org>
Reply-To: ooo-dev@incubator.apache.org
Delivered-To: mailing list ooo-dev@incubator.apache.org
Received: (qmail 98242 invoked by uid 99); 14 Oct 2011 19:28:15 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 19:28:15 +0000
X-ASF-Spam-Status: No, hits=0.0 required=5.0
	tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of dave2wave@comcast.net
 designates 76.96.27.243 as permitted sender)
Received: from [76.96.27.243] (HELO qmta13.emeryville.ca.mail.comcast.net)
 (76.96.27.243)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Oct 2011 19:28:04 +0000
Received: from omta13.emeryville.ca.mail.comcast.net ([76.96.30.52])
	by qmta13.emeryville.ca.mail.comcast.net with comcast
	id kjSf1h00517UAYkADjTcLD; Fri, 14 Oct 2011 19:27:36 +0000
Received: from [192.168.1.7] ([67.180.51.144])
	by omta13.emeryville.ca.mail.comcast.net with comcast
	id kjSz1h00K36gVt78ZjSztK; Fri, 14 Oct 2011 19:26:59 +0000
From: Dave Fisher <dave2wave@comcast.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: [DISCUSS] Marketing Team
Date: Fri, 14 Oct 2011 12:27:42 -0700
Message-Id: <B52136B0-A653-4A8B-94B7-39BF94A4DED1@comcast.net>
To: OOo-dev Apache Incubator <ooo-dev@incubator.apache.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Virus-Checked: Checked by ClamAV on apache.org

While discussing this month's PPMC Board Report we discussed making =
volunteers from the PPMC responsible for certain roles. We quickly =
proceeded with a Press Liaison due to the immediate need. Before =
settling on a larger set of roles let's have a discussion and come to a =
consensus.

Types of roles or teams:

(1) External or Marketing Team. Involving the relationship of the AOOo =
project community with the many communities in the OOo universe.=20

- Press Liaison. (Don Harbison is currently filling this role.)

- Security Officer. Responsible for security co-ordination with other =
entities.

- TDF Liaison. Dedicated to the special relationship between AOOo and =
LO. (Would we have other special relationships?)=20

- Brand Manager. Dedicated to the OOo brand.

- Legal Affairs. Assure that copyright, license, and terms of use are =
all proper. That the NOTICE and LICENSE files are correct. Seek =
copyright assignments from authors where helpful. (Is this another =
team?)

Regards,
Dave

On Oct 12, 2011, at 12:51 PM, Rob Weir wrote:

> On Wed, Oct 12, 2011 at 1:44 PM, Donald Harbison =
<dpharbison@gmail.com> wrote:
>> On Wed, Oct 12, 2011 at 1:28 PM, Dave Fisher <dave2wave@comcast.net> =
wrote:
>>=20
>>>=20
>>> On Oct 12, 2011, at 10:18 AM, Rob Weir wrote:
>>>=20
>>>> On Wed, Oct 12, 2011 at 1:09 PM, Dave Fisher =
<dave2wave@comcast.net>
>>> wrote:
>>>>> Rob,
>>>>>=20
>>>>> On Oct 12, 2011, at 9:34 AM, Rob Weir wrote:
>>>>>=20
>>>>>> On Wed, Oct 12, 2011 at 11:48 AM, Dave Fisher =
<dave2wave@comcast.net>
>>> wrote:
>>>>>>=20
>>>>>> <snip>
>>>>>>=20
>>>>>>> I think that "we" as the AOOo PPMC will need to find one or more =
PPMC
>>> members to fulfill certain external roles.
>>>>>=20
>>>>>=20
>>>>> I am emphasizing EXTERNALLY facing roles. These people would =
generally
>>> be people with the talent of handling sensitive issues in a delicate =
and
>>> appropriate manner on the list when they arise seemingly out of =
place.
>>> Knowing that there are volunteers available will help the rest of us =
focus
>>> on code or migration.
>>>>>=20
>>>>>=20
>>>>>>>=20
>>>>>>> Perhaps these roles are:
>>>>>>>=20
>>>>>>> (1) Public face of Security for AOOo.
>>>>>>>=20
>>>>>>=20
>>>>>> Work on handling security reports occurs on a private list,
>>>>>> ooo-security.  It is not visible publicly, or even to the PPMC in
>>>>>> general.  Where there needs to be a public communication, for =
example,
>>>>>> to report a vulnerability, it comes from members of ooo-security.
>>>>>> This is all per the recommended process from Apache Security [1]. =
 The
>>>>>> PPMC is welcome to debate and adopt contract guidelines, but I =
would
>>>>>> not recommend it.
>>>>>>=20
>>>>>> The members of the ooo-security list are stated on our FAQ page =
[2]
>>>>>>=20
>>>>>> So I think that part is already covered.
>>>>>=20
>>>>> Given what just happened with LO, we made improvements. But I =
think that
>>> some member of ooo-security needs to be watching for security =
related
>>> questions as they appear on ooo-dev and ooo-users. You and Dennis =
are very
>>> vocal across the whole spectrum of AOOo issues. I think that there =
needs to
>>> be someone we all know is on top of security and can publicly =
contact.
>>>>>=20
>>>>> The rest of us. Me, you, or whoever should refrain from answering =
such
>>> questions (or answer with deferment and deference). This public =
facing
>>> person could generally speak for the group.
>>>>>=20
>>>>>>> (2) Liaison with the TDF.
>>>>>>>=20
>>>>>>=20
>>>>>> Ideally, someone who is already both a PPMC member and a TDF =
member.
>>>>>> We have several.  "Half liaisons" (someone who is a member of one
>>>>>> organization but not the other) don't work quite as well.
>>>>>=20
>>>>> Half or full is not really the issue. Diplomatic and measured =
response
>>> that can both speak for the group and know when to defer back to the =
podling
>>> is important. To me a non-TDF member might be better.
>>>>>=20
>>>>>>> (3) Press Liaison.
>>>>>>>=20
>>>>>>=20
>>>>>> As a podling we're a bit limited here, per Podling guidelines =
[3], but
>>>>>> there is certainly some scope for doing good work here, if =
someone
>>>>>> wants to volunteer.
>>>>>=20
>>>>> Someone should be looking out at the real world and letting us =
know
>>> what's being said about AOOo and then striving to correct the =
record. This
>>> needs to be someone on the PPMC. The person is this role would work =
with
>>> press@a.o. They would establish relationships, etc.
>>>>>=20
>>>>=20
>>>> I don't think it works that way.  I wish it did, but it doesn't.
>>>>=20
>>>> What we've seen is this:
>>>>=20
>>>> 1) Reporters are either monitoring this list, or more likely being
>>>> tipped off by someone, pointing them to threads where there is =
juicy
>>>> stuff.
>>>>=20
>>>> 2) The write an article, quoting participants on this list. They =
are
>>>> not picky.  They'll quote members and non-members alike, me, =
Dennis,
>>>> Simony, whoever.
>>>>=20
>>>> 3) They then publish their article.  They never post a note to the
>>>> list, send a note to Press@, ask who our press liaison is.  They =
are
>>>> getting 50 bucks to write an article in 45 minutes, and that is =
what
>>>> they do.
>>>>=20
>>>> That is how it works.  If we want to change that, having a =
designated
>>>> person is not enough, unless that person actually does the =
preemptive
>>>> outreach.  If we wait for negative stories to be published we're =
too
>>>> late.
>>>=20
>>> Well it looks like a tough job. You do bring up one main benefit of =
a press
>>> liaison "preemptive outreach."
>>>=20
>>> We need someone explicitly building the relationships, becoming =
someone
>>> that the press will know to ask when they want clarification before =
they
>>> publish something negative or just plain wrong.
>>>=20
>>> I will volunteer to tackle this in concert with press@a.o, and Sally
>> Khudairi, VP Publicity, ASF.
>> Now where is that teflon suit?
>> /don
>>=20
>=20
> +1 for Don as press liaison.  I've seen him do good work in this area
> in other organizations.
>=20
> But shouldn't we raise these roles, the call for volunteers, etc., in
> a new thread?  Right now it is buried in a PMC report thread, which is
> not exactly a topic that attracts much attention.
>=20
> -Rob
>=20
>>> Regards,
>>> Dave
>>>=20
>>>>=20
>>>>=20
>>>>>>=20
>>>>>>> (4) Brand Manager / Cat Herder.
>>>>>>>=20
>>>>>>=20
>>>>>> You see those as the same thing?  We've had a couple requests for
>>>>>> permission to use the OOo trademark and logo.  We handled those
>>>>>> requests well, I thought.  I don't think there is a volume of =
such
>>>>>> requests that would suggest we need a person dedicated to that.
>>>>>=20
>>>>> This is more about herding of wiki, BZ, blogs, fora, and websites =
to
>>> have proper branding. Looking out for the OOo and AOOo brand in the =
wild. It
>>> is cat herding because each of these exist in both the legacy OOo =
site and
>>> in various stages of migration.
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>> With people in these roles who are active then perhaps the rest =
of us
>>> can defer immediate responses to questions in these areas when they =
occur on
>>> ooo-dev. With slight formality we might be able to stop the periodic =
and
>>> damaging flames of misunderstanding.
>>>>>>>=20
>>>>>>=20
>>>>>> Other areas where we could use some volunteer leadership:
>>>>>>=20
>>>>>> 5) wiki master
>>>>>>=20
>>>>>> 6) bugzilla master
>>>>>>=20
>>>>>> 7) web master
>>>>>=20
>>>>> These are more obvious roles that are as much internal to the =
project as
>>> external. Never-the-less these are roles.
>>>>>=20
>>>>> (8) User Forum sys admins - supplementing the current proposal =
with
>>> individuals like perhaps Drew.
>>>>>=20
>>>>> On Oct 12, 2011, at 9:50 AM, Donald Whytock wrote:
>>>>>=20
>>>>>> On Wed, Oct 12, 2011 at 12:34 PM, Rob Weir <robweir@apache.org> =
wrote:
>>>>>>> Other areas where we could use some volunteer leadership:
>>>>>>>=20
>>>>>> < snip >
>>>>>=20
>>>>>=20
>>>>>> IP master?  Coordinating the re-licensing process, looking at =
external
>>>>>> packages linked to, and being the go-to for future contributions?
>>>>>=20
>>>>> Sure -
>>>>>=20
>>>>> (9) Legal Maven. Clearing Terms of Use with Apache legal, checking
>>> NOTICE and LICENSE, requesting authors relicense source, etc.
>>>>>=20
>>>>> Regards,
>>>>> Dave
>>>>>=20
>>>>>>=20
>>>>>> Don
>>>>>=20
>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> [1] http://www.apache.org/security/committers.html
>>>>>> [2] http://incubator.apache.org/openofficeorg/ppmc-faqs.html
>>>>>> [3] http://incubator.apache.org/guides/branding.html
>>>>>=20
>>>>>=20
>>>=20
>>>=20
>>=20