TWE: Research: Skills Issue: Onboard and Assess: Karen McCoy

[karenamccoy]

Overview

We need to get our team members familiar with GitHub and Google Drive for a better onboarding experience.

During these tasks you will be asked to refer to and/or add link to the Resources section, and that section is at the bottom of this comment (go view it now).

Note

While going through the action items, we need you to make new comments in this issue as practices when prompted. Please do not delete comments, but you may hide them if needed.

Important

Please keep track of the time you spend on each section of the issue because you need to leave comments on the time spent on each section and tally them up to update the size label of this issue once you finish all the action items.

Action Items

Table of Contents

Sections
1 - Joining the internship/TWE team
2 - Customize the GitHub issue
3 - Practicing Mardown
4 - Getting familiar with GitHub
5 - Locating a research plan folder from research wiki page
6 - Locating a research plan folder from a research plan's wiki page and summarizing the research plan
7 - Wrapping up
8 - Resources

1 - JOINING THE INTERNSHIP/TWE TEAM

• Add yourself to the #Internship Slack channel.

• Self assign this issue (gear in right side panel).

  • If there are no gears in the right side panel of this issue (next to Assignees, Labels, Projects, Milestone, Development):
  • Check if you are logged in to GitHub. (If not, you’ll see a Sign in button on the top right of this browser tab.)
    • If you are not logged in:
      • Log in and try to self assign again. If that does not work, continue with the instructions below.
    • If you are logged in:

      • Contact a team lead on the #Internship Slack channel with the following message:

        Hi. I don't see the gear on my issue, here are my details:
        - issue: #
        - GitHub handle:
        - date onboarded:
        - row on roster:
        

      • Add the following text to a comment on this issue:

        I don't have access, I have messaged a team lead in the Internship Slack channel.
        
        [return to section 1](#section-1)
        

• Post the following message in a comment below on this issue and then answer it.

  ### 1 - JOINING THE INTERNSHIP/TWE TEAM update
  >How many hours did it take you to finish this step?
  
  A:
  
  [return to section 1](#section-1)
  

⇧ Table of Contents

2 - CUSTOMIZING THE GITHUB ISSUE

• Practice navigating to sections of this issue comment using anchor links

  • Since it is your first issue, we included links for each section to help you navigate more efficiently. Now time to practice a bit.
  • Go to Table of Contents at the top, click on 3 - Practicing Markdown to see if it takes you to section 3.
  • Scroll to the end of section 3, and click on ⇧ Table of Contents to see if it takes you back to Table of Contents.

• Update the issue title

  • Search for [Replace brackets with your name] in the issue title
  • Choose Edit
  • Replace with your name
  • Choose Save to save the changes you made to the title

• Customize the issue settings (located in right side panel)

  • Under Labels, notice any labels that contain the word "missing". For example, size: missing.
  • Add the following labels because they are relevant to this issue.
    • feature: skills assessment
    • Participant Type: TWE Team Member
    • Role: UI/UX Research
    • Leave the size: missing label as it is for now and update the size label once you finish all action items in the issue.
      • Size labels are reflective of how much time you spend on each issue. For example, size: 1 pt is 6 hours, and size: 0.25pt is 1.5 hours. Please update the time spent on this issue once you complete this issue.
  • Under Projects, choose gear, choose "Repository," and choose TWE: Project Board.
  • Add the milestone: Project Management.
  • Go back to the Labels section, remove the corresponding labels that contain the word "missing" since you have just added the relevant labels and the milestone.
  • Move your issue from the Project Board's "New Issue Approval" column to the "In progress (actively working)" column.

• Post the following message in a comment below on this issue and then answer it.

  ### 2 - CUSTOMIZE THE ISSUE update
  >How many hours did it take you to finish this step?
  
  A:
  
  [return to section 2](#section-2)
  

⇧ Table of Contents

3 - PRACTICING MARKDOWN

• Open Resources 1.01 in a new tab to learn and practice doing the tasks below. Do each one in a comment on this issue, and check off the box after you’ve completed it.

• Headings: Create three different levels of headings (#, ##, ###) in a comment.

• Styling text: Write a sentence that includes bold, italic, strikethrough, and bold+italic in a comment.

• Blockquotes: Quote some text using > in a comment.

• Code block: Write a fenced code block (three backticks) with apples, oranges, grapes, and cherries on each line in a comment. It should look like this:

• Inline code: Copy the following sentence into a comment, and call out two commands, git commit and git add. It should look like this:

  The git commit command in Git serves to permanently record the changes that have been staged using git add into the local repository. 
  

• Color callout: Write a comment that includes a color code (e.g., `#0969DA`).

• Links: Write a comment that includes an inline link to Hack for La's website.

• Section links: Make a comment that includes a link that directs to Section links of Basic writing and formatting syntax(linked in Resources 1.01).

• Lists: Create both a bulleted list and a numbered list of at least three items.

• Nested lists: Create a list that has at least two levels of nesting.

• Task lists: Recreate a mini task list with at least two items.

• Mentions: Mention yourself (@yourusername) in a comment.

• Issue reference: Reference this issue by number (use #) in a comment.

• Emoji: Add at least two emoji to a comment (e.g., 🎉 ).

• Image: Add an image by linking to one online, or drag/drop into a comment.

• Paragraphs: Write two short paragraphs separated by a blank line.

• Footnote: Create a footnote in your comment using [^1].

• Ignore formatting: Write *Not italic* in a comment so the asterisks show literally.

• Post the following message in a comment below on this issue and then answer it.

  ### 3 - MARKDOWN PRACTICE update
  >How many hours did it take you to finish this step?
  
  A:
  
  [return to section 3](#section-3)
  

⇧ Table of Contents

4 - GETTING FAMILIAR WITH GITHUB

TWE Wiki

• Go to Resources 1.02 and open the link in a new tab
• Locate the Wiki tab at the top of the GitHub page
• Open the Wiki and copy the URL
  • Wiki is the project's knowledge base, where you can learn more about the project status, workflow, and documentation, etc.
• Go to Resources 2.01 and paste the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into an inline link (AKA a hyperlink).
• Choose "Save" in GitHub and make sure all the checkboxes above have been checked.
• Come back to the wiki page and glance through the page to see how it is structured.

TWE Overview Wiki Page, Join the Team Wiki Page, and Project Board

• Go to the Overview page under the TWE Team Member section
• Copy the URL of the Overview page
• Go to Resources 2.02 and paste the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into an inline link (AKA a hyperlink).
• Choose "Save" in GitHub and make sure all the checkboxes above have been checked.
• Read each section of the Overview page, including links that directs you to a different page from the Overview page.
  • The Overview page provides a basic introduction to the project as well as our workflow, expectations, etc.
  • If you have any questions regarding the project, please leave them in issue Get your Team Questions Answered here #59 (see Resources 1.03)
• Go to the Join the Team page at the end of the Overview page (under the Next steps for new team members section) or open the Join the Team page under the TWE Team Member section
• Copy the URL of the Join the Team page
• Go to Resources 2.03 and paste the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into an inline link (AKA a hyperlink).
• Choose "Save" in GitHub and make sure all the checkboxes above have been checked.
• Read each section of the Join the Team page, including links that directs you to a different page from the Join the Team page.
  • The Join the Team page provides more information regarding our workflow.
  • If you have any questions regarding the project, please leave them in issue Get your Team Questions Answered here #59 (see Resources 1.03)
  • In the How we work section,
    • Learn about Kanban and the guidelines we implement on the project based on the documentation on the page.
    • Check out TWE: Project Board, and there are two ways to access the Project Board:
      • Open the project board link under the How we work section;
      • Locate the Projects tab at the top of the GitHub page, and locate the TWE: Project Board.
    • Observe the Project Board and take notes on how it works based on the How we work section.
    • Copy the URL of the TWE: Project Board page
    • Go to Resources 2.04 and paste the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into an inline link (AKA a hyperlink).
    • Choose "Save" in GitHub and make sure all the checkboxes above have been checked.
      • Remember we asked you to put this issue into the In Progress column earlier? Hopefully it is making more sense to you now.
    • Provide a weekly update on the issue you are working on. Please copy the template we provided in the How we work section and make an update in a comment at the bottom of your issue now.
      • Please provide weekly updates on each issue you will be working on going forward.

TWE Wiki Page Based on Role

• When you finish reading the Join the Team page, scroll down to the end of the page to locate the Role section
• Open the dedicated role page based on your role
• Copy the URL of the dedicated role page
• Go to Resources 2.05, remove [Replace ROLE] and replace it with Research, so it should say [Research Wiki].
• Paste the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into an inline link (AKA a hyperlink).
• Choose "Save" in GitHub and make sure all the checkboxes above have been checked.
• Glance through the page to get familiar with it

TWE Issues

• Locate the Issues tab at the top of the GitHub page

• Open the Issues tab

• Learn and practice how to filter issues from the documentation listed in Resources 1.04.

• Apply the role: UI/UX Research label to filter the issues

• Copy the URL of the filtered results after the role: UI/UX Research label is applied

• Go to Resources 2.06 and paste the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into an inline link (AKA a hyperlink).

• Choose "Save" in GitHub and make sure all the checkboxes above have been checked.

• Post the following message in a comment below on this issue and then answer it.

  ### 4 - GETTING FAMILIAR WITH GITHUB update
  >How many hours did it take you to finish this step?
  
  A:
  
  [return to section 4](#section-4)
  

⇧ Table of Contents

5 - LOCATING A RESEARCH PLAN FOLDER FROM RESEARCH WIKI PAGE

• Open Resources 2.05 if it is not already open in another tab

• Open Google Drive/Research Folder under Research Assets section so you will be directed to the Google Drive's Research folder

• Open the folder named 2. Research by Plan # and Name

• Locate the folder of Research Plan 14 (RP014)

• Copy the link of the RP014 folder

  1. Choose the three vertical dots on the right side of the RP[Replace 000] folder
  2. Choose "Share"
  3. Choose "Get link"
  4. Choose "Copy Link" and "Done"

• In Resources # 2.07, place the link you just copied between parentheses at the end of the line so it turns into a clickable link.

• Choose "Save" in GitHub and make sure all the checkboxes above have been checked.

• Post the following message in a comment below on this issue and then answer it.

  ### 5 - LOCATING A RESEARCH PLAN FOLDER FROM RESEARCH WIKI PAGE update
  >How many hours did it take you to finish this step?
  
  A:
  
  [return to section 5](#section-5)
  

⇧ Table of Contents

6 - LOCATING A RESEARCH PLAN FOLDER FROM A RESEARCH PLAN'S WIKI PAGE AND SUMMARIZING THE RESEARCH PLAN

• Open Resources 2.05 if it is not already open in another tab

• Go to the Research Output Overview wiki page under Research Roadmaps & Research Plans Wiki Pages

  • Locate Intern research wiki page under Research Documents by Participant Type
  • Copy the link of the Intern research wiki page
  • In Resources # 2.08, place the link you just copied between parentheses at the end of the line so it turns into a clickable link.
  • Choose "Save" in GitHub and make sure all the checkboxes above have been checked.
  • Locate the wiki page of Research Plan 6 (RP006) under Individual research plans
  • Copy the link of the Research Plan 6's wiki page
  • In Resources # 2.09, place the link you just copied between parentheses at the end of the line so it turns into a clickable link.
  • Choose "Save" in GitHub and make sure all the checkboxes above have been checked.
  • Locate the research plan folder from RP006's wiki page
  • Copy the shareable link
  • In Resources # 2.10, place the link you just copied between parentheses at the end of the line so it turns into a clickable link.
  • Choose "Save" in GitHub and make sure all the checkboxes above have been checked.

• Read through each section of RP006's wiki page, and provide a summary of Research Plan 006's research goals and progress/status (what has been done, what hasn't, etc.) as part of the comment below.

• Post the following message in a comment below on this issue and then answer the questions.

  ### 6 - LOCATING A RESEARCH PLAN FOLDER FROM A RESEARCH PLAN'S WIKI PAGE AND SUMMARIZING THE RESEARCH PLAN update
  >Under which section did you find RP006's Google Drive research folder on this wiki page?
  
  A:
  
  >What are Research Plan 006's research goals and progress/status (what has been done, what hasn't, etc.) according to the wiki page?
  
  A:
  
   >How many hours did it take you to finish this step?
  
  A:
  [return to section 6](#section-6)
  

⇧ Table of Contents

7 - Wrapping up

• Calculate how many hours you have spent working on this issue based on your comments on each section, and updated the size of this issue by choosing the appropriate size label.
• Once you’ve finished, put this issue in the Questions/Review column, and leave a comment and @ message the lead(s) you report to in this issue to notify them that you have completed the issue.
• The lead(s) reviews the issue and comments and provides feedback.
• Assignee revises and/or edits the issue based on feedback.
• We will confirm your onboarding is complete once all action items and comments pass the review.

⇧ Table of Contents

8 - Resources

Resources for creating this issue

• 1.01 GitHub: Basic writing and formatting syntax
• 1.02 Internship/TWE on GitHub
• 1.03 Get your team questions answered here
• 1.04 Filtering and searching issues and pull requests

Resources gathered during the completion of this issue

• 2.01 Internship/TWE Wiki
• 2.02 Internship Volunteer Overview
• 2.03 Join the Team
• 2.04 TWE: Project Board
• 2.05 Research Wiki
• 2.06 Filtered Issues: UI/UX Research
• 2.07 RP014 Research Folder
• 2.08 Intern Research Overview Wiki Page
• 2.09 Research Plan 6: Intern Intake Interviews Wiki Page
• 2.10 Research Plan 6: Intern Intake Interviews Research Folder

⇧ Table of Contents

[pandanista]

@karenamccoy: Please provide update:

1. Progress: "What is the current status of your project? What have you completed and what is left to do?" - we know you just came back from break, please just summarize the progress from before then
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.

[karenamccoy]

1 - JOINING THE INTERNSHIP/TWE TEAM update

How many hours did it take you to finish this step?

A: 1 hour

return to section 1

[karenamccoy]

@pandanista : Update:

1. Progress: just finished the first section and I am currently working on this.
2. none
3. availability: I have about 5 hours this week to work on this issue.
4. ETA: I expect to have this finished by Sunday morning.