HADES is developed and maintained by the HADES Workgroup of the OHDSI community.

Online discussions

Online discussions can take place in the HADES Teams or on the OHDSI forums.

Meetings

The HADES workgroup has regular meetings. Meetings are open to all, and will be held on the third Thursday of the month.

Next HADES meeting

Date: May 19, 2022

Time (DST where appropriate):

  • 6pm Central European time
  • 5pm UK time
  • 12pm (noon) Eastern Time (New York / New Jersey / Pennsylvania)
  • 9am Pacific Time (Los Angeles / Stanford)

Teams meeting details:

URL: Join Microsoft Teams Meeting

Prior meetings

2022

  • April 21: Upcoming hack-a-thon, Q2 key results. See recordings in Teams
  • March 17: Key results. Modularization. See recordings in Teams
  • February 17: 2022 objectives and key results. See recordings in Teams
  • January 20: 2022 objectives and key results. See recordings in Teams

2021

  • November 18: Study packages, Hydra, renv, and Docker. Notes and slides

  • October 22; Study packages.

  • September 16: CDM 5.4.0, interfaces with ATLAS and ARACHNE. Notes

  • June 17: Unit-test-a-thon, integration testing. Notes

  • May 20: PLP GUI. Notes

  • April 15: Unit testing, CDM 5.4.0, HADES paper. Notes

  • March 18: Upcoming HADES packages, unit testing. Notes

  • February 18: Continuous Integration, OKRs, package maintainer expectations, 64-bit ints. Notes

  • January 21: Study package guidelines, system requirements, GitHub Actions, Objectives and key results. Notes.

2020

  • December 17: GitHub Actions, System Requirements, CDMv6, Communication. Notes.

  • November 19: Study packages & CDM v6. Notes.

  • October 15: HADES kickoff, versioning and releasing. Notes, slides, and recording.

Package maintainers

Each package in HADES has one or two maintainers. These maintainers have the final responsibility and authority over their package. These are the expectations of package maintainers:

  • Represent the package in the HADES group discussions.
  • Ensure that issues are resolved in a timely manner.
  • Review and merge pull requests.
  • Create releases (and communicate upcoming releases to those that need to know).
  • Adapt the package to changes in its dependencies (including R packages, R itself, and the infrastructure).
  • Develop new functionality depending on the needs of the community.
  • Adhere to and enforce the HADES standards, such as the Developer Guidelines and Code Style Guide.