[NF SDG] Internship Public Meeting Notes

[TheCedarPrince]

These are the public meeting notes for the NumFOCUS Small Development Grant project across JuliaHealth.

[kosuri-indu]

Date: January 5, 2026
Attendees: @kosuri-indu, @TheCedarPrince, @cncastillo

Agenda & Discussion Summary

• Created this issue to serve as a public, ongoing log for meeting notes related to the NumFOCUS Small Development Grant project.
• Reviewed the approved proposal and overall goals:
  • Attracting new JuliaHealth community members
  • Highlighting JuliaHealth workflows
  • Strengthening ecosystem robustness (docs, CI, maintenance)
• Confirmed Some Logistics

Project Direction & Execution Plan

Initial focus (Goals 2 & 3):

1. Conduct a detailed audit of documentation and CI status for key JuliaHealth packages.
   • Focus first on packages in the General Registry
   • Prioritize based on activity and adoption (e.g. stars)
2. Summarize audit findings as a JuliaHealth blog post (more details below).
3. Develop standardized documentation and CI templates.
   • Move one package to DocumenterVitepress as a reference example
   • Document challenges encountered during the migration
4. Submit follow-up issues to individual repositories based on audit findings.

Audit Scope (Initial Ideas)

• Presence of documentation (e.g. gh-pages, docs builds)
• CI status and coverage (GitHub Actions, coverage config)
• Repository structure (src/, test/, docs/)
• Maintenance signals (activity, stars, open/closed issues)
• GPU / Buildkite CI behavior (wherever applicable)

Audit outputs should be mainly be reproducible, ideally scriptable and reusable in CI.

Other Topics Discussed

• GPU CI / Buildkite behavior and associated noise concerns
• Manual vs Automated builds for the JuliaHealth website
• Early discussion around style guides (e.g. Blue style vs Runic), noted as a potential future topic

TO-DOS:

@kosuri-indu

• Start the work on audit of documentation and CI status for key JuliaHealth packages
• Begin outlining reproducible audit metrics alongside

@TheCedarPrince:

• Share access to the JuliaHealth code coverage
• Suggest an approach/tool for timesheet tracking

@cncastillo:

• As mentioned in the meeting, you were planning to reach out to NumFOCUS (Arliss) with a few questions related to the form i believe -- just adding a quick reminder here.

[kosuri-indu]

Date: January 19, 2026
Attendees: @kosuri-indu, @cncastillo
Async feedback: @TheCedarPrince

Agenda & Discussion Summary

• Reviewed the completed JuliaHealth ecosystem audit, including:
  • Reproducible GitHub Actions–based audit pipeline
  • Visualization outputs (RESULTS.md)
  • Repository structure and audit methodology
• Discussed feedback from Jacob (shared asynchronously via voice notes).
• Walked through the audit repository layout, scripts, metrics, and visualization choices.
• Reviewed the draft JuliaHealth blog post summarizing audit findings.
• Discussed next 2-week work plan following completion of the audit phase.

Review Feedback (Jacob – Async)

• Overall feedback was positive:
  • Audit exceeded expectations in scope, depth and execution.
  • Results and visualizations are insightful and well structured.
• Requested clarifications and refinements, not major changes:
  • Add short explanations for audit variables (e.g. “standard layout”, CI, coverage).
  • Refine terminology for ecosystem maturity
  • Improve wording around maintenance status to avoid implying abandonment.
  • Consider community input (Slack / Discourse) on how to classify maintenance states.
  • Add brief documentation explaining contributor distributions.
  • Rename or refine README quality metric (lines of code alone is insufficient).
• Suggested longer-term idea:
  • Potentially exposing audit outputs as a dedicated JuliaHealth website section
    (e.g. "Ecosystem Overview / Statistics"), updated automatically via CI.
• Blog post feedback:
  • Should be readable and navigable
  • Possibly split content or structure it for easier consumption

Audit Review & Technical Discussion (Live with Carlos)

• Confirmed audit pipeline:
  • Fully reproducible via GitHub Actions
  • Manual trigger enabled; discussed adding monthly scheduled runs
• Registry handling:
  • General Registry handled via local clone (avoiding excessive GitHub API calls)
  • Registry data currently static and manually refreshed
  • Agreed this is acceptable for now; future automation possible
• Key findings discussed:
  • Discovery of registry metadata issues (repository links not updated after migration to JuliaHealth)
    • Several packages may require General Registry PRs to fix repo URLs
  • Code of Conduct not being there
  • Few changes recommended for metrics/audit dimensions.
• Visualization choices:
  • VegaLite chosen for speed and CI-friendliness
  • PNG outputs used instead of interactive HTML due to Markdown limitations
• Metrics discussion:
  • Contributors counts may include bots (e.g. Dependabot)
  • Maintainers who are the most responsive could be added
  • README assessment to be refined using measurable features (badges, code blocks, links etc) - A Paper was suggested to refer to.
  • License presence confirmed across all packages (100%), license type not yet analyzed (but would want to)
• Validation:
  • Audit repository structure and documentation are clear and easy to follow
  • No major missing components identified

Blog Post Review

• Draft blog post reviewed live.
• Content focuses on:
  • Motivation (NumFOCUS grant goals)
  • Audit methodology
  • Ecosystem-wide findings
  • Actionable recommendations
• Feedback:
  • Visual-first approach is good (“images > text”)
  • Additional explanatory text only needed where it improves clarity
  • README quality metric should be refined before final publication
• Plan to finalize and merge blog post after incorporating feedback.

Project Direction & Execution Plan (Next 2 Weeks)

• Finalize audit phase:
  • Incorporate Jacob’s and Carlos’s feedback
  • Refine terminology, metrics, and documentation
• Complete and merge blog post
• Begin standardization work:
  • Draft a standard JuliaHealth package layout
  • Define baseline requirements:
    • Documentation structure
    • CI configuration
    • Community files (CONTRIBUTING.md, CODE_OF_CONDUCT.md)
• Explore DocumenterVitepress migration:
  • Start with a simpler package as a test case
  • Consider migrating KomaMRI after validating the workflow
• Prepare to open follow-up issues on repositories based on audit findings.

TO-DOs

@kosuri-indu

• Update audit results based on review feedback
• Finalize and update the blog post PR.
• Draft a proposed standard JuliaHealth package layout and templates.
• DocumenterVitepress migration on a simple package & then probably in KomaMRI.jl.

@cncastillo, @TheCedarPrince

• Provide feedback during final review of updated audit and blog post.
• Assist with registry metadata fixes if needed.
• Assist if any issues with KomaMRI.jl's DocumterVitepress.