Staff Onboarding Checklist
From Dryad wiki
Revision as of 13:27, 9 December 2014 by Ryan Scherle (talk | contribs)
A sample checklist for onboarding new staff. Each staff member will have different needs, but these are some of the most common.
Items that need to be updated on this checklist:
- add system architecture diagrams, which include everything from the Architecture Overview page.
First:
- Email help@datadryad.org to request an @datadryad.org email address.
Accounts that the staff member must create:
- access to wiki - staff self-creates an account, using the @datadryad.org email, then asks admin@datadryad.org for privileged access
- Google Dryad Dev list dryad-dev@googlegroups.com - sign yourself up
- Accounts in Dryad production and development servers -- create the accounts, and ask admin@datadryad.org for privileges
- Dryad Announce list -- sign up yourself (from Dryad homepage)
Accounts/access created by Dryad administrators:
- Dryad Dropbox folder
- Slack
- Dryad private team list
- Trello -- may use a pre-existing Trello account, or a new account based on the @datadryad.org email
- FogBugz
- Dryad Users list
- keys and ID cards needed for physical access to Dryad space
- update mail aliases as required
- update Website staff list
The staff member should become familiar with:
- The other Dryad staff
- Strategic plan, development roadmap & NSF grant project description
- The Grants that have funded Dryad development
- Architecture Overview
- Submission System Workflow
- Curation Practices
- Emergency Contact Procedures
- Using Trello
- Basic Dryad submission workflow
- Create a data package on the staging server that includes at least two of the instructional documents listed above
If the staff member will be performing development, they should be trained on:
- The wiki
- Add relevant information to Participants and WG:Participants
- Update documentation for a feature
- Development Process
- How To Install Dryad and use it
- Using Git
- Testing
- Write a test case -- see sample list in the notes from the Dryad Developer Retreat 2014
See also: Staff Offboarding Checklist