The Herald Community consists of software developers, designers, and healthcare experts all working together to improve healthcare software for all.
We have a Project Advisory Group consisting of Public Health Authorities and experts in Digital Contact Tracing. Membership is invite only but output will be posted as unattributed minutes in our project website.
We also organise public meetings in varying timezones to present the latest updates, and to gather public feedback and answer questions. You can see when these are on the Linux Foundation Public Health’s Calendar.
Join the Linux Foundation Public Health’s Slack and our #herald-general channel and talk to our community members: https://slack.lfph.io/
Follow us on Twitter at @HeraldProximity
You can also view our Public Roadmap on Miro
Below are some items the Herald project team are looking for specific assistance with. If you feel you can help then please visit the links below:-
|Help Summary||Ideal timeline||Links|
DCT Distance conversion and Risk Exposure algorithm design, implementation, and evaluation
The Herald project have published 2.3 million data points from phones at 1cm resolution and are working on distance conversion routines to make them more accurate. We’ve also provided a general analysis streaming API to enable this and various disease exposure estimation routines to be created and implementation on mobile devices. If you would like to help us implement and evaluate these methods please come talk to us on Slack
|Apr-Sep 2021||API Sample tests|
Website information architecture
We need someone who is experienced at helping a very broad community with different interests to find information on our website. We’re improved it recently, but more work still is needed. Please visit our #herald-general slack channel on the LFPH slack instance detailed above
|Any time||This site!|
Pseudo Device Address randomness methods
Some phones incorrectly rotate their BLe MAC address every few seconds. This causes device discovery routines to reconsider a device even though it may have only just been identified recently. The Pseudo Device Address is a method around this. The mechanism used to generate this address needs to be reliable on a wide range of phones - even when idle for many hours - and prevent a passing attacker from predicting future addresses based on just the current observable address. There are many methods - we’re looking for suggestions that work across Android devices going back, ideally, to Android 5.0.
|Early-Mid Jan 2021||Android GitHub Issue #118|