Onboarding task presets/templates

[lwsanty]

Pre-history

1. a couple of months ago @bluer73 started a practice of one month post-onboarding feedback call
2. often developers have onboarding tasks that help them to be involved into process more smoothly
3. current repo with guides(from code conventions to company culture) that we refer freshmen to
4. additional info can be obtained via direct texting with the team(s)

Problems

• on the first day of work employee doesn't know which slack channels are required
• sometimes employee does not know which repositories relate to the team, which ones are abandoned, deprecated etc(for instance not all our frozen repos are marked as deprecated)
• sometimes employee does not pay too much attention to find the following info in guides:
  1.1) code conventions
  1.2) CI requirements
  1.3) who's in charge for repos creation

...and so on.

This leads to overcome through mistakes path. I believe we can workaround it.

Possible solution that could ease onboarding routine

We can create onboarding tasks template that will gather most of the required info for development at one place, so we could minimize the following questions amount.

Template should be created for each team.

Template's content

TBD, I wanted this issue to be a field of discussion

Abstractly it could look like this:

Team slack channels: @dev-..., @su-...
Required slack channels: ...
Team lead: ...
Repositories your team is working on:...

Onboarding task: #1234
Please take this info into account:
- you need to create a repository/to work with this repository, to make it happen...
- you may need to access cluster(link to manual), and contact infra team(@infras-channel)
- current repository is written in go, please consider using this convention (link)
- you need to setup CI for current repository, we do it in a such way (link)
- policy of PR reviews (link)
- docs
...

Advantages

• employee will have a cheat-sheet with all required info
• code review troubles will be minimized
• saved time for those who ask and answer questions

Disadvantages

It may be non-constant sometimes, depending on the specification of the issue, but we can generalize it in some way.

[bluer73]

@lwsanty really good idea- I can work with each team lead on this and then make sure they are as generalised as possible overall