Uvic-Robotics-Club/Tutorials

New member tutorial

Closed this issue · 0 comments

s-sparrow commented

What: Complete the following tutorial that will introduce you to Slack, CIRC, and github projects. Check-off each box as you complete the tasks.

Why: To introduce new members to our workflow.

Subtasks:

  • Since you are now starting this issue, go to the New Software Members project board and drag and drop this issue from ‘To Do’ to ‘In Progress’. When you are dragging and dropping, make sure to click on the white-space in the issue. Make sure that you are moving the issue that is assigned to you, and not someone else!

Slack

  • Get invitation and join our Slack channel.
  • Join the #software Slack channel.
  • Navigate to your profile settings: click on your name in the top left > click 'Profile & account' > click 'Edit Profile'
  • Add the name that you prefer to be called by as your ‘Display name’.
  • Add your full name to the 'Full name' section.
  • Add your position (for instance, “Software Member”) to the ‘What I do’ section.
  • Set your profile photo to a photo of yourself. This is extremely useful so that other team members can get to know your face/name. It also helps the Mechanical and Electrical teams find you if they need to contact you but don’t know your name yet.

Competition

  • Visit CIRC main page and watch the 2019 Canadian International Rover Challenge Wrap-Up Video on the main page
  • Visit CIRC competition tasks and read through all five of the CIRC 2020 Competition Tasks. To get you started, there is a short summary of these tasks in our #software Slack channel.

Software Team Plan

  • Navigate to the UVic Robotics organization projects page.
  • Look over the Rover Roadmap project board. This gives a broad overview of all of the components that are needed for us to enter the CIRC competition. It is a good idea to get familiar with it.
  • Look over the February Sprint project board. This is the workflow that our team will follow:
  1. To do: Holds issues that are yet to be started
  2. In progress: Holds issues that are currently in progress
  3. Review in progress: Holds issues that have an active pull request (you will learn about pull requests soon)
  4. Reviewer approved: Holds issues where all reviewers have approved the corresponding pull request
  5. Done: Holds issues that are completed and no longer require any more work.

By the end of February, all issues should be in the Done category.

  • Notice how some issues have someone assigned to them, which is signified by their Github profile picture in the bottom-right of the issue
  • Notice how some issues have labels (eg. High priority) attached to them
  • Click on the title text of any issue so that the issue’s preview pops up on the right-side of the screen. Then click on “Go to issue for full details” at the bottom of the page. This is what a full issue looks like, which a single member will work on.
  • If it is not obvious to others that your Github username matches you, then add (at least) your first name to your Github profile. This will make it easier to identify who is assigned to what issue.

Misc

  • Navigate back to the New Software Members project board and notice that your issue has a status bar, which corresponds to the number of subtasks you have checked-off. When you are assigned an issue with subtasks, make sure to check them off (at least) before weekly meetings. This helps your team lead track your progress.
  • If you have any questions or feedback about any of the above tasks, then message Sarah.
  • When you have checked off all of the boxes, navigate back to the project board that this issue is in and move the issue from ‘In progress’ to ‘Done’ :)