DebConf Publicity
 1.- Communication channels
The Debian Publicity team handles a set of media to spread the word about the project and the community:
- Debian Project News (biweekly or monthly) - translated to several languages
- Announcements (by mail to debian-news, debian-announce, and in www.debian.org/News) - translated to several languages
- bits.debian.org (The Debian blog) - translated to several languages (starting in late 2015) - It's also shown in planet.debian.org
- @firstname.lastname@example.org (pump.io social network) - English only, often mirrored to @email@example.com (GNU Social Network), @debian at Twitter, and G+.
In addition to that, we have some DebConf specific resources (not handled by the Debian Publicity team):
- @debconf at twitter
- blog.debconf.org which is shown also in DebConf website (until DC15) and planet.debian.org
- DebConf related mailing lists
All these are in English, maybe translated to the local language.
 2.- Human resources
- Laura Arjona, from the Debian Publicity team (DC15 first time, will continue for DC16)
- Ideally, somebody else from DebConf team or local volunteers.
- If we want to publish in a local language different than English and Spanish, it's mandatory that somebody else gets involved.
 3.- Messages to publish and other tasks
Initial list (we could have a look at former DebConf publications to add some more and set a orientative calendar)
- DebConf organization starting
- Do you want to sponsor DebConf?
- Volunteers recruitment (locals or not)
- We have logo!
- Sponsors brochure
- First set of sponsors
- Call for talks
- First set of talks approved
- More sponsors
- Debconf is starting
- Debian birthday
- Debconf live coverage?
- Wraping up - thanks
- DebConf report published
- It would be nice that we add the news about DebConf that we know are published in other media to the corresponding "Press Coverage" page: http://wiki.debian.org/PressCoverage and the important dates about DebConf to the Debian Timeline: https://wiki.debian.org/Teams/Publicity/Timeline
- For each important news item that we have about DebConf (for example, a "thank you sponsors" blog post), we can contribute paragraphs to DPN and dents/twits about it.
 4.- Local media coverage
Coordinate, if needed, the media coverage about DebConf in local media (press contacts, help sponsors if the journalist needs/asks for sponsorship...)
Things done in the past about this topic:
- When we publish announcements (CfP, for example), blog posts, news in the website, we send the URLs to the media so they mirror or write about them (for example, if DebConf happens in Spain, we should contact and send the URLs/news to Meneame, the Spanish reddit, and Barrapunto, the Spanish slashdot).
- We can prepare specific material to be published in their sites (a "Press release"), in coordination with some journalist (for example, for DebConf15 there was coordination with FSFE).
- We can offer/negotiate some kind of sponsorship for them to attend DebConf so they make a coverage themselves, first hand (for DebConf15 it was made with Linux Weekly News, with 8 articles published: https://lwn.net/Archives/ConferenceByYear/#2015-DebConf ).
 5.- Issues
- Decide date of publication for each message item, so people in charge of writing it, or actually publishing it, can organize themselves or ask for help.
- Which messages to publish in which media: We have very different target audiences (sponsors, people thinking bout going to debconf, people near Debian that will follow the conference by streaming, local people/organizations interested in knowing what is going to happen in their city, future Debian users/contributors). Debian publicity handled media is more known maybe to the Debian community, the DebConf media is maybe more interesting for Sponsors and for local audience... Each media has also its own advantages/problems and some people don't want things to be crossposted everywhere. In addition to that, the message needs to be reworded depending on the media and on the target audience
- Proper English, review, or certain translations can be very needed. It's common that we need to act in a short margin of time (we don't have all the details until last moment, and when we have them, we need to be quick publishing, or it will not be news, because a mail to a public mailing list is already sent...). Relaying in only one person to publish everything is stressing and some things will not be published (life happens). Asking for review/proofread and/or translations (l10n-english and l10n-*) needs minimum 2 days margin.
- Contacts with local media (or global tech media) so they amplify our voice is recommended, but difficult to achieve (currently, no list of press contacts...). Somebody is required to answer to journalists offering media coverage, and if possible, coordinate their coverage (see 4. above)
- Live coverage of DebConf itself, or some kind of reports, interviews, photos... would be VERY NICE, but it's unlikely to happen if no dedicated person does it (debconf team is busy during DebConf, larjona not attending). A person at least caring about the microblogging (@debian and @debconf) is very desirable.
- DebConf Publicity as entry point for Debian Publicity: If there are local volunteers (maybe not very involved in Debian) that help in DebConf publicity, they can jump to Debian Publicity team VERY EASILY (and vice-versa).