veyepar: Intro to Kernel Hacking - finding things to work on.

Author(s):	Tobin Harding
Location	Great Hall CB01.05.009
Date	jan Mon 22	Days Raw Files
Start	15:00	First Raw Start	14:51
Duration	0:20:0	Offset	0:08:10
End	15:20	Last Raw End	15:21
Chapters	00:00
Total cuts_time	12 min.

http://lca2018.linux.org.au/schedule/presentation/135/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive public tweet mp4 svg png

assets release.pdf Intro_to_Kernel_Hacking_finding_things_to_work_on.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

Finding something to work on is a problem faced by all kernel newbies. The
internet abounds with information on creating your first patch, someone (*cough*
me) even blogs, and presents, on doing your first patch set. But one patch does
not a kernel developer make, nor one patch set.

This talk is aimed at developers wishing to get started working on the kernel
but unable to find things to work on. You will hopefully walk away with
increased enthusiasm and confidence that you can find something interesting and
tractable to work on within the kernel.

We will discuss the idea that barriers to kernel development are primarily
social not technical. You can expect some suggestions on how to manoeuvre within
the kernel development process and some tips for maximizing your chances of
success. Their will be a brief discussion on motivation - nothing hard can be
achieved without the motivation to do so.

You can hope to learn how to find, and interact with, other more experienced
kernel developers and how that can assist you in finding the solution that works
for you.

You can _however_ also hope to gain some concrete technical suggestions for
getting started with kernel development and finding things to work on.

Tobin is a hobbyist kernel developer. Whilst achieving a very small amount of
success he has experienced many obstacles that can be lumped together under the
problem of 'finding something to work on'. It is his hope that you can gain from
this and find yourself happily hacking away on interesting kernel problems.

Comment:

production notes