Hello Jenkins community,
I’m Saviti Veerababu, an undergrad student with a strong background in Java and experience in Python, Django, and C++. Since 2022, I’ve been using IntelliJ IDEA Ultimate for my projects, which has given me a solid grasp of Java development and exposure to REST APIs through its built-in tools.
I’m thrilled to apply for GSoC 2025 with Jenkins and am excited about the “Swagger/OpenAPI Standardization for Jenkins REST API” project. Jenkins’ role in open-source CI/CD inspires me, and I see this project as a chance to make its REST API more developer-friendly with clear, automated Swagger docs—something I’d love as a user. My Java skills and IntelliJ REST experience feel like a natural fit for generating these specs.
I’d love to hear from mentors Kris Stern, Bruno Verachten, @iamrajiv, Bervianto Leo Pratama, and @themeinerlp. For a 175-hour scope, would you prioritize extracting core API specs from Javadocs/annotations or tackling plugin API generation first?
Also, could you suggest a good newbie contribution to get started and gain some experience?
Looking forward to your input!
Best,
Saviti Veerababu
GitHub: M1D0R1x (M1D0R1x) · GitHub