Difference between revisions of "Staff Onboarding Checklist"

From Dryad wiki
Jump to: navigation, search
Line 2: Line 2:
  
 
Items that need to be updated on this checklist:
 
Items that need to be updated on this checklist:
* add system architecture diagrams, which include everything from the [[Architecture Overview]] page.
 
  
First:
+
*add system architecture diagrams, which include everything from the [[Architecture Overview]] page.
* Email help@datadryad.org to request an @datadryad.org email address.
 
  
Accounts that the staff member must create:
+
'''First:'''
* 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:
+
*Email help@datadryad.org to request an @datadryad.org email address.
* 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
 
* keys and ID cards needed for physical access to Dryad space
 
* update [[WG:Mailing_Lists|mail aliases]] as required
 
* update [http://datadryad.org/pages/whoWeAre#staff Website staff list]
 
* access to [[Password Management]] system
 
  
The staff member should become familiar with:
+
== Accounts that the staff member must create ==
* 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
 
* [[WG:Emergency|Emergency Contact Procedures]]
 
* [[Using Trello]]
 
* Basic Dryad submission workflow
 
** Create a data package on the [http://staging.datadryad.org 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:
+
*access to wiki - staff self-creates an account, using the @datadryad.org email, then asks admin@datadryad.org for privileged access
* The wiki
+
*Google Dryad Dev list dryad-dev@googlegroups.com - sign yourself up
** Add relevant information to [[Participants]] and [[WG:Participants]]
+
*Accounts in Dryad production and development servers -- create the accounts, and ask admin@datadryad.org for privileges
** Update documentation for a feature
+
*Dryad Announce list -- sign up yourself (from Dryad homepage)
* [[Development Process]]
+
 
* [[How To Install Dryad]] and use it
+
== Accounts/access created by Dryad administrators ==
* [[Using Git]]
+
 
* [[Testing]]
+
*Dryad Dropbox folder (no longer using)
** Write a test case -- see sample list in the notes from the [https://docs.google.com/document/d/19LGb1UwVuUccBmX46VvwKqQamkXScGfKVEGZaxr7gBc/edit Dryad Developer Retreat 2014]
+
*Slack
 +
*Dryad private team list
 +
*Trello -- may use a pre-existing Trello account, or a new account based on the @datadryad.org email
 +
*FogBugz
 +
*Calendars -- Staff, Curation (if relevant)
 +
*keys and ID cards needed for physical access to Dryad space (if relevant)
 +
*update [[WG:Mailing Lists|mail aliases]] as required
 +
*update [http://datadryad.org/pages/whoWeAre#staff Website staff list]
 +
*access to [[Password Management]] system
 +
 
 +
== New staff should become familiar with ==
 +
 
 +
*The other Dryad staff
 +
*Strategic plan, development roadmap & NSF grant project description
 +
*Shared [https://drive.google.com/drive/u/0/folders/0B41Lvam80179fl9lLUtFS0Y4Wm5ZWXcycGEtME5xaGlHTDJUbm9WQjYwR1JUWFVzRlB4SVk Google Drive]
 +
*[https://drive.google.com/a/datadryad.org/file/d/0B41Lvam80179UDRkM205UGVEYUU/view?usp=sharing Personnel Policy Manual]
 +
*The wiki
 +
*The [[Grants]] that have funded Dryad development
 +
*[[Architecture Overview]]
 +
*[[Submission System Workflow]]
 +
*[https://docs.google.com/document/d/1OrIlrKvtuM1du70l3ap-36Bsc2abYssGpIhm24rRfV0/edit Curation Practices]
 +
*[[WG:Emergency|Emergency Contact Procedures]]
 +
*[[Using Trello]]
 +
*Basic Dryad submission workflow
 +
**Create a data package on the [http://staging.datadryad.org 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 [https://docs.google.com/document/d/19LGb1UwVuUccBmX46VvwKqQamkXScGfKVEGZaxr7gBc/edit Dryad Developer Retreat 2014]
  
 
See also: [[Staff Offboarding Checklist]]
 
See also: [[Staff Offboarding Checklist]]
 
+
[[Category:Project Management|Project_Management]]
[[Category:Project Management]]
 

Revision as of 06:21, 25 May 2016

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:

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 (no longer using)
  • Slack
  • Dryad private team list
  • Trello -- may use a pre-existing Trello account, or a new account based on the @datadryad.org email
  • FogBugz
  • Calendars -- Staff, Curation (if relevant)
  • keys and ID cards needed for physical access to Dryad space (if relevant)
  • update mail aliases as required
  • update Website staff list
  • access to Password Management system

New staff should become familiar with

If the staff member will be performing development, they should be trained on

See also: Staff Offboarding Checklist