Joining the Team - hackforla/internship GitHub Wiki

Introduction

Welcome to the internship team. This guide will help get you up to speed on what you need to know to get started as a project team member.


Joining the Internship team

  1. You are welcome to join the team if we have an open role on one of the Community of Practices Open Roles boards.
  2. Make sure that you can make the appropriate meeting times.
  3. Join the internship Slack channel and introduce yourself.
  4. Slack us in the #internship channel with your Gmail address and we will setup an onboarding session for you which will include:
    1. Adding you to our Shared Google Drive
    2. You filling out the roster
    3. Adding you to GitHub
    4. Adding you to Figma
    5. Adding you to 1Password if needed
  5. Review our Standard Issue Format, so that you know how to read issues

Meeting Times

Our meeting times can be found on the HfLA website, TechWorkExperience page

  • Please note that any meetings that fall on the 1st through the 7th are leads only planning.

How we work

  • our GitHub project board uses Kanban automation and methodology
  • Read the Guide: Kanban for Successful Open Source Projects (WIP)
  • Follow these tips and guidelines
    1. Items in the prioritized backlog column are not assigned yet

    2. Items that are assigned should be in the In progress column

    3. Only one person should be assigned to each issue (exception: multiple people can be assigned to an agenda)

    4. Only one issue should be assigned to a person (exception: you can be assigned also to agendas)

    5. All issues will have helpful links. When you are assigned to an issue, look for the Resources section.

      1. Tip: Use two windows side by side. One with the issue open and the other one with resource links displayed to avoid back and forth. To prevent loss of work, refresh both windows after each edit.
    6. Any links to materials you create or find while working on the issue should be added to the Resources section.

    7. If there are questions needed (i.e., you have a blocker, then you can put the issue in the questions and review column with a note about what you need as the last comment). Please do not assign the person you need help from to the issue. This is how Bonnie got assigned to 100 issues. 💀

    8. Provide weekly updates (in comments at the bottom of your issue) using this template

      Please provide update
      1. Progress: 
      2. Blockers: 
      3. Availability:
      4. ETA: 
      5. Pictures (if necessary): 
      
      How to fill out the template

      Please provide update Progress: "What is the current status of your project? What have you completed and what is left to do?" Blockers: "Difficulties or errors encountered." Availability: "How much time will you have this week to work on this issue?" ETA: "When do you expect this issue to be completed?" Pictures (if necessary): "Add any pictures that will help illustrate what you are working on."

    9. Review your notes with the team at team meetings.

Role

⚠️ **GitHub.com Fallback** ⚠️