discuss: TLDP Job descriptions for Stein Gjoen
Subject:
Re: TLDP Job descriptions for Stein Gjoen
From:
"Bas v.d. Wiel" ####@####.####
Date:
10 Mar 2005 19:57:26 -0000
Message-Id: <4230A68B.3020200@extranet.kompas-media.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Emma Jane Hogbin wrote:
| <snip>
|
| At this point I feel that this is more of a "soft skill" that
| should be incorporated into all "staff" positions. If there 4 staff
| positions (I'm making this number up, I could have just as easily
| have said 20) then the tasks of public relations and point of
| contact would be shared by all of the 4 (or 20) staff members as
| appropriate. Each staff person will have a different background
| with different contacts (and attend different conferences) and
| therefore be able to do public relations in different ways.
|
I've been involved in the promo/PR-effort for KDE some time ago (until
I decided I just liked Gnome better). They have a small group of
people and a mailing list especially for promotional purposes. Of
course KDE is a lot bigger than TLDP but their idea behind this team
seemed sound to me. To show a single and consistent identity to the
outside world, a small group works on promotional materials and a PR
policy.
TLDP is a lot smaller than KDE so it wouldn't need a whole team that's
solely devoted to PR, but still the idea is worth considering. Key
question is: do we need to actively manage our identity (meaning
uniformity in communications with the outside world) as a singular
entity or are we happy as a loosely knit group? It all depends on what
image we want to express to the outside world. TLDP is a collection
with many individually recognizable contributions. We should mirror
that diversity since it's one of our biggest strengths but also find
some middle ground where we can act as a whole so that we don't emit
contradictory messages to the world.
Bas
- --
Interesse in een digitale handtekening voor uw e-mail? Neem contact op!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFCMKaLjsOWd4ShSbERAgqhAJ462BUUVY77nHIuOoBCejI5GPO8gACfS4kJ
Mv2IbZw7MZrZ/v6oLlWEIAs=
=jyix
-----END PGP SIGNATURE-----
