On Sat, Feb 21, 2026 at 8:05 AM Harshit Nagpal <[email protected]> wrote:
> Dear Sir/Madam, > > I hope you are doing well. I'm writing this email to express my interest > in the Libcdio project under the GNU organization. > > I read the project description and I think it's a good fit for me – I'm > well-versed with C and have a decent level of proficiency with Rust as well. > > I would really like to get a bit more briefing about the project. > Specifically: > > The project size isn't mentioned > I don't know what this means. > Are there any pre-qualification tasks, or do I just need to submit a > proposal? > In the past, I know it was preferred to have people already contributing to projects they work on before the Summer of Code. How should I prepare? Look at the code in https://github.com/libcdio/libcdio and https://github.com/libcdio/libcdio-paranoia. Browse the code, check it out, and build it to get to understand what it is and what it does. On the Google Summer of Code side, see https://summerofcode.withgoogle.com/rules and https://developers.google.com/open-source/gsoc/faq Are there any specific libraries I should study or practice with that will > help in accomplishing the task? > The libraries that are relatively small and very self-contained, and are not hardware dependant are libiso9660 (library for reading ISO-9660 libraries), libudf (library for reading UDF filesystems), and cd-paranoia (error and jitter correction). The first two are in the libcdio GitHub repository, and the last is in the libcdio-paranoia GitHub repository.
