Hi everyone, I'm Ratnesh, a CS student. I mostly work on backend stuff (Go, PostgreSQL, Redis, queue-based workers) and I've been getting into open source this year. I had a patch merged in GNU Mailman, and I've been contributing to Spack, a few package fixes and a PR on `spack checksum`.
Over the last few days I've been going through the new Go version of the Airavata server. When I ran the tests on Go 1.26, TestRootRedirectsToDashboard failed. It turns out Go 1.26 changed the trailing-slash redirect in ServeMux from 301 to 307, and CI doesn't catch it because it builds with Go 1.25 from go.mod. I opened an issue for it: https://github.com/apache/airavata/issues/761 Then I noticed #758 and #759 already include the same fix, so I didn't open a duplicate PR. On the Custos side I sent a small PR that adds a Dependabot config for GitHub Actions. #695 pinned the actions to SHAs, so this covers the "keep them updated" part of the ASF policy from #563: https://github.com/apache/airavata-custos/pull/737 I'd like to keep going, mainly around job submission and monitoring in internal/orchestration. Two quick questions: 1. Is Airavata planning to take part in GSoC 2027 through the ASF? And would mentors consider proposals from contributors who aren't from the project's partner universities? 2. Is there any part of the Go server where outside help would be most useful right now? I'm planning my GSoC prep over the next couple of weeks, so even a short reply would help a lot. Thanks, Ratnesh
