< Return to Video

https:/.../gsoc-session.webm

  • 0:06 - 0:09
    Thank you for coming with us! So...
  • 0:11 - 0:14
    All right. How many have heard about the Google
    Summer of Code?
  • 0:14 - 0:19
    Already, if you are not aware, I could be
    introducing more about what is it and
  • 0:20 - 0:24
    and then talk more about what we are going
    to do in the session
  • 0:25 - 0:27
    So, can you raise the hand
  • 0:28 - 0:31
    if you are already aware of the Google Summer of Code?
  • 0:34 - 0:35
    OK!
  • 0:37 - 0:39
    Thank you - I think most of you are aware,
  • 0:39 - 0:41
    it's bringing the student developers
  • 0:41 - 0:43
    into the open source community, it's all about that
  • 0:44 - 0:47
    So, the session is going to be
  • 0:48 - 0:50
    mostly the students introducing their projects
  • 0:50 - 0:53
    and getting the feedback, and discussing with their mentors.
  • 0:54 - 0:57
    If they are getting any questions from IRC, they can discuss
  • 0:58 - 1:00
    How they can improve the project in their
  • 1:00 - 1:02
    ...Their ongoing projects.
  • 1:04 - 1:07
    OK. so let me introduce about myself. I am Jaminy,
  • 1:09 - 1:10
    So, I come from Sri Lanka
  • 1:11 - 1:15
    I am one of the coordinators for
    Google Summer of Code with Debian
  • 1:17 - 1:20
    So, Debian has been participating in the Google Summer of Code
  • 1:21 - 1:22
    from 2005, and
  • 1:23 - 1:25
    it has been 13 years it has been participating,
  • 1:26 - 1:28
    and we had a break in 2017
  • 1:28 - 1:32
    and now we are back in 2018 with Google Summer of Code
  • 1:34 - 1:37
    and these are the teams for GSoC coordination
  • 1:37 - 1:39
    I am representing the team
  • 1:39 - 1:43
    Daniel Pocock, Alexander, and it's me
  • 1:45 - 1:48
    This year, we have accepted 25 students
  • 1:50 - 1:51
    And that's the link for the projects
  • 1:53 - 1:54
    that are ongoing this year
  • 2:00 - 2:04
    So, there is an interesting GSoC statistic this year
  • 2:04 - 2:06
    this year we have selected
  • 2:07 - 2:09
    I mean, this was from the Google Open Source blog,
  • 2:10 - 2:13
    and they said there are three students
  • 2:14 - 2:15
    Four students accepted from Kosovo
  • 2:16 - 2:17
    And...
  • 2:18 - 2:21
    The three students are from our Debian community, and they are here joining us
  • 2:22 - 2:23
    joining with us,
  • 2:24 - 2:25
    to introduce more about their project
  • 2:26 - 2:28
    I hope that, without wasting more time,
  • 2:29 - 2:31
    I could give the chance for the students to introduce,
  • 2:32 - 2:34
    to talk more about their projects.
  • 2:35 - 2:36
    Arthur, can you...
  • 2:39 - 2:42
    [ audience clapping ]
  • 2:52 - 2:54
    So, you hear me? OK?
  • 2:56 - 2:57
    Yes? Nice.
  • 2:59 - 3:00
    So...
  • 3:01 - 3:03
    Hello, my name is Arthur del Esposto
  • 3:04 - 3:05
    I am going to talk about my GSoC project
  • 3:06 - 3:09
    that is titled "Improving Distro Tracker to better support Debian teams"
  • 3:09 - 3:12
    My mentor is Lucas Kanashiro and my co-mentor is Raphael Hertzog.
  • 3:15 - 3:17
    I will provide you some context about why we are doing this.
  • 3:18 - 3:19
    So, basically,
  • 3:19 - 3:23
    Debian teams used to rely on Packages Entropy Tracker
  • 3:23 - 3:25
    with the assistance that basically got some information about
  • 3:27 - 3:29
    the package from Debian, from Alioth,
  • 3:30 - 3:32
    and display some kind of information
  • 3:32 - 3:35
    inside tables and some categories.
  • 3:38 - 3:41
    And we also had inside our Debian infrastructure
  • 3:42 - 3:44
    the tracker.debian.org, which you probably have used before,
  • 3:45 - 3:49
    that basically gathers the same sort of information from several sources inside Debian
  • 3:50 - 3:54
    and puts this in a Web application.
  • 3:55 - 3:56
    So, for example, you have the base
  • 3:57 - 3:58
    of a specific package, the Web defaults,
  • 3:59 - 4:01
    and you can get all the information related to that package.
  • 4:02 - 4:04
    And what we want to do, because...
  • 4:05 - 4:08
    that has not been maintained anymore
  • 4:08 - 4:10
    and also, he used to track the
  • 4:11 - 4:13
    package repository from Alioth.
  • 4:13 - 4:15
    And what we really want to do
  • 4:16 - 4:20
    is just continuing to support Debian teams
    to track the health of the packages and to
  • 4:20 - 4:22
    and to prioritize their work efforts
  • 4:22 - 4:23
    by migrating the PET features
  • 4:23 - 4:25
    to Distro Tracker, and also
  • 4:25 - 4:28
    we want to track Salsa repositories instead of Alioth.
  • 4:29 - 4:31
    So, what are the results we have so far?
  • 4:32 - 4:33
    So, basically...
  • 4:33 - 4:34
    if you enter a team page,
  • 4:35 - 4:36
    of anything inside Distro Tracker
  • 4:36 - 4:38
    you are going to get this kind of table
  • 4:39 - 4:40
    so basically you have the first column
  • 4:41 - 4:42
    with the package name
  • 4:42 - 4:44
    the second column with the changelog version
  • 4:45 - 4:46
    and the VCS of that package,
  • 4:46 - 4:48
    the third column with the archive version,
  • 4:49 - 4:51
    we also are tracking the bugs here
  • 4:51 - 4:52
    and the last column
  • 4:53 - 4:55
    has the upstream version.
  • 4:55 - 4:57
    OK, of this package.
  • 4:57 - 5:00
    And, another interesting feature
  • 5:00 - 5:02
    that we are providing you is that if
  • 5:03 - 5:04
    you pass the mouse over
  • 5:04 - 5:06
    one of those fields, you are going to get
  • 5:06 - 5:08
    more detailed information about that specific field.
  • 5:09 - 5:11
    OK, so for example here we have
  • 5:12 - 5:14
    the information links to BTS
  • 5:14 - 5:16
    related to the bugs
  • 5:16 - 5:18
    that exist for the package.
  • 5:20 - 5:23
    We also provide some categories
  • 5:23 - 5:25
    so basically we could have
  • 5:25 - 5:27
    more than one category of package tables
  • 5:28 - 5:29
    for example, you could have like
  • 5:30 - 5:31
    packages with RC bugs,
  • 5:31 - 5:33
    packages that have a new version
  • 5:33 - 5:35
    in the upstream, and we have
  • 5:35 - 5:37
    specific pages where each of these
  • 5:37 - 5:39
    package tables. OK?
  • 5:40 - 5:41
    And we have
  • 5:41 - 5:43
    a large number of teams
  • 5:43 - 5:47
    inside Debian, inside this specifically
    inside the Distro Tracker,
  • 5:47 - 5:48
    so we also provide this
  • 5:50 - 5:51
    autocomplete text field
  • 5:52 - 5:53
    so you can easily find
  • 5:53 - 5:56
    your team, the team that you are interested in.
  • 5:58 - 5:58
    And...
  • 5:59 - 6:02
    that was my resource, and so far we have
  • 6:02 - 6:03
    faced some challenges,
  • 6:04 - 6:06
    first is that Distro Tracker
  • 6:06 - 6:08
    has a generic purpose architecture
  • 6:08 - 6:10
    because it should be used by several
  • 6:11 - 6:13
    distros, so it's also being
  • 6:13 - 6:15
    used by the Kali community, so basically
  • 6:15 - 6:18
    everything you are going to do you have
    to make it extensible, have to design it
  • 6:19 - 6:21
    to be extensible by this specific application
  • 6:21 - 6:23
    that implements that specific features from
  • 6:24 - 6:25
    their distros.
  • 6:26 - 6:28
    Also, the database design is challenging, because
  • 6:29 - 6:32
    we have to collect all this data from several
  • 6:33 - 6:34
    database tables
  • 6:37 - 6:38
    and some of these
  • 6:38 - 6:41
    context is realized in JSON fields inside the database
  • 6:42 - 6:43
    so it's not easy to get these. And also,
  • 6:44 - 6:45
    we have faced some problems,
  • 6:45 - 6:47
    some performance problems, because we are
  • 6:48 - 6:50
    we are handling a large number of table cells
  • 6:50 - 6:51
    dynamically, so basically we are building
  • 6:52 - 6:53
    it of these table cells
  • 6:54 - 6:55
    in run time.
  • 6:58 - 7:01
    And, until the end of GSoC, I plan to
  • 7:01 - 7:03
    create a cache mechanism, I am already
  • 7:03 - 7:05
    working on that, proposed a merge request on it,
  • 7:05 - 7:07
    to try to improve the performance of
  • 7:07 - 7:08
    table rendering
  • 7:10 - 7:11
    I also want to have all my
  • 7:11 - 7:15
    merge requests accepted
  • 7:15 - 7:16
    inside Salsa
  • 7:17 - 7:19
    We also want to provide more
  • 7:19 - 7:21
    package tables with new categories
  • 7:22 - 7:24
    and also provide a new feature that
  • 7:25 - 7:26
    you could be able to sort the team
  • 7:27 - 7:29
    for content based on columns, for example
  • 7:29 - 7:30
    I want to sort my
  • 7:32 - 7:33
    my table based on
  • 7:33 - 7:34
    on the number of bugs, for example.
  • 7:36 - 7:38
    And there is also that we
  • 7:38 - 7:40
    got good results so far, and
  • 7:40 - 7:43
    I have received valuable feedback from the Debian community
  • 7:43 - 7:45
    and I have a lot of ideas to continue
  • 7:45 - 7:47
    working on this after the GSoC as well
  • 7:48 - 7:49
    The GSoC has been
  • 7:49 - 7:51
    an amazing experience, I have been learning a lot,
  • 7:51 - 7:54
    which Kanashiro has had to log all the
    community members
  • 7:55 - 7:57
    I look into contributing to Debian
  • 7:57 - 7:58
    of course
  • 7:58 - 8:02
    Thank you to the Debian community to
  • 8:02 - 8:04
    provide me this opportunity to come here to DebConf
  • 8:05 - 8:06
    to present my work.
  • 8:06 - 8:09
    Lets get moving on, and thanks.
  • 8:09 - 8:13
    [ audience clapping ]
  • 8:31 - 8:33
    So, my project is called
  • 8:33 - 8:35
    "Port Kali Packages to Debian"
  • 8:36 - 8:40
    and my mentors are Raphaël Hertzog
    and Gianfranco Costamagna.
  • 8:40 - 8:43
    Unfortunately, they didn't come to
  • 8:43 - 8:44
    this year's DebConf, and
  • 8:47 - 8:49
    we are from the pkg-security
  • 8:49 - 8:51
    tools packaging team, so this is
  • 8:51 - 8:53
    something I have been working on
  • 8:53 - 8:56
    for the past one year and a half
  • 8:56 - 8:59
    I think I started packaging
  • 8:59 - 9:00
    on 2016
  • 9:00 - 9:02
    and in 2017 I started
  • 9:02 - 9:04
    working on the security tools packaging
  • 9:04 - 9:06
    because this is something that really
  • 9:06 - 9:07
    interests me, so
  • 9:08 - 9:09
    What actually is Kali Linux?
  • 9:10 - 9:14
    Kali Linux is a digital
    forensics and pentesting distribution
  • 9:14 - 9:16
    that has like lots of packages
  • 9:16 - 9:17
    is by far
  • 9:18 - 9:20
    the most used distribution
  • 9:20 - 9:22
    for "capture-the-flag" competitions
  • 9:23 - 9:24
    and is based on unstable
  • 9:25 - 9:27
    and the thing is that Kali has
  • 9:27 - 9:29
    a more relaxed policy
  • 9:29 - 9:31
    than Debian's, so that's the reason
  • 9:31 - 9:32
    of the
  • 9:33 - 9:34
    differences between the packages
  • 9:35 - 9:39
    I mean, the packages that Kali has and Debian hasn't
  • 9:39 - 9:40
    so, at first
  • 9:40 - 9:42
    I did gather some information about
  • 9:43 - 9:44
    what packages can I work on
  • 9:45 - 9:46
    and what are the problems
  • 9:46 - 9:48
    that it should rather get them on Main
  • 9:49 - 9:50
    So, I first started using
  • 9:51 - 9:53
    this dashboard from Kali Linux, and they have
  • 9:53 - 9:58
    also used the tracker system that we
    use on Debian
  • 9:58 - 9:59
    and this is a special dashboard
  • 9:59 - 10:01
    where we can see how many
  • 10:01 - 10:03
    packages are on Kali Linux that
  • 10:03 - 10:04
    aren't on Debian
  • 10:05 - 10:07
    at the time, and this is for today, so there are
  • 10:07 - 10:09
    477 packages
  • 10:09 - 10:11
    but this includes dependencies
  • 10:11 - 10:13
    and lots of packages are not
  • 10:13 - 10:15
    that really important, and
  • 10:15 - 10:19
    some of them are not installed by default on Kali
  • 10:19 - 10:20
    So, the first thing,
  • 10:21 - 10:22
    I already knew some packages that
  • 10:22 - 10:24
    I really would like to see on Debian, and
  • 10:24 - 10:26
    the first one was Metasploit
  • 10:26 - 10:28
    because it's one of the most used
  • 10:28 - 10:29
    frameworks for pentesting
  • 10:30 - 10:32
    I have started by looking at
  • 10:32 - 10:34
    what should I do
  • 10:35 - 10:36
    and it was a really tough job
  • 10:36 - 10:38
    because Metasploit is currently
  • 10:38 - 10:40
    bundling all their gem dependencies
  • 10:41 - 10:42
    Because of, this is a huge problem
  • 10:43 - 10:44
    there was a big discussion
  • 10:44 - 10:45
    n the Debian mailing lists about that,
  • 10:45 - 10:47
    but whatever, I use repology
  • 10:48 - 10:49
    in order to see what distros
  • 10:50 - 10:51
    were already packaging this stuff
  • 10:52 - 10:53
    and at the end, there should
  • 10:54 - 10:55
    be around 40 packages
  • 10:56 - 10:58
    that I had to package in order
  • 10:58 - 10:59
    to see if it would work, because
  • 11:00 - 11:01
    you have the version problem, because
  • 11:01 - 11:03
    bundling the distro version, and
  • 11:03 - 11:06
    we decided not to do that
  • 11:06 - 11:08
    during this project, so I
  • 11:08 - 11:10
    had to look for other packages
  • 11:10 - 11:12
    and I didn't want to
  • 11:12 - 11:14
    do this manually, so I
  • 11:14 - 11:15
    developed a
  • 11:16 - 11:17
    kind of big shell script
  • 11:18 - 11:19
    it shouldn't be a shell script, it should be in
  • 11:19 - 11:21
    a programming language, but
  • 11:21 - 11:23
    got big worked on, and to this
  • 11:24 - 11:25
    scripts I give
  • 11:25 - 11:27
    I input it a list of packages, and it
  • 11:27 - 11:28
    cloned all the Kali
  • 11:29 - 11:31
    Git repositories for this package,
  • 11:31 - 11:33
    build each one of them, and did
  • 11:33 - 11:35
    some basic checks, like if
  • 11:35 - 11:36
    it is a default
  • 11:37 - 11:38
    Kali package, if it's
  • 11:39 - 11:41
    buildable, because some of the packages
  • 11:42 - 11:44
    are not buildable because we don't have
  • 11:44 - 11:45
    the build dependencies in Debian right now,
  • 11:45 - 11:48
    it checks if it is DEP5 compliant already,
  • 11:48 - 11:49
    if we need manpages, if we need
  • 11:50 - 11:51
    hardening, if
  • 11:51 - 11:53
    it is bundling some gems, and if
  • 11:53 - 11:56
    there are [?], there is about
  • 11:56 - 11:58
    twenty or thirty something
  • 11:58 - 11:59
    columns on here
  • 12:00 - 12:02
    so you have lots of info
  • 12:02 - 12:03
    and in order to know
  • 12:04 - 12:06
    which are the most important issues
  • 12:06 - 12:08
    Raphaël gave me the idea to
  • 12:08 - 12:10
    look for the number of uploads that
  • 12:11 - 12:12
    the package had since
  • 12:13 - 12:14
    it hit Kali, so I
  • 12:14 - 12:15
    can only
  • 12:16 - 12:18
    just sort for the number of uploads
  • 12:18 - 12:20
    and I have the most important ones.
  • 12:20 - 12:22
    This made the process
  • 12:22 - 12:25
    really easy, like a lot more
  • 12:25 - 12:26
    easy, and I
  • 12:26 - 12:28
    am publishing this on our team's
  • 12:29 - 12:30
    wiki page, and I will keep using this
  • 12:31 - 12:32
    like, forever
  • 12:33 - 12:35
    because it really helps other people that
  • 12:35 - 12:37
    want to contribute to our team, and
  • 12:39 - 12:41
    this is another software
  • 12:41 - 12:43
    that I tried, how many time do I have?
  • 12:44 - 12:45
    OK
  • 12:45 - 12:47
    another package that I really want to
  • 12:47 - 12:49
    see on Debian is zaproxy, and
  • 12:49 - 12:51
    for zaproxy,
  • 12:51 - 12:53
    I had to do a manual checking, because it is
  • 12:53 - 12:54
    a Java program, and
  • 12:55 - 12:58
    Java has... I really don't like Java, so
  • 12:58 - 13:00
    they bundle like
  • 13:00 - 13:02
    ...zaproxy is great software, but
  • 13:03 - 13:04
    they bundle some
  • 13:05 - 13:06
    libraries, and I
  • 13:06 - 13:08
    talked to upstream, and they are very
  • 13:09 - 13:10
    receptive, and they
  • 13:10 - 13:12
    want to help us, but
  • 13:13 - 13:15
    I didn't manage to package it yet,
  • 13:15 - 13:17
    I think I will do it after GSoC
  • 13:18 - 13:19
    but there are
  • 13:19 - 13:22
    some packages that we need to introduce
  • 13:22 - 13:23
    on Debian. Some of the packages that zaproxy
  • 13:24 - 13:25
    upstream is thinking about
  • 13:26 - 13:28
    dropping them, and putting just
    on the extensions, because
  • 13:29 - 13:34
    the core doesn't need them
    and some of the packages are old
  • 13:35 - 13:36
    and stuff like that, we have
  • 13:37 - 13:39
    there is a lot of problems
    that you can have
  • 13:40 - 13:41
    like... there was a
  • 13:41 - 13:44
    package which was GPL licensed
  • 13:44 - 13:45
    but it was linking against
  • 13:46 - 13:48
    OpenSSL, and in order
  • 13:48 - 13:50
    to do that, you have to either add
  • 13:50 - 13:51
    a license exception to your license
  • 13:52 - 13:54
    And I talked to upstream, and
  • 13:54 - 13:56
    it cooperative upstream,
  • 13:57 - 13:58
    it is a software which is used
  • 13:59 - 14:00
    to break
  • 14:00 - 14:01
    WiFi password,
  • 14:01 - 14:03
    like, doing offline cracking
  • 14:04 - 14:06
    and upsream decided to change its license
  • 14:06 - 14:08
    to BSD license
  • 14:08 - 14:09
    so we could release that on Debian. I
  • 14:10 - 14:12
    can't remember right now if it's on the NEW queue
  • 14:12 - 14:14
    or if it already hit
  • 14:14 - 14:16
    unstable, but I think is on the NEW queue.
  • 14:18 - 14:19
    So, in the end,
  • 14:21 - 14:22
    the results are, I made the script,
  • 14:22 - 14:24
    which is going to be used by
  • 14:25 - 14:26
    some time. There are some
  • 14:26 - 14:27
    fixes that can be
  • 14:29 - 14:32
    We have to do on the script to
    make it better
  • 14:32 - 14:34
    to make the checking better, because
  • 14:34 - 14:35
    we still have some corner cases where
  • 14:35 - 14:37
    it doesn't work really well,
  • 14:38 - 14:39
    we got some new packages in Debian,
  • 14:40 - 14:41
    which is really good. I have to
  • 14:41 - 14:44
    make some upstream contributions, because
  • 14:44 - 14:46
    for some packages I wrote
  • 14:46 - 14:48
    their manpage, and I sent it
  • 14:48 - 14:50
    to upstream, there was this
  • 14:50 - 14:52
    company of software that
  • 14:52 - 14:54
    changed its licensing to be like
  • 14:54 - 14:56
    correctly compliant with
  • 14:56 - 14:58
    OpenSSL license, and
  • 14:59 - 15:00
    and we got now a better
  • 15:00 - 15:02
    Kali and Debian for its users, because
  • 15:02 - 15:04
    when a package is just
  • 15:04 - 15:06
    in Kali, they don't like
  • 15:07 - 15:08
    to do hardening,
  • 15:08 - 15:10
    that's one example of things that
  • 15:10 - 15:13
    gets better when the package hits Debian
  • 15:13 - 15:16
    because when we enable hardening
  • 15:17 - 15:19
    sometimes we see problems that makes
    the package to
  • 15:19 - 15:22
    fail to build, and then we fix that,
  • 15:22 - 15:24
    upload to Debian, and when the package hits
  • 15:24 - 15:26
    unstable, Kali starts
  • 15:26 - 15:29
    taking this package from Debian, and
  • 15:29 - 15:30
    they can use our infrastructure
  • 15:31 - 15:32
    to do some QA
  • 15:32 - 15:35
    and stuff like that, and they
  • 15:35 - 15:37
    there are two people from Kali that I know at least,
  • 15:37 - 15:38
    Raphaël and Sophie, and they work
  • 15:39 - 15:41
    on Debian also, on our team, so
  • 15:41 - 15:43
    when there's a new release, they upload
  • 15:43 - 15:44
    the release on Debian,
  • 15:45 - 15:47
    so Debian users win
  • 15:47 - 15:49
    by that also, and
  • 15:49 - 15:51
    they already did lots of work
  • 15:51 - 15:52
    on their packages, so
  • 15:53 - 15:55
    yes, I think that's
  • 15:56 - 15:58
    the summary of the results
  • 16:00 - 16:00
    Thank you.
  • 16:01 - 16:04
    [ audience clapping ]
  • 16:32 - 16:33
    Hello, I am Enkelena Haxhiu
  • 16:33 - 16:35
    I am from the Republic of Kosovo, and
  • 16:36 - 16:38
    I am here to represent my Google Summer of Code
  • 16:40 - 16:41
    project. My mentors are
  • 16:41 - 16:42
    Bruno Milena and Gabriela.
  • 16:43 - 16:44
    So, my project is
  • 16:45 - 16:46
    a Mozilla Firefox
  • 16:46 - 16:48
    web extension to
  • 16:48 - 16:50
    give free and...
  • 16:50 - 16:52
    to give free software alternatives
  • 16:53 - 16:54
    to the apps on the Internet, so to have
  • 16:55 - 16:56
    avoiding non-free
  • 16:57 - 16:59
    apps and sites.
  • 16:59 - 17:01
    So, the goals for this project
  • 17:02 - 17:03
    were that
  • 17:03 - 17:05
    while the user is surfing
  • 17:05 - 17:07
    on the Internet, the moment that he
  • 17:07 - 17:08
    uses a non-free
  • 17:08 - 17:10
    software,
  • 17:10 - 17:13
    my extension will detect it
  • 17:13 - 17:15
    and then give an
  • 17:15 - 17:18
    alternative to it, a free software alternative.
  • 17:18 - 17:20
    The user should be able
  • 17:20 - 17:22
    to stop it when it's annoying,
  • 17:22 - 17:24
    and the notifications should be
  • 17:24 - 17:25
    only once per session,
  • 17:25 - 17:27
    and we wanted to have like a
  • 17:27 - 17:30
    database through self-hosted
  • 17:30 - 17:32
    API, or to use
  • 17:32 - 17:34
    a free software device
  • 17:34 - 17:36
    and then all this database
  • 17:36 - 17:37
    show it on our Web page.
  • 17:39 - 17:40
    I started by making
  • 17:42 - 17:44
    the user experience design,
  • 17:44 - 17:46
    based on that, because
  • 17:46 - 17:48
    should work like, should work fine,
  • 17:48 - 17:50
    I made some sketches and mockups
  • 17:50 - 17:52
    and then the persona
  • 17:52 - 17:54
    and then the finding the bad habits of apps,
  • 17:54 - 17:56
    like research, and
  • 17:56 - 17:58
    I started implementing it by
  • 17:59 - 18:00
    coding it, I used Mozilla
  • 18:00 - 18:02
    API to make my extension
  • 18:02 - 18:04
    communicate with the Web browser API
  • 18:05 - 18:06
    I created a
  • 18:07 - 18:08
    JSON data file, it's like
  • 18:09 - 18:10
    a proof of concept to just take
  • 18:11 - 18:12
    the data, because this is going to be
  • 18:13 - 18:14
    later in a real database.
  • 18:15 - 18:16
    So the code
  • 18:16 - 18:18
    logic, do
  • 18:18 - 18:20
    select and display the alternatives
  • 18:20 - 18:21
    based on the current
  • 18:22 - 18:24
    active website, is that
  • 18:24 - 18:26
    we should get the URL,
  • 18:26 - 18:28
    identify it by sending...
  • 18:29 - 18:30
    Identify it, and then to send
  • 18:30 - 18:32
    to that JSON file, check
  • 18:32 - 18:34
    and, based on
  • 18:34 - 18:36
    that, to give an alternative.
  • 18:36 - 18:38
    If it exists, of course. We did
  • 18:38 - 18:40
    We don't want to annoy the user
  • 18:41 - 18:42
    like, to show too much notifications
  • 18:43 - 18:44
    so we made it only once
  • 18:44 - 18:46
    per session for the current app,
  • 18:46 - 18:48
    and it has the ability to
  • 18:48 - 18:50
    stop and start it. We use the
  • 18:50 - 18:52
    local storage to hold the
  • 18:52 - 18:53
    user settings
  • 18:54 - 18:56
    and then we have to present this
  • 18:56 - 18:58
    free software list through
  • 18:58 - 19:00
    a web page that is generated by
  • 19:00 - 19:01
    that database.
  • 19:03 - 19:04
    This is like a simple diagram
  • 19:05 - 19:06
    of basically what I just said.
  • 19:08 - 19:10
    These are some screenshots with words
  • 19:11 - 19:12
    for example, Dropbox is a nonfree
  • 19:12 - 19:16
    software, and this is
  • 19:17 - 19:19
    the notification that it gets
  • 19:19 - 19:21
    it says, "Dropbox has open source alternatives
  • 19:21 - 19:23
    like seafile",
  • 19:24 - 19:25
    and then, I have here
  • 19:26 - 19:28
    the web page that it gets
  • 19:29 - 19:31
    the extension popup
  • 19:31 - 19:33
    and all these things. This is how it looks like.
  • 19:34 - 19:36
    And then, i made a project website
  • 19:37 - 19:39
    which holds all the data
  • 19:40 - 19:41
    I made the design of it and
  • 19:41 - 19:43
    the frontend and the data generation.
  • 19:43 - 19:45
    I plan to leave this open
  • 19:45 - 19:47
    so developers can add stuff there
  • 19:48 - 19:50
    to the database, and then
  • 19:50 - 19:52
    generates it, and
  • 19:52 - 19:54
    it goes, like, right away to the
  • 19:55 - 19:57
    to the project website.
  • 19:58 - 19:59
    I don't need to hard-code...
  • 20:00 - 20:01
    hard-code it or something.
  • 20:01 - 20:03
    Then I made the documentation of it,
  • 20:03 - 20:05
    I split it into three sections,
  • 20:05 - 20:08
    in the information about the project,
  • 20:08 - 20:09
    general things,
  • 20:09 - 20:11
    what's the purpose, how it works, and
  • 20:12 - 20:14
    the second one is the contribution,
  • 20:14 - 20:16
    how can developers contribute
  • 20:16 - 20:18
    to it, and the third one
  • 20:18 - 20:19
    is about
  • 20:19 - 20:21
    the technical aspects, like
  • 20:21 - 20:23
    debugging, and cloning the repo for new
  • 20:23 - 20:24
    developers. So this is like
  • 20:24 - 20:25
    an example of it.
  • 20:27 - 20:28
    And for the future,
  • 20:28 - 20:30
    I plan to continue my
  • 20:30 - 20:33
    project, even after GSoC
  • 20:33 - 20:35
    the first thing I need to do
  • 20:35 - 20:37
    like, probably now, I am
  • 20:37 - 20:38
    going to put it in the
  • 20:39 - 20:40
    Mozilla Firefox market,
  • 20:41 - 20:43
    and later I can make it
  • 20:43 - 20:45
    for other browsers like Chromium
  • 20:45 - 20:47
    but we need to change the
  • 20:47 - 20:49
    API there, and I thought
  • 20:49 - 20:51
    the package could get in Debian, because
  • 20:52 - 20:54
    while I was here, I learnt about
  • 20:54 - 20:56
    packaging and
  • 20:56 - 20:57
    upstreaming and all that stuff, so
  • 20:57 - 20:59
    I think I am probably going to do that
  • 20:59 - 21:01
    but not for now, because I want
  • 21:01 - 21:02
    my users to be
  • 21:02 - 21:05
    like, all Internet users, not just
  • 21:05 - 21:07
    Debian operating system users.
  • 21:08 - 21:10
    Another thing is that I want
  • 21:10 - 21:12
    it to be integrated with other free
  • 21:12 - 21:14
    software services, like SUSI
  • 21:14 - 21:17
    artificial intelligence, and
  • 21:17 - 21:18
    Thunderbird in upstream
  • 21:18 - 21:20
    SUSI is a
  • 21:20 - 21:23
    speaking and texting artificial
  • 21:23 - 21:25
    intelligence that gives you responses
  • 21:25 - 21:27
    and I plan to use
  • 21:27 - 21:29
    that giving the suggestions
  • 21:29 - 21:30
    by speech.
  • 21:31 - 21:33
    On my extension,
  • 21:33 - 21:35
    with Thunderbird I felt it to be
  • 21:36 - 21:37
    like, to work
  • 21:37 - 21:39
    like in Mozilla, but, you know, when a
  • 21:39 - 21:41
    user gets an e-mail from a non-free side,
  • 21:42 - 21:43
    then it should
  • 21:43 - 21:45
    send a suggestion,
  • 21:45 - 21:47
    "use this, don't use this", like
  • 21:47 - 21:49
    I just basically explained,
  • 21:49 - 21:51
    and with upstream, I thought that
  • 21:52 - 21:53
    all my database should be
  • 21:54 - 21:55
    there, to put it there, and
  • 21:55 - 21:58
    it could help upstream, and it can
  • 21:58 - 21:59
    it could help me.
  • 21:59 - 22:00
    Here, I have my
  • 22:01 - 22:03
    experience with Debian, I heard about Debian
  • 22:04 - 22:06
    last year, in a girl's hackathon
  • 22:07 - 22:08
    and then later
  • 22:08 - 22:10
    in Tirana, in Albania, where
  • 22:10 - 22:12
    in a Debian bugs squashing party,
  • 22:12 - 22:14
    a DD was there, and
  • 22:14 - 22:16
    we planned on
  • 22:16 - 22:18
    -- sorry --
  • 22:18 - 22:19
    working a bit more than
  • 22:19 - 22:22
    With Daniel Pocock we had
  • 22:22 - 22:23
    we made...
  • 22:23 - 22:26
    A speech together, we gave under
  • 22:26 - 22:28
    in the biggest open source conference
  • 22:28 - 22:30
    in the whole Balkans, it was about
  • 22:30 - 22:32
    Free Software. And about my project,
  • 22:33 - 22:34
    I read a whole book to
  • 22:34 - 22:36
    understsand it a little bit more, to be
  • 22:36 - 22:38
    more prepared. And I want to
  • 22:38 - 22:40
    thank the Debian people for giving me this
  • 22:40 - 22:42
    opportunity to talk here, in front of you,
  • 22:43 - 22:45
    and I hope I'll be a DD soon.
  • 22:46 - 22:47
    Thank you!
  • 23:53 - 23:55
    So... Yeah, it's working.
  • 23:56 - 23:58
    So, before... My name is Elena
  • 23:59 - 24:01
    Elena Gjevukaj, and I come from Kosovo.
  • 24:01 - 24:04
    Before I start,
  • 24:04 - 24:06
    to present my project, I want to mention that
  • 24:06 - 24:09
    this year in the GSoC is the first time
  • 24:09 - 24:11
    that our country is participating.
  • 24:12 - 24:14
    It was funny, because even when we had
  • 24:14 - 24:16
    applied for the GSoC, we had
  • 24:17 - 24:18
    to ask Google to add
  • 24:18 - 24:20
    our country in the list, so
  • 24:21 - 24:21
    you know how...
  • 24:22 - 24:24
    We thought that we didn't
  • 24:25 - 24:27
    have any more opportunities
  • 24:27 - 24:28
    or any...
  • 24:29 - 24:31
    we just thought they aren't going to accept us.
  • 24:31 - 24:33
    But hopefully for us, we have
  • 24:34 - 24:35
    a great mentor,
  • 24:35 - 24:37
    Daniel Pocock, I think many of you
  • 24:38 - 24:39
    guys know him,
  • 24:40 - 24:41
    and he helped us
  • 24:41 - 24:43
    with everything that we needed
  • 24:43 - 24:45
    for all of the applications
  • 24:46 - 24:47
    and everything else.
  • 24:48 - 24:50
    So, going back to my project,
  • 24:50 - 24:52
    My project
  • 24:52 - 24:54
    is basically what I just said
  • 24:54 - 24:56
    right now. So, knowing that
  • 24:56 - 24:58
    newcomers to the open source have a lot
  • 24:58 - 24:59
    of problems to,
  • 25:00 - 25:02
    to just set up
  • 25:02 - 25:04
    a development environment
  • 25:06 - 25:06
    and
  • 25:07 - 25:10
    that's why we wanted
  • 25:11 - 25:11
    to create...
  • 25:13 - 25:14
    to create a GUI
  • 25:15 - 25:18
    so my project is a new contributor...
  • 25:18 - 25:19
    contributor wizard
  • 25:19 - 25:21
    and is basically a GUI that
  • 25:21 - 25:23
    could be distributed as a
  • 25:24 - 25:25
    package, and
  • 25:25 - 25:27
    to help the newcomer
  • 25:27 - 25:29
    to Debian and open source
  • 25:29 - 25:31
    to start their work
  • 25:31 - 25:34
    on the open source projects.
  • 25:35 - 25:36
    For example, if you want to
  • 25:36 - 25:39
    apply in GSoC or Outreachy
  • 25:39 - 25:41
    or other programs like this
  • 25:41 - 25:43
    you will need a lot of things
  • 25:43 - 25:45
    because if you are a new person,
  • 25:45 - 25:47
    you are newcoming to Debian, or
  • 25:48 - 25:49
    any other version of
  • 25:49 - 25:51
    Linux, you will have a lot of
  • 25:51 - 25:53
    problems to start up, so
  • 25:53 - 25:55
    what we want to do with this
  • 25:55 - 25:57
    is to help students
  • 25:57 - 25:59
    to run this computer
  • 25:59 - 26:01
    program in their desktop
  • 26:01 - 26:03
    and have to understand
  • 26:03 - 26:05
    everything that they need, for example
  • 26:05 - 26:07
    they will need for sure, how to use
  • 26:07 - 26:09
    IRC, they will need
  • 26:09 - 26:11
    basically a blog to explain
  • 26:12 - 26:13
    their work or add portfolio on it,
  • 26:13 - 26:15
    so they will need
  • 26:15 - 26:17
    a PGP or
  • 26:18 - 26:19
    other things like this
  • 26:19 - 26:21
    that we usually use in open source
  • 26:21 - 26:23
    so, my part of the project
  • 26:23 - 26:24
    in this
  • 26:25 - 26:27
    in this month of
  • 26:27 - 26:28
    the Google Summer of Code,
  • 26:29 - 26:31
    was the blog module,
  • 26:32 - 26:33
    basically, I created
  • 26:33 - 26:34
    a module that will
  • 26:35 - 26:36
    generate automatically
  • 26:37 - 26:39
    ...build dynamic and static websites.
  • 26:40 - 26:42
    And the other part
  • 26:42 - 26:44
    of it was that I did a lot of
  • 26:44 - 26:46
    research on what students
  • 26:46 - 26:47
    need for...
  • 26:47 - 26:50
    and we should include in the research
  • 26:52 - 26:54
    Another thing that I want to
  • 26:54 - 26:56
    mention is that students
  • 26:56 - 26:58
    don't know that much...
  • 26:58 - 27:02
    They have problems using the terminal
  • 27:02 - 27:04
    or installing
  • 27:04 - 27:07
    programs when they have usually installed Debian,
  • 27:07 - 27:09
    I will make sure
  • 27:09 - 27:13
    add that type of tutorials, or
  • 27:13 - 27:14
    for example
  • 27:14 - 27:16
    description of something
  • 27:16 - 27:17
    that will help them, how
  • 27:18 - 27:19
    to proceed and apply, and
  • 27:19 - 27:22
    maybe be a successful applicant
  • 27:22 - 27:24
    for GSoC. So, that's it.
  • 27:24 - 27:25
    Thank you!
  • 27:26 - 27:29
    [ audience clapping ]
  • 27:49 - 27:50
    Hello everyone!
  • 27:52 - 27:53
    My name is Diellza Shabani
  • 27:54 - 27:55
    and I also come from Kosovo,
  • 27:56 - 27:58
    I am a student of Computer Science
  • 27:58 - 27:59
    and Engineering,
  • 28:00 - 28:02
    I'm finishing my studies
  • 28:02 - 28:03
    this year hopefully,
  • 28:04 - 28:05
    so I am also doing
  • 28:05 - 28:07
    a Google Summer of Code project,
  • 28:07 - 28:09
    I haven't prepared any slides,
  • 28:10 - 28:12
    because I
  • 28:12 - 28:13
    didn't see it necessary,
  • 28:14 - 28:16
    so, my project's name is
  • 28:17 - 28:18
    "Click to dial up from
  • 28:18 - 28:20
    Linux Desktop", and
  • 28:20 - 28:21
    my mentor is Thomas Levine,
  • 28:22 - 28:24
    he couldn't join us
  • 28:25 - 28:26
    at the conference this year,
  • 28:27 - 28:28
    so, what I have been
  • 28:28 - 28:30
    working on this project is that
  • 28:33 - 28:34
    we are three students
  • 28:34 - 28:36
    in this project, because it's really
  • 28:37 - 28:38
    a big thing, we started
  • 28:38 - 28:41
    working in this last year
  • 28:41 - 28:42
    in the [?] hackathon,
  • 28:42 - 28:43
    in [?],
  • 28:44 - 28:46
    we started doing the project
  • 28:46 - 28:48
    in Python first,
  • 28:48 - 28:50
    we did some
  • 28:50 - 28:52
    pop-ups and some really basic things,
  • 28:53 - 28:54
    ...So,
  • 28:54 - 28:57
    we thought to continue that, but
  • 28:57 - 28:58
    now that the project is
  • 28:59 - 29:01
    bigger, and there are three students
  • 29:01 - 29:03
    doing this, it is separated
  • 29:03 - 29:04
    in two different things, and
  • 29:05 - 29:06
    the two other students
  • 29:07 - 29:09
    are doing something else,
  • 29:09 - 29:11
    and we plan to do
  • 29:11 - 29:13
    something like mobile
  • 29:13 - 29:14
    application,
  • 29:15 - 29:17
    but still haven't figured it out.
  • 29:19 - 29:20
    For the moment, we are
  • 29:20 - 29:22
    doing only a website,
  • 29:22 - 29:24
    a Web application,
  • 29:24 - 29:25
    and
  • 29:26 - 29:28
    we are working on
  • 29:28 - 29:30
    the existing projects
  • 29:30 - 29:32
    that Google Summer of Code students have
  • 29:32 - 29:34
    done before, like Omnitel
  • 29:34 - 29:35
    and Lumicall
  • 29:36 - 29:38
    I am basically working on them
  • 29:38 - 29:40
    and making changes, an doing
  • 29:40 - 29:42
    task classes
  • 29:42 - 29:43
    and methods, so...
  • 29:44 - 29:46
    After we finish that, I think
  • 29:46 - 29:48
    we will continue with the website, and
  • 29:48 - 29:49
    hopefully,
  • 29:50 - 29:52
    because the GSoC is really
  • 29:52 - 29:54
    coming to an end,
  • 29:54 - 29:56
    and we have not very much time
  • 29:56 - 29:57
    left. But...
  • 29:57 - 30:00
    After this, we will probably be working
  • 30:00 - 30:01
    in doing the mobile app.
  • 30:01 - 30:03
    However, this is
  • 30:04 - 30:06
    all I have to tell
  • 30:06 - 30:08
    right now about my project
  • 30:09 - 30:11
    the opportunity to be here and to
  • 30:12 - 30:14
    present for you guys.
  • 30:14 - 30:15
    Thank you.
  • 30:15 - 30:19
    [ audience clapping ]
  • 30:35 - 30:37
    OK, so... Can you hear me?
  • 30:40 - 30:42
    So, hi everyone!
  • 30:44 - 30:46
    I am not actually a Google Summer of Code student,
  • 30:46 - 30:50
    but I have been an Outreachy intern
  • 30:50 - 30:52
    around one year ago.
  • 30:52 - 30:54
    So, first
  • 30:54 - 30:56
    before continuing my
  • 30:56 - 30:57
    talk, I'd like to ask
  • 30:58 - 30:59
    how many of you are coming from
  • 31:00 - 31:03
    a social background, and has not
    finished for computer science or
  • 31:04 - 31:05
    science-related?
  • 31:07 - 31:08
    OK, great.
  • 31:08 - 31:10
    So we got three other people
  • 31:11 - 31:12
    in the audience. So
  • 31:12 - 31:13
    I am Kristi Progri, and I am actually,
  • 31:14 - 31:15
    I finished my university for
  • 31:16 - 31:18
    international affairs and diplomacy
  • 31:19 - 31:20
    and in the beginning I thought
  • 31:20 - 31:22
    that this was exactly the school,
  • 31:22 - 31:24
    that I'd never ever find something
  • 31:24 - 31:26
    to do with my life,
  • 31:26 - 31:28
    but then, I thought that, OK,
  • 31:29 - 31:30
    probably it would be nice
  • 31:30 - 31:32
    if I could just merge it with
  • 31:32 - 31:34
    something that is tech-related,
  • 31:34 - 31:36
    and free software, since during that time
  • 31:36 - 31:38
    I was also part of the
  • 31:38 - 31:39
    free software community
  • 31:39 - 31:42
    I ended up in the end having a diploma
  • 31:42 - 31:44
    thesis for on-line diplomacy,
  • 31:44 - 31:46
    and this was
  • 31:46 - 31:48
    what kind of opened
  • 31:48 - 31:50
    the doors further to
  • 31:50 - 31:52
    continue, and to get
  • 31:52 - 31:53
    to know more
  • 31:54 - 31:56
    for political and Internet.
  • 31:57 - 31:58
    So, I applied
  • 31:59 - 31:59
    in Mozilla
  • 32:00 - 32:01
    in a team for taking part
  • 32:02 - 32:04
    in the Outreachy, working with the
  • 32:04 - 32:06
    diversity and inclusion team there,
  • 32:06 - 32:07
    building up the
  • 32:08 - 32:09
    strategy for conducting
  • 32:10 - 32:11
    first language interviews, since
  • 32:12 - 32:14
    one of the barriers that we had during
  • 32:15 - 32:16
    all this time was that
  • 32:16 - 32:18
    people coming from different...
  • 32:18 - 32:20
    different countries
  • 32:20 - 32:21
    and not speaking
  • 32:22 - 32:24
    everyone by default English, so
  • 32:24 - 32:26
    trying to have a strategy
  • 32:26 - 32:28
    on how to conduct the language...
  • 32:28 - 32:30
    On how to conduct interviews, and
  • 32:30 - 32:32
    to grow up communities in the local
  • 32:32 - 32:33
    aspect, to really help to
  • 32:34 - 32:36
    take further steps to
  • 32:36 - 32:38
    all the free software initiatives, and
  • 32:38 - 32:40
    everything that's regarding to that.
  • 32:41 - 32:42
    So
  • 32:42 - 32:43
    this was
  • 32:44 - 32:45
    kind of the aspect from the field
  • 32:46 - 32:47
    doing on the Outreachy. For those
  • 32:48 - 32:50
    who don't know Outreachy, it's
  • 32:50 - 32:52
    exactly... It is an intership that
  • 32:52 - 32:54
    that lasts for three months,
  • 32:54 - 32:56
    it happens twice per year,
  • 32:57 - 32:58
    it has
  • 32:58 - 33:00
    kind of the same ideology
  • 33:00 - 33:02
    as the Google Summer of Code, but
  • 33:02 - 33:04
    it's also for people that
  • 33:04 - 33:05
    are not students but have
  • 33:06 - 33:07
    finished their
  • 33:08 - 33:09
    studies.
  • 33:09 - 33:12
    and besides Outreachy and
  • 33:12 - 33:14
    the Google Summer of Code, there also
  • 33:14 - 33:15
    are initiatives that
  • 33:16 - 33:18
    help out students
  • 33:18 - 33:20
    to continue and
  • 33:20 - 33:22
    getting on more knowledge regarding
  • 33:22 - 33:23
    the free software, such as
  • 33:23 - 33:25
    Rails' Girls Summer of Code,
  • 33:26 - 33:28
    I don't know if you have heard about that, it is
  • 33:28 - 33:30
    an internship happening on the
  • 33:30 - 33:32
    during the summer, it lasts
  • 33:32 - 33:35
    for three months,
  • 33:35 - 33:37
    three months I think,
  • 33:37 - 33:38
    and it's actually
  • 33:38 - 33:40
    only regarding coding. But
  • 33:40 - 33:42
    until now, I think, for as far
  • 33:42 - 33:44
    as I know, Outreachy is the only one
  • 33:44 - 33:45
    that can,
  • 33:45 - 33:48
    that requires also people that do not have
  • 33:48 - 33:49
    technical
  • 33:50 - 33:52
    skills, or at least that have
  • 33:52 - 33:54
    not finished for it,
  • 33:54 - 33:55
    any technical
  • 33:55 - 33:57
    subject or degree.
  • 33:58 - 34:00
    So, this was also
  • 34:00 - 34:02
    my short presentation
  • 34:02 - 34:03
    to say, and the
  • 34:04 - 34:06
    last one I think for the session, so
  • 34:06 - 34:08
    there is anyone in the audience
  • 34:09 - 34:10
    who'd like to make a question, any
  • 34:10 - 34:12
    suggestion or comment, please feel free
  • 34:12 - 34:14
    and thank you very much for
  • 34:14 - 34:15
    being here.
  • 34:16 - 34:19
    [ audience clapping ]
  • 34:38 - 34:40
    [Delib:] Hello. Jaminy,
  • 34:42 - 34:46
    So many of us are so interested in the
  • 34:46 - 34:48
    the edges of Debian,
  • 34:48 - 34:50
    and who is coming, and are they
    staying
  • 34:51 - 34:52
    and you have met
  • 34:52 - 34:54
    so many mentees,
  • 34:54 - 34:56
    and talked with so many mentors. Could you share
  • 34:56 - 34:58
    with us a little bit about
  • 34:58 - 34:59
    what is working well and
  • 35:00 - 35:01
    what might work a little better
  • 35:02 - 35:03
    in the future?
  • 35:08 - 35:10
    [Jaminy:] So, there are many newcomers
  • 35:10 - 35:12
    coming from Google Summer of Code,
  • 35:13 - 35:14
    I think the main thing
  • 35:14 - 35:17
    that actually happens is they should be
  • 35:17 - 35:19
    keep motivated and keep working on
  • 35:19 - 35:20
    after the Google Summer of Code,
  • 35:21 - 35:23
    I feel that would be one of the
  • 35:23 - 35:24
    major things they have to do
  • 35:25 - 35:27
    even after the Google Summer of Code
  • 35:36 - 35:38
    [Delib:] Do you have ideas of how
  • 35:40 - 35:42
    community members or the mentors
  • 35:42 - 35:44
    could do things differently, so that
  • 35:45 - 35:47
    they could stay more motivated?
  • 35:48 - 35:49
    Stay more interested?
  • 35:52 - 35:54
    [Jaminy:] I think the mentors, it's all about the communication,
  • 35:55 - 35:56
    I think they should keep communicating
  • 35:57 - 35:58
    with the students and keep them
  • 35:59 - 36:00
    giving suggestions
  • 36:01 - 36:02
    and advising
  • 36:03 - 36:05
    them, how can they improve further on
  • 36:05 - 36:06
    their projects,
  • 36:06 - 36:08
    and how they can keep moving
  • 36:08 - 36:11
    keep... Moving on
  • 36:11 - 36:12
    further with the project.
  • 36:13 - 36:14
    [Delib:] So, listening to what their interests are,
  • 36:15 - 36:16
    and giving them ideas on how to
  • 36:16 - 36:17
    pursue those interests?
  • 36:18 - 36:18
    [Jaminy:] Yes.
  • 36:27 - 36:29
    [Tassia:] I have a question: Is it
  • 36:29 - 36:32
    ...I have the impression that I might be wrong, so
  • 36:32 - 36:33
    [Jaminy:] Do you have questions for me, or
  • 36:33 - 36:35
    for students? [Tassia:] For you.
  • 36:35 - 36:37
    [Jaminy:] OK.
  • 36:38 - 36:40
    [Tassia:] Sorry [both laugh]
  • 36:40 - 36:41
    But just, for
  • 36:42 - 36:43
    what I've been following, for
  • 36:43 - 36:45
    the past years, I thing that when students
  • 36:46 - 36:47
    enter work with a team
  • 36:47 - 36:49
    my impression is that it's easier
  • 36:49 - 36:51
    for them to continue working afterwards.
  • 36:52 - 36:53
    Is it
  • 36:55 - 36:56
    in comparison when
  • 36:56 - 36:58
    there are ad-hoc projects
  • 36:59 - 37:00
    that some times don't
  • 37:01 - 37:02
    continue being developed,
  • 37:03 - 37:04
    and I think,
  • 37:04 - 37:07
    then the motivation might probably...
  • 37:07 - 37:09
    Do you perceive it? Or
  • 37:10 - 37:11
    you don't think it makes sense?
  • 37:11 - 37:13
    [Jaminy:] Currently I'm not, but I hope
  • 37:13 - 37:15
    to continue after my...
  • 37:15 - 37:17
    Now I'm currently doing early career,
  • 37:17 - 37:19
    so I would prefer continuing
  • 37:19 - 37:20
    later.
  • 37:21 - 37:23
    [Tassia:] No, sorry, I think you didn't understand my question.
  • 37:24 - 37:25
    It was about the projects
  • 37:25 - 37:27
    within teams,
  • 37:27 - 37:28
    like, lets say, the students that work with
  • 37:29 - 37:30
    the Perl team, or that work inside
  • 37:31 - 37:32
    another team
  • 37:33 - 37:35
    in comparison with just
  • 37:35 - 37:36
    one mentor and one
  • 37:37 - 37:37
    mentee
  • 37:40 - 37:40
    and if that
  • 37:41 - 37:42
    reflects on the
  • 37:42 - 37:45
    motivation of the student to continue
  • 37:45 - 37:47
    doing work for Debian
  • 37:47 - 37:49
    afterwards. Do you thing there is
  • 37:49 - 37:51
    a relation, or not?
  • 37:52 - 37:54
    [Jaminy:] Yes, I think there
  • 37:54 - 37:55
    is, I mean, the
  • 37:55 - 37:57
    mentor-mentee relations keeps
  • 37:57 - 37:59
    going on?
  • 38:00 - 38:02
    Eventually they get your question probably?
  • 38:07 - 38:09
    [Delib:] Do you think it's easier for students
  • 38:09 - 38:11
    to be part of a team, instead of
  • 38:11 - 38:12
    just one mentor?
  • 38:13 - 38:15
    [Jaminy:] Yes, I think they
  • 38:15 - 38:17
    get valious knowledge, so it's better to
  • 38:17 - 38:18
    be in a team
  • 38:18 - 38:20
    than sticking to one mentor.
  • 38:22 - 38:23
    [Andreas:] Do we have some
  • 38:23 - 38:25
    statistics? How many of
  • 38:25 - 38:27
    the students have entered Debian?
  • 38:27 - 38:29
    or not? Because I have had three
  • 38:29 - 38:31
    GSoC students, and three Outreachy
  • 38:31 - 38:33
    students, and
  • 38:33 - 38:34
    none of them
  • 38:34 - 38:37
    really remained there. They are intererested,
  • 38:37 - 38:38
    they are using Debian, but
  • 38:39 - 38:40
    my experience
  • 38:40 - 38:43
    or the result of my experience
  • 38:43 - 38:45
    was that I tried to give them tasks
  • 38:45 - 38:47
    which are easy to end,
  • 38:47 - 38:49
    which are small tasks,
  • 38:49 - 38:51
    and if they go, then that's not
  • 38:51 - 38:53
    ... How many people stayed in Debian?
  • 38:55 - 38:57
    [Jaminy:] You mean...
  • 38:59 - 39:00
    You mean, from the past?
  • 39:01 - 39:03
    [Andreas:] How many people stayed in Debian?
  • 39:03 - 39:05
    of the students?
  • 39:05 - 39:06
    From the past, yes.
  • 39:10 - 39:12
    [?:] I think you can answer
  • 39:12 - 39:14
    after the session, because
  • 39:14 - 39:16
    we run out of time.
  • 39:16 - 39:18
    [Jaminy:] OK. I'd like to take this opportunity
  • 39:19 - 39:20
    to thank all the mentors
  • 39:20 - 39:22
    who made this program successful.
  • 39:22 - 39:23
    And you can feel free to talk to students
  • 39:23 - 39:25
    after the session, and give them
  • 39:25 - 39:27
    suggestions or feedback.
  • 39:27 - 39:28
    Thank you!
  • 39:28 - 39:30
    [ Audience clapping ]
Title:
https:/.../gsoc-session.webm
Video Language:
English
Team:
Debconf
Project:
2018_debconf18
Duration:
39:38

English subtitles

Revisions Compare revisions