Repository navigation
GSoC 2026: DevOps improvement and standardization #2540
Replies: 3 comments
|
@Shlokpalrecha sorry about the confusion. We only had that project there because we created that page by copying the 2025 one. There aren't enough features missing to have a feature parity project, at most would be a couple plots. We will add a warning to the page next year that it shouldn't be read until GSoC confirms which organizations are participating. We need to have the page published before that for GSoC to review our application and we are used to having public WIP pages, but we should be more clear about their status. If you have other clear ideas about what you'd like to contribute given you started looking at things with a lot of time and have reached out, we can discuss any other idea here as we mention on the wiki page. There is definitely work outside devops and feature parity to be done too. It will be a bit more work on your end though as you need to think about both idea and proposal, and any idea outside devops will require some understanding of Bayesian modeling which has been a common pain point for past participants (I know nothing about your background though so this might not apply). |
|
Hi @OriolAbril, Thank you for the clarification! That makes total sense, I can see from @The-Broken-Keyboard's GSoC 2025 work that significant feature parity progress was made. I'm very interested in the DevOps project! After reading the project description, I think it aligns well with what I've been learning through my PRs. My work on #414 and #415 has taught me the importance of good tests, clear documentation, and consistent API design and I'd love to help systematize those practices across the ArviZ repos. I'm going to start contributing to DevOps-related issues to familiarize myself with the infrastructure side. I'll focus on areas like type hints, testing improvements, and CI/CD workflows. Thanks again for your time and for being open to discussion. Best, |
|
Hi @OriolAbril, |
Uh oh!
There was an error while loading. Please reload this page.
Hi @OriolAbril and @aloctavodia,
I'm interested in applying for GSoC 2026 with ArviZ. I've been contributing to arviz-plots recently - my figure titles PR (#414) was merged, and I'm glad that the facet_map PR (#415) is being included in the upcoming release.
While preparing my application, I noticed that the Feature Parity project was initially listed on the GSoC 2026 wiki but has since been removed, leaving only the DevOps project. Since my recent contributions have been plotting features, I wanted to understand this change better.
Could you share why the Feature Parity project was removed? I'm trying to align my preparation and contributions with ArviZ's actual needs for GSoC. Should I focus on DevOps-related work (type hints, testing, CI/CD) instead, or is there still a possibility the Feature Parity project might be offered?
I'm happy to contribute in whatever area is most helpful for ArviZ. Thanks for your guidance!
Best regards,
Shlok
All reactions