Lately I’ve been sending quite a number of patches to Hydra with a focus on the future: tests, schema design, etc. We’ve also merged PRs to run the tests in parallel and format the documentation with Markdown.
I’ve run in to some problems when I want to merge or upstream some patches:
- Who can help me review this?
- Will this break somebody’s important use case?
The first point is fairly easy, I test it as well as I can and ping a Perl Monger friend if I can’t find anyone else.
The second point is much trickier. Today there is no avenue to ask Hydra users about possibly breaking changes. Its fairly organic growth makes it hard to even know what the features are sometimes! Now, Hydra has been long considered to be “unreleased” software, which is the epitome of “if it breaks you get to keep both pieces” but I’d like for my own work to be in collaboration with its users.
So, Hydra users, how should we talk to each other and collaborate? Is a Discourse Category the right way to go?
Separately, what if we had a team on Hydra of users that know Perl, and PR authors could ping the team to get some review?
Note, I’m not saying this is totally changing how Hydra is developed or supported. I don’t think every change would go through a rigorous process any time soon. I don’t think its status of being “unreleased” would change any time soon, either. I’m just trying to think about ways we could collaborate a bit better when possible.