Erwin Tenhumberg wrote:
Are you saying that MarCons are spokesmen for the project? That would
be good to know. I didn't realize that came out of the recent discussion.
To be honest, I had not thought too much about that when I quickly wrote
my reply.
Alright, no problem. For a moment I thought I had missed something.
Thus, without a check I would not go that far that
a member of the marcon list is automatically also an official PR
spokesperson.
Though that would be convenient. It'd avoid having more and more lists.
It's good to keep things clear and simple.
Since we had lots of trouble in different areas and different projects
with people expressing their own opinions and implementing their own
personal strategies in the name of OpenOffice.org.
Well, I'll take your word for it. So let's move on and get a list of
spokespeople. I have a proposal. I suggest that the PR team of OOo
consist of:
* Marketing Leads.
* MarCons.
* Representatives from NL projects (e.g. NL leads + a PR person?).
The good thing about this is that it keeps marketing tasks cleanly
inside the marketing sphere. I think this list is very good because:
(a) It is simple and clear.
(b) It doesn't tie down the project needlessly (ie. it allows quick
responses to events).
I think that both (a) and (b) are very important.
This also makes the "keeping on message" part straight forward:
* If a lead tells the press things that aren't true, we address it
just the same way we'd address any other failure on the lead to do their
job. There's no need to alter our current structure.
* If a MarCon can't be trusted to be truthful to the press, would you
want him as a MarCon anyways? After all, what MarCons do is be marketing
contacts for the project.
* Each NL project can remove the "PR person" role if someone turns out
to be a loose canon. Incidentally, there's no reason why the PR person
can't be the project lead. Indeed, this would make sense for smaller NL
projects.
What do you think?
In addition, we could add a few additional
PR experts with the "approval" of the community council.
I think that going through the CC for this will only paralize the
project. This doesn't mean that "the CC sucks". You know I was in the CC
just recently. But you can't be effective, while expecting the CC to be
in charge of everything. We have Marketing Leads, and we trust them to
do marketing, including MarCon management.
Whoever the project picks, we would also need a mechanism to
stop people from doing/saying what they want to do/say if start
to act like a loose cannon.
What I suggested above has that feature, while being simple, and not
requiring changes in the project structure or procedures. It simply
empowers the Marketing project and its Leads to do their job.
BTW, sorry for appearing so negative and critizing again in my
comments. ;-)
You were fine :-)
Cheers,
Daniel.
--
/\/`) Leave your mark at OpenOffice.org
/\/_/ http://oooauthors.org
/\/_/
\/_/ "The pedant keep things in order, the genius
/ rules the chaos" -- Sigrid Kronenberger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
