Welcome to the CD2H project (Center for Data to Health)
This page contains the steps you'll need to take after you have completed an onboarding request form AND have been granted permissions (this can take 1-3 business days).
If you are looking to join the CD2H project but have not yet requested onboarding, please do so at bit.ly/cd2h-onboarding-form
1) How should I communicate with team members?
- For simplicity, we have one main Google group (cd2h-allhands) which grants access to documents, calendar, and more. The individual CD2H projects are encouraged to use Slack for their communications, and GitHub issues commenting (see below) where appropriate. Some of the projects prefer communication by email; members of the projects will be in touch.
- When you've been added to the google group and you're logged in, you can catch up with recent announcements here if desired.
Step 1: Join our slack using the invitation you were emailed; don't forget to configure your notification settings per below to not get overwhelmed.
Once in Slack, click on "Channels" to see a list of channels and join just the ones that are interesting to you
2) Where are the shared docs and who can see them?
- In CD2H we make heavy use of Google Docs; to access them you will need to have been invited to the cd2h-allhands google group; membership in the group confers docs access and you will need to be signed in.
- With only a few exceptions, all CD2H docs are accessible to all onboarded team members (regardless of the particular team or sub-project).
- Every document you create in the CD2H should live in that folder somewhere; however, the precise sub-folder is less important.
3) What is GitHub for?
- GitHub is a platform for managing collaborative informatics projects. If you are new to GitHub and would like some tutorials a good place to start is here. GitHub is free and it is for everyone, not just developers.
- Some of the project information in GitHub is pulled dynamically into a dashboard here.
- GitHub is where we will be tracking all of the CD2H work, whether it is code, data, training, engagement, NIH reporting, or anything in between.
- Some of the content at github.com/data2health is world-visible; however most of the private repositories are readable by members who have onboarded and have accepted the invitation to github.com/data2health
Step 3a: Accept the GitHub invitation by logging into GitHub and clicking the blue banner at the top of github.com/data2health, then configure notifications per below.
Step 3b: Configure your GitHub account so that it has both your name and a photo (preferably a head shot, but could be an avatar, or even an object if you prefer)
4) What meetings should I attend?
There are no meeting requirements for unfunded collaborators; however, all are welcome*.
The embedded view of the calendar is available at the team portal (bit.ly/cd2hhome); you must first be added to the "cd2h-allhands" Google group and be signed in to see it. Click below to learn how to integrate the project calendar into your client (eg. outlook, ical)
* With the exception of the Program director and leadership meetings, all CD2H meetings are open for participation by anyone who has completed onboarding. The all-hands meetings are required for those funded through CD2H.
Boost the signal, squash the noise:
Configure your notifications
- Log in to GitHub.com
- Go to github.com/settings/notifications and UNclick "Automatically watch repositories"
- Go to github.com/watching and unsubscribe from all repositories. You can then go back and select the 1 or 2 you really do want to watch. Note that if you unsubscribe you will still get emails if you're involved (eg. author, assigned, or commenter). "Not watching" is generally the level you want at the repo level.
- Go to github.com/issues/assigned to see the issues that you are assigned across all of GitHub