Hi Jenkins Mentors and Community!
I am Iseouwa(G00dS0ul), a Computer Engineering student and currently in my fourth year of studies. My major stack to be contribution to the Jenkins is C# and .NET 10 Ecosystem(Currently working heavily with .NET 10 in my projects). I am very interested in using my skill to improve Jenkins Ecosystem.
Before i start writing my proposal about this idea i want to get a take from the mentors and community on which of these paths would provide more value to the Jenkins Ecosystem right now.
- Path A: A Brand New Component (C# Code & Pipeline Generation)
Basically, Jenkins Ecosystem is built on Automation, I would love to create an automated generator for the .NET ecosystem. This could either be a modern, auto-generating C# SDK/REST API Client (Since the existing one is outdated), or a C# to Jenkinsfile Generator that allows .NET developers to define their pipelines using native C# instead of raw Groovy. - Path B(Modernizing Existing Architecture (WinSW / API Clients)
If the Jenkins community would prefer to modernize and strengthen existing architecture, I am equally interested in diving into the codebase for WinSW to improve memory logging and update its .NET architecture, or optimize the existing C# REST API Clients.
I would appreciate your insight on the new C# utility, if the it will be something the community would adopt, or should i focus my official proposal entirely on revamping the existing Windows agent like WinSW?
Thank you for your time, I look forward to contributing.