0:00:01.621,0:00:05.141
This talk will give an overview of[br]what the Debian publicity team does

0:00:05.340,0:00:07.901
and how they work and how you can[br]support them.

0:00:09.561,0:00:13.101
Please give a warm round of applause to[br]Cédric Boutillier and his talk

0:00:13.381,0:00:15.561
"Debian, a giant with a tiny voice"

0:00:15.860,0:00:21.700
[Applause]

0:00:22.721,0:00:26.220
I'm sorry, I have a kind of technical[br]problem.

0:00:26.542,0:00:30.941
I don't remember the shortcut to bring[br]full screen in okular.

0:00:35.941,0:00:38.581
Ctrl-Shift-P… ok, thank you.

0:00:45.541,0:00:50.581
This is my first DebConf, so I would like[br]to take this opportunity to present myself

0:00:50.881,0:00:56.461
I'm Cédric Boutillier, I'm known as boutil[br]on IRC and I'm a Debian member

0:00:56.640,0:01:02.961
since 2012 and a couple of years before[br]that, I started contributing to Debian

0:01:03.581,0:01:05.121
as a member of the ruby team.

0:01:05.421,0:01:11.901
I also joined the french localization team[br]and I started to translate

0:01:12.301,0:01:17.161
some announcements and that's how I became[br]part of the publicity team.

0:01:18.240,0:01:24.121
What I will talk about today is[br]the structure of the publicity team,

0:01:24.861,0:01:31.961
the various services we are handling in[br]the team and how you can in fact

0:01:32.101,0:01:37.261
get involved in the team and promote[br]Debian through the publicity team.

0:01:38.541,0:01:41.401
So, what is the structure of the team.

0:01:41.541,0:01:47.420
It's a bit complicated because in fact the[br]publicity in Debian is for the moment

0:01:47.620,0:01:51.501
two teams: the Press team and the[br]Publicity team.

0:01:53.061,0:01:58.441
The members of the Press team are[br]delegated by the DPL and

0:01:58.620,0:02:03.041
they can speak in the name of the project[br]when it's needed

0:02:03.281,0:02:05.941
to contact for example journalists.

0:02:07.101,0:02:13.301
They have a private mail alias[br]press@debian.org and they serve as a

0:02:13.501,0:02:17.221
contact point for journalists and the[br]outside world.

0:02:17.721,0:02:22.581
And there is the Debian Publicity team,[br]which is much larger, but…

0:02:22.962,0:02:29.860
not much larger, larger but not as well[br]structured as the Press team.

0:02:30.301,0:02:35.500
We have a public mailing list,[br]debian-publicity@lists.debian.org

0:02:35.900,0:02:40.061
and an IRC channel, #debian-publicity.

0:02:41.140,0:02:45.502
And we should also include in this team[br]all the people doing reviews,

0:02:45.781,0:02:51.821
especially translating our broken english[br]into proper english − Hello Justin −

0:02:53.000,0:02:59.180
and all the translators doing the work to[br]translate

0:02:59.460,0:03:04.501
various announcements in various[br]languages.

0:03:05.981,0:03:10.181
We have also in this Publicity team the[br]maintainers of the Debian blog,

0:03:10.441,0:03:13.980
more on that later, that are also[br]delegated by the DPL.

0:03:15.300,0:03:21.060
And in fact, we should also include the[br]whole project, because publicity is

0:03:21.261,0:03:27.361
the duty of the whole project and[br]everyone should be concerned by this.

0:03:30.981,0:03:36.580
I will now review the various tools we can[br]have in the team.

0:03:38.561,0:03:40.841
First, there are the press announcements.

0:03:41.021,0:03:45.600
They are published on the website in the[br]News/ subsection.

0:03:47.041,0:03:54.160
They inform journalists and users of[br]important changes and they are prepared

0:03:54.300,0:03:57.980
by the Press team and the Publicity team

0:03:58.581,0:04:03.761
and also with various involved teams when[br]there are specific changes.

0:04:06.501,0:04:16.561
It includes the news for the new releases[br]and some times also

0:04:16.681,0:04:22.301
news that are published in coordination[br]with other companies or

0:04:22.561,0:04:23.841
other projects.

0:04:25.221,0:04:29.301
These announcements are a very[br]official way to communicate

0:04:29.540,0:04:30.741
about the project

0:04:31.401,0:04:34.501
and on the wiki, at the moment there is[br]some information about

0:04:35.041,0:04:41.781
how you could approach the team to propose[br]such an announcement.

0:04:43.640,0:04:50.201
There is another tool which is used[br]to publish communication about the project

0:04:50.501,0:04:51.781
in a less formal way.

0:04:51.981,0:04:56.601
It's the Debian blog, AKA bits.debian.org

0:05:00.341,0:05:07.602
It first lived as an unofficial service[br]under news.debian.net for two years

0:05:08.501,0:05:12.761
then it was reopened as an official[br]service in 2013.

0:05:16.360,0:05:26.522
Blogposts that are published there are[br]less formal,

0:05:26.781,0:05:34.101
we can have all kind of announcements[br]there

0:05:34.381,0:05:39.001
so every Debian member has a commit access[br]to the git repository

0:05:39.220,0:05:44.902
to draft an article which is then reviewed[br]before the final publishing.

0:05:46.540,0:05:53.282
Some teams already have published informal[br]reports to this blog and

0:05:53.441,0:06:00.281
it would be nice if it became something[br]usual that teams having sprints

0:06:00.601,0:06:04.940
publish informal reports in this blog.

0:06:06.381,0:06:11.881
We have also some Google Summer of Code[br]announcements and things like that.

0:06:16.141,0:06:20.942
Something I know quite well is the Debian[br]Project News.

0:06:22.941,0:06:32.500
This is a newsletter that at its creation was[br]supposed to be weekly released,

0:06:33.281,0:06:43.361
then after some break it was revived as a[br]bi-monthly newsletter

0:06:43.581,0:06:51.781
but at the moment we kind of lack manpower[br]so it's more or less released once a month.

0:06:53.761,0:06:56.681
So what's the structure.

0:06:58.921,0:07:07.041
It's available on the website under the[br]News/weekly/ section of the website.

0:07:07.241,0:07:13.661
It's also released as an e-mail on[br]debian-news and on localized versions

0:07:13.841,0:07:16.901
of this newsletter for translations.

0:07:17.321,0:07:23.541
It's also available as a RSS feed and[br]links to the newsletter are also

0:07:23.741,0:07:25.521
sent to Identica.

0:07:26.661,0:07:35.201
It's translated into various languages and[br]how do we create this newsletter?

0:07:35.441,0:07:40.960
We gather various information from mailing[br]lists, blog posts and

0:07:41.241,0:07:44.820
write some short paragraphs about this.

0:07:45.041,0:07:50.081
We have also recurrent sections in this[br]mailing list about

0:07:50.240,0:07:56.721
security announcements, interesting new[br]packages, during freeze time

0:07:56.881,0:08:07.881
we publish a summary of the RC bugs statistics[br]and recently we added some information

0:08:08.081,0:08:11.102
about the reproducible builds statistics[br]too.

0:08:13.401,0:08:19.160
A new section that appeared from time to[br]time in the last issues is the

0:08:19.360,0:08:23.201
"Team, what do you do?" section which was[br]introduced by Donald Norwood.

0:08:23.761,0:08:27.362
The principle of this section is to[br]interview teams.

0:08:29.761,0:08:36.621
I think it's a nice way for users and[br]people interested in Debian in general

0:08:36.701,0:08:39.641
to discover the various teams,

0:08:41.420,0:08:51.561
not only teams doing packaging but teams[br]doing like cross archive work or

0:08:51.720,0:08:55.321
work on other fields of the project.

0:08:56.840,0:09:03.081
If your team is invited to answer these[br]questions, please find some time

0:09:03.260,0:09:05.982
to answer to our e-mail and

0:09:06.181,0:09:11.881
if your team is interested in[br]participating in this initiative or

0:09:12.042,0:09:16.202
if you know a team that you would be[br]interested in knowing more about,

0:09:17.081,0:09:20.261
please tell us and we'll try to[br]contact them.

0:09:24.141,0:09:27.301
How can you help the Publicity team.

0:09:29.581,0:09:33.641
You should consider publicity as a way[br]way to advertise your work

0:09:34.341,0:09:40.640
so you can first join the publicity team[br]and work directly on

0:09:40.941,0:09:45.641
what we are producing: announcements[br]or this newsletter

0:09:45.801,0:09:52.001
by writing, reviewing or translating[br]articles like for the Debian Project News.

0:09:53.340,0:09:59.361
Debian is a very large project and it's[br]very difficult for us to monitor

0:09:59.601,0:10:06.701
all the mailing lists and all the IRC[br]channels and things like that

0:10:06.961,0:10:11.201
so if you can help and collect some[br]information about what happens

0:10:11.380,0:10:12.621
in the project, it's very good.

0:10:13.241,0:10:21.681
For example, if you are already a Debian[br]contributor and you did or you saw

0:10:21.841,0:10:24.602
something amazing in the Debian project

0:10:24.821,0:10:32.661
you could just send us an e-mail with just[br]a few lines and a couple of links

0:10:32.942,0:10:36.221
and we could include this into the[br]newsletter.

0:10:36.760,0:10:42.541
If you have a package that you are very[br]happy of,

0:10:42.781,0:10:48.051
you are very happy this package entered[br]the archive and you would like that

0:10:48.221,0:10:52.001
a lot of people use this package, you can[br]also tell us about it

0:10:52.142,0:10:58.622
and we will advertise it in the next[br]Debian Project Newsletter issue.

0:11:01.301,0:11:04.641
Working in the Publicity team is also a[br]good entry point

0:11:04.822,0:11:09.761
for people interested in Debian but who[br]are not contributors yet.

0:11:11.241,0:11:16.821
It's a way where people can learn more[br]about the Debian project.

0:11:17.041,0:11:23.940
So, if you are interested in Debian and[br]you don't know exactly where to start,

0:11:24.061,0:11:26.642
it could be a good starting point.

0:11:33.382,0:11:35.781
What is the workflow we are using.

0:11:35.881,0:11:42.681
Recently, during DebCamp, we migrated[br]from SVN to Git

0:11:42.902,0:11:48.661
so now, all the documents we are handling[br]are kept in Git repositories.

0:11:49.201,0:11:54.781
The Debian Project News, the announcements[br]and the blog have their own Git repository

0:11:55.582,0:12:00.420
Every Debian Member has directly commit[br]access to these Git repositories

0:12:01.041,0:12:09.061
and others can easily get write access by[br]joining the Publicity team project on Alioth

0:12:09.660,0:12:16.120
Coordination to produce these documents,[br]annoucements and the DPN,

0:12:17.060,0:12:21.921
is usually done through the mailing list[br]or the IRC channel

0:12:22.421,0:12:26.081
and once the announcement or the DPN is[br]finished

0:12:26.360,0:12:34.701
then some calls for review or translation[br]are sent to translation and localization

0:12:34.901,0:12:35.700
mailing lists.

0:12:36.861,0:12:40.482
There is more information on the wiki.

0:12:42.421,0:12:48.402
There is an other way to publish news[br]about your work, which is

0:12:48.540,0:12:51.561
the Misc Developer News.

0:12:51.861,0:12:55.401
It's a wiki page at this address.

0:12:56.081,0:13:04.641
This page contains a template you can use[br]and you can edit the wiki page.

0:13:08.481,0:13:13.100
If you are the person adding the fifth[br]news to this wiki page,

0:13:13.770,0:13:19.161
you win the right to collect these five[br]news and send an e-mail

0:13:19.301,0:13:22.961
to debian-devel-announce mailing list[br]with the five news.

0:13:23.280,0:13:29.161
It's quite a light way to send news about[br]the project,

0:13:31.141,0:13:33.640
especially if you are not the fifth one.

0:13:38.502,0:13:41.541
Debian is also present on various social[br]networks.

0:13:42.481,0:13:46.921
We have an official identi.ca account

0:13:50.660,0:13:52.061
which is represented here.

0:13:52.342,0:13:56.021
We're also present on GNU Social, Twitter[br]and Google+.

0:13:59.042,0:14:02.141
There was a special event this year, the[br]release of Jessie and

0:14:02.281,0:14:10.561
we did some live denting on identi.ca and[br]some messages were sent to Twitter

0:14:10.700,0:14:13.740
during the whole weekend, non stop.

0:14:14.121,0:14:16.961
We sent like 150 messages.

0:14:18.661,0:14:23.561
So if you want to propose a DENT, you can[br]go directly to

0:14:23.741,0:14:29.641
the #debian-publicity IRC channel and send[br]a proposition with a DENT: prefix

0:14:30.641,0:14:35.281
and when this proposition is acknowledged[br]by someone of the team,

0:14:35.442,0:14:40.561
this message will appear on the social[br]network.

0:14:41.100,0:14:45.360
You can also e-mail your proposition to[br]Debian Publicity.

0:14:45.961,0:14:50.361
For example, if you want to publish[br]messages about DebConf,

0:14:50.440,0:14:52.002
you are welcome to do so.

0:14:56.161,0:15:03.301
Last tool we have in the Debian Publicity[br]team is the Debian timeline.

0:15:03.581,0:15:08.501
It was created by Chris Lamb and now[br]maintained by the Publicity team.

0:15:09.001,0:15:16.901
It's a web page showing a timeline with[br]various events related to Debian.

0:15:18.021,0:15:23.101
You have the history of all the releases[br]and various events like sprints,

0:15:23.561,0:15:28.901
bug squashing parties, various transitions[br]and things like that.

0:15:32.302,0:15:37.200
All the source code of Debian timeline is[br]maintained in a Git repository.

0:15:37.762,0:15:44.461
So every Debian member can commit to this[br]timeline and then a publicity member

0:15:44.621,0:15:54.721
can push to the server the changes to[br]update the timeline.

0:15:54.981,0:16:01.681
You can look at this timeline and if you[br]see that some event is missing,

0:16:02.561,0:16:09.322
either directly commit to Git or send us[br]an e-mail to the Debian Publicity team

0:16:10.422,0:16:12.620
so we can add this event.

0:16:14.761,0:16:19.461
We have also a lot of projects but[br]currently have no time

0:16:19.501,0:16:20.901
to implement them.

0:16:21.641,0:16:26.321
Examples of this would be to revive the[br]"debaday" website

0:16:26.441,0:16:30.381
which was presenting a new Debian package[br]everyday.

0:16:31.741,0:16:38.962
We could also try to revive the audio[br]interviews which are known

0:16:39.081,0:16:41.561
under the name of "This Week in Debian",

0:16:42.061,0:16:47.222
or subtitle the existing audio interviews[br]in english

0:16:47.521,0:16:51.941
and translate these subtitles into other[br]languages.

0:16:54.121,0:16:58.480
We are also open to new ideas for[br]recurrent sections

0:16:58.521,0:17:00.321
in the Debian Project News.

0:17:01.880,0:17:08.441
We could also try to gather some[br]statistics and

0:17:09.021,0:17:12.021
track mentions of Debian on external[br]websites

0:17:13.341,0:17:19.121
to see how Debian is doing from another[br]point of view.

0:17:20.541,0:17:24.161
You're welcome to propose your own idea.

0:17:24.681,0:17:29.641
We'll have a BOF this afternoon and you[br]are welcome to come and

0:17:30.022,0:17:32.681
discuss with us your own ideas on that.

0:17:34.721,0:17:36.701
Here are some useful links.

0:17:37.322,0:17:42.561
For Debian contributors, you have the[br]mailing and various wiki pages

0:17:43.241,0:17:46.821
about the workflow of the team and

0:17:48.362,0:17:53.821
for users, these are the mailing list and[br]social network

0:17:54.161,0:17:55.901
where we publish some information.

0:17:57.381,0:18:01.821
This is our contact information if you[br]want to get in touch with us

0:18:02.320,0:18:08.321
and please come to the BOF this[br]afternoon in Amsterdam room at 15:00

0:18:08.580,0:18:12.081
We will be happy to discuss with you[br]everything related to publicity.

0:18:12.801,0:18:13.661
Thank you.

0:18:14.122,0:18:20.241
[Applause]

0:18:21.262,0:18:22.162
[Talk master] Thank you very much.

0:18:22.421,0:18:24.881
Are there questions from the audience at[br]this point?

0:18:28.680,0:18:30.821
That doesn't seem to be the case.

0:18:36.281,0:18:38.642
[Q] Less a question and more a comment,[br]really.

0:18:39.781,0:18:41.681
??? highlighting some of[br]the feedback

0:18:41.781,0:18:42.922
we got around the release.

0:18:43.462,0:18:49.301
Both the release team and basically[br]everyone around was

0:18:49.521,0:18:52.540
really really impressed with the live[br]denting and the live tweeting

0:18:52.742,0:18:53.621
of the release.

0:18:54.061,0:18:58.280
It's something that makes it really[br]visible for Debian and

0:18:58.421,0:19:02.321
when we release things and we're able to[br]produce that publicity

0:19:02.662,0:19:04.521
then it makes Debian a really big thing

0:19:04.721,0:19:07.261
so just a huge thanks, really for ???[br]with that.

0:19:07.561,0:19:11.041
I definitely encourage everyone to get[br]involved with the Publicity team.

0:19:12.681,0:19:16.760
It's also a really easy way for people to[br]get involved,

0:19:16.901,0:19:17.881
so if you know anyone who says

0:19:18.001,0:19:20.941
"Oh, I'd like help Debian but I'm not very[br]good at packaging things"

0:19:21.121,0:19:24.861
A bit like me as I haven't done anyone in[br]about 5 years or something.

0:19:25.021,0:19:27.901
Getting involved in the Publicity team and[br]helping out is something that

0:19:28.861,0:19:30.362
I really encourage.

0:19:30.481,0:19:34.460
It's a really good team, it really needs[br]help and we can do so much more with it.

0:19:43.081,0:19:48.640
[Q] At some point there was a project to[br]collect a box which could be used

0:19:48.681,0:19:52.021
at the exhibits, when Debian goes out and[br]exhibit.

0:19:52.381,0:19:54.961
What is the status now of that.

0:19:55.261,0:19:59.380
Did it progress any or do we have a box,[br]like in European states where we could

0:19:59.641,0:20:02.621
easily distribute to a local party to go,[br]to bring at the conference

0:20:02.961,0:20:05.581
and what it would constitute, I wonder.

0:20:06.462,0:20:09.101
Do we have resources for, well…

0:20:09.341,0:20:12.141
Many people disagree that "Oh, we[br]shouldn't have stickers"

0:20:12.322,0:20:13.281
or something like that.

0:20:13.401,0:20:16.121
I think it's already a visibility, right?

0:20:16.261,0:20:20.541
If we have really nice giveaways like all[br]those stickers we have on our laptops.

0:20:20.701,0:20:21.962
Of course we could buy them, right?

0:20:22.261,0:20:24.580
But when we go to the conference and[br]the cost of those

0:20:24.680,0:20:29.120
if we print them in bulk, it's[br]ridiculously small.

0:20:29.981,0:20:35.381
I think it would be beneficial if we have[br]a box, which we could bring

0:20:35.521,0:20:40.841
to a conference and has really nice[br]banners, some nice giveaways.

0:20:41.001,0:20:45.641
Maybe not just to throw them around, but[br]even just for good visitors,

0:20:45.901,0:20:48.821
to give a sticker, I think it's nice.

0:20:49.241,0:20:51.100
And that's what we do for NeuroDebian[br]as well.

0:20:51.960,0:20:56.561
For those close to us, we give those nice[br]stickers for the laptop,

0:20:56.801,0:20:58.282
they are happy, we are happy.

0:20:58.621,0:21:01.621
We have nice exhibit table usually[br]I think.

0:21:02.081,0:21:05.101
So, what is the status there and what[br]should we do about it?

0:21:05.921,0:21:12.880
[A] I think it was handled by the Event[br]team, but this Event team

0:21:13.981,0:21:17.001
doesn't exist anymore, so…

0:21:24.081,0:21:26.621
[Maulkin] I think that's the sound [br]of someone volunteering.

0:21:27.101,0:21:30.161
[laughter]

0:21:30.361,0:21:37.801
So, more seriously, I think it was Martin[br]Zobel wanted a banner and said

0:21:37.941,0:21:40.321
"Oh, we should have a banner.[br]Can we spend the money?"

0:21:40.461,0:21:41.582
and I said "Yes, carry on."

0:21:42.821,0:21:44.441
He said "But I haven't told you how much[br]it cost yet."

0:21:44.661,0:21:48.400
"Carry on, it's not gonna be like ₤5000,[br]so just go, make a banner."

0:21:49.401,0:21:53.181
But he couldn't get anyone to make the[br]artwork for him or do anything like that

0:21:53.380,0:21:57.761
so he sent out some requests and noone[br]was able to do that.

0:21:57.981,0:22:01.541
So, if you want to put a box together and[br]you think we should make stickers,

0:22:01.981,0:22:03.921
do that, that sounds good.

0:22:04.722,0:22:08.460
[Mr Let's do a box] Banner usually use[br]???

0:22:09.281,0:22:12.300
And that's why volunteering [br]???

0:22:12.441,0:22:13.400
at least twice a year.

0:22:13.780,0:22:16.162
So I'm there already.

0:22:16.381,0:22:19.320
But box, we have already some box with[br]some hardware

0:22:19.861,0:22:24.320
and if we could reuse it, I wonder,[br]that would be more efficient.

0:22:26.502,0:22:30.122
Do we have any interesting hardware we[br]should go present as well

0:22:30.281,0:22:32.080
that would be nice in that box.

0:22:34.461,0:22:37.181
Ok, volunteering. Got it.

0:22:37.560,0:22:39.021
[laughter]

0:22:39.181,0:22:42.100
[] If you need help with artwork,[br]just call Valessio.

0:22:53.381,0:22:56.342
[Talk master] Ok. Thank you very much.

0:22:56.520,0:22:58.681
Let's give the presenter another round[br]of applause.

0:22:59.081,0:23:04.361
[Applause]