I am Utkarsh, a 21 y/o undergrad student! Besides being a full-time student, I am an open source advocate, a software developer, and a somewhat-polyglot developer.
I am also a Debian Developer, maintaining & working on over 900+ packages (written in C, C++, Python, Ruby, JavaScript, Go, and Perl), including some "interesting" packages like the Ruby interpreter, Rails, Micro, and libgit2. Besides, I also co-maintain the fasttrack.debian.net service & is an FTP Trainee.
I was a Google Summer of Code student twice (once in 2019 and then in 2020), both times in Debian, where I authored my "baby" project, RuboCop::Packaging, which is a linter and an auto-corrector, written in Ruby, helping downstream Ruby teams of Debian, Ubuntu, Fedora, openSUSE, et al.
And finally, I work on Debian LTS part-time, a project by Freexian, extending the lifetime of all Debian stable releases to (at least) 5 years, where I patch and backport security fixes for packages in the APT archive for oldstable and oldoldstable releases.
Besides, I am a philatelist, a semi-occassional drummer, an avid reader, and have perhaps mastered the art of sticker fights! To know more or get in touch, I go by the handle utkarsh2102 across the web! \o/
Accepted Talks:
Why Point Releases are important and how you can help prepare them?
Even stable is updated once in a while. Those updates are called “Point Releases”. They usually incorporate the security fixes released until the time of the update and fixes for important bugs in the current release.
Whilst there are over hundreds of bugs fixed in each point update, there are even more that can be fixed with your help! This talk takes you through that and tells you how exactly can you help fix those bugs/security issues and help in preparing a solid point update!