Skip to content

Onboarding checklist for new comers due 4/18

该描述提供简版checklist，每一条checklist对应的具体内容仍需在此处自行查阅，包括role和warm up task的内容。

这个issue底下是每个新人建立自己的Onboarding checklist的位置，新建方式为在底下评论区评论。【不要直接对着描述里的内容打勾，在自己的评论里直接打勾即可】，以免影响他人复制。

不要太依赖翻译功能，如果使用机翻，要注意任务内容是否理解准确

meeting timeline (UTC+8):

Weekday Mon. Tue. Wed. Thu. Fri. Sat.
AM 10:00 10:00 9:00 9:00 9:00 11:00
PM 9:00 9:00 9:00 9:00 9:00 -

checklist模板如下，直接复制描述中的文字粘贴即可，一次复制完所有天数的checklist。Gitlab可自动将文字转成Markdown语法格式：

pre-day：

  1. Attend the MindCoord Welcome Meeting.
  2. Send contracts with your signature to wolfie@mindcoord.com.
  3. Read the Human Resources Policy and Procedure Manual.
  4. Sign the Employee Handbook Receipt Acknowledgment and send it to wolfie@mindcoord.com.
  5. In MindCorrd, all documents should be written in markdown format, if you're new to markdown, please read this and practice it, it would help you a lot in your regular job. Here is the style guide for all documents in MindCoord.
  6. Team members working in China only: Apply VPN from DingTalk "OA工作台"->"OA审批"->"物品领用", Choose "郭培智" from "Athena" as the application reciever.
  7. Get a connection to your chatting buddy assigned by your onboarding assistant. You must finish a chatting task before your final report day. Feel free to chat and it's nothing you need to worried about your job.
  8. Install necessary software for work. All the related information is listed on Software Standard.
  9. Connect with or follow mindcoord's social media sites: LinkedIn, Twitter and YouTube. (Send a screenshot to your onboarding assistant on DingTalk)
  10. Update your LinkedIn profile to reflect your new position with mindcoord. (Send a screenshot to your onboarding assistant on DingTalk)
  11. Pay attention to your first daily meeting, it will be started tonight (Beijing Time Zone).
  12. Sign up on https://git.mindcoord.com. (Use your official email address, @binarygrow or @mindcoord)

day1：

  1. Attend the meeting of Workflow in MindCoord.

  2. Learn workflow in MindCoord from the workflow meeting. Tutorial of SourceTree can be learned from here.

  3. For those new to Git and Gitlab, it's important to get familiar with the below and guide for git. You're not expected to become a GitLab master in a day, but to understand that the below is a key reference as you acclimate.

  4. Finish the "First Step" task.

    issue:

    • Epic: "first step"(Jump from here if you want to create an issue directly from an epic)
    • Issue title is required (no less than 15 characters)
    • Description is required, and the content is about your first GitLab trial
    • Assignee: yourself
    • Milestone: "first step"
    • Label: "working on it"
    • Weight: 1
    • Due date: August 8, 2030
    • Close the issue after submitting your MR, and leave a comment to refer to your MR, which approves you to close this issue (!Important!: In the real workflow, you can only close your issue after you receive your MR approval! This step is only for practice)

    branch:

    • Name: dev_XXX (your first name) (if there is a duplicate name, add any number from 0 to 99)
    • Create a folder named "folder2"
    • Create a markdown file named "my-first-step" in folder2. Use markdown syntax write your impression of MindCoord in 3 items on the created markdown file
    • Exchange the files according to the name of the files
    • Don't change or add or delete anything not mentioned above

    MR:

    • Title is required (no less than 15 characters)
    • Description is required, and the content is arbitrary (must refer to the issue you created; must @your onboarding assistant)
    • Assignee: yourself
    • Approvers: your onboarding assistant received:
    • If you receive an MR approval email, then the task has been finished.

  5. Particularly if you're new to working in a 100% remote environment, read over our Guide for starting a new remote role. You'll find other tips for operating (and thriving!) in an all-remote setting within the All-Remote section of our handbook.

  6. Learn our commit rules from here.

  7. When you are first starting at MindCoord and creating new merge requests, you can assign the MRs to your manager. Going forward, it's best practice to assign the MR to the relevant department; for example, if you are making an edit to the People Experience section of the handbook, please assign it to someone within People Experience. If you're unsure of who to assign a merge request to or if you have any questions or problems, feel free to reach out to your manager or onboarding buddy. Please see permission levels chart to find out more about what each level can do.

  8. If you get a conflict when merging the branch, learn the solution from here.

  9. Read your role and start your Warm up task(check Day1- Remote Work Getting Started).

day2-4：

  1. Finish your chatting task with your chatting buddy.
  2. Still, Warm up task(check Day1- Remote Work Getting Started).

day5：

  1. Make a presentation for your onboarding task.
  2. Finish the questionnaire of The first week of onboarding after your final report.
Edited by GinLu