Difference between revisions of "Staff Onboarding Checklist"

From Dryad wiki
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
*add system architecture diagrams, which include everything from the [[Architecture Overview]] page.
 
*add system architecture diagrams, which include everything from the [[Architecture Overview]] page.
  
'''First:'''
+
== Accounts/access created by Dryad administrators ==
 
+
<ul style="line-height: 20.8px;">
*Email help@datadryad.org to request an @datadryad.org email address.
+
<li>'''FIRST''': &nbsp;<span style="line-height: 1.6;">Email help@datadryad.org to request an @datadryad.org email address.</span></li>
 +
<li>Slack</li>
 +
<li>Dryad private team email list</li>
 +
<li>Trello -- may use a pre-existing Trello account, or a new account based on the @datadryad.org email</li>
 +
<li>FogBugz</li>
 +
<li>Calendars -- Staff, Curation (if relevant)</li>
 +
<li>keys and ID cards needed for physical access to Dryad space (if relevant)</li>
 +
<li>payroll setup</li>
 +
<li>update&nbsp;[http://wiki.datadryad.org/WG%3AMailing%20Lists mail aliases]&nbsp;as required</li>
 +
<li>update&nbsp;[http://datadryad.org/pages/whoWeAre#staff Website staff list]</li>
 +
<li>access to&nbsp;[http://wiki.datadryad.org/Password%20Management Password Management]&nbsp;system</li>
 +
</ul>
  
 
== Accounts that the staff member must create ==
 
== Accounts that the staff member must create ==
Line 16: Line 27:
 
*Dryad Announce list -- sign up yourself (from Dryad homepage)
 
*Dryad Announce list -- sign up yourself (from Dryad homepage)
  
== Accounts/access created by Dryad administrators ==
+
== Resources with which new staff should become familiar ==
 
 
*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 [[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
 
*The other Dryad staff
Line 45: Line 43:
 
**Create a data package on the [http://staging.datadryad.org staging server] that includes at least two of the instructional documents listed above
 
**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 ==
+
=== If the staff member will be performing development, they should be trained on: ===
  
 
*The wiki
 
*The wiki

Latest revision as of 06:29, 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:

Accounts/access created by Dryad administrators

  • FIRST:  Email help@datadryad.org to request an @datadryad.org email address.
  • Slack
  • Dryad private team email 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)
  • payroll setup
  • update mail aliases as required
  • update Website staff list
  • access to Password Management system

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)

Resources with which new staff should become familiar

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

See also: Staff Offboarding Checklist