As part of improving maintainability and contributor experience across the JuliaHealth ecosystem, this issue is intended to discuss on having a shared code style guideline for JuliaHealth packages.
During the kickoff discussion, @TheCedarPrince and @cncastillo mentioned that:
- Julia packages currently follow mixed styles
- Enforcing strict formatting at PR time can create overhead for contributors
- Some ecosystems are moving toward styles like Runic, while others use Blue style.
Points to consider:
- Whether JuliaHealth should recommend a common style guide (e.g. Blue style, Runic)
- If formatting should be applied post-merge instead of blocking PRs
- Whether style checks should be optional or run periodically (e.g. scheduled CI)
- How to minimize contributor overhead while improving long-term maintainability
As part of improving maintainability and contributor experience across the JuliaHealth ecosystem, this issue is intended to discuss on having a shared code style guideline for JuliaHealth packages.
During the kickoff discussion, @TheCedarPrince and @cncastillo mentioned that:
Points to consider: