WIP: Develop a fuller onboarding process
To better help our new hires (and potentially our existing engineers) be ready for the wide range of topics they will encounter here at GitLab, we want to revamp the Onboarding process to cover more areas and better help our engineers succeed.
-
Determine all areas that training is needed on (#1594 (closed)) -
Determine the methods to tackle each area - Current ideas include:
- Training Videos
- Documentation
- Basic troubleshooting scenarios
- Current ideas include:
-
Make a project that contains an issue board with the various modules to complete - Concept: Have new hire use an import of said project to work through an issue board on their GitLab account
- WIP Demo of it can be found here
-
Get issue boards importable/exportable (MR) -
Determine which areas are Core, Secondary, or Tertiary -
Complete Core issues - #1678 (closed)
- #1679 (closed)
- #1680 (closed)
- #1680 (closed)
- #1681 (closed)
- #1682 (closed)
- #1683 (closed)
- #1684 (closed)
- #1685 (closed)
- #1686 (closed)
- #1687 (closed)
- #1688 (closed)
- #1689 (closed)
- #1690 (closed)
- #1691 (closed)
- #1692 (closed)
- #1693 (closed)
- #1694 (closed)
- #1695 (closed)
- #1696 (closed)
- #1697 (closed)
- #1698 (closed)
- #1916 (closed)
-
Complete Secondary issues -
Complete Tertiary issues -
Determine any documentation that is missing, incomplete, inaccurate, etc. -
Generate videos to help with various areas -
Utilize epics for group/personal level burndown -
Generate README to explain the process and the like #1699 (closed) -
Make Issue Boards Exportable/Importable (Merge Request)
Edited by Jason Colyer