Hello Hridaya,
The requirement for applying is to solve at least one difficultyInteresting 
easy hack: 
https://wiki.documentfoundation.org/Development/EasyHacks/by_Required_Skill/Skill_C%2B%2B#Skill_Level:_Interesting

Here are few links where you can get an idea on how to get started
1)https://wiki.documentfoundation.org/Special:MyLanguage/Development

First you have to build LibreOffice locally on your system and then solve a 
DifficultyInteresting Problem and submit on Gerrit.
You can look here on how to get started
Getting Started with LibreOffice Development - LibreOffice Conference 2021
https://www.youtube.com/watch?v=whHBiTwstWI
This wonderful video by Libreoffice has everything needed to get started.

The friendly and wonderful team and community members at LibreOffice has done a 
great job by making wiki documentations and videos . So, the materials 
available are self explanatory and will help you get started.

If you get stuck then read
https://wiki.documentfoundation.org/Special:MyLanguage/Development/GetInvolved

https://wiki.documentfoundation.org/Development/lode

And if you face any problem, the friendly team and community at LibreOffice is 
always ready to help!

Best Regards,
Manish Mahapatra

On Sunday, 30 March 2025 at 11:49 AM, Hridya Sadanand 
<hridyasadana...@gmail.com> wrote:

> Dear LibreOffice Developers,
>
> My name is [Your Name], and I am excited to participate in GSoC 2025 with 
> LibreOffice. I am particularly interested in the "Improve Word Processor Test 
> Coverage" project and eager to contribute.
>
> I am currently learning C++ and have experience reading and understanding 
> existing code. While I am new to LibreOffice development, I am ready to dive 
> into the codebase, understand the current test framework, and help improve 
> test coverage for LibreOffice Writer.
>
> I would appreciate any guidance on getting started, such as useful resources, 
> test coverage reports, or first tasks to explore. I look forward to working 
> with the community and learning from everyone here.
>
> Best regards,
> Hridya Sadanand

Reply via email to