veyepar: Little bioinformatician's pragmatic guide to internships in Debian

Author(s):	Nadiya Sitdykova, Tatiana Malygina
Location	Rex
Date	aug Sun 06	Days Raw Files
Start	14:30	First Raw Start	error-in-template
Duration	00:20:00	Offset	None
End	14:50	Last Raw End
Chapters
Total cuts_time	None min.

https://debconf17.debconf.org/talks/148/
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Little_bioinformaticians_pragmatic_guide_to_internships_in_Debian.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Outreachy is yet another internship for newbies. It closes gap between "uses" and "contributes" and gives certain categories of people a good motive to start making the world to be a better place.
Every Outreachy intern requires personal approach to work with. Yet this "personal" doesn't mean something too different from approach applied to any other program's intern.
We are going to tell how we learned about Outreachy and why we decided to choose Debian. Why internships matter. We are going to provide our personalized view to internship process and how to be motivated enough to finish it. 
And we will draw a precise portrait of a Perfect Internship Mentor :)
 
We also want to talk about why CI for Debian packages matters and how it helps us and our friends in everyday work and career and provide some examples. And how hard it is to stay (and why you should stay).
 
Writing tests can sometimes be boring and routine, and we are going to provide some approaches we used to semi-automate it. Yet it doesn't mean it can be automated fully, because every package is unique and often only after you take a closer look  you can build a good tests and find a bug no one else fixed yet.

Comment:

production notes