Dear Beam Community, I received the email.
I am Brijesh Thummar, a second-year Bachelor’s student in Computer Science Engineering from India. I am an active open-source contributor, and contributing to open source has been a fascinating journey for me, allowing me to learn and grow continuously. Before GSoC 2025, I officially contributed to Apache in the Gravitino and incubator-stormcrawler repositories, with total of 7 PR, 4 of them is merged already and 3 active ones. (from February 2025). As I became more familiar with Apache, I started exploring various codebases and contributing actively. Beyond Apache, I have contributed to projects under Jenkins, Eclipse Foundation, NASA, Redis, Oracle, Docker and many more. One of my most significant achievements was my 128th PR being merged into Apache Gravitino, where I fixed an issue titled [fix(logging): Correct logger class in IcebergTableRenameOperations]. Apart from open source, I have been actively involved in my university’s Tech Fest 2024 and currently serve as the Org Head and Security Lead of the university’s tech community and Tech Fest 2025, as well as the official Web Development Team Lead. Also to mention i am working towards becoming an Apache committer. I have experience in writing workflows for Apache and other organizations, with strong proficiency in YAML and CI/CD processes, and REST API. Given my background, I believe I can be helpful in working on the GSoc mentioned project. I am confident in handling the workflow and configuration aspects of the project. Project idea : Beam YAML ML, Iceberg, and Kafka User Accessibility project. After going through the GSoC 2025 website, I immediately chose Apache as my preferred organization. Upon reviewing the idea list, I found Beam particularly fascinating. I have explored the documentation and code structure and have decided to work on Seata as my GSoC project idea. I would love guidance on how to get started with contributions, understanding the workflow, and best practices for contributing to Seata. Any pointers on relevant issues, documentation, or discussions would be highly appreciated. Looking forward to collaborating with the Seata community! Best regards, Brijesh Thummar
