0:00:05.640,0:00:09.240
Thank you for coming with us! So...

0:00:10.820,0:00:14.420
All right. How many have heard about the Google[br]Summer of Code?

0:00:14.470,0:00:19.020
Already, if you are not aware, I could be[br]introducing more about what is it and

0:00:20.154,0:00:24.220
and then talk more about what we are going[br]to do in the session[br]

0:00:25.440,0:00:27.200
So, can you raise the hand

0:00:27.678,0:00:30.694
if you are already aware of the Google Summer of Code?

0:00:33.995,0:00:34.912
OK!

0:00:37.160,0:00:38.763
Thank you - I think most of you are aware,

0:00:39.131,0:00:40.880
it's bringing the student developers

0:00:40.880,0:00:43.306
into the open source community, it's all about that

0:00:44.007,0:00:47.202
So, the session is going to be

0:00:47.536,0:00:49.771
mostly the students introducing their projects

0:00:50.189,0:00:53.033
and getting the feedback, and discussing with their mentors.

0:00:53.870,0:00:56.544
If they are getting any questions from IRC, they can discuss

0:00:57.934,0:00:59.552
How they can improve the project in their

0:00:59.762,0:01:01.565
...Their ongoing projects.

0:01:03.801,0:01:06.565
OK. so let me introduce about myself. I am Jaminy,

0:01:08.559,0:01:09.995
So, I come from Sri Lanka

0:01:11.263,0:01:15.413
I am one of the coordinators for[br]Google Summer of Code with Debian

0:01:17.371,0:01:20.300
So, Debian has been participating in the Google Summer of Code

0:01:20.801,0:01:21.860
from 2005, and

0:01:22.692,0:01:25.038
it has been 13 years it has been participating,

0:01:25.618,0:01:27.602
and we had a break in 2017

0:01:28.224,0:01:31.550
and now we are back in 2018 with Google Summer of Code

0:01:33.755,0:01:37.048
and these are the teams for GSoC coordination

0:01:37.400,0:01:38.514
I am representing the team

0:01:39.330,0:01:42.627
Daniel Pocock, Alexander, and it's me

0:01:44.993,0:01:48.168
This year, we have accepted 25 students

0:01:49.828,0:01:51.367
And that's the link for the projects

0:01:52.518,0:01:54.325
that are ongoing this year

0:02:00.390,0:02:03.713
So, there is an interesting GSoC statistic this year

0:02:04.384,0:02:06.044
this year we have selected

0:02:06.754,0:02:09.201
I mean, this was from the Google Open Source blog,

0:02:09.765,0:02:13.451
and they said there are three students

0:02:13.704,0:02:15.233
Four students accepted from Kosovo

0:02:15.677,0:02:16.909
And...

0:02:17.711,0:02:21.264
The three students are from our Debian community, and they are here joining us

0:02:22.225,0:02:23.369
joining with us,

0:02:23.700,0:02:25.434
to introduce more about their project

0:02:26.469,0:02:28.183
I hope that, without wasting more time,

0:02:28.672,0:02:31.405
I could give the chance for the students to introduce,

0:02:31.832,0:02:33.603
to talk more about their projects.

0:02:34.706,0:02:35.753
Arthur, can you...

0:02:39.461,0:02:41.612
[ audience clapping ]

0:02:51.709,0:02:53.669
So, you hear me? OK?

0:02:56.175,0:02:57.492
Yes? Nice.

0:02:59.344,0:03:00.226
So...

0:03:01.285,0:03:03.322
Hello, my name is Arthur del Esposto

0:03:03.729,0:03:05.176
I am going to talk about my GSoC project

0:03:05.899,0:03:08.544
that is titled "Improving Distro Tracker to better support Debian teams"

0:03:09.364,0:03:12.499
My mentor is Lucas Kanashiro and my co-mentor is Raphael Hertzog.

0:03:14.501,0:03:17.140
I will provide you some context about why we are doing this.

0:03:18.191,0:03:19.045
So, basically,

0:03:19.316,0:03:22.604
Debian teams used to rely on Packages Entropy Tracker

0:03:22.844,0:03:25.076
with the assistance that basically got some information about

0:03:26.725,0:03:28.961
the package from Debian, from Alioth,

0:03:30.364,0:03:31.905
and display some kind of information

0:03:32.358,0:03:35.070
inside tables and some categories.

0:03:38.225,0:03:41.132
And we also had inside our Debian infrastructure

0:03:41.587,0:03:44.103
the tracker.debian.org, which you probably have used before,

0:03:44.735,0:03:49.206
that basically gathers the same sort of information from several sources inside Debian

0:03:50.180,0:03:54.027
and puts this in a Web application.

0:03:54.730,0:03:56.181
So, for example, you have the base

0:03:56.587,0:03:58.262
of a specific package, the Web defaults,

0:03:58.651,0:04:01.110
and you can get all the information related to that package.

0:04:02.351,0:04:04.338
And what we want to do, because...

0:04:04.654,0:04:07.919
that has not been maintained anymore

0:04:08.359,0:04:09.826
and also, he used to track the

0:04:10.794,0:04:12.536
package repository from Alioth.

0:04:13.254,0:04:14.918
And what we really want to do

0:04:15.551,0:04:19.544
is just continuing to support Debian teams[br]to track the health of the packages and to

0:04:19.928,0:04:21.659
and to prioritize their work efforts

0:04:21.862,0:04:23.147
by migrating the PET features

0:04:23.428,0:04:24.895
to Distro Tracker, and also

0:04:25.284,0:04:27.614
we want to track Salsa repositories instead of Alioth.

0:04:28.918,0:04:30.796
So, what are the results we have so far?

0:04:31.684,0:04:32.645
So, basically...

0:04:32.896,0:04:34.213
if you enter a team page,

0:04:34.547,0:04:36.093
of anything inside Distro Tracker

0:04:36.470,0:04:38.163
you are going to get this kind of table

0:04:38.658,0:04:40.500
so basically you have the first column

0:04:40.803,0:04:41.769
with the package name

0:04:42.355,0:04:44.432
the second column with the changelog version

0:04:44.706,0:04:45.993
and the VCS of that package,

0:04:46.412,0:04:48.310
the third column with the archive version,

0:04:49.126,0:04:51.078
we also are tracking the bugs here

0:04:51.340,0:04:52.300
and the last column

0:04:53.070,0:04:54.734
has the upstream version.

0:04:55.072,0:04:57.006
OK, of this package.

0:04:57.249,0:05:00.200
And, another interesting feature

0:05:00.391,0:05:02.201
that we are providing you is that if

0:05:02.743,0:05:04.043
you pass the mouse over

0:05:04.414,0:05:06.115
one of those fields, you are going to get

0:05:06.415,0:05:08.453
more detailed information about that specific field.

0:05:09.265,0:05:10.799
OK, so for example here we have

0:05:11.711,0:05:13.615
the information links to BTS

0:05:14.315,0:05:15.652
related to the bugs

0:05:16.140,0:05:17.603
that exist for the package.

0:05:19.768,0:05:23.034
We also provide some categories

0:05:23.419,0:05:24.866
so basically we could have

0:05:25.259,0:05:27.244
more than one category of package tables

0:05:27.539,0:05:29.436
for example, you could have like

0:05:29.616,0:05:30.751
packages with RC bugs,

0:05:31.004,0:05:32.890
packages that have a new version

0:05:33.129,0:05:34.637
in the upstream, and we have

0:05:35.088,0:05:37.219
specific pages where each of these

0:05:37.462,0:05:39.121
package tables. OK?

0:05:40.041,0:05:41.102
And we have

0:05:41.374,0:05:42.857
a large number of teams

0:05:43.329,0:05:46.539
inside Debian, inside this specifically[br]inside the Distro Tracker,

0:05:46.975,0:05:48.166
so we also provide this

0:05:49.730,0:05:51.202
autocomplete text field

0:05:51.667,0:05:53.007
so you can easily find

0:05:53.357,0:05:56.417
your team, the team that you are interested in.

0:05:57.592,0:05:57.971
And...

0:05:58.856,0:06:01.547
that was my resource, and so far we have

0:06:01.915,0:06:03.194
faced some challenges,

0:06:03.809,0:06:05.502
first is that Distro Tracker

0:06:05.806,0:06:08.130
has a generic purpose architecture

0:06:08.363,0:06:10.179
because it should be used by several

0:06:10.523,0:06:12.543
distros, so it's also being

0:06:12.784,0:06:14.541
used by the Kali community, so basically

0:06:14.855,0:06:18.403
everything you are going to do you have[br]to make it extensible, have to design it

0:06:18.769,0:06:20.930
to be extensible by this specific application

0:06:21.254,0:06:22.956
that implements that specific features from

0:06:23.511,0:06:25.359
their distros.

0:06:26.251,0:06:28.164
Also, the database design is challenging, because

0:06:28.526,0:06:31.850
we have to collect all this data from several

0:06:32.991,0:06:34.325
database tables

0:06:36.586,0:06:37.668
and some of these

0:06:37.871,0:06:41.291
context is realized in JSON fields inside the database

0:06:41.616,0:06:43.495
so it's not easy to get these. And also,

0:06:43.761,0:06:45.231
we have faced some problems,

0:06:45.482,0:06:47.254
some performance problems, because we are

0:06:47.578,0:06:49.680
we are handling a large number of table cells

0:06:49.845,0:06:51.284
dynamically, so basically we are building

0:06:51.560,0:06:53.353
it of these table cells

0:06:54.165,0:06:55.193
in run time.

0:06:57.913,0:07:00.513
And, until the end of GSoC, I plan to

0:07:00.891,0:07:02.714
create a cache mechanism, I am already

0:07:02.996,0:07:04.528
working on that, proposed a merge request on it,

0:07:05.059,0:07:07.078
to try to improve the performance of

0:07:07.367,0:07:08.376
table rendering

0:07:09.799,0:07:11.121
I also want to have all my

0:07:11.472,0:07:14.575
merge requests accepted

0:07:15.111,0:07:16.058
inside Salsa

0:07:17.457,0:07:18.856
We also want to provide more

0:07:19.206,0:07:21.249
package tables with new categories

0:07:22.409,0:07:23.956
and also provide a new feature that

0:07:24.637,0:07:26.353
you could be able to sort the team

0:07:26.633,0:07:28.614
for content based on columns, for example

0:07:29.144,0:07:30.396
I want to sort my

0:07:31.504,0:07:32.566
my table based on

0:07:32.753,0:07:34.004
on the number of bugs, for example.

0:07:36.442,0:07:37.681
And there is also that we

0:07:38.211,0:07:39.827
got good results so far, and

0:07:40.210,0:07:42.694
I have received valuable feedback from the Debian community

0:07:43.101,0:07:44.925
and I have a lot of ideas to continue

0:07:45.253,0:07:46.938
working on this after the GSoC as well

0:07:47.692,0:07:48.634
The GSoC has been

0:07:48.868,0:07:50.695
an amazing experience, I have been learning a lot,

0:07:51.261,0:07:54.373
which Kanashiro has had to log all the[br]community members

0:07:55.222,0:07:57.070
I look into contributing to Debian

0:07:57.395,0:07:58.276
of course

0:07:58.499,0:08:01.531
Thank you to the Debian community to

0:08:01.866,0:08:04.380
provide me this opportunity to come here to DebConf

0:08:04.578,0:08:05.666
to present my work.

0:08:06.278,0:08:08.895
Lets get moving on, and thanks.

0:08:09.021,0:08:12.689
[ audience clapping ]

0:08:31.352,0:08:33.225
So, my project is called

0:08:33.494,0:08:34.881
"Port Kali Packages to Debian"

0:08:35.708,0:08:39.530
and my mentors are Raphaël Hertzog[br]and Gianfranco Costamagna.

0:08:39.974,0:08:42.629
Unfortunately, they didn't come to

0:08:42.788,0:08:44.322
this year's DebConf, and

0:08:46.588,0:08:48.917
we are from the pkg-security

0:08:49.157,0:08:50.631
tools packaging team, so this is

0:08:50.973,0:08:52.883
something I have been working on

0:08:53.467,0:08:55.856
for the past one year and a half

0:08:56.200,0:08:58.512
I think I started packaging

0:08:58.762,0:08:59.745
on 2016

0:09:00.038,0:09:01.575
and in 2017 I started

0:09:01.816,0:09:03.609
working on the security tools packaging

0:09:04.166,0:09:05.621
because this is something that really

0:09:05.848,0:09:07.117
interests me, so

0:09:07.583,0:09:09.329
What actually is Kali Linux?

0:09:10.051,0:09:13.582
Kali Linux is a digital[br]forensics and pentesting distribution

0:09:14.020,0:09:15.721
that has like lots of packages

0:09:16.268,0:09:17.458
is by far

0:09:17.658,0:09:19.635
the most used distribution

0:09:20.183,0:09:22.164
for "capture-the-flag" competitions

0:09:23.164,0:09:24.424
and is based on unstable

0:09:24.852,0:09:26.551
and the thing is that Kali has

0:09:26.789,0:09:28.740
a more relaxed policy

0:09:28.989,0:09:30.675
than Debian's, so that's the reason

0:09:30.991,0:09:31.892
of the

0:09:32.617,0:09:34.120
differences between the packages

0:09:34.637,0:09:39.160
I mean, the packages that Kali has and Debian hasn't

0:09:39.369,0:09:40.163
so, at first

0:09:40.496,0:09:42.436
I did gather some information about

0:09:42.661,0:09:44.209
what packages can I work on

0:09:44.657,0:09:46.208
and what are the problems

0:09:46.473,0:09:48.346
that it should rather get them on Main

0:09:48.686,0:09:50.395
So, I first started using

0:09:50.653,0:09:53.006
this dashboard from Kali Linux, and they have

0:09:53.395,0:09:57.653
also used the tracker system that we[br]use on Debian

0:09:58.005,0:09:59.084
and this is a special dashboard

0:09:59.304,0:10:01.093
where we can see how many

0:10:01.331,0:10:02.921
packages are on Kali Linux that

0:10:03.134,0:10:04.128
aren't on Debian

0:10:04.777,0:10:06.632
at the time, and this is for today, so there are

0:10:06.797,0:10:08.591
477 packages

0:10:09.335,0:10:10.695
but this includes dependencies

0:10:11.014,0:10:12.772
and lots of packages are not

0:10:13.105,0:10:14.867
that really important, and

0:10:15.089,0:10:18.831
some of them are not installed by default on Kali

0:10:19.315,0:10:20.451
So, the first thing,

0:10:20.643,0:10:22.014
I already knew some packages that

0:10:22.181,0:10:23.707
I really would like to see on Debian, and

0:10:24.035,0:10:25.706
the first one was Metasploit

0:10:25.956,0:10:28.280
because it's one of the most used

0:10:28.452,0:10:29.415
frameworks for pentesting

0:10:29.766,0:10:31.836
I have started by looking at

0:10:32.088,0:10:34.330
what should I do

0:10:34.554,0:10:36.026
and it was a really tough job

0:10:36.232,0:10:37.968
because Metasploit is currently

0:10:38.183,0:10:40.154
bundling all their gem dependencies

0:10:40.585,0:10:42.447
Because of, this is a huge problem

0:10:42.706,0:10:43.762
there was a big discussion

0:10:44.023,0:10:45.230
n the Debian mailing lists about that,

0:10:45.476,0:10:47.259
but whatever, I use repology

0:10:47.582,0:10:49.246
in order to see what distros

0:10:49.547,0:10:51.332
were already packaging this stuff

0:10:51.589,0:10:53.466
and at the end, there should

0:10:53.730,0:10:55.362
be around 40 packages

0:10:55.592,0:10:57.878
that I had to package in order

0:10:58.094,0:10:59.362
to see if it would work, because

0:10:59.600,0:11:01.292
you have the version problem, because

0:11:01.489,0:11:03.056
bundling the distro version, and

0:11:03.264,0:11:05.643
we decided not to do that

0:11:05.820,0:11:07.533
during this project, so I

0:11:07.780,0:11:09.692
had to look for other packages

0:11:09.988,0:11:11.568
and I didn't want to

0:11:11.731,0:11:13.694
do this manually, so I

0:11:13.918,0:11:15.088
developed a

0:11:16.276,0:11:17.460
kind of big shell script

0:11:17.711,0:11:19.107
it shouldn't be a shell script, it should be in

0:11:19.326,0:11:20.788
a programming language, but

0:11:21.223,0:11:23.329
got big worked on, and to this

0:11:23.547,0:11:25.091
scripts I give

0:11:25.346,0:11:26.916
I input it a list of packages, and it

0:11:27.090,0:11:28.444
cloned all the Kali

0:11:28.767,0:11:30.868
Git repositories for this package,

0:11:31.406,0:11:33.081
build each one of them, and did

0:11:33.474,0:11:34.983
some basic checks, like if

0:11:35.290,0:11:36.314
it is a default

0:11:37.450,0:11:38.473
Kali package, if it's

0:11:39.493,0:11:41.359
buildable, because some of the packages

0:11:41.633,0:11:43.532
are not buildable because we don't have

0:11:43.721,0:11:44.996
the build dependencies in Debian right now,

0:11:45.284,0:11:47.530
it checks if it is DEP5 compliant already,

0:11:47.749,0:11:49.392
if we need manpages, if we need

0:11:49.752,0:11:50.665
hardening, if

0:11:50.946,0:11:52.987
it is bundling some gems, and if

0:11:53.348,0:11:55.871
there are [?], there is about

0:11:56.329,0:11:57.794
twenty or thirty something

0:11:58.089,0:11:59.445
columns on here

0:11:59.770,0:12:01.503
so you have lots of info

0:12:01.786,0:12:03.494
and in order to know

0:12:03.734,0:12:05.762
which are the most important issues

0:12:06.236,0:12:08.186
Raphaël gave me the idea to

0:12:08.426,0:12:10.417
look for the number of uploads that

0:12:10.799,0:12:12.410
the package had since

0:12:12.627,0:12:13.714
it hit Kali, so I

0:12:13.957,0:12:15.271
can only

0:12:15.527,0:12:17.707
just sort for the number of uploads

0:12:17.996,0:12:19.895
and I have the most important ones.

0:12:20.242,0:12:22.233
This made the process

0:12:22.487,0:12:24.540
really easy, like a lot more

0:12:24.772,0:12:25.835
easy, and I

0:12:26.407,0:12:28.265
am publishing this on our team's

0:12:28.576,0:12:30.454
wiki page, and I will keep using this

0:12:30.813,0:12:32.313
like, forever

0:12:32.574,0:12:34.568
because it really helps other people that

0:12:34.792,0:12:37.132
want to contribute to our team, and

0:12:38.696,0:12:40.727
this is another software

0:12:41.046,0:12:43.217
that I tried, how many time do I have?

0:12:43.740,0:12:44.559
OK

0:12:45.127,0:12:47.085
another package that I really want to

0:12:47.281,0:12:48.873
see on Debian is zaproxy, and

0:12:49.263,0:12:50.761
for zaproxy,

0:12:51.013,0:12:52.701
I had to do a manual checking, because it is

0:12:52.943,0:12:54.121
a Java program, and

0:12:54.641,0:12:57.870
Java has... I really don't like Java, so

0:12:58.250,0:12:59.630
they bundle like

0:13:00.044,0:13:02.176
...zaproxy is great software, but

0:13:02.746,0:13:04.282
they bundle some

0:13:04.501,0:13:06.154
libraries, and I

0:13:06.405,0:13:08.388
talked to upstream, and they are very

0:13:08.652,0:13:09.904
receptive, and they

0:13:10.204,0:13:11.817
want to help us, but

0:13:12.732,0:13:14.719
I didn't manage to package it yet,

0:13:15.174,0:13:17.283
I think I will do it after GSoC

0:13:17.662,0:13:19.241
but there are

0:13:19.453,0:13:21.594
some packages that we need to introduce

0:13:21.773,0:13:23.468
on Debian. Some of the packages that zaproxy

0:13:23.798,0:13:25.406
upstream is thinking about

0:13:25.606,0:13:28.456
dropping them, and putting just[br]on the extensions, because

0:13:29.095,0:13:34.056
the core doesn't need them[br]and some of the packages are old

0:13:34.698,0:13:35.814
and stuff like that, we have

0:13:36.920,0:13:38.740
there is a lot of problems [br]that you can have

0:13:40.019,0:13:41.155
like... there was a

0:13:41.434,0:13:43.589
package which was GPL licensed

0:13:44.093,0:13:45.445
but it was linking against

0:13:45.735,0:13:47.554
OpenSSL, and in order

0:13:47.820,0:13:49.748
to do that, you have to either add

0:13:50.005,0:13:51.433
a license exception to your license

0:13:51.685,0:13:53.781
And I talked to upstream, and

0:13:54.187,0:13:56.319
it cooperative upstream,

0:13:56.633,0:13:58.371
it is a software which is used

0:13:58.913,0:13:59.819
to break

0:14:00.066,0:14:00.990
WiFi password,

0:14:01.284,0:14:02.798
like, doing offline cracking

0:14:04.175,0:14:05.892
and upsream decided to change its license

0:14:06.457,0:14:07.682
to BSD license

0:14:08.065,0:14:09.381
so we could release that on Debian. I

0:14:09.746,0:14:12.159
can't remember right now if it's on the NEW queue

0:14:12.455,0:14:13.892
or if it already hit

0:14:14.132,0:14:15.629
unstable, but I think is on the NEW queue.

0:14:17.708,0:14:18.610
So, in the end,

0:14:20.579,0:14:22.240
the results are, I made the script,

0:14:22.486,0:14:24.491
which is going to be used by

0:14:24.708,0:14:26.071
some time. There are some

0:14:26.259,0:14:27.419
fixes that can be

0:14:29.455,0:14:31.980
We have to do on the script to[br]make it better

0:14:32.368,0:14:33.574
to make the checking better, because

0:14:33.785,0:14:35.196
we still have some corner cases where

0:14:35.493,0:14:36.954
it doesn't work really well,

0:14:37.975,0:14:39.427
we got some new packages in Debian,

0:14:39.686,0:14:40.894
which is really good. I have to

0:14:41.135,0:14:43.555
make some upstream contributions, because

0:14:44.466,0:14:45.793
for some packages I wrote

0:14:46.028,0:14:47.663
their manpage, and I sent it

0:14:48.124,0:14:49.852
to upstream, there was this

0:14:50.225,0:14:51.859
company of software that

0:14:52.090,0:14:53.618
changed its licensing to be like

0:14:54.015,0:14:55.818
correctly compliant with

0:14:56.104,0:14:57.818
OpenSSL license, and

0:14:58.869,0:15:00.034
and we got now a better

0:15:00.229,0:15:01.977
Kali and Debian for its users, because

0:15:02.320,0:15:03.832
when a package is just

0:15:04.035,0:15:05.897
in Kali, they don't like

0:15:06.986,0:15:08.098
to do hardening,

0:15:08.314,0:15:09.906
that's one example of things that

0:15:10.187,0:15:12.518
gets better when the package hits Debian

0:15:13.381,0:15:16.445
because when we enable hardening

0:15:16.653,0:15:19.150
sometimes we see problems that makes[br]the package to

0:15:19.344,0:15:21.683
fail to build, and then we fix that,

0:15:21.931,0:15:23.832
upload to Debian, and when the package hits

0:15:24.159,0:15:25.735
unstable, Kali starts

0:15:26.054,0:15:28.877
taking this package from Debian, and

0:15:29.107,0:15:30.418
they can use our infrastructure

0:15:30.715,0:15:31.944
to do some QA

0:15:32.193,0:15:34.835
and stuff like that, and they

0:15:35.048,0:15:36.879
there are two people from Kali that I know at least,

0:15:37.120,0:15:38.450
Raphaël and Sophie, and they work

0:15:38.656,0:15:40.691
on Debian also, on our team, so

0:15:40.946,0:15:42.763
when there's a new release, they upload

0:15:43.015,0:15:44.300
the release on Debian,

0:15:44.746,0:15:46.612
so Debian users win

0:15:46.944,0:15:48.513
by that also, and

0:15:48.808,0:15:50.778
they already did lots of work

0:15:51.138,0:15:52.492
on their packages, so

0:15:52.776,0:15:54.753
yes, I think that's

0:15:56.320,0:15:58.477
the summary of the results

0:15:59.529,0:16:00.463
Thank you.

0:16:01.367,0:16:04.305
[ audience clapping ]

0:16:31.556,0:16:33.169
Hello, I am Enkelena Haxhiu

0:16:33.405,0:16:35.371
I am from the Republic of Kosovo, and

0:16:35.722,0:16:38.286
I am here to represent my Google Summer of Code

0:16:39.512,0:16:40.555
project. My mentors are

0:16:40.716,0:16:42.139
Bruno Milena and Gabriela.

0:16:43.156,0:16:44.154
So, my project is

0:16:44.505,0:16:45.782
a Mozilla Firefox

0:16:46.152,0:16:47.908
web extension to

0:16:48.103,0:16:49.818
give free and...

0:16:50.092,0:16:52.384
to give free software alternatives

0:16:52.689,0:16:54.349
to the apps on the Internet, so to have

0:16:54.609,0:16:56.251
avoiding non-free

0:16:56.910,0:16:58.863
apps and sites.

0:16:59.339,0:17:01.291
So, the goals for this project

0:17:01.795,0:17:02.858
were that

0:17:03.141,0:17:04.720
while the user is surfing

0:17:04.942,0:17:06.647
on the Internet, the moment that he

0:17:06.818,0:17:07.982
uses a non-free

0:17:08.229,0:17:09.692
software,

0:17:10.424,0:17:12.554
my extension will detect it

0:17:12.945,0:17:14.724
and then give an

0:17:14.963,0:17:17.640
alternative to it, a free software alternative.

0:17:18.319,0:17:19.844
The user should be able

0:17:20.039,0:17:21.590
to stop it when it's annoying,

0:17:21.821,0:17:23.710
and the notifications should be

0:17:23.922,0:17:25.044
only once per session,

0:17:25.355,0:17:27.156
and we wanted to have like a

0:17:27.367,0:17:29.545
database through self-hosted

0:17:29.794,0:17:31.579
API, or to use

0:17:31.810,0:17:33.878
a free software device

0:17:34.119,0:17:35.514
and then all this database

0:17:35.774,0:17:36.960
show it on our Web page.

0:17:38.622,0:17:40.483
I started by making

0:17:41.837,0:17:43.660
the user experience design,

0:17:44.024,0:17:45.708
based on that, because

0:17:46.035,0:17:47.960
should work like, should work fine,

0:17:48.289,0:17:50.013
I made some sketches and mockups

0:17:50.345,0:17:51.563
and then the persona

0:17:51.922,0:17:54.088
and then the finding the bad habits of apps,

0:17:54.484,0:17:55.911
like research, and

0:17:56.113,0:17:58.439
I started implementing it by

0:17:58.560,0:18:00.184
coding it, I used Mozilla

0:18:00.380,0:18:01.992
API to make my extension

0:18:02.066,0:18:04.207
communicate with the Web browser API

0:18:05.347,0:18:06.265
I created a

0:18:06.558,0:18:08.233
JSON data file, it's like

0:18:08.519,0:18:10.173
a proof of concept to just take

0:18:10.508,0:18:12.368
the data, because this is going to be

0:18:12.547,0:18:13.894
later in a real database.

0:18:14.558,0:18:15.826
So the code

0:18:16.078,0:18:17.529
logic, do

0:18:18.023,0:18:20.008
select and display the alternatives

0:18:20.378,0:18:21.464
based on the current

0:18:21.940,0:18:23.556
active website, is that

0:18:23.873,0:18:25.756
we should get the URL,

0:18:26.048,0:18:27.585
identify it by sending...

0:18:28.538,0:18:30.241
Identify it, and then to send

0:18:30.472,0:18:31.821
to that JSON file, check

0:18:32.181,0:18:34.018
and, based on

0:18:34.290,0:18:35.719
that, to give an alternative.

0:18:35.954,0:18:38.039
If it exists, of course. We did

0:18:38.314,0:18:40.182
We don't want to annoy the user

0:18:40.864,0:18:42.284
like, to show too much notifications

0:18:42.537,0:18:44.124
so we made it only once

0:18:44.372,0:18:45.965
per session for the current app,

0:18:46.371,0:18:48.101
and it has the ability to

0:18:48.383,0:18:49.708
stop and start it. We use the

0:18:49.974,0:18:51.923
local storage to hold the

0:18:52.170,0:18:53.183
user settings

0:18:54.054,0:18:56.068
and then we have to present this

0:18:56.284,0:18:57.795
free software list through

0:18:58.019,0:18:59.623
a web page that is generated by

0:18:59.878,0:19:01.101
that database.

0:19:02.502,0:19:04.017
This is like a simple diagram

0:19:04.984,0:19:06.475
of basically what I just said.

0:19:07.621,0:19:10.176
These are some screenshots with words

0:19:10.569,0:19:12.181
for example, Dropbox is a nonfree

0:19:12.426,0:19:15.587
software, and this is

0:19:16.665,0:19:18.986
the notification that it gets

0:19:19.344,0:19:21.139
it says, "Dropbox has open source alternatives

0:19:21.497,0:19:23.440
like seafile",

0:19:23.815,0:19:24.984
and then, I have here

0:19:26.041,0:19:27.936
the web page that it gets

0:19:28.522,0:19:30.505
the extension popup

0:19:31.232,0:19:33.470
and all these things. This is how it looks like.

0:19:34.002,0:19:36.365
And then, i made a project website

0:19:36.694,0:19:39.204
which holds all the data

0:19:39.661,0:19:41.035
I made the design of it and

0:19:41.215,0:19:43.083
the frontend and the data generation.

0:19:43.373,0:19:44.878
I plan to leave this open

0:19:45.249,0:19:47.350
so developers can add stuff there

0:19:47.671,0:19:49.720
to the database, and then

0:19:49.969,0:19:52.092
generates it, and

0:19:52.347,0:19:54.114
it goes, like, right away to the

0:19:55.489,0:19:57.198
to the project website.

0:19:57.528,0:19:59.082
I don't need to hard-code...

0:19:59.550,0:20:00.915
hard-code it or something.

0:20:01.176,0:20:02.532
Then I made the documentation of it,

0:20:02.720,0:20:05.062
I split it into three sections,

0:20:05.467,0:20:07.548
in the information about the project,

0:20:07.769,0:20:09.074
general things,

0:20:09.249,0:20:11.204
what's the purpose, how it works, and

0:20:11.501,0:20:13.757
the second one is the contribution,

0:20:14.055,0:20:15.983
how can developers contribute

0:20:16.199,0:20:17.991
to it, and the third one

0:20:18.216,0:20:19.355
is about

0:20:19.481,0:20:20.960
the technical aspects, like

0:20:21.154,0:20:22.724
debugging, and cloning the repo for new

0:20:22.912,0:20:24.094
developers. So this is like

0:20:24.246,0:20:25.379
an example of it.

0:20:26.898,0:20:28.128
And for the future,

0:20:28.337,0:20:29.884
I plan to continue my

0:20:30.093,0:20:32.722
project, even after GSoC

0:20:32.961,0:20:34.961
the first thing I need to do

0:20:35.154,0:20:37.094
like, probably now, I am

0:20:37.259,0:20:38.392
going to put it in the

0:20:38.590,0:20:40.263
Mozilla Firefox market,

0:20:40.845,0:20:42.641
and later I can make it

0:20:42.894,0:20:44.774
for other browsers like Chromium

0:20:45.125,0:20:46.723
but we need to change the

0:20:46.987,0:20:49.052
API there, and I thought

0:20:49.293,0:20:51.309
the package could get in Debian, because

0:20:51.523,0:20:53.627
while I was here, I learnt about

0:20:53.928,0:20:55.508
packaging and

0:20:55.704,0:20:56.952
upstreaming and all that stuff, so

0:20:57.365,0:20:58.995
I think I am probably going to do that

0:20:59.200,0:21:00.599
but not for now, because I want

0:21:00.846,0:21:01.970
my users to be

0:21:02.194,0:21:05.215
like, all Internet users, not just

0:21:05.422,0:21:07.452
Debian operating system users.

0:21:08.259,0:21:09.802
Another thing is that I want

0:21:10.023,0:21:12.041
it to be integrated with other free

0:21:12.213,0:21:14.007
software services, like SUSI

0:21:14.227,0:21:16.567
artificial intelligence, and

0:21:16.812,0:21:18.036
Thunderbird in upstream

0:21:18.245,0:21:20.166
SUSI is a

0:21:20.406,0:21:22.919
speaking and texting artificial

0:21:23.115,0:21:24.740
intelligence that gives you responses

0:21:25.485,0:21:26.730
and I plan to use

0:21:26.938,0:21:28.688
that giving the suggestions

0:21:29.070,0:21:30.015
by speech.

0:21:30.695,0:21:32.613
On my extension,

0:21:32.806,0:21:35.397
with Thunderbird I felt it to be

0:21:35.593,0:21:36.899
like, to work

0:21:37.110,0:21:38.608
like in Mozilla, but, you know, when a

0:21:38.816,0:21:41.182
user gets an e-mail from a non-free side,

0:21:41.531,0:21:42.739
then it should

0:21:43.150,0:21:44.603
send a suggestion,

0:21:44.978,0:21:47.225
"use this, don't use this", like

0:21:47.406,0:21:49.002
I just basically explained,

0:21:49.290,0:21:51.414
and with upstream, I thought that

0:21:51.830,0:21:53.307
all my database should be

0:21:53.525,0:21:54.819
there, to put it there, and

0:21:55.153,0:21:57.625
it could help upstream, and it can

0:21:57.873,0:21:58.770
it could help me.

0:21:59.012,0:22:00.440
Here, I have my

0:22:00.623,0:22:03.417
experience with Debian, I heard about Debian

0:22:03.978,0:22:06.123
last year, in a girl's hackathon

0:22:06.649,0:22:07.673
and then later

0:22:07.852,0:22:09.527
in Tirana, in Albania, where

0:22:09.703,0:22:12.023
in a Debian bugs squashing party,

0:22:12.253,0:22:13.868
a DD was there, and

0:22:14.043,0:22:15.998
we planned on

0:22:16.216,0:22:17.539
-- sorry --

0:22:17.757,0:22:19.286
working a bit more than

0:22:19.464,0:22:21.734
With Daniel Pocock we had

0:22:21.984,0:22:22.811
we made...

0:22:23.094,0:22:25.979
A speech together, we gave under

0:22:26.220,0:22:28.004
in the biggest open source conference

0:22:28.209,0:22:29.941
in the whole Balkans, it was about

0:22:30.156,0:22:32.433
Free Software. And about my project,

0:22:32.643,0:22:34.085
I read a whole book to

0:22:34.343,0:22:36.204
understsand it a little bit more, to be

0:22:36.421,0:22:38.208
more prepared. And I want to

0:22:38.452,0:22:40.214
thank the Debian people for giving me this

0:22:40.465,0:22:42.302
opportunity to talk here, in front of you,

0:22:43.044,0:22:45.146
and I hope I'll be a DD soon.

0:22:45.629,0:22:46.819
Thank you!

0:23:53.127,0:23:54.648
So... Yeah, it's working.

0:23:56.114,0:23:58.344
So, before... My name is Elena

0:23:58.848,0:24:00.745
Elena Gjevukaj, and I come from Kosovo.

0:24:01.127,0:24:04.032
Before I start,

0:24:04.250,0:24:05.800
to present my project, I want to mention that

0:24:06.363,0:24:08.953
this year in the GSoC is the first time

0:24:09.216,0:24:10.916
that our country is participating.

0:24:11.615,0:24:13.926
It was funny, because even when we had

0:24:14.320,0:24:16.317
applied for the GSoC, we had

0:24:16.579,0:24:18.177
to ask Google to add

0:24:18.458,0:24:19.959
our country in the list, so

0:24:20.590,0:24:21.278
you know how...

0:24:22.394,0:24:24.486
We thought that we didn't

0:24:24.707,0:24:26.867
have any more opportunities

0:24:27.142,0:24:27.998
or any...

0:24:28.743,0:24:30.750
we just thought they aren't going to accept us.

0:24:31.326,0:24:32.761
But hopefully for us, we have

0:24:33.727,0:24:34.798
a great mentor,

0:24:35.106,0:24:37.424
Daniel Pocock, I think many of you

0:24:37.626,0:24:38.988
guys know him,

0:24:39.555,0:24:41.141
and he helped us

0:24:41.410,0:24:42.855
with everything that we needed

0:24:43.132,0:24:45.179
for all of the applications

0:24:45.947,0:24:47.133
and everything else.

0:24:48.373,0:24:49.891
So, going back to my project,

0:24:50.282,0:24:51.783
My project

0:24:51.978,0:24:53.571
is basically what I just said

0:24:54.005,0:24:55.731
right now. So, knowing that

0:24:55.990,0:24:57.689
newcomers to the open source have a lot

0:24:57.939,0:24:59.347
of problems to,

0:24:59.612,0:25:01.781
to just set up

0:25:02.005,0:25:03.566
a development environment

0:25:05.686,0:25:06.281
and

0:25:07.493,0:25:10.307
that's why we wanted

0:25:10.651,0:25:11.473
to create...

0:25:12.717,0:25:13.951
to create a GUI

0:25:14.941,0:25:17.529
so my project is a new contributor...

0:25:17.877,0:25:18.967
contributor wizard

0:25:19.278,0:25:21.061
and is basically a GUI that

0:25:21.341,0:25:23.286
could be distributed as a

0:25:23.513,0:25:24.659
package, and

0:25:24.961,0:25:26.696
to help the newcomer

0:25:27.077,0:25:28.607
to Debian and open source

0:25:29.467,0:25:30.504
to start their work

0:25:30.882,0:25:33.979
on the open source projects.

0:25:35.093,0:25:36.026
For example, if you want to

0:25:36.305,0:25:38.689
apply in GSoC or Outreachy

0:25:39.119,0:25:40.651
or other programs like this

0:25:41.078,0:25:42.778
you will need a lot of things

0:25:43.119,0:25:45.237
because if you are a new person,

0:25:45.457,0:25:47.277
you are newcoming to Debian, or

0:25:47.542,0:25:48.904
any other version of

0:25:49.112,0:25:50.592
Linux, you will have a lot of

0:25:50.861,0:25:52.719
problems to start up, so

0:25:53.033,0:25:54.830
what we want to do with this

0:25:55.153,0:25:57.006
is to help students

0:25:57.226,0:25:59.114
to run this computer

0:25:59.347,0:26:00.978
program in their desktop

0:26:01.204,0:26:02.882
and have to understand

0:26:03.103,0:26:04.834
everything that they need, for example

0:26:05.099,0:26:06.839
they will need for sure, how to use

0:26:07.058,0:26:08.620
IRC, they will need

0:26:08.870,0:26:11.405
basically a blog to explain

0:26:11.616,0:26:13.255
their work or add portfolio on it,

0:26:13.484,0:26:15.028
so they will need

0:26:15.203,0:26:17.208
a PGP or

0:26:17.582,0:26:18.886
other things like this

0:26:19.093,0:26:20.836
that we usually use in open source

0:26:21.141,0:26:22.931
so, my part of the project

0:26:23.337,0:26:24.032
in this

0:26:24.952,0:26:26.761
in this month of

0:26:26.971,0:26:28.390
the Google Summer of Code,

0:26:28.653,0:26:31.292
was the blog module,

0:26:31.553,0:26:32.886
basically, I created

0:26:33.147,0:26:34.486
a module that will

0:26:34.863,0:26:36.369
generate automatically

0:26:37.002,0:26:39.386
...build dynamic and static websites.

0:26:39.775,0:26:42.005
And the other part

0:26:42.217,0:26:43.779
of it was that I did a lot of

0:26:44.034,0:26:45.654
research on what students

0:26:45.964,0:26:46.973
need for...

0:26:47.320,0:26:50.015
and we should include in the research

0:26:52.041,0:26:54.074
Another thing that I want to

0:26:54.295,0:26:55.535
mention is that students

0:26:55.791,0:26:57.687
don't know that much...

0:26:57.928,0:27:02.153
They have problems using the terminal

0:27:02.494,0:27:03.648
or installing

0:27:04.063,0:27:06.810
programs when they have usually installed Debian,

0:27:07.031,0:27:08.678
I will make sure

0:27:08.933,0:27:12.634
add that type of tutorials, or

0:27:12.826,0:27:14.118
for example

0:27:14.406,0:27:15.656
description of something

0:27:15.862,0:27:17.400
that will help them, how

0:27:17.599,0:27:19.081
to proceed and apply, and

0:27:19.404,0:27:21.720
maybe be a successful applicant

0:27:21.974,0:27:23.682
for GSoC. So, that's it.

0:27:24.153,0:27:25.296
Thank you!

0:27:25.606,0:27:29.352
[ audience clapping ]

0:27:48.897,0:27:50.277
Hello everyone!

0:27:51.934,0:27:53.411
My name is Diellza Shabani

0:27:53.650,0:27:55.174
and I also come from Kosovo,

0:27:55.997,0:27:57.794
I am a student of Computer Science

0:27:58.246,0:27:59.197
and Engineering,

0:28:00.217,0:28:01.532
I'm finishing my studies

0:28:01.745,0:28:03.242
this year hopefully,

0:28:03.662,0:28:04.896
so I am also doing

0:28:05.153,0:28:06.707
a Google Summer of Code project,

0:28:07.188,0:28:09.057
I haven't prepared any slides,

0:28:09.669,0:28:11.627
because I

0:28:12.033,0:28:13.268
didn't see it necessary,

0:28:14.175,0:28:16.278
so, my project's name is

0:28:16.849,0:28:18.024
"Click to dial up from

0:28:18.204,0:28:19.532
Linux Desktop", and

0:28:19.761,0:28:21.380
my mentor is Thomas Levine,

0:28:22.356,0:28:23.521
he couldn't join us

0:28:24.502,0:28:25.922
at the conference this year,

0:28:26.532,0:28:28.086
so, what I have been

0:28:28.328,0:28:30.255
working on this project is that

0:28:32.951,0:28:34.104
we are three students

0:28:34.298,0:28:36.347
in this project, because it's really

0:28:36.522,0:28:37.952
a big thing, we started

0:28:38.196,0:28:40.512
working in this last year

0:28:40.744,0:28:41.909
in the [?] hackathon,

0:28:42.274,0:28:43.460
in [?],

0:28:44.500,0:28:45.896
we started doing the project

0:28:46.355,0:28:48.180
in Python first,

0:28:48.475,0:28:49.652
we did some

0:28:49.892,0:28:52.388
pop-ups and some really basic things,

0:28:53.282,0:28:54.055
...So,

0:28:54.352,0:28:56.531
we thought to continue that, but

0:28:56.767,0:28:58.459
now that the project is

0:28:58.677,0:29:00.674
bigger, and there are three students

0:29:00.907,0:29:02.561
doing this, it is separated

0:29:02.766,0:29:04.432
in two different things, and

0:29:05.177,0:29:06.402
the two other students

0:29:06.763,0:29:08.620
are doing something else,

0:29:09.332,0:29:10.698
and we plan to do

0:29:10.991,0:29:12.696
something like mobile

0:29:12.905,0:29:13.972
application,

0:29:15.282,0:29:17.449
but still haven't figured it out.

0:29:19.049,0:29:20.103
For the moment, we are

0:29:20.281,0:29:21.679
doing only a website,

0:29:21.977,0:29:23.703
a Web application,

0:29:23.940,0:29:25.033
and

0:29:26.129,0:29:27.563
we are working on

0:29:28.171,0:29:29.760
the existing projects

0:29:30.025,0:29:32.046
that Google Summer of Code students have

0:29:32.336,0:29:33.772
done before, like Omnitel

0:29:33.980,0:29:35.164
and Lumicall

0:29:35.926,0:29:37.804
I am basically working on them

0:29:38.156,0:29:39.852
and making changes, an doing

0:29:40.311,0:29:41.711
task classes

0:29:42.132,0:29:43.411
and methods, so...

0:29:43.937,0:29:45.577
After we finish that, I think

0:29:45.810,0:29:47.702
we will continue with the website, and

0:29:47.975,0:29:49.042
hopefully,

0:29:49.845,0:29:51.913
because the GSoC is really

0:29:52.095,0:29:53.542
coming to an end,

0:29:54.184,0:29:55.986
and we have not very much time

0:29:56.277,0:29:57.076
left. But...

0:29:57.430,0:29:59.693
After this, we will probably be working

0:29:59.962,0:30:01.078
in doing the mobile app.

0:30:01.381,0:30:03.420
However, this is

0:30:03.655,0:30:06.017
all I have to tell

0:30:06.368,0:30:08.179
right now about my project

0:30:08.634,0:30:11.418
the opportunity to be here and to

0:30:11.725,0:30:13.877
present for you guys.

0:30:14.229,0:30:15.056
Thank you.

0:30:15.463,0:30:18.726
[ audience clapping ]

0:30:35.318,0:30:37.257
OK, so... Can you hear me?

0:30:40.077,0:30:41.733
So, hi everyone!

0:30:43.513,0:30:45.961
I am not actually a Google Summer of Code student,

0:30:46.368,0:30:49.610
but I have been an Outreachy intern

0:30:50.140,0:30:51.657
around one year ago.

0:30:52.150,0:30:53.713
So, first

0:30:53.999,0:30:55.756
before continuing my

0:30:55.986,0:30:57.202
talk, I'd like to ask

0:30:57.652,0:30:59.483
how many of you are coming from

0:30:59.697,0:31:03.362
a social background, and has not [br]finished for computer science or

0:31:03.660,0:31:04.795
science-related?

0:31:07.046,0:31:08.006
OK, great.

0:31:08.213,0:31:10.482
So we got three other people

0:31:10.684,0:31:11.731
in the audience. So

0:31:11.916,0:31:13.496
I am Kristi Progri, and I am actually,

0:31:13.688,0:31:15.218
I finished my university for

0:31:15.741,0:31:17.919
international affairs and diplomacy

0:31:18.653,0:31:20.147
and in the beginning I thought

0:31:20.337,0:31:22.038
that this was exactly the school,

0:31:22.287,0:31:24.212
that I'd never ever find something

0:31:24.458,0:31:26.161
to do with my life,

0:31:26.445,0:31:28.284
but then, I thought that, OK,

0:31:28.572,0:31:29.906
probably it would be nice

0:31:30.162,0:31:31.887
if I could just merge it with

0:31:32.197,0:31:33.826
something that is tech-related,

0:31:34.081,0:31:35.958
and free software, since during that time

0:31:36.160,0:31:37.830
I was also part of the

0:31:38.055,0:31:39.159
free software community

0:31:39.352,0:31:41.883
I ended up in the end having a diploma

0:31:42.082,0:31:43.867
thesis for on-line diplomacy,

0:31:44.278,0:31:45.584
and this was

0:31:45.852,0:31:48.043
what kind of opened

0:31:48.134,0:31:49.752
the doors further to

0:31:49.956,0:31:51.820
continue, and to get

0:31:52.309,0:31:53.285
to know more

0:31:54.077,0:31:55.838
for political and Internet.

0:31:56.524,0:31:58.382
So, I applied

0:31:58.600,0:31:59.433
in Mozilla

0:32:00.025,0:32:01.484
in a team for taking part

0:32:01.756,0:32:03.812
in the Outreachy, working with the

0:32:04.027,0:32:05.709
diversity and inclusion team there,

0:32:05.932,0:32:07.485
building up the

0:32:07.701,0:32:09.222
strategy for conducting

0:32:09.574,0:32:11.330
first language interviews, since

0:32:11.789,0:32:14.296
one of the barriers that we had during

0:32:14.511,0:32:15.741
all this time was that

0:32:16.002,0:32:18.118
people coming from different...

0:32:18.375,0:32:19.517
different countries

0:32:19.740,0:32:21.327
and not speaking

0:32:21.797,0:32:23.920
everyone by default English, so

0:32:24.180,0:32:25.896
trying to have a strategy

0:32:26.155,0:32:27.657
on how to conduct the language...

0:32:28.082,0:32:29.666
On how to conduct interviews, and

0:32:29.968,0:32:31.672
to grow up communities in the local

0:32:31.989,0:32:33.474
aspect, to really help to

0:32:33.704,0:32:35.536
take further steps to

0:32:35.966,0:32:37.768
all the free software initiatives, and

0:32:38.188,0:32:39.789
everything that's regarding to that.

0:32:40.832,0:32:41.672
So

0:32:41.892,0:32:43.064
this was

0:32:43.662,0:32:45.418
kind of the aspect from the field

0:32:45.735,0:32:47.362
doing on the Outreachy. For those

0:32:47.610,0:32:49.585
who don't know Outreachy, it's

0:32:49.878,0:32:52.039
exactly... It is an intership that

0:32:52.260,0:32:53.820
that lasts for three months,

0:32:53.986,0:32:55.633
it happens twice per year,

0:32:57.265,0:32:57.846
it has

0:32:58.033,0:32:59.744
kind of the same ideology

0:33:00.020,0:33:01.501
as the Google Summer of Code, but

0:33:01.760,0:33:03.752
it's also for people that

0:33:03.954,0:33:05.468
are not students but have

0:33:06.228,0:33:07.448
finished their

0:33:07.793,0:33:08.804
studies.

0:33:09.405,0:33:11.627
and besides Outreachy and

0:33:12.005,0:33:13.534
the Google Summer of Code, there also

0:33:13.827,0:33:15.320
are initiatives that

0:33:15.926,0:33:17.548
help out students

0:33:17.939,0:33:19.760
to continue and

0:33:20.007,0:33:21.575
getting on more knowledge regarding

0:33:21.776,0:33:23.208
the free software, such as

0:33:23.408,0:33:25.495
Rails' Girls Summer of Code,

0:33:25.928,0:33:27.826
I don't know if you have heard about that, it is

0:33:28.018,0:33:29.967
an internship happening on the

0:33:30.362,0:33:31.770
during the summer, it lasts

0:33:32.170,0:33:34.588
for three months,

0:33:35.402,0:33:36.622
three months I think,

0:33:36.913,0:33:37.929
and it's actually

0:33:38.138,0:33:39.676
only regarding coding. But

0:33:39.987,0:33:41.914
until now, I think, for as far

0:33:42.117,0:33:44.241
as I know, Outreachy is the only one

0:33:44.446,0:33:45.209
that can,

0:33:45.413,0:33:48.267
that requires also people that do not have

0:33:48.478,0:33:49.499
technical

0:33:49.870,0:33:51.760
skills, or at least that have

0:33:52.045,0:33:53.665
not finished for it,

0:33:54.153,0:33:55.010
any technical

0:33:55.306,0:33:57.045
subject or degree.

0:33:57.684,0:33:59.635
So, this was also

0:33:59.837,0:34:01.905
my short presentation

0:34:02.059,0:34:03.398
to say, and the

0:34:03.627,0:34:05.902
last one I think for the session, so

0:34:06.149,0:34:08.349
there is anyone in the audience

0:34:08.582,0:34:10.045
who'd like to make a question, any

0:34:10.251,0:34:12.001
suggestion or comment, please feel free

0:34:12.170,0:34:14.190
and thank you very much for

0:34:14.329,0:34:15.294
being here.

0:34:16.126,0:34:19.017
[ audience clapping ]

0:34:37.899,0:34:40.337
[Delib:] Hello. Jaminy,

0:34:42.427,0:34:45.726
So many of us are so interested in the

0:34:46.123,0:34:48.011
the edges of Debian,

0:34:48.255,0:34:49.963
and who is coming, and are they[br]staying

0:34:50.797,0:34:51.855
and you have met

0:34:52.068,0:34:53.750
so many mentees,

0:34:53.890,0:34:55.708
and talked with so many mentors. Could you share

0:34:55.934,0:34:57.894
with us a little bit about

0:34:58.273,0:34:59.451
what is working well and

0:34:59.735,0:35:01.191
what might work a little better

0:35:01.968,0:35:02.838
in the future?

0:35:08.356,0:35:10.194
[Jaminy:] So, there are many newcomers

0:35:10.396,0:35:12.151
coming from Google Summer of Code,

0:35:12.566,0:35:13.892
I think the main thing

0:35:14.125,0:35:17.085
that actually happens is they should be

0:35:17.276,0:35:18.829
keep motivated and keep working on

0:35:18.991,0:35:20.173
after the Google Summer of Code,

0:35:20.581,0:35:22.743
I feel that would be one of the

0:35:22.947,0:35:24.297
major things they have to do

0:35:24.566,0:35:26.773
even after the Google Summer of Code

0:35:36.439,0:35:38.443
[Delib:] Do you have ideas of how

0:35:39.809,0:35:41.951
community members or the mentors

0:35:42.160,0:35:44.359
could do things differently, so that

0:35:44.727,0:35:46.616
they could stay more motivated?

0:35:47.751,0:35:49.230
Stay more interested?

0:35:51.630,0:35:54.197
[Jaminy:] I think the mentors, it's all about the communication,

0:35:54.514,0:35:56.443
I think they should keep communicating

0:35:56.740,0:35:58.435
with the students and keep them

0:35:58.822,0:36:00.263
giving suggestions

0:36:01.035,0:36:02.328
and advising

0:36:02.539,0:36:04.556
them, how can they improve further on

0:36:04.948,0:36:06.017
their projects,

0:36:06.458,0:36:08.245
and how they can keep moving

0:36:08.490,0:36:10.776
keep... Moving on

0:36:10.968,0:36:12.387
further with the project.

0:36:12.818,0:36:14.409
[Delib:] So, listening to what their interests are,

0:36:14.819,0:36:16.231
and giving them ideas on how to

0:36:16.378,0:36:17.414
pursue those interests?

0:36:17.619,0:36:18.423
[Jaminy:] Yes.

0:36:27.096,0:36:28.954
[Tassia:] I have a question: Is it

0:36:29.255,0:36:31.993
...I have the impression that I might be wrong, so

0:36:32.256,0:36:33.220
[Jaminy:] Do you have questions for me, or

0:36:33.421,0:36:34.771
for students? [Tassia:] For you.

0:36:35.152,0:36:37.129
[Jaminy:] OK.

0:36:37.799,0:36:39.761
[Tassia:] Sorry [both laugh]

0:36:40.235,0:36:41.419
But just, for

0:36:41.674,0:36:43.225
what I've been following, for

0:36:43.433,0:36:45.470
the past years, I thing that when students

0:36:45.622,0:36:47.152
enter work with a team

0:36:47.437,0:36:49.278
my impression is that it's easier

0:36:49.493,0:36:51.278
for them to continue working afterwards.

0:36:51.583,0:36:52.931
Is it

0:36:54.885,0:36:56.103
in comparison when

0:36:56.326,0:36:57.970
there are ad-hoc projects

0:36:58.677,0:37:00.101
that some times don't

0:37:00.534,0:37:02.324
continue being developed,

0:37:02.550,0:37:03.834
and I think,

0:37:04.497,0:37:06.858
then the motivation might probably...

0:37:07.294,0:37:09.452
Do you perceive it? Or

0:37:09.620,0:37:10.827
you don't think it makes sense?

0:37:11.116,0:37:12.761
[Jaminy:] Currently I'm not, but I hope

0:37:12.935,0:37:15.074
to continue after my...

0:37:15.251,0:37:17.223
Now I'm currently doing early career,

0:37:17.437,0:37:18.948
so I would prefer continuing

0:37:19.151,0:37:19.674
later.

0:37:21.312,0:37:23.444
[Tassia:] No, sorry, I think you didn't understand my question.

0:37:23.852,0:37:25.131
It was about the projects

0:37:25.321,0:37:26.502
within teams,

0:37:26.758,0:37:28.360
like, lets say, the students that work with

0:37:28.567,0:37:30.459
the Perl team, or that work inside

0:37:30.630,0:37:32.474
another team

0:37:33.051,0:37:34.575
in comparison with just

0:37:34.869,0:37:36.309
one mentor and one

0:37:36.566,0:37:37.464
mentee

0:37:39.769,0:37:40.404
and if that

0:37:40.667,0:37:42.235
reflects on the

0:37:42.492,0:37:44.911
motivation of the student to continue

0:37:45.170,0:37:46.642
doing work for Debian

0:37:47.308,0:37:49.166
afterwards. Do you thing there is

0:37:49.393,0:37:50.670
a relation, or not?

0:37:51.908,0:37:53.776
[Jaminy:] Yes, I think there

0:37:53.946,0:37:55.185
is, I mean, the

0:37:55.336,0:37:56.975
mentor-mentee relations keeps

0:37:57.141,0:37:58.838
going on?

0:37:59.954,0:38:02.066
Eventually they get your question probably?

0:38:06.619,0:38:08.629
[Delib:] Do you think it's easier for students

0:38:08.854,0:38:10.699
to be part of a team, instead of

0:38:10.877,0:38:12.081
just one mentor?

0:38:13.315,0:38:14.768
[Jaminy:] Yes, I think they

0:38:14.941,0:38:16.819
get valious knowledge, so it's better to

0:38:17.021,0:38:18.063
be in a team

0:38:18.389,0:38:20.392
than sticking to one mentor.

0:38:21.731,0:38:22.987
[Andreas:] Do we have some

0:38:23.192,0:38:24.680
statistics? How many of

0:38:24.891,0:38:26.843
the students have entered Debian?

0:38:27.011,0:38:28.751
or not? Because I have had three

0:38:28.922,0:38:30.983
GSoC students, and three Outreachy

0:38:31.258,0:38:32.632
students, and

0:38:32.838,0:38:34.229
none of them

0:38:34.488,0:38:36.805
really remained there. They are intererested,

0:38:37.035,0:38:38.453
they are using Debian, but

0:38:38.669,0:38:39.872
my experience

0:38:40.130,0:38:42.803
or the result of my experience

0:38:42.985,0:38:44.729
was that I tried to give them tasks

0:38:45.104,0:38:46.691
which are easy to end,

0:38:46.993,0:38:48.528
which are small tasks,

0:38:48.715,0:38:50.727
and if they go, then that's not

0:38:50.930,0:38:53.094
... How many people stayed in Debian?

0:38:55.095,0:38:56.693
[Jaminy:] You mean...

0:38:58.681,0:38:59.933
You mean, from the past?

0:39:00.896,0:39:03.040
[Andreas:] How many people stayed in Debian?

0:39:03.346,0:39:04.723
of the students?

0:39:05.147,0:39:06.468
From the past, yes.

0:39:10.315,0:39:12.190
[?:] I think you can answer

0:39:12.453,0:39:14.258
after the session, because

0:39:14.483,0:39:15.858
we run out of time.

0:39:16.066,0:39:18.392
[Jaminy:] OK. I'd like to take this opportunity

0:39:18.576,0:39:19.940
to thank all the mentors

0:39:20.144,0:39:21.573
who made this program successful.

0:39:21.738,0:39:23.268
And you can feel free to talk to students

0:39:23.477,0:39:24.985
after the session, and give them

0:39:25.143,0:39:26.939
suggestions or feedback.

0:39:27.350,0:39:28.190
Thank you!

0:39:28.381,0:39:30.500
[ Audience clapping ]