Hello list,
As discussed on the last meeting (2 Dec. 2008, 1830 CET, freenode
#europython), I volunteered for the role of Publicity Communication
Coordination (PCC). For me to successfully do PCC I welcome any
suggestions, tips or other comments from anybody.
First I like to apologies for the length of this mail, I'll promise to
keep it shorter in the future but to get starting I need to elaborate a
bit. And I wanted to make sure that I am going in the right direction,
if I step on someones toes, please slap me ;-)
So far I have come up with this:
My responsibilities:
- Search & identify publicity channels
- Map a representer to each channel (if no representer available, assume
myself)
- Check if the publicity channel has been used for each outgoing
publicity message
Dependencies:
- Exact dates
- Messages to send out to the public
Open thoughts:
- I assume we send multiple messages like summed up at:
http://www.europython.org/Planning/Publicity, i.e.:
- Call for participation, e.g.: 14 December)
- Call for participation 2 (two week before the submission deadline?
e.g.: 22 March)
- Registration announcement 14 February (do we want to open registration
even before we have the schedule?)
- Announcement of the schedule (May 14, a Tuesday).
- Reminder, halfway between announcement and event (1 June)
Questions:
- Should we send out another reminder a week or two before the event or
is this going to be a bit too much spamming?
- Should we use the publicity channel also to make awareness for
sponsors, i.e. including that in the call for participation?
- Do you want me to change: http://www.europython.org/Planning/Publicity
so that it is workable (for me) and reflects the current state?
- Do you want non electronic promotions to be send out to like posters?
Is it even worth it? If yes, what about:
- Where to send
- Printing/Postage
- Cost
- Who is going to write the messages, I have no objections to do that
but would require review.
- If a channel is a public channel, what e-mail account (if necessary)
should the sender be using? I think that in a publicity perspective it
is bad to use a non-reply'able address. However a real address must be
actively read, but using a existing (private) address will result in
association with EP2009, is that what we want?
I would like to get a bit of wiggle on since the first announcement is
so far planned in less then two weeks. I leave it till about Friday
before I get seriously moving. If nobody objects, I'll feedback on this
list.
Your input is greatly appreciated!
Thanks,
Martin
--
Kind Regards,
Martin P. Hellwig
IT Architect
DCUK Technologies LTD
M: +31 615 679 200
T: +44 2476 386 689
[EMAIL PROTECTED]
_______________________________________________
Europython-improve mailing list
[email protected]
http://mail.python.org/mailman/listinfo/europython-improve
