Historical: v2.2.0 public launch checklist¶
Archived historical checklist. The repository is public as AdamEddahmouni/nosograph; this checklist described the v2.3.0 launch state. The current release is v2.4.0.
Current maintainer checklist: github-public-settings.md · RELEASING.md
Public Launch Checklist (NosoGraph)¶
Use this list when flipping the repository to public on GitHub. NosoGraph is Apache-2.0 licensed and intended for open research use. The GitHub remote may still be named med-research until renamed by maintainers.
Before you change visibility¶
Run locally:
make venv-sync
make ci-local
Confirm:
- No secrets in tracked files (
.envis gitignored; use.env.exampleonly). - No PHI or patient-identifiable data in commits.
- Runtime databases under
data/are not version-controlled. - README honestly describes disease tier maturity (registry ≠ curation).
- docs/audits/release-readiness-report.md gates reviewed.
GitHub repository settings¶
- General → Change repository visibility → Public
- Settings → Actions → General — allow workflows
- Settings → Security — enable Dependabot alerts, secret scanning
- Settings → General → Features — enable Issues (templates under
.github/ISSUE_TEMPLATE/) - About box — Description: NosoGraph — The Open Computational Map of Human Disease
- Topics:
bioinformatics,drug-discovery,fastapi,python,computational-biology,open-science,knowledge-graph,disease-ontology
Branch protection (recommended)¶
On master:
- Require pull request before merging
- Require status checks:
lint,security,test (3.11),test (3.12),integration-tests - Do not require
typecheckuntil mypy backlog cleared
After going public¶
- Create GitHub Release from
v2.2.0per RELEASING.md - Confirm README badge is green on
master - Optionally rename repository to
nosograph(update URLs in docs)
What stays out of scope¶
- FHIR / OMOP / Phenopackets (PLANNED)
- Billing / Stripe (NOT_IMPLEMENTED)
- Clinical decision support or PHI processing
Support channels¶
- Bugs / features: GitHub Issues
- Security: Private advisory — never public issues
- Governance: GOVERNANCE.md