Prerequisite

Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page and attend an onboarding session.
Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

We need to update the prework checklist issue to provide current and relevant information to junior developers.

Action Items

[x] Navigate to .github/ISSUE_TEMPLATE/pre-work-template--dev.md
[x] Replace the contents with the text provided in the Resources/Issue Template Text section below
[x] Test the updated template using these instructions. Copy the contents of that comment into a new comment in this issue, and check off the boxes as you complete the steps.

For PR Reviewers and Merge Team To review this issue, click the link below under "Link for reviewers" and verify that the labels match the updated labels string in the issue.

Link for Reviewers This URL will be inserted by the dev during the test process and will be used by reviewers to preview the updated template. URL of the issue branch on the test Repository: [REPLACE THIS TEXT AND BRACKETS WITH THE URL]

For PM, Merge Team, or Tech Lead

[ ] Once the pull request associated with this issue is approved and merged, please update and edit epic #4307 by
- [ ] Checking off the dependency for this issue
- [ ] If all dependencies are checked off, please move issue to the New Issue Approval column and remove the Dependency label

Resources

Issue Template Text

### Prerequisite
We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

### Overview
As a new developer on the HfLA website team, fill in the following fields as you complete each onboarding item.

### Special Notes
 
1. Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues.  Do not close this issue. 
2. The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.  

### Action Items

- [ ] To find contact information for the merge team members and technical leads, please take a look at our [Meet the Team wiki page](https://github.com/hackforla/website/wiki/Meet-the-Team)
- [ ] Register for Zoom meetings using the form at [NEED TO FILL IN THE URL TO ZOOM REG FORM]
- [ ]  If you have not done so already, add yourself to the [team roster](https://docs.google.com/spreadsheets/d/11u71eT-rZTKvVP8Yj_1rKxf2V45GCaFz4AXA7tS_asM/edit#gid=0)
- [ ] Self Assign this issue (gear in right side panel).  
    - [ ] If there are no gears in the right side panel, contact a merge team member or technical lead and ask them to check your membership in the `website-write` and `website` teams on GitHub.
- [ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
- [ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
- [ ] Signup for a [Figma](https://Figma.com) account
- [ ] Attend weekly team meetings:
  - [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
  - [ ] (Optional) Office Hours, Thursdays 7-8pm PST
  - [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
- [ ] Note: There are no meetings on the 1st-7th of every month.
- [ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
- [ ] Complete steps 1.1 - 1.6 in [Part 1: Setting up the development environment within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-1-setting-up-the-development-environment)
  - [ ] OPTIONAL: If you run into any issues, use [4.1 How do I ask for help within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#41-what-do-i-do-if-i-need-help) as a visual example to get a hold of our [HfLA website leadership team](https://github.com/hackforla/website/projects/7#card-69730135). That way we can help you resolve any set up issues immediately.
- [ ] Read section 2.1 - 2.4 in [Part 2: How the Website team works with GitHub issues within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-2-how-the-website-team-works-with-github-issues)
  - [ ] Follow the steps in section [2.3 Where can I find GitHub issues to work on?](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#23-where-can-i-find-github-issues-to-work-on) to assign yourself your first issue under the Project Board's Prioritized Backlog column and use [2.7 Working on a Issue within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#27-working-on-an-issue) to start working on your issue
  - [ ] Read [2.6 What to do when you need to stop mid issue](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#26-what-to-do-when-you-need-to-stop-mid-issue)
- [ ] Once you take a good first issue, you will provide estimates and progress reports. Also, once you finish providing your "Estimate" action item below, please answer the question in the "Time spent so far" action item (also below).
   - [ ] Estimate: Copy the below and put it in the "good first issue" that you picked.
 Check this box when you have completed this task so that we can identify if you understood the instructions and know what to do on all subsequent issues upon assignment. (Note: Please provide estimates on all the issues that you pick up, going forward.)
    ```
   Availability for this week:
   My estimated ETA for completing this issue:
    ```
   - [ ] Time spent so far: Copy the question below into a new comment below (in this pre-work issue only) and answer it. This is just to get feedback on how long it took you to get to this point on this pre-work. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.
    ```
    How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
    ```
   - [ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report.  If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. **This update should be done every week for every issue that you are assigned to**. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
    ```
    Provide Update
    1. Progress
    2. Blockers
    3. Availability
    4. ETA
    ```
- [ ] Read sections 3.1.a - 3.1.c in [3.1 How to make a pull request](https://github.com/hackforla/website/blob/2e3c45fede99e61f479548ccca3f0dda83e351db/CONTRIBUTING.md#31-how-to-make-a-pull-request) to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
- [ ] Additional notes:
   - [ ] Please don't forget to review pull requests whenever you are able to.  The [How to review Pull Requests](https://github.com/hackforla/website/wiki/How-to-review-pull-requests) guide will teach you how to review pull requests.
   - [ ] Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
- [ ] Read and understand how we progress through issues. Then, you can check this off.
Progress through issues in the [prioritized backlog](https://github.com/hackforla/website/projects/7#column-7198257) only with increasing complexity in the following order:
  - Good first issue (two per person)
  - Small (one per person, with some exceptions, see below)
  - Medium (one per person, with some exceptions, see below) 
  - Large (you can work on more than one large issue, but only one at a time)
    - The reasons for this progression are:
      - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
      - We are trying to teach you the team methodology through the issues themselves.
      - It ensures you understand what we expect and the quality of contributions.
    - You can work on back-to-back small issues if it meets the following criteria:
      - You are learning something new and need to work on an issue of a lesser complexity
      - Special request by a lead or pm
    - You can work on a second medium issue if it meets the following criteria:
      - You are learning something new and need to work on an issue of a lesser complexity
      - Special request by a lead or pm
- [ ] Read the [Start Here - Developers](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=8583%3A0) in Figma
- [ ] Go familiarize yourself with the [Hack for LA Design System page in Figma](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3)  (where you can see components and their SCSS classes)


### What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?
- First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
- Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
- Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
- Lastly, you can add the issue to the "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

### Resources/Instructions
- [Contributing.md - Hack for LA](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md)
- [GitHub Project Board - Hack for LA](https://github.com/hackforla/website/projects/7)
- [GitHub Project Board Prioritized Backlog highlighted and sorted by Front End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+front+end%22)
- [GitHub Project Board Prioritized Backlog highlighted and sorted by Back End/DevOps](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22)
- [Figma - Hack for LA](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website)
- [Google Drive - Hack for LA website team](https://drive.google.com/drive/folders/1p76K0FgfiAWeIIEyoyJ_Iik8FVj8cBjT?usp=sharing)
- [Agenda / Notes - Dev Team Tuesday meeting](https://github.com/hackforla/website/issues/2010)
- [Agenda / Notes - All Team meeting](https://github.com/hackforla/website/issues/2027)
- [How to review Pull Requests](https://github.com/hackforla/website/wiki/How-to-review-pull-requests)

Jul 13 '23 02:07 roslynwythe

@ExperimentsInHonesty here is the text with strikethrough marks displayed to make it easier for you to review.

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a new developer on the HfLA website team, fill in the following fields as you complete each onboarding item.

Special Notes

1. It may take you a few weeks to finish this issue, because part of it is learning how to provide updates on issues that take more than a week to complete. Please keep this issue open until you have been able to do all the steps. 2 1. Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues. Do not close this issue. 3 2. The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.

Action Items

[ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
[ ] Share your GitHub handle and Gmail address in the hfla-site-onboarding slack channel so you can be added to the Google Drive (alternative to go to meeting and direct message a merge team member at the meeting)
- [ ] To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page
[ ] ~~Also, confirm with a merge team member or a technical lead that they have added you to the Google Calendar invites for our Zoom meetings~~ Register for Zoom meetings using the form at [NEED TO FILL IN THE URL TO ZOOM REG FORM]
[ ] ~~(Once added to the Drive) Add yourself to the team roster~~ If you have not done so already, add yourself to the team roster
[ ] After you have finished adding yourself to the roster, let a merge team member or a technical lead know you have added yourself to the roster and would like to be added to the website-write and website teams on GitHub.
[ ] ~~Once added to the website-write team:~~
- [ ] Self Assign this issue (gear in right side panel).
  - [ ] If there are no gears in the right side panel, contact a merge team member or technical lead and ask them to check your membership in the website-write and website teams on GitHub.
- [ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
- [ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
[ ] Signup for a Figma account
[ ] Attend weekly team meetings:
- [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
- [ ] (Optional) Office Hours, Thursdays 7-8pm PST
- [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
[ ] Note: There are no meetings on the 1st-7th of every month.
[ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
[ ] Complete steps 1.1 - 1.6 in Part 1: Setting up the development environment within Contributing.md
- [ ] OPTIONAL: If you run into any issues, use 4.1 How do I ask for help within Contributing.md as a visual example to get a hold of our HfLA website leadership team. That way we can help you resolve any set up issues immediately.
[ ] Read section 2.1 - 2.4 in Part 2: How the Website team works with GitHub issues within Contributing.md
- [ ] Follow the steps in section 2.3 Where can I find GitHub issues to work on? to assign yourself your first issue under the Project Board's Prioritized Backlog column and use 2.7 Working on a Issue within Contributing.md to start working on your issue
- [ ] Read 2.6 What to do when you need to stop mid issue
[ ] Once you take a good first issue, you will provide estimates and progress reports. Also, once you finish providing your "Estimate" action item below, please answer the question in the "Time spent so far" action item (also below).
- [ ] Estimate: Copy the below and put it in the "good first issue" that you picked. Check this box when you have completed this task so that we can identify if you understood the instructions and know what to do on all subsequent issues upon assignment. (Note: Please provide estimates on all the issues that you pick up, going forward.)
```
Availability for this week:
My estimated ETA for completing this issue:
```
- [ ] Time spent so far: Copy the question below into a new comment below (in this pre-work issue only) and answer it. This is just to get feedback on how long it took you to get to this point on this pre-work. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.
```
How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
```
- [ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
```
Provide Update
1. Progress
2. Blockers
3. Availability
4. ETA
```
[ ] Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
[ ] Additional notes:
- [ ] Please don't forget to review pull requests whenever you are able to. The How to review Pull Requests guide will teach you how to review pull requests.
- [ ] Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
[ ] Read and understand how we progress through issues. Then, you can check this off. Progress through issues in the prioritized backlog only with increasing complexity in the following order:
- Good first issue (~~one~~ two per person)
- ~~Good second issue (one per person)~~
- Small (one per person, with some exceptions, see below)
- Medium (~~you can work on more than one medium issue, but only one at a time~~one per person, with some exceptions, see below)
- Large (you can work on more than one large issue, but only one at a time)
  - The reasons for this progression are:
    - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
    - We are trying to teach you the team methodology through the issues themselves.
    - It ensures you understand what we expect and the quality of contributions.
  - You can work on back-to-back small issues if it meets the following criteria:
    - You are learning something new and need to work on an issue of a lesser complexity
    - Special request by a lead or pm
  - You can work on a second medium issue if it meets the following criteria:
    - You are learning something new and need to work on an issue of a lesser complexity
    - Special request by a lead or pm
[ ] Read the Start Here - Developers in Figma
[ ] Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)
[ ] Once all tasks are completed, close this issue. This issue will remain open until you get through your first progress report. Once you have done that, we are confident you know how to keep the momentum going on your issue and keep your team informed.

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
Lastly, you can add the issue to the ~~"Development team meeting discussion items"~~ "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

Resources/Instructions

Jul 13 '23 04:07 roslynwythe

Bonnie's Draft -WIP. Will tell you when I am done

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a new developer on the HfLA website team, fill in the following fields as you complete each onboarding item.

Special Notes

This issue will stay open for as long as you are on the Website team. Use it as a place to indicate that you have completed a level as well as get instructions on how to progress.
Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues. Do not close this issue.
The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.

Action Items

[ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
[ ] Share your GitHub handle and Gmail address in the hfla-site-onboarding slack channel so you can be added to the Google Drive (alternative to go to meeting and direct message a merge team member at the meeting)
- [ ] To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page
[ ] ~~Also, confirm with a merge team member or a technical lead that they have added you to the Google Calendar invites for our Zoom meetings~~ Register for Zoom meetings using the form at [NEED TO FILL IN THE URL TO ZOOM REG FORM]
[ ] ~~(Once added to the Drive) Add yourself to the team roster~~ If you have not done so already, add yourself to the team roster
[ ] After you have finished adding yourself to the roster, let a merge team member or a technical lead know you have added yourself to the roster and would like to be added to the website-write and website teams on GitHub.
[ ] ~~Once added to the website-write team:~~
- [ ] Self Assign this issue (gear in right side panel).
  - [ ] If there are no gears in the right side panel, contact a merge team member or technical lead and ask them to check your membership in the website-write and website teams on GitHub.
- [ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
- [ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
[ ] Signup for a Figma account
[ ] Attend weekly team meetings:
- [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
- [ ] (Optional) Office Hours, Thursdays 7-8pm PST
- [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
[ ] Note: There are no meetings on the 1st-7th of every month.
[ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
[ ] Complete steps 1.1 - 1.6 in Part 1: Setting up the development environment within Contributing.md
- [ ] OPTIONAL: If you run into any issues, use 4.1 How do I ask for help within Contributing.md as a visual example to get a hold of our HfLA website leadership team. That way we can help you resolve any set up issues immediately.
[ ] Read section 2.1 - 2.4 in Part 2: How the Website team works with GitHub issues within Contributing.md
- [ ] Follow the steps in section 2.3 Where can I find GitHub issues to work on? to assign yourself your first issue under the Project Board's Prioritized Backlog column and use 2.7 Working on a Issue within Contributing.md to start working on your issue
- [ ] Read 2.6 What to do when you need to stop mid issue
[ ] Once you take a good first issue, you will provide estimates and progress reports. Also, once you finish providing your "Estimate" action item below, please answer the question in the "Time spent so far" action item (also below).
- [ ] Estimate: Copy the below and put it in the "good first issue" that you picked. Check this box when you have completed this task so that we can identify if you understood the instructions and know what to do on all subsequent issues upon assignment. (Note: Please provide estimates on all the issues that you pick up, going forward.)
```
Availability for this week:
My estimated ETA for completing this issue:
```
- [ ] Time spent so far: Copy the question below into a new comment below (in this pre-work issue only) and answer it. This is just to get feedback on how long it took you to get to this point on this pre-work. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.
```
How many hours did it take you to finish the pre-work up to and including adding your initial ETA and availability for your good first issue, including attending your first meetings?
```
- [ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
```
Provide Update
1. Progress
2. Blockers
3. Availability
4. ETA
```
[ ] Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
[ ] Additional notes:
- [ ] Please don't forget to review pull requests whenever you are able to. The How to review Pull Requests guide will teach you how to review pull requests.
- [ ] Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
[ ] Read and understand how we progress through issues. Then, you can check this off. Progress through issues in the prioritized backlog only with increasing complexity in the following order:
- Good first issue (~~one~~ two per person)
- ~~Good second issue (one per person)~~
- Small (one per person, with some exceptions, see below)
- Medium (~~you can work on more than one medium issue, but only one at a time~~one per person, with some exceptions, see below)
- Large (you can work on more than one large issue, but only one at a time)
  - The reasons for this progression are:
    - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
    - We are trying to teach you the team methodology through the issues themselves.
    - It ensures you understand what we expect and the quality of contributions.
  - You can work on back-to-back small issues if it meets the following criteria:
    - You are learning something new and need to work on an issue of a lesser complexity
    - Special request by a lead or pm
  - You can work on a second medium issue if it meets the following criteria:
    - You are learning something new and need to work on an issue of a lesser complexity
    - Special request by a lead or pm
[ ] Read the Start Here - Developers in Figma
[ ] Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)
[ ] Once all tasks are completed, close this issue. This issue will remain open until you get through your first progress report. Once you have done that, we are confident you know how to keep the momentum going on your issue and keep your team informed.

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
Lastly, you can add the issue to the ~~"Development team meeting discussion items"~~ "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

Resources/Instructions

Jul 23 '23 18:07 ExperimentsInHonesty

This link but added to the project board, would show anyone who needs to write issues, which ERs are ready for that ISSUE Tab Project Board

Nov 14 '23 02:11 ExperimentsInHonesty

@roslynwythe

I am still working on this draft, but this is what I accomplished on the plane. Additional items I plan to incorporate

[x] finish the issue ladder
[ ] add in making issues
[ ] have them express interest in joining the merge team at a specific spot
[ ] have them check off items on self assessment
- [ ] at onset
- [ ] ongoing

Details

Bonnie's Draft -WIP. Will tell you when I am done

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a developer on the website team this issue will be your companion and a place to track your progress with the path we have set out for you.

Special Notes

This issue will stay open for as long as you are on the Website team. Use it as a place to indicate that you have completed a level as well as get instructions on how to progress.
Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues. Do not close this issue until you leave the team (see todo items associated with leaving professionally)
The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.
During the General Hack for LA onboarding, you will be directed to fill out a form that will add you to the website team roster, google drive and GitHub teams. If you have not done that yet, you will not be able to do the action items in section 1.0
- [WE NEED TO WRITE AN AUTOMATION THAT ADDS PEOPLE TO THE ROSTER AUTOMATICALLY]

Action Items

1.0 JOINING THE WEBSITE TEAM.

[ ] Self Assign this issue (gear in right side panel).
- [ ] If there are no gears in the right side panel, contact a merge team member or technical lead and ask them to check your membership in the website-write and website teams on GitHub.
[ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
[ ] Register for Zoom meetings using the form at [NEED TO FILL IN THE URL TO ZOOM REG FORM]
[ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
[ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
[ ] Signup for a Figma account

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

### 1.0 JOINING THE WEBSITE TEAM update
>How many hours did it take you to finish this step?

2.0 TEAM MEETINGS

[ ] Attend weekly team meetings:
- [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
- [ ] (Optional) Office Hours, Thursdays 7-8pm PST
- [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
[ ] Note: The meetings the the 1st-7th of every month are plannign meetings for leads and merge team You are welcome to observe but we don't provide team member support.
[ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.

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

### 2.0 TEAM MEETINGS update
>which meetings did you register for
 - [ ] Developer (front-end/back-end)
 - [ ] (Optional) Office Hours
 - [ ] All team meeting 
>When did you attend your first team meeting?

3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP

[ ] Complete steps 1.1 - 1.6 in Part 1: Setting up the development environment within Contributing.md
- [ ] OPTIONAL: If you run into any issues, use 4.1 How do I ask for help within Contributing.md as a visual example to get a hold of our HfLA website leadership team. That way we can help you resolve any set up issues immediately.
[ ] Post the following message in a comment below on this issue and then answer it. While keeping in mind that this is just to get feedback on how long it took you to get to this point. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace. Getting your dev enviorment setup will be easier for some people because they might already have some experience or items installed on their computer and you may not. This is an important step, be patient with yourself and your computer but keep on it till you get it done.
```
### 3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP update
>How many hours did it take you to finish this step?
```

4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE

[ ] Read section 2.1 - 2.4 in Part 2: How the Website team works with GitHub issues within Contributing.md
- [ ] Follow the steps in section 2.3 Where can I find GitHub issues to work on? to assign yourself your first issue under the Project Board's Prioritized Backlog column and use 2.7 Working on a Issue within Contributing.md to start working on your issue
- [ ] Read 2.6 What to do when you need to stop mid issue
Once you self assign an issue, an automation will post a welcome meesage in a comment giving you additional guidance on to manage your issue (includes how to provide estimates and progress reports there).
- [ ] On assignment, you will be prompted to estimate Availability and ETA. Once you have done that on your good first issue, check this box on this issue to let us know you have completed that task and understand how to do it in future. If you hae any questions about estimating the issue you choose, please add them to the issue, put the issue in the questions/review column, and add the label ready for dev lead and help wanted
  
  Availability for this week:
  
  My estimated ETA for completing this issue:
[ ] Post the following message in a comment below on this issue and then answer it.
```
### 4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE update
>How many hours did it take you to finish this step?
```
5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENTT ISSUES
- [ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
```
Provide Update
1. Progress
2. Blockers
3. Availability
4. ETA
```
- [ ] Post the following message in a comment below on this issue and then answer it.
```
### 5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENTT ISSUES update
>on what issue did you give your first weekly update?
- #
```

6.0 PULL REQUESTS

[ ] Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
[ ] Additional notes:
- [ ] Please don't forget to review pull requests whenever you are able to. The How to review Pull Requests guide will teach you how to review pull requests.
- [ ] Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
- [ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.
```
### 6.0 PULL REQUESTS update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>Wwhat is the number of your first merged pull request?
- #
```

7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES

[ ] Read the Start Here - Developers in Figma
[ ] Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)

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

### 7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEXT ISSUESupdate
>How many hours did it take you to finish this step?
>Do you have any questions about what you read?
   - [ ] yes, I had questions, and I left comments in the approatte issues [WE NEED TO UPDATE THOSE TWO RESROUCES TO HAVE LINKS TO ISSUES WHERE PEOPLE CAN PUT QUESTIONS AND MOVE THE ISSUES TO THE QUESTIONS/REVIEW COLUMN]
   - [ ] no, I did not have any questions

8.0 MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)

Do another Good first issue (two per person total). We have you do another simple issue becaues this we want you to
- see the difference once you have sucessfull setup your dev enviornment
- see how each PR gets eaiser to do with repetion
- make sure you know how to branch propertly (most problems show up in the second commit)

[ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.

### 8.0 MOVE ON TO 2ND GOOD FIRST ISSUE update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>Wwhat is the number of your 2nd merged pull request?
- #

9.0 UUNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIOIRTIZED BACKLOG AND ON ISSUE MAKING AND TEMPER CHECK

Congrats on making it this far. Issues get more complicated from here, either they include more changes, or have several files to change or you have to research something that we are unsure how to do, or there is complicated logic that needs writing or rewriting. Each issue size that you take on will guide you to a more complicated level in sequence, and you can see from the labels and overviews what they are about.

Its important that you try to work on issues that fill in gaps in your knowlege (see the self test for a reminder about what to look for).

So keep going, the fun stuff is about to start.

Having said that, we are also going to have you take on some issue making (sadly there is no issue making fairy). so pay attention to how the issues you have already worked on are constructed and how they change as they go up the ladder. That way when we start you on the isusue making portion of the team work, you will know what you are shooting for when its your time to make issues.

Also, we want you on the Merge team. This will ensure you are a competent developer and an awsome collaborative contributor to any team you join in the future.

[ ] Let us know that you have re-reviewed your issues, have read the above and are continuing on the team

### 9.0 UUNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIOIRTIZED BACKLOG AND ON ISSUE MAKING update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] Im am so ready, bring it on (continuing)
- [ ] I am worn out from the setup and the good first issues but still game (continuing)
- [ ] I won't be continuing, (please let us know why in a comment and close this issue)

[THIS WHOLE THING COULD BE MOVED TO A WIKI PAGE THAT EXPLAINS THE VALUE TO THEIR CAREER AND HAVE A TLDR HERE]

10.0 SMALL

prioritized backlog [CHANGE THIS LINK TO JUST HAVE SMALL ISSUES]

[ ] Assign youself a small issue
[ ] Submit your PR.
[ ] While you are waiting for your PR to be reviewed, please review other peoples good first issues.

[ ] Once your pull request has been merged post the following message in a comment below on this issue and then answer it.

### 10.0 SMALL update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>Wwhat is the number of your small merged pull request?
- #
>Did you review any good first issue PRs?
- [ ] no
- [ ] yes
  - if yes, what were the numbers
    - #
    - #
    Did you catch anything?
    - [ ] yes
    - [ ] no
      - if you did't catch anything, did anyone else who reviewed it after you, catch anything?
        - [ ] no
        - [ ] yes
           - if yes, descrube what you learned?

11.0 Medium

prioritized backlog [CHANGE THIS LINK TO MEDIUM SIZE ISSUES]

[ ] Assign youself a medium issue
[ ] Submit your PR.
[ ] While you are waiting for your PR to be reviewed, please review other peoples good small issues

[ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it.

### 11.0 MEDIUM update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>Wwhat is the number of your medium merged pull request?
- #
>Did you review any small issue PRs?
- [ ] no
- [ ] yes
  - if yes, what were the numbers
    - #
    - #
    Did you catch anything?
    - [ ] yes
    - [ ] no
      - if you did't catch anything, did anyone else who reviewed it after you, catch anything?
        - [ ] no
        - [ ] yes
           - if yes, descrube what you learned?

12.0 LARGE

prioritized backlog [CHANGE THIS LINK TO LARGE SIZE ISSUES]

[ ] Assign youself a large issue
[ ] Submit your PR.
[ ] While you are waiting for your PR to be reviewed, please review other peoples medium issues
[ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it.
```
### 12.0 LARGE update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>Wwhat is the number of your large merged pull request?
- #
>Did you review any medium issue PRs?
- [ ] no
- [ ] yes
  - if yes, what were the numbers
    - #
    - #
    Did you catch anything?
    - [ ] yes
    - [ ] no
      - if you did't catch anything, did anyone else who reviewed it after you, catch anything?
        - [ ] no
        - [ ] yes
           - if yes, descrube what you learned?
```
- Medium (~~you can work on one medium issue, but only one at a time~~one per person, with some exceptions, see below)
- Large (you can work on more than one large issue, but only one at a time)
  - The reasons for this progression are:
    - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
    - We are trying to teach you the team methodology through the issues themselves.
    - It ensures you understand what we expect and the quality of contributions.
  - You can work on back-to-back small issues if it meets the following criteria:
    - You are learning something new and need to work on an issue of a lesser complexity
    - Since we have a limited number of these, you must get approval from lead or pm
  - You can work on a second medium issue if it meets the following criteria:
    - You are learning something new and need to work on an issue of a lesser complexity
    - Since we have a limited number of these, you must get approval from lead or pm

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
Lastly, you can add the issue to the ~~"Development team meeting discussion items"~~ "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

Resources/Instructions

Contributing.md - Hack for LA
GitHub Project Board - Hack for LA
GitHub Project Board Prioritized Backlog highlighted and sorted by Front End
GitHub Project Board Prioritized Backlog highlighted and sorted by Back End/DevOps
Figma - Hack for LA
Google Drive - Hack for LA website team
Agenda / Notes - Dev Team Tuesday meeting
Agenda / Notes - All Team meeting
How to review Pull Requests
To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page

Mar 13 '24 00:03 ExperimentsInHonesty

[x] The following issues have been made and will need to be rolled into this issue
https://github.com/hackforla/website/issues/6451
https://github.com/hackforla/website/issues/5632
https://github.com/hackforla/website/issues/6645

Solution

I prioritized as time sensitive and added the text If issue https://github.com/hackforla/website/issues/4944 is closed DO NOT WORK ON THIS ISSUE, instead move this issue to the Questions column, and add the ready for dev lead label
- #6451
- #5632
I assigned
- #6645 to Roslyn since she owns the onboarding sheet.

Apr 16 '24 22:04 ExperimentsInHonesty

Hi @ExperimentsInHonesty, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

Apr 16 '24 22:04 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

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 (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, April 23, 2024 at 12:06 AM PST.}

Apr 26 '24 07:04 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

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 (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, April 30, 2024 at 12:06 AM PST.}

May 03 '24 07:05 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

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 (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, May 7, 2024 at 12:06 AM PST.}

May 10 '24 07:05 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

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 (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, May 14, 2024 at 12:06 AM PST.}

May 17 '24 07:05 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

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 (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, May 21, 2024 at 12:06 AM PST.}

May 24 '24 07:05 github-actions[bot]

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

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 (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, May 28, 2024 at 12:06 AM PST.}

May 31 '24 07:05 github-actions[bot]

This is the latest draft. @JessicaLucindaCheng I need some help with the instructions for the how to work on Issue making.

readable draft

Bonnie's Draft -WIP. Will tell you when I am done

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a developer on the website team this issue will be your companion and a place to track your progress with the path we have set out for you.

Special Notes

This issue will stay open for as long as you are on the Website team. Use it as a place to indicate that you have completed a level as well as get instructions on how to progress.
Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues. Do not close this issue until you leave the team (please see to do items associated with leaving professionally)
The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.
During the General Hack for LA onboarding, you will be directed to fill out a form that will add you to the website team roster, google drive and GitHub teams. If you have not done that yet, you will not be able to do the action items in section 1.0
- [WE NEED TO WRITE AN AUTOMATION THAT ADDS PEOPLE TO THE ROSTER AUTOMATICALLY]

Action Items

1.0 JOINING THE WEBSITE TEAM.

[ ] 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 to see if you are logged in to GitHub (if you are not logged in your will see a sign in button on the top right of the screen and another message/button at the bottom of the issue).
  - if you are logged in - [ ] contact a merge team member or technical lead on the hfla-site 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 the merge team / technical lead in the hfla-site slack channel.
[ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
[ ] Register for Zoom meetings using the form at [Replace with URL TO SLIDE WITH ZOOM REGISTRATION LINKS - this will get replaced by an automation that happens during onboarding, but in the meantime we will link to the slide]
[ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
[ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
[ ] Sign up for a Figma account

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

### 1.0 JOINING THE WEBSITE TEAM update
>How many hours did it take you to finish this step?

2.0 TEAM MEETINGS

[ ] Attend weekly team meetings:
- [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
- [ ] (Optional) Office Hours, Thursdays 7-8pm PST
- [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
[ ] Note: The meetings the the 1st-7th of every month are planning meetings for leads and merge team You are welcome to observe but we don't provide team member support.
[ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know through a slack message in the #hfla-site Slack channel as well as an @ mention in a comment of the issue that you would be working on, if you are planning to take a week off or a longer vacation.

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

### 2.0 TEAM MEETINGS update
>which meetings did you register for
 - [ ] Developer (front-end/back-end)
 - [ ] (Optional) Office Hours
 - [ ] All team meeting 
>When did you attend your first team meeting?

3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP

[ ] Complete steps 1.1 - 1.7 in Part 1: Setting up the development environment within Contributing.md
- [ ] OPTIONAL: If you run into any issues, use 4.1 How do I ask for help within Contributing.md as a visual example to get a hold of our HfLA website leadership team. That way we can help you resolve any set up issues immediately.
[ ] Post the following message in a comment below on this issue and then answer it. While keeping in mind that this is just to get feedback on how long it took you to get to this point. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace. Getting your dev environment setup will be easier for some people because they might already have some experience or items installed on their computer and you may not. This is an important step, be patient with yourself and your computer but keep on it till you get it done.
```
### 3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP update
>How many hours did it take you to finish this step?
```

4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE

[ ] Read section 2.1 - 2.4 in Part 2: How the Website team works with GitHub issues within Contributing.md
- [ ] Follow the steps in section 2.3 Where can I find GitHub issues to work on? to assign yourself your first issue under the Project Board's Prioritized Backlog column and use 2.7 Working on a Issue within Contributing.md to start working on your issue
- [ ] Read 2.6 What to do when you need to stop mid issue
Once you self assign an issue, an automation will post a welcome message in a comment giving you additional guidance to manage your issue (includes how to provide estimates and progress reports there).
- [ ] On assignment, you will be prompted to estimate Availability and ETA.
  
  Availability for this week:
  
  My estimated ETA for completing this issue:
  
  Once you have done that on your good first issue, check this box on this issue to let us know you have completed that task and understand how to do it in future.
  - [ ] If you have any questions about estimating the issue you choose, please add them to the issue, put the issue in the questions/review column, and add the label ready for dev lead and help wanted

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

### 4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE update
>How many hours did it take you to finish this step?

5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES

[ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
```
Provide Update
1. Progress
2. Blockers
3. Availability
4. ETA
```

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

### 5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES update
>on what issue did you give your first weekly update?
- #

6.0 PULL REQUEST SUBMISSION

[ ] Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
[ ] Additional notes:
- Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
- Please keep an eye on your PR, if someone leaves you a comment asking for a change, please respond in a timely way.
- [ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.
```
### 6.0 PULL REQUESTS update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

>What is the number of your first merged pull request?
- #
```

7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES

[ ] Read the Start Here - Developers in Figma
[ ] Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)

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

### 7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES update
>How many hours did it take you to finish this step?
>Do you have any questions about what you read?
   - [ ] yes, I had questions, and I left comments in the appropriate issues [WE NEED TO UPDATE THOSE TWO RESOURCES TO HAVE LINKS TO ISSUES WHERE PEOPLE CAN PUT QUESTIONS AND MOVE THE ISSUES TO THE QUESTIONS/REVIEW COLUMN]
   - [ ] no, I did not have any questions

8.0 MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)

Do another good first issue (two per person total). We have you do another simple issue because this we want you to
- see the difference once you have successful setup your dev environment
- see how each PR gets easier to do with repetition
- make sure you know how to branch properly (most problems show up in the second commit)

[ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.

### 8.0 MOVE ON TO 2ND GOOD FIRST ISSUE update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>What is the number of your 2nd merged pull request?
- #

9.0 PULL REQUEST REVIEWS - GFI

Now that you have two merged good first issue PRs, you are eligible to review good first issue PRs, Review Required from other people who are following in the same journey path as you.

See How to review Pull Requests guide will teach you how to review pull requests.

Please review 5 good first issue PRs. Each PR requires at least two reviews, so by reviewing 5 good first issue PRs you are repaying the effort that others did for you (provided 4 reviews for your 2 good first issues) plus 1 extra review to help us all make up the deficit for people who submit a PR but don't get this far.

[ ] reviewed 1st good first issue pr
[ ] reviewed 2nd good first issue pr
[ ] reviewed 3rd good first issue pr
[ ] reviewed 4th good first issue pr

[ ] reviewed 5th good first issue pr

[ ] When you have reviewed a good first issue PR, please paste the following text in a comment below

### 9.0 PULL REQUEST REVIEWS - GFI - Update
I have reviewed a `good first issue` PR #
>Did you catch anything?

- [ ] yes
- [ ] no

>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned?

[ ] If there are no good first issue PRs to review right now, paste this comment instead and check back later. You can also go onto section 10.
```
### 9.0 PULL REQUEST REVIEWS - GFI - Update
There are currently no `good first issue` PRs to review, but ill check back later.
```

10.0 UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECK

Congrats on making it this far. Issues get more complicated from here, either they include more changes, or have several files to change or you have to research something that we are unsure how to do, or there is complicated logic that needs writing or rewriting. Each issue size that you take on will guide you to a more complicated level in sequence, and you can see from the labels and overviews what they are about.

Its important that you try to work on issues that fill in gaps in your knowledge (see the self test for a reminder about what to look for). Go ahead and document your self test, so if later you need help finding an issue, we can see what you might be looking for.

Self Test

[Replace with SELF TEST]

So keep going, the fun stuff is about to start.

Having said that, we are also going to have you take on some issue making (surprise! There is no issue making fairy, only volunteers like you that created issues for the people that come after them). Pay attention to how the issues you have already worked on are constructed and how they change as they go up the ladder. That way when we start you on the issue making portion of the team work, you will know what you are shooting for when its your time to make issues.

Also, we want you on the Merge team. This will ensure you are a competent developer and an awesome collaborative contributor to any team you join in the future.

[ ] Let us know that you have re-reviewed your issues, have read the above and are continuing on the team

### 10.0 UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] Im am so ready, bring it on (continuing)
- [ ] I am worn out from the setup and the good first issues but still game (continuing)
- [ ] I won't be continuing, (please let us know why in a comment and close this issue)

[THIS WHOLE THING COULD BE MOVED TO A WIKI PAGE THAT EXPLAINS THE VALUE TO THEIR CAREER AND HAVE A TLDR HERE]

11.0 SMALL

prioritized backlog

[ ] Assign yourself a small issue for the role you have indicated (front/backend or both)
[ ] Follow the instructions the bot adds as comments on the issue
[ ] Submit your PR

[ ] Once your pull request has been merged post the following message in a comment below on this issue and then answer it:

### 11.0 SMALL update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>What is the number of your small merged pull request?
- #

12.0 PULL REQUEST REVIEWS - Small

Now that you have your small PR merged, you are eligible to review small PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `small PRs. Each PR requires at least two reviews, so by reviewing 3 good first issue PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 small issue PR) plus 1 extra review to help us all make up the deficit for people who submit small PRs and then drop off the team.

[ ] reviewed 1st small pr
[ ] reviewed 2nd small pr

[ ] reviewed 3rd small pr

[ ] When you have reviewed a small PR, please paste the following text in a comment below

### 12.0 PULL REQUEST REVIEWS - Small - Update
I have reviewed a `small` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned?

[ ] If there are no small PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.
```
### 12.0 PULL REQUEST REVIEWS - Small - Update
There are currently no `small` PRs to review, but i'll check back later.
```

13.0 [INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (good first, and small)]

14.0 Medium

prioritized backlog

[ ] Assign yourself a medium issue
[ ] Follow the instructions the bot adds as comments on the issue
[ ] Submit your PR.
[ ] While you are waiting for your PR to be reviewed, please review other peoples good small issues

[ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it.

### 14.0 MEDIUM update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>What is the number of your medium merged pull request?
- #
>Did you review any small issue PRs?
- [ ] no
- [ ] yes
  - if yes, what were the numbers
    - #
    - #
    Did you catch anything?
    - [ ] yes
    - [ ] no
      - if you did't catch anything, did anyone else who reviewed it after you, catch anything?
        - [ ] no
        - [ ] yes
           - if yes, describe what you learned?

15.0 PULL REQUEST REVIEWS - Medium

Now that you have your medium PR merged, you are eligible to review medium PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `medium PRs. Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.

[ ] reviewed 1st medium pr
[ ] reviewed 2nd medium pr

[ ] reviewed 3rd medium pr

[ ] When you have reviewed a medium PR, please paste the following text in a comment below

### 15.0 PULL REQUEST REVIEWS - Medium - Update
I have reviewed a `medium` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned?

[ ] If there are no medium PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.
```
### 15.0 PULL REQUEST REVIEWS - Medium - Update
There are currently no `medium` PRs to review, but i'll check back later.
```

16.0

[INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (medium)] or [INSERT INSTRUCTIONS FOR LEVEL 2 ISSUE MAKING (good first, small, medium)]

17.0 LARGE

prioritized backlog [CHANGE THIS LINK TO LARGE SIZE ISSUES]

[ ] Assign yourself a large issue
[ ] Submit your PR.

[ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it.

### 17.0 LARGE update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>What is the number of your large merged pull request?
- #

18.0 PULL REQUEST REVIEWS - Large

Now that you have your large PR merged, you are eligible to review large PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `large PRs. Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.

[ ] reviewed 1st large pr
[ ] reviewed 2nd large pr

[ ] reviewed 3rd large pr

[ ] When you have reviewed a large PR, please paste the following text in a comment below

### 18.0 PULL REQUEST REVIEWS - Large - Update
I have reviewed a `large` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned?

[ ] If there are no large PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.
```
### 18.0 PULL REQUEST REVIEWS - Large - Update
There are currently no `large` PRs to review, but i'll check back later.
```

19.0

[INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (large)] or [INSERT INSTRUCTIONS FOR LEVEL 2 ISSUE MAKING (medium, large)] [INSERT INSTRUCTIONS FOR LEVEL 3 ISSUE MAKING (good first, small, medium)] [INSERT INSTRUCTIONS FOR LEVEL 4 ISSUE MAKING (good first, small, medium)]

FAQ section

Are there exceptions to which size issues I work on?

Medium (~~you can work on one medium issue, but only one at a time~~one per person, with some exceptions, see below)
Large (you can work on more than one large issue, but only one at a time)
- The reasons for this progression are:
  - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
  - We are trying to teach you the team methodology through the issues themselves.
  - It ensures you understand what we expect and the quality of contributions.
- You can work on back-to-back small issues if it meets the following criteria:
  - You are learning something new and need to work on an issue of a lesser complexity
  - Since we have a limited number of these, you must get approval from lead or pm
- You can work on a second medium issue if it meets the following criteria:
  - You are learning something new and need to work on an issue of a lesser complexity
  - Since we have a limited number of these, you must get approval from lead or pm

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
Lastly, you can add the issue to the ~~"Development team meeting discussion items"~~ "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

Resources/Instructions

Contributing.md - Hack for LA
GitHub Project Board - Hack for LA
GitHub Project Board Prioritized Backlog highlighted and sorted by Front End
GitHub Project Board Prioritized Backlog highlighted and sorted by Back End/DevOps
Figma - Hack for LA
Google Drive - Hack for LA website team
Agenda / Notes - Dev Team Tuesday meeting
Agenda / Notes - All Team meeting
How to review Pull Requests
To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page

misc notes

Copy and customize this response, and leave it in a comment on this issue I need to take some time off from the team. I believe I will be back on [Replace with DATE YOU WILL BE BACK] - If you have put work in, please make sure its well documented. - Add the label away - Move this issue to the questions column - if you are assigned to an issue, if you have not yet made any progress on the issue, please unassign.

copyable draft

Bonnie's Draft -WIP.  Will tell you when I am done

### Prerequisite
We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

### Overview
As a developer on the website team this issue will be your companion and a place to track your progress with the path we have set out for you.

### Special Notes
1. This issue will stay open for as long as you are on the Website team.  Use it as a place to indicate that you have completed a level as well as get instructions on how to progress. 
2. Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues.  Do not close this issue until you leave the team (please see to do items associated with leaving professionally)
3. The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.  
4. During the General Hack for LA onboarding, you will be directed to fill out a form that will add you to the website team roster, google drive and GitHub teams.  If you have not done that yet, you will not be able to do the action items in section 1.0
   - [WE NEED TO WRITE AN AUTOMATION THAT ADDS PEOPLE TO THE ROSTER AUTOMATICALLY]

### Action Items

#### 1.0 JOINING THE WEBSITE TEAM.
- [ ] 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 to see if you are logged in to GitHub (if you are not logged in your will see a sign in button on the top right of the screen and another message/button at the bottom of the issue).  
        - if you are logged in
          - [ ] contact a merge team member or technical lead on the hfla-site 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 the merge team / technical lead in the hfla-site slack channel.
             ```
- [ ] Add yourself to the [#hfla-site](https://hackforla.slack.com/archives/C4UM52W93) and [#hfla-site-pr](https://hackforla.slack.com/archives/C025ERFDM4Y) Slack channels
- [ ] Register for Zoom meetings using the form at [Replace  with URL TO SLIDE WITH ZOOM REGISTRATION LINKS - this will get replaced by an automation that happens during onboarding, but in the meantime we will link to the slide]
- [ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
- [ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
- [ ] Sign up for a [Figma](https://Figma.com) account
- [ ] Post the following message in a comment below on this issue and then answer it.
    ```
    ### 1.0 JOINING THE WEBSITE TEAM update
    >How many hours did it take you to finish this step?
    ```

#### 2.0 TEAM MEETINGS
- [ ] Attend weekly team meetings:
  - [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
  - [ ] (Optional) Office Hours, Thursdays 7-8pm PST
  - [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
- [ ] Note: The meetings the the 1st-7th of every month are planning meetings for leads and merge team  You are welcome to observe but we don't provide team member support.
- [ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know through a slack message in the #hfla-site Slack channel as well as an @ mention in a comment of the issue that you would be working on, if you are planning to take a week off or a longer vacation.
- [ ] Post the following message in a comment below on this issue and then answer it.
    ```
    ### 2.0 TEAM MEETINGS update
    >which meetings did you register for
     - [ ] Developer (front-end/back-end)
     - [ ] (Optional) Office Hours
     - [ ] All team meeting 
    >When did you attend your first team meeting?
    
    ```

#### 3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP
- [ ] Complete steps 1.1 - 1.7 in [Part 1: Setting up the development environment within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-1-setting-up-the-development-environment)
  - [ ] OPTIONAL: If you run into any issues, use [4.1 How do I ask for help within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#41-what-do-i-do-if-i-need-help) as a visual example to get a hold of our [HfLA website leadership team](https://github.com/hackforla/website/projects/7#card-69730135). That way we can help you resolve any set up issues immediately.
- [ ] Post the following message in a comment below on this issue and then answer it.  While keeping in mind that this is just to get feedback on how long it took you to get to this point. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace.  Getting your dev environment setup will be easier for some people because they might already have some experience or items installed on their computer and you may not. This is an important step, be patient with yourself and your computer but keep on it till you get it done.
    ```
    ### 3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP update
    >How many hours did it take you to finish this step?
    ```

#### 4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE
- [ ] Read section 2.1 - 2.4 in [Part 2: How the Website team works with GitHub issues within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#part-2-how-the-website-team-works-with-github-issues)
  - [ ] Follow the steps in section [2.3 Where can I find GitHub issues to work on?](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#23-where-can-i-find-github-issues-to-work-on) to assign yourself your first issue under the Project Board's Prioritized Backlog column and use [2.7 Working on a Issue within Contributing.md](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#27-working-on-an-issue) to start working on your issue
  - [ ] Read [2.6 What to do when you need to stop mid issue](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md#26-what-to-do-when-you-need-to-stop-mid-issue)
- Once you self assign an issue, an automation will post a welcome message in a comment giving you additional guidance to manage your issue (includes how to provide estimates and progress reports there).  
   - [ ] On assignment, you will be prompted to estimate Availability and ETA.  
      >Availability for this week:
      >
      >My estimated ETA for completing this issue: 

      Once you have done that on your good first issue, check this box on this issue to let us know you have completed that task and understand how to do it in future.  
         - [ ] If you have any questions about estimating the issue you choose, please add them to the issue, put the issue in the questions/review column, and add the label `ready for dev lead` and `help wanted`
- [ ] Post the following message in a comment below on this issue and then answer it.
    ```
    ### 4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE update
    >How many hours did it take you to finish this step?
    ```

#### 5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES
- [ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report.  If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. **This update should be done every week for every issue that you are assigned to**. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
    ```
    Provide Update
    1. Progress
    2. Blockers
    3. Availability
    4. ETA
    ```
- [ ] Post the following message in a comment below on this issue and then answer it.
    ```
    ### 5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES update
    >on what issue did you give your first weekly update?
    - #
    ```

#### 6.0 PULL REQUEST SUBMISSION
- [ ] Read sections 3.1.a - 3.1.c in [3.1 How to make a pull request](https://github.com/hackforla/website/blob/2e3c45fede99e61f479548ccca3f0dda83e351db/CONTRIBUTING.md#31-how-to-make-a-pull-request) to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
- [ ] Additional notes:
   - Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.  
   - Please keep an eye on your PR, if someone leaves you a comment asking for a change, please respond in a timely way.
   - [ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.
   ```
   ### 6.0 PULL REQUESTS update
   >Did you receive any reviews that required you to change anything on your PR? 
   - [ ] no
   - [ ] yes (if yes, describe what you learned)

   >What is the number of your first merged pull request?
   - #
   ```

#### 7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES
- [ ] Read the [Start Here - Developers](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=8583%3A0) in Figma
- [ ] Go familiarize yourself with the [Hack for LA Design System page in Figma](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3) (where you can see components and their SCSS classes)
- [ ] Post the following message in a comment below on this issue and then answer it.
    ```
    ### 7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES update
    >How many hours did it take you to finish this step?
    >Do you have any questions about what you read?
       - [ ] yes, I had questions, and I left comments in the appropriate issues [WE NEED TO UPDATE THOSE TWO RESOURCES TO HAVE LINKS TO ISSUES WHERE PEOPLE CAN PUT QUESTIONS AND MOVE THE ISSUES TO THE QUESTIONS/REVIEW COLUMN]
       - [ ] no, I did not have any questions
    ```

#### 8.0 MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)
- Do another good first issue (two per person total).  We have you do another simple issue because this we want you to 
   - see the difference once you have successful setup your dev environment
   - see how each PR gets easier to do with repetition
   - make sure you know how to branch properly (most problems show up in the second commit)
- [ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.
    ```
    ### 8.0 MOVE ON TO 2ND GOOD FIRST ISSUE update
    >Did you receive any reviews that required you to change anything on your PR? 
    - [ ] no
    - [ ] yes (if yes, describe what you learned)
    >What is the number of your 2nd merged pull request?
    - #
    ```
#### 9.0 PULL REQUEST REVIEWS - GFI
Now that you have two merged `good first issue` PRs, you are eligible to review [good first issue PRs, Review Required](https://github.com/hackforla/website/pulls?q=is%3Apr+is%3Aopen+label%3A%22good+first+issue%22+review%3Arequired) from other people who are following in the same journey path as you.

See [How to review Pull Requests](https://github.com/hackforla/website/wiki/How-to-review-pull-requests) guide will teach you how to review pull requests.

Please review 5 `good first issue` PRs.  Each PR requires at least two reviews, so by reviewing 5 good first issue PRs you are repaying the effort that others did for you (provided 4 reviews for your 2 good first issues) plus 1 extra review to help us all make up the deficit for people who submit a PR but don't get this far.
- [ ] reviewed 1st `good first issue` pr
- [ ] reviewed 2nd `good first issue` pr
- [ ] reviewed 3rd `good first issue` pr
- [ ] reviewed 4th `good first issue` pr
- [ ] reviewed 5th `good first issue` pr
   - [ ] When you have reviewed a `good first issue` PR, please paste the following text in a comment below
      ```
      ### 9.0 PULL REQUEST REVIEWS - GFI - Update
      I have reviewed a `good first issue` PR #
      >Did you catch anything?

      - [ ] yes
      - [ ] no

      >If you did't catch anything, did anyone else who reviewed it after you, catch anything?

       - [ ] no
       - [ ] yes
  
         >if yes, describe what you learned?
      ```
   - [ ] If there are no `good first issue` PRs to review right now, paste this comment instead and check back later.  You can also go onto section 10.
      ```
      ### 9.0 PULL REQUEST REVIEWS - GFI - Update
      There are currently no `good first issue` PRs to review, but ill check back later.
      ```

#### 10.0 UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECK
Congrats on making it this far.  Issues get more complicated from here, either they include more changes, or have several files to change or you have to research something that we are unsure how to do, or there is complicated logic that needs writing or rewriting. Each issue size that you take on will guide you to a more complicated level in sequence, and you can see from the labels and overviews what they are about.  

Its important that you try to work on issues that fill in gaps in your knowledge (see the self test for a reminder about what to look for).  Go ahead and document your self test, so if later you need help finding an issue, we can see what you might be looking for.

<details><summary>Self Test</summary>
<p>

[Replace with SELF TEST]

</p>
</details> 

So keep going, the fun stuff is about to start.

Having said that, we are also going to have you take on some issue making (surprise! There is no issue making fairy, only volunteers like you that created issues for the people that come after them).  Pay attention to how the issues you have already worked on are constructed and how they change as they go up the ladder. That way when we start you on the issue making portion of the team work, you will know what you are shooting for when its your time to make issues.

Also, we want you on the Merge team.  This will ensure you are a competent developer and an awesome collaborative contributor to any team you join in the future.

- [ ] Let us know that you have re-reviewed your issues, have read the above and are continuing on the team
    ```
    ### 10.0 UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING update
    >Did you receive any reviews that required you to change anything on your PR? 
    - [ ] Im am so ready, bring it on (continuing)
    - [ ] I am worn out from the setup and the good first issues but still game (continuing)
    - [ ] I won't be continuing, (please let us know why in a comment and close this issue)

    ```

[THIS WHOLE THING COULD BE MOVED TO A WIKI PAGE THAT EXPLAINS THE VALUE TO THEIR CAREER AND HAVE A TLDR HERE]

#### 11.0 SMALL
[prioritized backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+small%22#column-7198257)
- [ ] Assign yourself a small issue for the role you have indicated (front/backend or both)
- [ ] Follow the instructions the bot adds as comments on the issue
- [ ] Submit your PR  
- [ ] Once your pull request has been merged post the following message in a comment below on this issue and then answer it:
    ```
    ### 11.0 SMALL update
    >Did you receive any reviews that required you to change anything on your PR? 
    - [ ] no
    - [ ] yes (if yes, describe what you learned)
    >What is the number of your small merged pull request?
    - #
    ```

#### 12.0 PULL REQUEST REVIEWS - Small
Now that you have your small PR merged, you are eligible to review [small PRs, Review Required](https://github.com/hackforla/website/pulls?q=is%3Aopen+is%3Apr+label%3A%22Complexity%3A+Small%22+review%3Arequired) from other people who are following in the same journey path as you.

Please review 3 `small PRs.  Each PR requires at least two reviews, so by reviewing 3 good first issue PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 small issue PR) plus 1 extra review to help us all make up the deficit for people who submit small PRs and then drop off the team.
- [ ] reviewed 1st `small` pr
- [ ] reviewed 2nd `small` pr
- [ ] reviewed 3rd `small` pr
   - [ ] When you have reviewed a `small` PR, please paste the following text in a comment below
      ```
      ### 12.0 PULL REQUEST REVIEWS - Small - Update
      I have reviewed a `small` PR #
  
      >Did you catch anything?

       - [ ] yes
       - [ ] no
      >If you did't catch anything, did anyone else who reviewed it after you, catch anything?

       - [ ] no
       - [ ] yes
  
         >if yes, describe what you learned?
      ```
   - [ ] If there are no `small` PRs to review right now, paste this comment instead and check back later.  You can also go onto section 13.
      ```
      ### 12.0 PULL REQUEST REVIEWS - Small - Update
      There are currently no `small` PRs to review, but i'll check back later.
      ```

#### 13.0 [INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (good first, and small)]

#### 14.0 Medium
[prioritized backlog](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+medium%22#column-7198257)
- [ ] Assign yourself a medium issue
- [ ] Follow the instructions the bot adds as comments on the issue
- [ ] Submit your PR.  
- [ ] While you are waiting for your PR to be reviewed, please review other peoples good small issues
- [ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it.
    ```
    ### 14.0 MEDIUM update
    >Did you receive any reviews that required you to change anything on your PR? 
    - [ ] no
    - [ ] yes (if yes, describe what you learned)
    >What is the number of your medium merged pull request?
    - #
    >Did you review any small issue PRs?
    - [ ] no
    - [ ] yes
      - if yes, what were the numbers
        - #
        - #
        Did you catch anything?
        - [ ] yes
        - [ ] no
          - if you did't catch anything, did anyone else who reviewed it after you, catch anything?
            - [ ] no
            - [ ] yes
               - if yes, describe what you learned?
    ```

#### 15.0 PULL REQUEST REVIEWS - Medium
Now that you have your medium PR merged, you are eligible to review [medium PRs, Review Required](https://github.com/hackforla/website/pulls?q=is%3Aopen+is%3Apr+label%3A%22Complexity%3A+Medium%22+review%3Arequired) from other people who are following in the same journey path as you.

Please review 3 `medium PRs.  Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.
- [ ] reviewed 1st `medium` pr
- [ ] reviewed 2nd `medium` pr
- [ ] reviewed 3rd `medium` pr
   - [ ] When you have reviewed a `medium` PR, please paste the following text in a comment below
      ```
      ### 15.0 PULL REQUEST REVIEWS - Medium - Update
      I have reviewed a `medium` PR #
  
      >Did you catch anything?

       - [ ] yes
       - [ ] no
      >If you did't catch anything, did anyone else who reviewed it after you, catch anything?

       - [ ] no
       - [ ] yes
  
         >if yes, describe what you learned?
      ```
   - [ ] If there are no `medium` PRs to review right now, paste this comment instead and check back later.  You can also go onto section 13.
      ```
      ### 15.0 PULL REQUEST REVIEWS - Medium - Update
      There are currently no `medium` PRs to review, but i'll check back later.
      ```

#### 16.0 
[INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (medium)] or [INSERT INSTRUCTIONS FOR LEVEL 2 ISSUE MAKING (good first, small, medium)]

#### 17.0 LARGE
[prioritized backlog](https://github.com/hackforla/website/projects/7#column-7198257)
[CHANGE THIS LINK TO LARGE SIZE ISSUES]
- [ ] Assign yourself a large issue
- [ ] Submit your PR.  
- [ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it.
    ```
    ### 17.0 LARGE update
    >Did you receive any reviews that required you to change anything on your PR? 
    - [ ] no
    - [ ] yes (if yes, describe what you learned)
    >What is the number of your large merged pull request?
    - #
    ```

#### 18.0 PULL REQUEST REVIEWS - Large
Now that you have your large PR merged, you are eligible to review [large PRs, Review Required](https://github.com/hackforla/website/pulls?q=is%3Aopen+is%3Apr+label%3A%22Complexity%3A+Large%22+review%3Arequired) from other people who are following in the same journey path as you.

Please review 3 `large PRs.  Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.
- [ ] reviewed 1st `large` pr
- [ ] reviewed 2nd `large` pr
- [ ] reviewed 3rd `large` pr
   - [ ] When you have reviewed a `large` PR, please paste the following text in a comment below
      ```
      ### 18.0 PULL REQUEST REVIEWS - Large - Update
      I have reviewed a `large` PR #
  
      >Did you catch anything?

       - [ ] yes
       - [ ] no
      >If you did't catch anything, did anyone else who reviewed it after you, catch anything?

       - [ ] no
       - [ ] yes
  
         >if yes, describe what you learned?
      ```
   - [ ] If there are no `large` PRs to review right now, paste this comment instead and check back later.  You can also go onto section 13.
      ```
      ### 18.0 PULL REQUEST REVIEWS - Large - Update
      There are currently no `large` PRs to review, but i'll check back later.
      ```


#### 19.0 
[INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (large)] or [INSERT INSTRUCTIONS FOR LEVEL 2 ISSUE MAKING (medium, large)]
[INSERT INSTRUCTIONS FOR LEVEL 3 ISSUE MAKING (good first, small, medium)]
[INSERT INSTRUCTIONS FOR LEVEL 4 ISSUE MAKING (good first, small, medium)]

### FAQ section

#### Are there exceptions to which size issues I work on?
  - Medium (<s>you can work on one medium issue, but only one at a time</s>one per person, with some exceptions, see below) 
  - Large (you can work on more than one large issue, but only one at a time)
    - The reasons for this progression are:
      - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
      - We are trying to teach you the team methodology through the issues themselves.
      - It ensures you understand what we expect and the quality of contributions.
    - You can work on back-to-back small issues if it meets the following criteria:
      - You are learning something new and need to work on an issue of a lesser complexity
      - Since we have a limited number of these, you must get approval from lead or pm
    - You can work on a second medium issue if it meets the following criteria:
      - You are learning something new and need to work on an issue of a lesser complexity
      - Since we have a limited number of these, you must get approval from lead or pm

#### What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?
- First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
- Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
- Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
- Lastly, you can add the issue to the <s>"Development team meeting discussion items"</s> "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

### Resources/Instructions
- [Contributing.md - Hack for LA](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md)
- [GitHub Project Board - Hack for LA](https://github.com/hackforla/website/projects/7)
- [GitHub Project Board Prioritized Backlog highlighted and sorted by Front End](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+front+end%22)
- [GitHub Project Board Prioritized Backlog highlighted and sorted by Back End/DevOps](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+back+end%2Fdevops%22)
- [Figma - Hack for LA](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website)
- [Google Drive - Hack for LA website team](https://drive.google.com/drive/folders/1p76K0FgfiAWeIIEyoyJ_Iik8FVj8cBjT?usp=sharing)
- [Agenda / Notes - Dev Team Tuesday meeting](https://github.com/hackforla/website/issues/2010)
- [Agenda / Notes - All Team meeting](https://github.com/hackforla/website/issues/2027)
- [How to review Pull Requests](https://github.com/hackforla/website/wiki/How-to-review-pull-requests)
- To find contact information for the merge team members and technical leads, please take a look at our [Meet the Team wiki page](https://github.com/hackforla/website/wiki/Meet-the-Team)


---
misc notes

Copy and customize this response, and leave it in a comment on this issue
      ```
      I need to take some time off from the team.  I believe I will be back on [Replace with DATE YOU WILL BE BACK]
      ```
      - If you have put work in, please make sure its well documented.
         - Add the label `away`
         - Move this issue to the questions column
      - if you are assigned to an issue, if you have not yet made any progress on the issue, please unassign.

Jun 03 '24 07:06 ExperimentsInHonesty

Bonnie's Draft -WIP. Will tell you when I am done

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a developer on the website team this issue will be your companion and a place to track your progress with the path we have set out for you.

Special Notes

This issue will stay open for as long as you are on the Website team. Use it as a place to indicate that you have completed a level as well as get instructions on how to progress.
Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues. Do not close this issue until you leave the team (please see to do items associated with leaving professionally)
The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.
During the General Hack for LA onboarding, you will be directed to fill out a form that will add you to the website team roster, google drive and GitHub teams. If you have not done that yet, you will not be able to do the action items in section 1.0
- [WE NEED TO WRITE AN AUTOMATION THAT ADDS PEOPLE TO THE ROSTER AUTOMATICALLY]

Action Items

1.0 JOINING THE WEBSITE TEAM.

[ ] 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 to see if you are logged in to GitHub (if you are not logged in your will see a sign in button on the top right of the screen and another message/button at the bottom of the issue).
  - if you are logged in - [ ] contact a merge team member or technical lead on the hfla-site 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 the merge team / technical lead in the hfla-site slack channel.
[ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
[ ] Register for Zoom meetings using the form at [Replace with URL TO SLIDE WITH ZOOM REGISTRATION LINKS - this will get replaced by an automation that happens during onboarding, but in the meantime we will link to the slide]
[ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
[ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
[ ] Sign up for a Figma account

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

### 1.0 JOINING THE WEBSITE TEAM update
>How many hours did it take you to finish this step?

2.0 TEAM MEETINGS

Ready, set, GO!

[ ] Attend weekly team meetings:
- [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
- [ ] (Optional) Office Hours, Thursdays 7-8pm PST
- [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
[ ] Note: The meetings the the 1st-7th of every month are planning meetings for leads and merge team You are welcome to observe but we don't provide team member support.
[ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know through a slack message in the #hfla-site Slack channel as well as an @ mention in a comment of the issue that you would be working on, if you are planning to take a week off or a longer vacation.

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

### 2.0 TEAM MEETINGS update
>which meetings did you register for
 - [ ] Developer (front-end/back-end)
 - [ ] (Optional) Office Hours
 - [ ] All team meeting 
>When did you attend your first team meeting?

3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP

[ ] Complete steps 1.1 - 1.7 in Part 1: Setting up the development environment within Contributing.md
- [ ] OPTIONAL: If you run into any issues, use 4.1 How do I ask for help within Contributing.md as a visual example to get a hold of our HfLA website leadership team. That way we can help you resolve any set up issues immediately.
[ ] Post the following message in a comment below on this issue and then answer it. While keeping in mind that this is just to get feedback on how long it took you to get to this point. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace. Getting your dev environment setup will be easier for some people because they might already have some experience or items installed on their computer and you may not. This is an important step, be patient with yourself and your computer but keep on it till you get it done.
```
### 3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP update
>How many hours did it take you to finish this step?
```

4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE

[ ] Read section 2.1 - 2.4 in Part 2: How the Website team works with GitHub issues within Contributing.md
- [ ] Follow the steps in section 2.3 Where can I find GitHub issues to work on? to assign yourself your first issue under the Project Board's Prioritized Backlog column and use 2.7 Working on a Issue within Contributing.md to start working on your issue
- [ ] Read 2.6 What to do when you need to stop mid issue
Once you self assign an issue, an automation will post a welcome message in a comment giving you additional guidance to manage your issue (includes how to provide estimates and progress reports there).
- [ ] On assignment, you will be prompted to estimate Availability and ETA.
  
  Availability for this week:
  
  My estimated ETA for completing this issue:
  
  Once you have done that on your good first issue, check this box on this issue to let us know you have completed that task and understand how to do it in future.
  - [ ] If you have any questions about estimating the issue you choose, please add them to the issue, put the issue in the questions/review column, and add the label ready for dev lead and help wanted

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

### 4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE update
>How many hours did it take you to finish this step?

5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES

[ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
```
Provide Update
1. Progress
2. Blockers
3. Availability
4. ETA
```

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

### 5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES update
>on what issue did you give your first weekly update?
- #

6.0 PULL REQUEST SUBMISSION

[ ] Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
[ ] Additional notes:
- Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
- Please keep an eye on your PR, if someone leaves you a comment asking for a change, please respond in a timely way.
- [ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.
```
### 6.0 PULL REQUESTS update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

>What is the number of your first merged pull request?
- #
```

7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES

[ ] Read the Start Here - Developers in Figma
[ ] Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)

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

### 7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES update
>How many hours did it take you to finish this step?
>Do you have any questions about what you read?
   - [ ] yes, I had questions, and I left comments in the appropriate issues [WE NEED TO UPDATE THOSE TWO RESOURCES TO HAVE LINKS TO ISSUES WHERE PEOPLE CAN PUT QUESTIONS AND MOVE THE ISSUES TO THE QUESTIONS/REVIEW COLUMN]
   - [ ] no, I did not have any questions

8.0 MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)

Do another good first issue (two per person total). We have you do another simple issue because this we want you to
- see the difference once you have successful setup your dev environment
- see how each PR gets easier to do with repetition
- make sure you know how to branch properly (most problems show up in the second commit)

[ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.

### 8.0 MOVE ON TO 2ND GOOD FIRST ISSUE update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>What is the number of your 2nd merged pull request?
- #

9.0 PULL REQUEST REVIEWS - GFI

Now that you have two merged good first issue PRs, you are eligible to review good first issue PRs, Review Required from other people who are following in the same journey path as you.

See How to review Pull Requests guide will teach you how to review pull requests.

Please review 5 good first issue PRs. Each PR requires at least two reviews, so by reviewing 5 good first issue PRs you are repaying the effort that others did for you (provided 4 reviews for your 2 good first issues) plus 1 extra review to help us all make up the deficit for people who submit a PR but don't get this far.

[ ] reviewed 1st good first issue pr
[ ] reviewed 2nd good first issue pr
[ ] reviewed 3rd good first issue pr
[ ] reviewed 4th good first issue pr

[ ] reviewed 5th good first issue pr

[ ] When you have reviewed a good first issue PR, please paste the following text in a comment below

### 9.0 PULL REQUEST REVIEWS - GFI - Update
I have reviewed a `good first issue` PR #
>Did you catch anything?

- [ ] yes
- [ ] no

>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned?

[ ] If there are no good first issue PRs to review right now, paste this comment instead and check back later. You can also go onto section 10.
```
### 9.0 PULL REQUEST REVIEWS - GFI - Update
There are currently no `good first issue` PRs to review, but ill check back later.
```

10.0 UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECK

Congrats on making it this far. Issues get more complicated from here, either they include more changes, or have several files to change or you have to research something that we are unsure how to do, or there is complicated logic that needs writing or rewriting. Each issue size that you take on will guide you to a more complicated level in sequence, and you can see from the labels and overviews what they are about.

Its important that you try to work on issues that fill in gaps in your knowledge (see the self test for a reminder about what to look for). Go ahead and document your self test, so if later you need help finding an issue, we can see what you might be looking for.

Self Test

[Replace with SELF TEST]

So keep going, the fun stuff is about to start.

Having said that, we are also going to have you take on some issue making (surprise! There is no issue making fairy, only volunteers like you that created issues for the people that come after them). Pay attention to how the issues you have already worked on are constructed and how they change as they go up the ladder. That way when we start you on the issue making portion of the team work, you will know what you are shooting for when its your time to make issues.

Also, we want you on the Merge team. This will ensure you are a competent developer and an awesome collaborative contributor to any team you join in the future.

[ ] Let us know that you have re-reviewed your issues, have read the above and are continuing on the team

### 10.0 UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] Im am so ready, bring it on (continuing)
- [ ] I am worn out from the setup and the good first issues but still game (continuing)
- [ ] I won't be continuing, (please let us know why in a comment and close this issue)

[THIS WHOLE THING COULD BE MOVED TO A WIKI PAGE THAT EXPLAINS THE VALUE TO THEIR CAREER AND HAVE A TLDR HERE]

11.0 SMALL

prioritized backlog, small issues

[ ] Assign yourself a small issue for the role you have indicated (front/backend or both)
[ ] Follow the instructions the bot adds as comments on the issue
[ ] Submit your PR

[ ] Once your pull request has been merged post the following message in a comment below on this issue and then answer it:

### 11.0 SMALL update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>What is the number of your small merged pull request?
- #

12.0 PULL REQUEST REVIEWS - Small

Now that you have your small PR merged, you are eligible to review small PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `small PRs. Each PR requires at least two reviews, so by reviewing 3 good first issue PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 small issue PR) plus 1 extra review to help us all make up the deficit for people who submit small PRs and then drop off the team.

[ ] reviewed 1st small pr
[ ] reviewed 2nd small pr

[ ] reviewed 3rd small pr

[ ] When you have reviewed a small PR, please paste the following text in a comment below

### 12.0 PULL REQUEST REVIEWS - Small - Update
I have reviewed a `small` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned?

[ ] If there are no small PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.
```
### 12.0 PULL REQUEST REVIEWS - Small - Update
There are currently no `small` PRs to review, but i'll check back later.
```

13.0 [INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (good first, and small)]

14.0 Medium

[ ] Assign yourself a medium issue from the prioritized backlog column, filtered to show medium issues
- [ ] If there are no medium size issues in the prioritized backlog column
  - [ ] add the label needs issue: medium to this issue, so that we can notify you when new medium size issues are released
  - [ ] add the following comment to this issue
```
There are no medium issues right now.  Please let me know if one becomes available.
```
  - [ ] skip the rest of the 14.0 instructions, and the 15.0 instructions and go onto instructions 16.0. You will circle back to these sections when an issue becomes available

[ ] If there is medium size issue in the prioritized backlog column and you have self assigned
- [ ] Follow the instructions the bot adds as comments on the issue
- [ ] Submit your PR
- [ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it
```
### 14.0 MEDIUM update
>Did you receive any reviews that required you to change anything on your PR? 
 - [ ] no
 - [ ] yes (if yes, describe what you learned)
>What is the number of your medium merged pull request?
- #
```

15.0 PULL REQUEST REVIEWS - Medium

Now that you have your medium PR merged, you are eligible to review medium PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `medium PRs. Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.

[ ] reviewed 1st medium pr
[ ] reviewed 2nd medium pr

[ ] reviewed 3rd medium pr

[ ] When you have reviewed a medium PR, please paste the following text in a comment below

### 15.0 PULL REQUEST REVIEWS - Medium - Update
I have reviewed a `medium` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned?

[ ] If there are no medium PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.
```
### 15.0 PULL REQUEST REVIEWS - Medium - Update
There are currently no `medium` PRs to review, but i'll check back later.
```

16.0

[ ] Use this link to look for Issue Making: Level 1 + ' Complexity: Medium` issues to create.
- If you find any results in the make issues column
  - [ ] assign yourself to the first issue in that column
  - [ ] create the issue(s) it calls for. These new issues will end up in the new issue approval column with the label ready for merge team
  - [ ] once you have made the issues and added the labels, move the issue making issue into the questions column
  - [ ] add a comment, letting the merge team know that you have made the issues (include a link to each of the new issues)
  - [ ] add the label ready for merge team
  - [ ] there will likely be some back and forth with the merge team, until your issues are ready to be prioritized. When it is, the issue making issue will be closed and you are welcome to move onto the next checkbox
- I if you had to skip 14.0 working on a medium issue
  - [ ] circle back to 14.0 by picking up one of the medium issues you just made.
    - [ ] hide the comment below that says "There are no medium issues right now. Please let me know if one becomes available."
    - [ ] remove from this issue, the label needs issue: medium
- If there are no Level 1 Issue making Medium size Epics or ER, use these links to check for issue making issues in this order and do the first one that has results. Then continue picking up these issues until you get to a level 2 medium or a level 2 medium issue becomes available in the prioritized backlog.
  - Issue Making: Level 2 + good first issue
  - Issue Making: Level 2 + Complexity: Small
  - Issue Making: Level 2 + Complexity: Medium
    - Once you have made a medium size issue and its been approved, you can work on the medium issue (go back to section 14.0
      - [ ] hide the comment below that says "There are no medium issues right now. Please let me know if one becomes available."
      - [ ] remove from this issue, the label needs issue: medium

17.0 LARGE

prioritized backlog, large issues

[ ] Assign yourself a large issue
- [ ] If there are no large size issues
  - [ ] please add the label needs issue: large to this issue, so that we can notify you when new medium size issues are released
  - [ ] skip the rest of the 17.0 instructions, and the 18.0 instructions and go onto instructions 19.0. You will circle back to these sections when an issue becomes available
[ ] Submit your PR.

[ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it.

### 17.0 LARGE update
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)
>What is the number of your large merged pull request?
- #

18.0 PULL REQUEST REVIEWS - Large

Now that you have your large PR merged, you are eligible to review large PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `large PRs. Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.

[ ] reviewed 1st large pr
[ ] reviewed 2nd large pr

[ ] reviewed 3rd large pr

[ ] When you have reviewed a large PR, please paste the following text in a comment below

### 18.0 PULL REQUEST REVIEWS - Large - Update
I have reviewed a `large` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned?

[ ] If there are no large PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.
```
### 18.0 PULL REQUEST REVIEWS - Large - Update
There are currently no `large` PRs to review, but i'll check back later.
```

19.0

[INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (large)] or [INSERT INSTRUCTIONS FOR LEVEL 2 ISSUE MAKING (medium, large)] [INSERT INSTRUCTIONS FOR LEVEL 3 ISSUE MAKING (good first, small, medium)] [INSERT INSTRUCTIONS FOR LEVEL 4 ISSUE MAKING (good first, small, medium)]

FAQ section

Are there exceptions to which size issues I work on?

Medium (~~you can work on one medium issue, but only one at a time~~one per person, with some exceptions, see below)
Large (you can work on more than one large issue, but only one at a time)
- The reasons for this progression are:
  - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
  - We are trying to teach you the team methodology through the issues themselves.
  - It ensures you understand what we expect and the quality of contributions.
- You can work on back-to-back small issues if it meets the following criteria:
  - You are learning something new and need to work on an issue of a lesser complexity
  - Since we have a limited number of these, you must get approval from lead or pm
- You can work on a second medium issue if it meets the following criteria:
  - You are learning something new and need to work on an issue of a lesser complexity
  - Since we have a limited number of these, you must get approval from lead or pm

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
Lastly, you can add the issue to the ~~"Development team meeting discussion items"~~ "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

Resources/Instructions

Contributing.md - Hack for LA
GitHub Project Board - Hack for LA
GitHub Project Board Prioritized Backlog highlighted and sorted by Front End
GitHub Project Board Prioritized Backlog highlighted and sorted by Back End/DevOps
Figma - Hack for LA
Google Drive - Hack for LA website team
Agenda / Notes - Dev Team Tuesday meeting
Agenda / Notes - All Team meeting
How to review Pull Requests
To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page

misc notes

Copy and customize this response, and leave it in a comment on this issue I need to take some time off from the team. I believe I will be back on [Replace with DATE YOU WILL BE BACK] - If you have put work in, please make sure its well documented. - Add the label away on hold - Move this issue to the questions column - if you are assigned to an issue, if you have not yet made any progress on the issue, please unassign.

Jun 04 '24 16:06 ExperimentsInHonesty

Bonnie's Draft -WIP. Will tell you when I am done

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a developer on the website team this issue will be your companion and a place to track your progress with the path we have set out for you.

Special Notes

This issue will stay open for as long as you are on the Website team. Use it as a place to indicate that you have completed a level as well as get instructions on how to progress.
Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues. Do not close this issue until you leave the team (please see to do items associated with leaving professionally)
The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.
During the General Hack for LA onboarding, you will be directed to fill out a form that will add you to the website team Google drive and GitHub teams, and then you will add yourself to the roster. If you have not done that yet, you will not be able to do the action items in section 1
- [WE NEED TO WRITE AN AUTOMATION THAT ADDS PEOPLE TO THE ROSTER AUTOMATICALLY]

Action Items

Sections 1 - Joining the website team 2 - Team Meetings (Options and Requirements) 3 - Development Environment Setup 4 - First GitHub Issue (GFI) 5 - Weekly Updates 6 - 1st Pull Request 7 - Additional reading 1 8 - 2nd good first issue 9 - Pull Request Reviews - GFI 10 - Additional reading 2 11 - Small Issue 12 - Pull Request Reviews - Small 13 - Issue Making - Level 1 (GFI & Small) 14 - Medium Issue 14.1 Issue Making - Level 2 (Medium) 15 - Pull Request Reviews - Medium 16 - Issue Making - Level 2 (GFI) 17 - Merge Team Skills Review 18 - Large Issue 19 - Pull Request Reviews - Large 20 - Issue Making - Level 1 (Large) and additional levels 21 - X-Large Issue 22 - Joining the Merge team FAQ Resources

1 - JOINING THE WEBSITE TEAM.

[ ] 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 to see if you are logged in to GitHub (if you are not logged in your will 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 merge team member or technical lead on the hfla-site 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: [return to section 1](#section-1)
      - [ ] add the following text to a comment on this issue
        I don't have access, I have messaged the merge team / technical lead in the hfla-site slack channel. [return to section 1](#section-1)
[ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
[ ] Register for Zoom meetings using the form at [Replace with URL TO SLIDE WITH ZOOM REGISTRATION LINKS - this will get replaced by an automation that happens during onboarding, but in the meantime we will link to the slide]
[ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
[ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
[ ] Sign up for a Figma account
[ ] Fill out the INTAKE Self Test so that we can help you find issues that will match where you need to fill in.

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

### 1 - JOINING THE WEBSITE TEAM update
>How many hours did it take you to finish this step?

A:

[return to section 1](#section-1)

⇧ Table of Contents

2 - TEAM MEETINGS (OPTIONS AND REQUIREMENTS)

[ ] Attend weekly team meetings:
- [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm PST
- [ ] (Optional) Office Hours, Thursdays 7-8pm PST
- [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm PST
[ ] Note: The meetings on the 1st-7th of every month are planning meetings for leads and merge team. You are welcome to observe but we don't provide team member support.
[ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know through a slack message in the #hfla-site Slack channel as well as an @ mention in a comment of the issue that you would be working on, if you are planning to take a week off or a longer vacation.

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

### 2 - TEAM MEETINGS update
>which meetings did you register for
 - [ ] Developer (front-end/back-end)
 - [ ] (Optional) Office Hours
 - [ ] All team meeting 
>When did you attend your first team meeting?

A:

[return to section 2](#section-2)

⇧ Table of Contents

3 - DEVELOPMENT ENVIRONMENT SETUP

[ ] Complete steps 1.1 - 1.7 in Part 1: Setting up the development environment within Contributing.md
- [ ] OPTIONAL: If you run into any issues, use 4.1 How do I ask for help within Contributing.md as a visual example to get a hold of our HfLA website leadership team. That way we can help you resolve any set up issues immediately.
- [ ] If you have never setup your development environment before, please update your Ongoing Skills List to check off "Setting up your local environment from a contributing file"
[ ] Post the following message in a comment below on this issue and then answer it. While keeping in mind that this is just to get feedback on how long it took you to get to this point. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace. Getting your dev environment setup will be easier for some people because they might already have some experience or items installed on their computer and you may not. This is an important step, be patient with yourself and your computer but keep on it till you get it done.
```
### 3 - GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP update
>How many hours did it take you to finish this step?

A:

[return to section 3](#section-3)
```

⇧ Table of Contents

4 - FINDING AND ASSIGNING YOUR FIRST GITHUB ISSUE (GFI)

[ ] Read section 2.1 - 2.2 in Part 2: How the Website team works with GitHub issues within Contributing.md
[ ] Take the first issue from this prefiltered view of the project board (status: prioritized backlog, good first issues = dev: GFI)
- [ ] Follow the steps in section 2.4 Claiming an Issue to assign yourself your first issue.
- [ ] under the Project Board's Prioritized Backlog column and use 2.7 Working on a Issue within Contributing.md to start working on your issue
- [ ] Read 2.6 What to do when you need to stop mid issue
Once you self assign an issue, an automation will post a welcome message in a comment giving you additional guidance to manage your issue (includes how to provide estimates and progress reports there).
- [ ] On assignment, you will be prompted to estimate Availability and ETA.
  
  Availability for this week:
  
  My estimated ETA for completing this issue:
  
  Once you have done that on your good first issue, check this box, above, on this issue to let us know you have completed that task and understand how to do it in future.
  - If you have any questions about estimating the issue you choose, please add them to the issue, put the issue in the questions/review column, and add the label ready for dev lead and help wanted

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

### 4 - FINDING AND ASSIGNING YOUR FIRST GITHUB ISSUE update
>How many hours did it take you to finish this step?

A:

[return to section 4](#section-4)

⇧ Table of Contents

5 - GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES

[ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
```
Provide Update
1. Progress
2. Blockers
3. Availability
4. ETA
```

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

### 5 - GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES update
>on what issue did you give your first weekly update?

- #

[return to section 5](#section-5)

⇧ Table of Contents

6 - SUBMITTING YOUR FIRST PULL REQUEST

[ ] Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
Confirm you understand the following:
- [ ] Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
- [ ] Please keep an eye on your PR, if someone leaves you a comment asking for a change, please respond in a timely way.

[ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.

### 6 - PULL REQUESTS update
>What is the number of your first merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 6](#section-6)

⇧ Table of Contents

7 - ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES

[ ] Read the Start Here - Developers in Figma
[ ] Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)

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

### 7 - ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES update
>How many hours did it take you to finish this step?

A:
>Do you have any questions about what you read?
   - [ ] yes, I had questions, and I left comments in the appropriate issues [WE NEED TO UPDATE THOSE TWO RESOURCES TO HAVE LINKS TO ISSUES WHERE PEOPLE CAN PUT QUESTIONS AND MOVE THE ISSUES TO THE QUESTIONS/REVIEW COLUMN]
   - [ ] no, I did not have any questions

[return to section 7](#section-7)

⇧ Table of Contents

8 - MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)

Do another good first issue (two per person total). We have you do another simple issue because this we want you to
- see the difference once you have successful setup your dev environment
- see how each PR gets easier to do with repetition
- make sure you know how to branch properly (most problems show up in the second commit)
[ ] Take the first issue from this prefiltered view of the project board (status: prioritized backlog, good first issues = dev: GFI)
[ ] Submit your PR

Once your pull request has been accepted

[ ] Update your Ongoing Skills List to check off "GitHub branching" & "Pull Requests"

[ ] post the following message in a comment below on this issue and then answer it.

### 8 - MOVE ON TO 2ND GOOD FIRST ISSUE update
>What is the number of your 2nd merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 8](#section-8)

⇧ Table of Contents

9 - GOOD FIRST ISSUE (GFI) PULL REQUEST REVIEWS

Now that you have two merged good first issue PRs, you are eligible to review good first issue PRs, Review Required from other people who are following in the same journey path as you.

See How to review Pull Requests guide will teach you how to review pull requests.

Please review 5 good first issue PRs. Each PR requires at least two reviews, so by reviewing 5 good first issue PRs you are repaying the effort that others did for you (provided 4 reviews for your 2 good first issues) plus 1 extra review to help us all make up the deficit for people who submit a PR but don't get this far.

[ ] reviewed 1st good first issue pr
[ ] reviewed 2nd good first issue pr
[ ] reviewed 3rd good first issue pr
[ ] reviewed 4th good first issue pr

[ ] reviewed 5th good first issue pr

[ ] After each good first issue PR that your review, please paste the following text in a comment below

### 9 - PULL REQUEST REVIEWS - GFI - Update
I have reviewed a `good first issue` PR #
>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

     >if yes, describe what you learned:

    A: 

[return to section 9](#section-9)

[ ] Once all 5 good first PRs have been merged, check of the box for "good first issue" under "Reviewed other people's Pull Requests" on the Ongoing Skills List

[ ] If there are no good first issue PRs to review right now, paste this comment instead and check back later. You can also go onto section 10.

### 9 - PULL REQUEST REVIEWS - GFI - Update
There are currently no `good first issue` PRs to review, but ill check back later.

[return to section 9](#section-9)

⇧ Table of Contents

10 - UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECK

Congrats on making it this far. Issues get more complicated from here, either they include more changes, or have several files to change or you have to research something that we are unsure how to do, or there is complicated logic that needs writing or rewriting. Each issue size that you take on will guide you to a more complicated level in sequence, and you can see from the labels and overviews what they are about.

Its important that you try to work on issues that fill in gaps in your knowledge (see the self tests for a reminder about what to look for).

INTAKE Self Test
ONGOING Skills List

So keep going, the fun stuff is about to start.

Having said that, we are also going to have you take on some issue making (surprise! There is no issue making fairy, only volunteers like you that created issues for the people that come after them). Pay attention to how the issues you have already worked on are constructed and how they change as they go up the ladder. That way when we start you on the issue making portion of the team work, you will know what you are shooting for when its your time to make issues.

Also, we want you on the Merge team. This will ensure you are a competent developer and an awesome collaborative contributor to any team you join in the future.

[ ] Let us know that you have re-reviewed your issues, have read the above and are continuing on the team

### 10 - UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING update
>Up to now we have just been getting you ready.  Now the fun starts.  Are you continuing?
- [ ] I'm so ready, bring it on (continuing)
- [ ] I am worn out from the setup and the good first issues but still game (continuing)
- [ ] I won't be continuing, (please let us know why and close this issue)

Comments:

[return to section 10](#section-10)

[THIS WHOLE THING COULD BE MOVED TO A WIKI PAGE THAT EXPLAINS THE VALUE TO THEIR CAREER AND HAVE A TLDR HERE]

⇧ Table of Contents

11 - MOVING ON TO A SMALL ISSUE

[ ] Assign yourself a small issue, for the role you have indicated, from this prefiltered view of the project board (status: prioritized backlog, small = dev: small)
[ ] Follow the instructions the bot adds as comments on the issue
[ ] Submit your PR

[ ] Once your pull request has been merged post the following message in a comment below on this issue and then answer it:

### 11 - SMALL update
>What is the number of your small merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 11](#section-11)

⇧ Table of Contents

12 - PULL REQUEST REVIEWS - SMALL

Now that you have your small PR merged, you are eligible to review small PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `small PRs. Each PR requires at least two reviews, so by reviewing 3 good first issue PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 small issue PR) plus 1 extra review to help us all make up the deficit for people who submit small PRs and then drop off the team.

[ ] reviewed 1st small pr
[ ] reviewed 2nd small pr

[ ] reviewed 3rd small pr

[ ] When you have reviewed a small PR, please paste the following text in a comment below

### 12 - PULL REQUEST REVIEWS - Small - Update
I have reviewed a `small` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned:

   A: 

[return to section 12](#section-12)

[ ] Once all 3 good first PRs have been merged, check off the box for "small" under "Reviewed other people's Pull Requests" on the Ongoing Skills List

[ ] If there are no small PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.

### 12 - PULL REQUEST REVIEWS - Small - Update
There are currently no `small` PRs to review, but i'll check back later.

[return to section 12](#section-12)

⇧ Table of Contents

13 - GET EXPERIENCE MAKING ISSUES - LEVEL 1 (GFI & Small)

Creating issues from templates will give you experience on how issues

are constructed
are queued up for review
are queued up for approval
are prioritized (milestones)
and appear in the prioritzed backlog

and like the good first and small issues you have already done, they are perscritive enough to do with no prior experience issue making.

[ ] Take the first issue from this prefiltered view of the project board (status: ERs and epics that are ready to be turned into issues, good first & small = IM: 1 + extra filters)
[ ] Assign yourself
[ ] Move the issue to the in progress column
[ ] Follow the instructions in the issue
[ ] create the issue(s) it calls for. These new issues will end up in the new issue approval column with the label ready for merge team

Once the ER or Epic has been accepted by the Merge team and closed and the issue(s) you created have been moved into the prioritized backlog

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

### 13 - GET EXPERIENCE MAKING ISSUES - LEVEL 1 (GFI & Small) update
>Which EPIC or ER did you work on (provide the issue number)

#

>How many hours did it take you to make the issue(s)?

Number of hours: 

>Did you find anything required clarification or anything we could improve about the instructions?

Suggestions for improvement: 

[return to section 13](#section-13)

⇧ Table of Contents

14 - MOVING ON TO A MEDIUM ISSUE

[ ] Take the first issue from this prefiltered view of the project board (status: prioritized backlog, medium issues = dev: medium)
- [ ] If there are no medium size issues in the prioritized backlog column, skip the rest of this section and go to Section 14.1
- [ ] If there is medium size issue in the prioritized backlog column
  - [ ] Assign yourself a medium for the role you have indicated (front/backend or both)
  - [ ] Follow the instructions the bot adds as comments on the issue
  - [ ] Submit your PR
  - [ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it
```
### 14 - MEDIUM update
>What is the number of your medium merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
 - [ ] no
 - [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 14](#section-14)
```

⇧ Table of Contents

14.1 MAKE A MEDIUM ISSUE FROM AN ER OR EPIC

Only work on this section if you needed a medium issue and one is not available from the prioritized backlog

[ ] add the label needs issue: medium to this issue, so that we can notify you when new medium size issues are released

[ ] add the following comment to this issue

There are no medium issues right now.  Please let me know if one becomes available.

[return to section 14](#section-14.1)

[ ] Take the first issue from this prefiltered view of the project board (status: ERs and epics that are ready to be turned into issues, medium = IM: Level 1 + Complexity: Medium
- If you find any results in the column
  - [ ] assign yourself to the first issue in that column
  - [ ] move the ER or EPIC to the in progress column
  - [ ] create the issue(s) it calls for. These new issues will end up in the new issue approval column with the label ready for merge team
  - [ ] once you have made the issues and added the labels, move the issue making ER or Epic issue into the questions column
  - [ ] add a comment, letting the merge team know that you have made the issues (include a link to each of the new issues)
  - [ ] add the label ready for merge team
  - [ ] there will likely be some back and forth with the merge team, until your issue(s)s are approved and a ready for prioritization label is added. When the new issue(s) are approved, the issue making issue will be closed and you are welcome to move onto the next checkbox
[ ] Check this prefiltered view of the project board (status: prioritized backlog, medium issues = dev: medium
- If there still is no medium issue to work in the in progress column.
  - [ ] Leave the following message as a comment one of the Medium issues you just created and when the issue is prioritized we will assign the issue to you if there are no other medium issues you have picked up.
```
- I created this issue, so I could have a medium issue to work on.  Please assign to me once approved.  My Skills Issue is #
```
    - once you get assigned,
      - [ ] hide the comment below that says "There are no medium issues right now. Please let me know if one becomes available."
      - [ ] remove from this issue, the label needs issue: medium
      - [ ] circle back to Section 14 and check off the first 4 boxes, and continue from there.

⇧ Table of Contents

15 - PULL REQUEST REVIEWS - Medium

Now that you have your medium PR merged, you are eligible to review medium PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `medium PRs. Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.

[ ] reviewed 1st medium pr
[ ] reviewed 2nd medium pr

[ ] reviewed 3rd medium pr

[ ] When you have reviewed a medium PR, please paste the following text in a comment below

### 15 - PULL REQUEST REVIEWS - Medium - Update
I have reviewed a `medium` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned:

   A:

[return to section 15](#section-15)

[ ] If there are no medium PRs to review right now, paste this comment instead and check back later. You can also go onto section 16.

### 15 - PULL REQUEST REVIEWS - Medium - Update
There are currently no `medium` PRs to review, but i'll check back later.

[return to section 15](#section-15)

⇧ Table of Contents

16 - ISSUE MAKING - LEVEL 2, GFI

[ ] Take the first issue from this prefiltered view of the project board (status: ERs and epics that are ready to be turned into issues, good first issue = IM: Level 2 + good first issue
- If you find any results in the make issues column
  - [ ] assign yourself to the first issue in that column
  - [ ] move the ER or EPIC to the in progress column
  - [ ] create the issue(s) it calls for. These new issues will end up in the new issue approval column with the label ready for merge team
  - [ ] once you have made the issues and added the labels, move the issue making ER or Epic issue into the questions column
  - [ ] add a comment, letting the merge team know that you have made the issues (include a link to each of the new issues)
  - [ ] add the label ready for merge team
  - [ ] there might be some back and forth with the merge team, until your issues are ready to be prioritized. When it is, the issue making issue will be closed and you are welcome to move onto the next checkbox

⇧ Table of Contents

17 - MERGE TEAM SKILLS REVIEW

We want everyone who joins this team to get onto the merge team so that you can get experience running meetings and office hours, mentoring, creating sufficent workflow for the team, escalations, and ultimately being responsible for final approval and merging of pull requests made by team members on lower sections. At this point we will check to see if you are ready to join the merge team, or what your next steps are to get you closer to ready.

[INSERT INSTRUCTIONS HERE]

⇧ Table of Contents

18 - MOVING ON TO A LARGE ISSUE

[ ] Take the first issue from this prefiltered view of the project board (status: prioritized backlog, large issues = dev: large)
[ ] Assign yourself a large issue
- [ ] If there are no large size issues
  - [ ] please add the label needs issue: large to this issue, so that we can notify you when new large size issues are released
  - [ ] skip the rest of the section 18 & 19 instructions and go onto section 20. You will circle back to these sections when an issue becomes available
[ ] Submit your PR.

[ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it.

### 18 - LARGE update
>What is the number of your large merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 18](#section-18)

⇧ Table of Contents

18.1 - ISSUE MAKING - LEVEL 1 (LARGE) AND ADDITIONAL LEVELS

Only work on this section if you needed a large issue and one is not available from the prioritized backlog

[ ] add the label needs issue: large to this issue, so that we can notify you when new large size issues are released
[ ] add the following comment to this issue

There are no large issues right now.  Please let me know if one becomes available.
      
[return to section 18.1](#section-18.1)

[ ] Take the first issue from this prefiltered view of the project board (status: ERs and epics that are ready to be turned into issues, large = IM: Level 1 + Complexity: Large)
- If there is a Large EPIC or ER available
  - [ ] assign yourself to the first issue in that column
  - [ ] move the ER or EPIC issue to the in progress column
  - [ ] create the issue(s) it calls for. These new issues will end up in the new issue approval column with the label ready for merge team
  - [ ] once you have made the issues and added the labels, move the issue making ER or Epic issue into the questions column
  - [ ] add a comment, letting the merge team know that you have made the issues (include a link to each of the new issues)
  - [ ] add the label ready for merge team
  - [ ] there will likely be some back and forth with the merge team, until your issue(s)s are approved and a ready for prioritization label is added. When the new issue(s) are approved, the issue making issue will be closed and you are welcome to move onto the next checkbox
[ ] Check this prefiltered view of the project board (status: prioritized backlog, medium issues = dev: large
- If there still is no large issue to work in the in progress column.
  - [ ] Leave the following message as a comment one of the Large issues you just created and when the issue is prioritized we will assign the issue to you if there are no other large issues you have picked up.
```
- I created this issue, so I could have a large issue to work on.  Please assign to me once approved.  My Skills Issue is #
```
    - once you get assigned,
      - [ ] hide the comment below that says "There are no large issues right now. Please let me know if one becomes available."
      - [ ] remove from this issue, the label needs issue: large
      - [ ] circle back to Section 18 and check off the first 4 boxes, and continue from there.
- If there is no Large EPIC or ER available, start looking for EPICs and ERs to make issues from and keep making issues until you work back up to Large
  - [ ] IM: Level 2 + Complexity: Small
  - [ ] IM: Level 2 + Complexity: Medium
  - [ ] IM: Level 2 + Complexity: Large
    - [ ] Follow the same instructions as above to get yourself assigned to it.

⇧ Table of Contents

19 - PULL REQUEST REVIEWS - LARGE

Now that you have your large PR merged, you are eligible to review large PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `large PRs. Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.

[ ] reviewed 1st large pr
[ ] reviewed 2nd large pr

[ ] reviewed 3rd large pr

[ ] When you have reviewed a large PR, please paste the following text in a comment below

### 19 - PULL REQUEST REVIEWS - Large - Update
I have reviewed a `large` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned:

   A:

[return to section 19](#section-19)

[ ] If there are no large PRs to review right now, paste this comment instead and check back later. You can also go onto section 20.

### 19 - PULL REQUEST REVIEWS - Large - Update
There are currently no `large` PRs to review, but i'll check back later.

[return to section 19](#section-19)

⇧ Table of Contents

20

[INSERT SOMETHING HERE]

IM: Level 3 + good first issue

IM: Level 3 + complexity: small

IM: Level 3 + complexity: medium

IM: Level 3 + complexity: large

IM: Level 3 + complexity: extra large

IM: Level 4 + good first issue

IM: Level 4 + complexity: small

IM: Level 4 + complexity: medium

IM: Level 4 + complexity: large

IM: Level 4 + complexity: extra large

⇧ Table of Contents

21 - MOVING ON TO A XTRA LARGE ISSUE

⇧ Table of Contents

22 - JOINING THE MERGE TEAM

⇧ Table of Contents

FAQ section

Are there exceptions to which size issues I work on?

Medium (~~you can work on one medium issue, but only one at a time~~one per person, with some exceptions, see below)
Large (you can work on more than one large issue, but only one at a time)
The reasons for this progression are: - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues. - We are trying to teach you the team methodology through the issues themselves. - It ensures you understand what we expect and the quality of contributions.
- You can work on back-to-back small issues if it meets the following criteria:
  - You are learning something new and need to work on an issue of a lesser complexity
  - Since we have a limited number of these, you must get approval from lead or pm
- You can work on a second medium issue if it meets the following criteria:
  - You are learning something new and need to work on an issue of a lesser complexity
  - Since we have a limited number of these, you must get approval from lead or pm

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
Also, you can post your question on the hfla-site slack channel and link the issue you're working on, so other developers can see and respond.
Lastly, you can add the issue to the ~~"Development team meeting discussion items"~~ "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

If you need to take some time off from the team

Copy and customize this response, and leave it in a comment on this issue I need to take some time off from the team. I believe I will be back on [Replace with DATE YOU WILL BE BACK] - If you have put work in, please make sure its well documented. - Add the label away on hold - Move this issue to the questions column - if you are assigned to an issue, if you have not yet made any progress on the issue, please unassign.

⇧ Table of Contents

Resources/Instructions

Contributing.md - Hack for LA
GitHub Project Board - Hack for LA
GitHub Project Board Prioritized Backlog highlighted and sorted by Front End
GitHub Project Board Prioritized Backlog highlighted and sorted by Back End/DevOps
Figma - Hack for LA
Google Drive - Hack for LA website team
Agenda / Notes - Dev Team Tuesday meeting
Agenda / Notes - All Team meeting
How to review Pull Requests
To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page

⇧ Table of Contents

Skills List - INTAKE

Skills List, self test on Intake, fill out when you join the team, don't update

Front End

[ ] Setting up your local environment from a contributing file
[ ] GitHub branching
[ ] Pull Requests

Back End

[ ] API requests
[ ] Cron Job Scripting
[ ] CRUD operations

All Developers

[ ] Reviewed other people's Pull Requests
[ ] Resolved Merge Conflicts
[ ] Written documentation for other Developers (Architecture, etc.)
[ ] Mentored other developers

Return to section 1 section 10

Skills List - ONGOING

Skills List, update as you do work on this team

Front End

[ ] Setting up your local environment from a contributing file (section 3)
[ ] GitHub branching (done in section 8)
[ ] Pull Requests (section 8)

Back End

[ ] API requests
Cron Job Scripting
- [ ] edit GitHub Action
- [ ] write GitHub Action
[ ] CRUD operations

All Developers

Reviewed other people's Pull Requests
- [ ] good first issue (section 9)
- [ ] smal (section 12)
- [ ] medium
- [ ] large
- [ ] x-large
[ ] Resolved Merge Conflicts
[ ] Written documentation for other Developers (Architecture, etc.)
[ ] Mentored other developers

⇧ Table of Contents

Jun 15 '24 19:06 ExperimentsInHonesty

Notes in Sections

1
7

Jun 15 '24 20:06 ExperimentsInHonesty

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

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 (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Wednesday, June 19, 2024 at 1:48 PM PST.}

Jun 22 '24 20:06 github-actions[bot]

Progress: Updating the text now. Blockers: limited time available because I am working on Project Board Migration Availability: a few hours now. ETA: a week or two

Jun 22 '24 22:06 ExperimentsInHonesty

16 is changing to have them to IM: 2 - GFI, small, medium insert between 16-17 Have your skills issue evaluated for joining the merge team

(save the IM: 1 - Mediums for when there is no medium issues, the person could make their own issue and then do it.)

RW is going to divide these up and I will work them into the skills list https://github.com/hackforla/website/issues/6398#issuecomment-2187709493

Cron job scripting should be broken down into

Editing one
Writing one

removed details accordion from skills list

Jun 25 '24 00:06 ExperimentsInHonesty

[ ] We need to re-review what the user experience of finishing something, and there are still boxes unchecked. Is there a way for us to solve that, that works for all sections.

Jun 25 '24 20:06 ExperimentsInHonesty

[ ] Add note to Special notes that the copy symbol can be used to copy the contents in the gray boxes.

Example

Try to copy the text in this gray box by clicking on the copy symbol to the right of this text ⇨

Jun 25 '24 20:06 ExperimentsInHonesty

[x] Add two returns after every comment so that their answer does not become part of the question

Example

>question

>question

or

>question

A:

Jun 25 '24 21:06 ExperimentsInHonesty

[x] add a jump to bottom link and a return to top link.

Example

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

### 1 - JOINING THE WEBSITE TEAM update
>How many hours did it take you to finish this step?

A:

[return to checkbox]

Jun 25 '24 21:06 ExperimentsInHonesty

Add all the activities to this spreadsheet https://docs.google.com/spreadsheets/d/1qsnMzEL6W8z-At1mYOF9VT5ZheBA_AVVGzvwlu1H0Jo/edit?gid=0#gid=0

Jun 27 '24 16:06 ExperimentsInHonesty

Unicode arrows

website: Right Arrow

⇨

website: Left Arrow

⇦

website: Up Arrow

⇧

website: Down Arrow

⇩

Jul 01 '24 19:07 ExperimentsInHonesty

old 16 draft

#### 16 - ISSUE MAKING - LEVEL 1, MEDIUM
- [ ] Take the first issue from this prefiltered view of the project board (status: ERs and epics that are ready to be turned into issues, medium = [IM: Level 1 + Complexity: Medium](https://github.com/orgs/hackforla/projects/86/views/8?filterQuery=status%3A%22ERs+and+epics+that+are+ready+to+be+turned+into+issues%22+label%3A%22Issue+Making%3A+Level+1%22+label%3A%22complexity%3A+medium%22)
   - If you find any results in the make issues column
      - [ ] assign yourself to the first issue in that column
      - [ ] move the ER or EPIC to the in progress column
      - [ ] create the issue(s) it calls for.  These new issues will end up in the new issue approval column with the label `ready for merge team`
      - [ ] once you have made the issues and added the labels, move the issue making ER or Epic issue into the questions column
      - [ ] add a comment, letting the merge team know that you have made the issues (include a link to each of the new issues)
      - [ ] add the label `ready for merge team`
      - [ ] there will likely be some back and forth with the merge team, until your issues are ready to be prioritized.  When it is, the issue making issue will be closed and you are welcome to move onto the next checkbox
   - If you had to skip section 14 working on a medium issue
     - [ ] Circle back to section 14.  If there still is no medium issue to work in the in progress column.
        - [ ] Leave the following message as a comment one of the Medium issues you just created and when the issue is prioritized we will assign the issue to you if there are no other medium issues you have picked up.
           ```
           - I created this issue, so I could have a medium issue to work on.  Please assign to me once approved.  My Skills Issue is #
           ``` 
        - [ ] once you get assigned, circle back to section 14 to update your checklist.
        - [ ] hide the comment below that says "There are no medium issues right now.  Please let me know if one becomes available." 
        - [ ] remove from this issue, the label `needs issue: medium`
   - If there are no Level 1 Issue making Medium size Epics or ER, use these links to check for issue making issues in this order and do the first one that has results.  Then continue picking up these issues until you get to a level 2 medium or a level 2 medium issue becomes available in the prioritized backlog.
      - [IM: 2 + good first issue](https://github.com/orgs/hackforla/projects/86/views/9?filterQuery=status%3A%22ERs+and+epics+that+are+ready+to+be+turned+into+issues%22+label%3A%22Issue+Making%3A+Level+2%22+label%3A%22good+first+issue%22)
      - [IM: 2 + Complexity: Small](https://github.com/orgs/hackforla/projects/86/views/9?filterQuery=status%3A%22ERs+and+epics+that+are+ready+to+be+turned+into+issues%22+label%3A%22Issue+Making%3A+Level+2%22+label%3A%22Complexity%3A+Small%22)
      - [IM: 2 + Complexity: Medium](https://github.com/orgs/hackforla/projects/86/views/9?filterQuery=status%3A%22ERs+and+epics+that+are+ready+to+be+turned+into+issues%22+label%3A%22Issue+Making%3A+Level+2%22+label%3A%22complexity%3A+medium%22)
         - Once you have made a medium size issue and its been approved, you can work on the medium issue (go back to section 14
            - [ ] hide the comment below that says "There are no medium issues right now.  Please let me know if one becomes available." 
            - [ ] remove from this issue, the label `needs issue: medium`

[**⇧** Table of Contents](#table-of=contents)

[DO WE WANT THEM TO MAKE ANOTHER MEDIUM ISSUE]

Jul 01 '24 19:07 ExperimentsInHonesty

IM: Level 2 + complexity: extra large

[x] If you didn't have to make a medium issue from level 1 to do their medium issue, then they have to make a medium issue to pay it back.
[ ] between 19 and 20 another merge team review
[x] Add the merge team member stuff https://github.com/hackforla/website/issues/6398#issuecomment-2199339386
[x] Dividing up GHA's into edited and created.

Jul 02 '24 00:07 ExperimentsInHonesty

Copy of HfLA: Skills Dashboard

Jul 02 '24 18:07 ExperimentsInHonesty

@ExperimentsInHonesty

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

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 (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, July 30, 2024 at 12:05 AM PST.}

Aug 02 '24 07:08 github-actions[bot]

Prerequisite

We are looking forward to having you on our team. Please make sure to attend the general Hack for LA onboarding to get the process started https://meetup.com/hackforla/events.

Overview

As a developer on the website team this issue will be your companion and a place to track your progress with the path we have set out for you.

Special Notes

This issue will stay open for as long as you are on the Website team. Use it as a place to indicate that you have completed a level as well as get instructions on how to progress.
Usually we don't want to you have more than one issue assigned to you at a time, this issue is the exception, because it is instructions on how to work on other issues. Do not close this issue until you leave the team (please see to do items associated with leaving professionally)
The action items listed below should mostly be worked on in a sequential order. However, you don't have to wait on one if you can proceed with the others, For instance, you don't have to wait for attending a weekly meeting before setting up your dev environment.
During the General Hack for LA onboarding, you will be directed to fill out a form that will add you to the website team Google drive and GitHub teams, and then you will add yourself to the roster. If you have not done that yet, you will not be able to do the action items in section 1
The template that this issue is made from is a work in progress. We will be updating it, and possibly updating your issue. It works through section 17. But after that its still a work in progress. If any of the links don't work, please leave a note in the comments on this issue https://github.com/hackforla/website/issues/4944, and we will get you an update.

Action Items

Sections 1 - Joining the website team 2 - Team Meetings (Options and Requirements) 3 - Development Environment Setup 4 - First GitHub Issue (GFI) 5 - Weekly Updates 6 - 1st Pull Request 7 - Additional reading 1 8 - 2nd good first issue 9 - Pull Request Reviews - GFI 10 - Additional reading 2 11 - Small Issue 12 - Pull Request Reviews - Small 13 - Issue Making - Level 1 (GFI & Small) 14 - Medium Issue 14.1 Issue Making - Level 2 (Medium) 15 - Pull Request Reviews - Medium 16 - Issue Making - Level 2 (GFI) 17 - Merge Team Skills Review FAQ Resources

1 - JOINING THE WEBSITE TEAM.

[ ] Add yourself to the #hfla-site and #hfla-site-pr Slack channels
[ ] 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 to see if you are logged in to GitHub (if you are not logged in you will 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 merge team member or technical lead on the hfla-site 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 the merge team / technical lead in the hfla-site Slack channel. [return to section 1](#section-1)
[ ] Register for Zoom meetings using the form at [Replace with URL TO SLIDE WITH ZOOM REGISTRATION LINKS - this will get replaced by an automation that happens during onboarding, but in the meantime we will link to the slide]
[ ] Add the "role: front end" or "role: back end" or both label(s) to this issue and remove the "role missing" label (gear in right side panel)
[ ] Add this issue to the Project Board under the Projects section (gear in right side panel)
[ ] Sign up for a Figma account
[ ] Fill out the INTAKE Self Test so that we can help you find issues that will match where you need to fill in.

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

### 1 - JOINING THE WEBSITE TEAM update
>How many hours did it take you to finish this step?

A:

[return to section 1](#section-1)

⇧ Table of Contents

2 - TEAM MEETINGS (OPTIONS AND REQUIREMENTS)

[ ] Attend weekly team meetings:
- [ ] Developer (front-end/back-end) weekly team meeting, Tuesdays 7-8pm Pacific
- [ ] (Optional) Office Hours, Thursdays 7-8pm Pacific
- [ ] All team meeting (UX, Development, Product), Sunday 10am-12pm Pacific
[ ] Note: The meetings on the 1st-7th of every month are planning meetings for leads and merge team. You are welcome to observe but we don't provide team member support.
[ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Tuesdays, Thursdays and Sundays). In case, you are unable in any given week, you should reach out to the tech leadership team. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the tech leadership team know through a Slack message in the #hfla-site Slack channel as well as an @ mention in a comment of the issue that you would be working on, if you are planning to take a week off or a longer vacation.

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

### 2 - TEAM MEETINGS update
>which meetings did you register for
 - [ ] Developer (front-end/back-end)
 - [ ] (Optional) Office Hours
 - [ ] All team meeting 
>When did you attend your first team meeting?

A:

[return to section 2](#section-2)

⇧ Table of Contents

3 - DEVELOPMENT ENVIRONMENT SETUP

[ ] Complete steps 1.1 - 1.7 in Part 1: Setting up the development environment within Contributing.md
- [ ] OPTIONAL: If you run into any issues, use 4.1 How do I ask for help within Contributing.md
- [ ] If you have never setup your development environment before, please update your Ongoing Skills List to check off "Setting up your local environment from a contributing file"
[ ] Post the following message in a comment below on this issue and then answer it. While keeping in mind that this is just to get feedback on how long it took you to get to this point. There is no right or wrong answers. There is no judgement. It is ok if you take a long time or if you do it really fast or at any pace. Getting your dev environment setup will be easier for some people because they might already have some experience or items installed on their computer and you may not. This is an important step, be patient with yourself and your computer but keep on it till you get it done.
```
### 3 - GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP update
>How many hours did it take you to finish this step?

A:

[return to section 3](#section-3)
```

⇧ Table of Contents

4 - FINDING AND ASSIGNING YOUR FIRST GITHUB ISSUE (GFI)

[ ] Read section 2.1 - 2.2 in Part 2: How the Website team works with GitHub issues within Contributing.md
[ ] Take the first issue from this prefiltered view of the project board (status: prioritized backlog, good first issues = dev: GFI)
- [ ] Follow the steps in section 2.4 Claiming an Issue to assign yourself your first issue.
- [ ] under the Project Board's Prioritized Backlog column and use 2.7 Working on a Issue within Contributing.md to start working on your issue
- [ ] Read 2.6 What to do when you need to stop mid issue
Once you self assign an issue, an automation will post a welcome message in a comment giving you additional guidance to manage your issue (includes how to provide estimates and progress reports there).
- [ ] On assignment, you will be prompted to estimate Availability and ETA.
  
  Availability for this week:
  
  My estimated ETA for completing this issue:
  
  Once you have done that on your good first issue, check this box, above, on this issue to let us know you have completed that task and understand how to do it in future.
  - If you have any questions about estimating the issue you choose, please add them to the issue, put the issue in the questions/review column, and add the label ready for dev lead and help wanted

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

### 4 - FINDING AND ASSIGNING YOUR FIRST GITHUB ISSUE update
>How many hours did it take you to finish this step?

A:

[return to section 4](#section-4)

⇧ Table of Contents

5 - GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES

[ ] Progress Reports: Copy the below and put it in the issue once you have been assigned to the issue at least 5 days (we check weekly on Fridays), or sooner if you have something to report. If you finish this issue before 5 days are reached, Yeah!!, do it on your next issue. This update should be done every week for every issue that you are assigned to. The checkbox here is meant for us to see if you understood the instructions when you end up doing your first weekly progress update.
```
Provide Update
1. Progress
2. Blockers
3. Availability
4. ETA
```

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

### 5 - GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES update
>on what issue did you give your first weekly update?

- #

[return to section 5](#section-5)

⇧ Table of Contents

6 - SUBMITTING YOUR FIRST PULL REQUEST

[ ] Read sections 3.1.a - 3.1.c in 3.1 How to make a pull request to learn more about how to make a pull request (PR) for the issue that you are working on and how to make changes to your PR if changes are requested by the reviewer
Confirm you understand the following:
- [ ] Please work on only one issue at a time and wait until your pull request is merged before picking up another issue.
- [ ] Please keep an eye on your PR, if someone leaves you a comment asking for a change, please respond in a timely way.

[ ] Once your pull request has been accepted, post the following message in a comment below on this issue and then answer it.

### 6 - PULL REQUESTS update
>What is the number of your first merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 6](#section-6)

⇧ Table of Contents

7 - ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES

[ ] Read the Start Here - Developers in Figma
[ ] Go familiarize yourself with the Hack for LA Design System page in Figma (where you can see components and their SCSS classes)

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

### 7 - ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES update
>How many hours did it take you to finish this step?

A:
>Do you have any questions about what you read?
   - [ ] yes, I had questions, and I left comments in the appropriate issues [WE NEED TO UPDATE THOSE TWO RESOURCES TO HAVE LINKS TO ISSUES WHERE PEOPLE CAN PUT QUESTIONS AND MOVE THE ISSUES TO THE QUESTIONS/REVIEW COLUMN]
   - [ ] no, I did not have any questions

[return to section 7](#section-7)

⇧ Table of Contents

8 - MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)

Do another good first issue (two per person total). We have you do another simple issue because this we want you to
- see the difference once you have successful setup your dev environment
- see how each PR gets easier to do with repetition
- make sure you know how to branch properly (most problems show up in the second commit)
[ ] Take the first issue from this prefiltered view of the project board (status: prioritized backlog, good first issues = dev: GFI)
[ ] Submit your PR

Once your pull request has been accepted

[ ] Update your Ongoing Skills List to check off "GitHub branching" & "Pull Requests"

[ ] post the following message in a comment below on this issue and then answer it.

### 8 - MOVE ON TO 2ND GOOD FIRST ISSUE update
>What is the number of your 2nd merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 8](#section-8)

⇧ Table of Contents

9 - GOOD FIRST ISSUE (GFI) PULL REQUEST REVIEWS

Now that you have two merged good first issue PRs, you are eligible to review good first issue PRs, Review Required from other people who are following in the same journey path as you.

See How to review Pull Requests guide will teach you how to review pull requests.

Please review 5 good first issue PRs. Each PR requires at least two reviews, so by reviewing 5 good first issue PRs you are repaying the effort that others did for you (provided 4 reviews for your 2 good first issues) plus 1 extra review to help us all make up the deficit for people who submit a PR but don't get this far.

[ ] reviewed 1st good first issue pr
[ ] reviewed 2nd good first issue pr
[ ] reviewed 3rd good first issue pr
[ ] reviewed 4th good first issue pr

[ ] reviewed 5th good first issue pr

[ ] After each good first issue PR that your review, please paste the following text in a comment below

### 9 - PULL REQUEST REVIEWS - GFI - Update
I have reviewed a `good first issue` PR #
>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

     >if yes, describe what you learned:

    A: 

[return to section 9](#section-9)

[ ] Once all 5 good first PRs have been merged, check of the box for "good first issue" under "Reviewed other people's Pull Requests" on the Ongoing Skills List

[ ] If there are no good first issue PRs to review right now, paste this comment instead and check back later. You can also go onto section 10.

### 9 - PULL REQUEST REVIEWS - GFI - Update
There are currently no `good first issue` PRs to review, but ill check back later.

[return to section 9](#section-9)

⇧ Table of Contents

10 - UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECK

Congrats on making it this far. Issues get more complicated from here, either they include more changes, or have several files to change or you have to research something that we are unsure how to do, or there is complicated logic that needs writing or rewriting. Each issue size that you take on will guide you to a more complicated level in sequence, and you can see from the labels and overviews what they are about.

Its important that you try to work on issues that fill in gaps in your knowledge (see the self tests for a reminder about what to look for).

INTAKE Self Test
ONGOING Skills List

So keep going, the fun stuff is about to start.

Having said that, we are also going to have you take on some issue making (surprise! There is no issue making fairy, only volunteers like you that created issues for the people that come after them). Pay attention to how the issues you have already worked on are constructed and how they change as they go up the ladder. That way when we start you on the issue making portion of the team work, you will know what you are shooting for when its your time to make issues.

Also, we want you on the Merge team. This will ensure you are a competent developer and an awesome collaborative contributor to any team you join in the future.

[ ] Let us know that you have re-reviewed your issues, have read the above and are continuing on the team

### 10 - UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING update
>Up to now we have just been getting you ready.  Now the fun starts.  Are you continuing?
- [ ] I'm so ready, bring it on (continuing)
- [ ] I am worn out from the setup and the good first issues but still game (continuing)
- [ ] I won't be continuing, (please let us know why and close this issue)

Comments:

[return to section 10](#section-10)

[THIS WHOLE THING COULD BE MOVED TO A WIKI PAGE THAT EXPLAINS THE VALUE TO THEIR CAREER AND HAVE A TLDR HERE]

⇧ Table of Contents

11 - MOVING ON TO A SMALL ISSUE

[ ] Assign yourself a small issue, for the role you have indicated, from this prefiltered view of the project board (status: prioritized backlog, small = dev: small)
[ ] Follow the instructions the bot adds as comments on the issue
[ ] Submit your PR

[ ] Once your pull request has been merged post the following message in a comment below on this issue and then answer it:

### 11 - SMALL update
>What is the number of your small merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
- [ ] no
- [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 11](#section-11)

⇧ Table of Contents

12 - PULL REQUEST REVIEWS - SMALL

Now that you have your small PR merged, you are eligible to review small PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `small PRs. Each PR requires at least two reviews, so by reviewing 3 good first issue PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 small issue PR) plus 1 extra review to help us all make up the deficit for people who submit small PRs and then drop off the team.

[ ] reviewed 1st small pr
[ ] reviewed 2nd small pr

[ ] reviewed 3rd small pr

[ ] When you have reviewed a small PR, please paste the following text in a comment below

### 12 - PULL REQUEST REVIEWS - Small - Update
I have reviewed a `small` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned:

   A: 

[return to section 12](#section-12)

[ ] Once all 3 good first PRs have been merged, check off the box for "small" under "Reviewed other people's Pull Requests" on the Ongoing Skills List

[ ] If there are no small PRs to review right now, paste this comment instead and check back later. You can also go onto section 13.

### 12 - PULL REQUEST REVIEWS - Small - Update
There are currently no `small` PRs to review, but i'll check back later.

[return to section 12](#section-12)

⇧ Table of Contents

13 - GET EXPERIENCE MAKING ISSUES - LEVEL 1 (GFI & Small)

Creating issues from templates will give you experience on how issues

are constructed
are queued up for review
are queued up for approval
are prioritized (milestones)
and appear in the prioritzed backlog

and like the good first and small issues you have already done, they are perscritive enough to do with no prior experience issue making.

[ ] Take the first issue from this prefiltered view of the project board (status: ERs and epics that are ready to be turned into issues, good first & small = IM: 1 + extra filters)
[ ] Assign yourself
[ ] Move the issue to the in progress column
[ ] Follow the instructions in the issue
[ ] create the issue(s) it calls for. These new issues will end up in the new issue approval column with the label ready for merge team

Once the ER or Epic has been accepted by the Merge team and closed and the issue(s) you created have been moved into the prioritized backlog

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

### 13 - GET EXPERIENCE MAKING ISSUES - LEVEL 1 (GFI & Small) update
>Which EPIC or ER did you work on (provide the issue number)

#

>How many hours did it take you to make the issue(s)?

Number of hours: 

>Did you find anything required clarification or anything we could improve about the instructions?

Suggestions for improvement: 

[return to section 13](#section-13)

⇧ Table of Contents

14 - MOVING ON TO A MEDIUM ISSUE

[ ] Take the first issue from this prefiltered view of the project board (status: prioritized backlog, medium issues = dev: medium)
- [ ] If there are no medium size issues in the prioritized backlog column, skip the rest of this section and go to Section 14.1
- [ ] If there is medium size issue in the prioritized backlog column
  - [ ] Assign yourself a medium for the role you have indicated (front/backend or both)
  - [ ] Follow the instructions the bot adds as comments on the issue
  - [ ] Submit your PR
  - [ ] Once your pull request has been merged, post the following message in a comment below on this issue and then answer it
```
### 14 - MEDIUM update
>What is the number of your medium merged pull request?
- #
>Did you receive any reviews that required you to change anything on your PR? 
 - [ ] no
 - [ ] yes (if yes, describe what you learned)

Comments: 

[return to section 14](#section-14)
```

⇧ Table of Contents

14.1 MAKE A MEDIUM ISSUE FROM AN ER OR EPIC

Only work on this section if you needed a medium issue and one is not available from the prioritized backlog

[ ] add the label needs issue: medium to this issue, so that we can notify you when new medium size issues are released

[ ] add the following comment to this issue

There are no medium issues right now.  Please let me know if one becomes available.

[return to section 14](#section-14.1)

[ ] Take the first issue from this prefiltered view of the project board (status: ERs and epics that are ready to be turned into issues, medium = IM: Level 1 + Complexity: Medium
- If you find any results in the column
  - [ ] assign yourself to the first issue in that column
  - [ ] move the ER or EPIC to the in progress column
  - [ ] create the issue(s) it calls for. These new issues will end up in the new issue approval column with the label ready for merge team
  - [ ] once you have made the issues and added the labels, move the issue making ER or Epic issue into the questions column
  - [ ] add a comment, letting the merge team know that you have made the issues (include a link to each of the new issues)
  - [ ] add the label ready for merge team
  - [ ] there will likely be some back and forth with the merge team, until your issue(s)s are approved and a ready for prioritization label is added. When the new issue(s) are approved, the issue making issue will be closed and you are welcome to move onto the next checkbox
[ ] Check this prefiltered view of the project board (status: prioritized backlog, medium issues = dev: medium
- If there still is no medium issue to work in the in progress column.
  - [ ] Leave the following message as a comment one of the Medium issues you just created and when the issue is prioritized we will assign the issue to you if there are no other medium issues you have picked up.
```
- I created this issue, so I could have a medium issue to work on.  Please assign to me once approved.  My Skills Issue is #
```
    - once you get assigned,
      - [ ] hide the comment below that says "There are no medium issues right now. Please let me know if one becomes available."
      - [ ] remove from this issue, the label needs issue: medium
      - [ ] circle back to Section 14 and check off the first 4 boxes, and continue from there.

⇧ Table of Contents

15 - PULL REQUEST REVIEWS - Medium

Now that you have your medium PR merged, you are eligible to review medium PRs, Review Required from other people who are following in the same journey path as you.

Please review 3 `medium PRs. Each PR requires at least two reviews, so by reviewing 3 medium PRs you are repaying the effort that others did for you (provided 2 reviews for your 1 medium issue PR) plus 1 extra review to help us all make up the deficit for people who submit medium PRs and then drop off the team.

[ ] reviewed 1st medium pr
[ ] reviewed 2nd medium pr

[ ] reviewed 3rd medium pr

[ ] When you have reviewed a medium PR, please paste the following text in a comment below

### 15 - PULL REQUEST REVIEWS - Medium - Update
I have reviewed a `medium` PR #

>Did you catch anything?

 - [ ] yes
 - [ ] no
>If you did't catch anything, did anyone else who reviewed it after you, catch anything?

 - [ ] no
 - [ ] yes

   >if yes, describe what you learned:

   A:

[return to section 15](#section-15)

[ ] If there are no medium PRs to review right now, paste this comment instead and check back later. You can also go onto section 16.

### 15 - PULL REQUEST REVIEWS - Medium - Update
There are currently no `medium` PRs to review, but i'll check back later.

[return to section 15](#section-15)

⇧ Table of Contents

16 - ISSUE MAKING - LEVEL 2, GFI

[ ] Take the first issue from this prefiltered view of the project board (status: ERs and epics that are ready to be turned into issues, good first issue = IM: Level 2 + good first issue
- If you find any results in the make issues column
  - [ ] assign yourself to the first issue in that column
  - [ ] move the ER or EPIC to the in progress column
  - [ ] create the issue(s) it calls for. These new issues will end up in the new issue approval column with the label ready for merge team
  - [ ] once you have made the issues and added the labels, move the issue making ER or Epic issue into the questions column
  - [ ] add a comment, letting the merge team know that you have made the issues (include a link to each of the new issues)
  - [ ] add the label ready for merge team
  - [ ] there might be some back and forth with the merge team, until your issues are ready to be prioritized. When it is, the issue making issue will be closed and you are welcome to move onto the next checkbox

⇧ Table of Contents

17 - MERGE TEAM SKILLS REVIEW

We want everyone who joins this team to get onto the merge team so that you can get experience running meetings and office hours, mentoring, creating sufficent workflow for the team, escalations, and ultimately being responsible for final approval and merging of pull requests made by team members on lower sections. At this point we will check to see if you are ready to join the merge team, or what your next steps are to get you closer to ready.

[ ] When you get to this point, please paste the following message into a comment below

I  have finished sections 1-16 and am ready to have my activity reviewed by the merge team

      [return to section 17](#section-17)

[ ] Copy the link your comment into the #hfla-site Slack channel

⇧ Table of Contents

FAQ section

Are there exceptions to which size issues I work on?

Medium (~~you can work on one medium issue, but only one at a time~~one per person, with some exceptions, see below)
Large (you can work on more than one large issue, but only one at a time)
The reasons for this progression are: - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues. - We are trying to teach you the team methodology through the issues themselves. - It ensures you understand what we expect and the quality of contributions.
- You can work on back-to-back small issues if it meets the following criteria:
  - You are learning something new and need to work on an issue of a lesser complexity
  - Since we have a limited number of these, you must get approval from lead or pm
- You can work on a second medium issue if it meets the following criteria:
  - You are learning something new and need to work on an issue of a lesser complexity
  - Since we have a limited number of these, you must get approval from lead or pm

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

First, you should post the question or blocker as a comment on your assigned issue, so it can be easily referred to in the next bullet points.
Then, add the label "Status: Help Wanted" so other developers can see it and potentially help answer your question. In addition, you will still need to post a Slack message or bring it up in meeting so we know you need help; see below for how to do that.
Also, you can post your question on the hfla-site Slack channel and link the issue you're working on, so other developers can see and respond.
Lastly, you can add the issue to the ~~"Development team meeting discussion items"~~ "Questions/In Review" column of the Project Board so that it can be addressed in the next development meeting. Please bring it during the meeting that you need help.

If you need to take some time off from the team

Copy and customize this response, and leave it in a comment on this issue I need to take some time off from the team. I believe I will be back on [Replace with DATE YOU WILL BE BACK] - If you have put work in, please make sure its well documented. - Add the label away on hold - Move this issue to the questions column - if you are assigned to an issue, if you have not yet made any progress on the issue, please unassign.

⇧ Table of Contents

Resources/Instructions

Contributing.md - Hack for LA
GitHub Project Board - Hack for LA
Figma - Hack for LA
Google Drive - Hack for LA website team
Agenda / Notes - Dev Team Tuesday meeting
Agenda / Notes - All Team meeting
How to review Pull Requests
To find contact information for the merge team members and technical leads, please take a look at our Meet the Team wiki page

⇧ Table of Contents

Skills List - INTAKE

Skills List, self test on Intake, fill out when you join the team, don't update

Front End

[ ] Setting up your local environment from a contributing file
[ ] GitHub branching
[ ] Pull Requests

Back End

[ ] API requests
[ ] Cron Job Scripting
[ ] CRUD operations

All Developers

[ ] Reviewed other people's Pull Requests
[ ] Resolved Merge Conflicts
[ ] Written documentation for other Developers (Architecture, etc.)
[ ] Mentored other developers

Return to section 1 section 10

Skills List - ONGOING

Skills List, update as you do work on this team

Front End

[ ] Setting up your local environment from a contributing file (section 3)
[ ] GitHub branching (done in section 8)
[ ] Pull Requests (section 8)

Back End

[ ] API requests
Cron Job Scripting
- [ ] edit GitHub Action
- [ ] write GitHub Action
[ ] CRUD operations

All Developers

Reviewed other people's Pull Requests
- [ ] good first issue (section 9)
- [ ] smal (section 12)
- [ ] medium
- [ ] large
- [ ] x-large
[ ] Resolved Merge Conflicts
[ ] Written documentation for other Developers (Architecture, etc.)
[ ] Mentored other developers

⇧ Table of Contents

Aug 06 '24 00:08 ExperimentsInHonesty

website website copied to clipboard

Update Pre-work checklist template

Prerequisite

Overview

Action Items

Resources

Prerequisite

Overview

Special Notes

Action Items

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

Resources/Instructions

Prerequisite

Overview

Special Notes

Action Items

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

Resources/Instructions

Prerequisite

Overview

Special Notes

Action Items

1.0 JOINING THE WEBSITE TEAM.

2.0 TEAM MEETINGS

3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP

4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE

5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENTT ISSUES

6.0 PULL REQUESTS

7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES

8.0 MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)

9.0 UUNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIOIRTIZED BACKLOG AND ON ISSUE MAKING AND TEMPER CHECK

10.0 SMALL

11.0 Medium

12.0 LARGE

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

Resources/Instructions

Solution

Prerequisite

Overview

Special Notes

Action Items

1.0 JOINING THE WEBSITE TEAM.

2.0 TEAM MEETINGS

3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP

4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE

5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES

6.0 PULL REQUEST SUBMISSION

7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES

8.0 MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)

9.0 PULL REQUEST REVIEWS - GFI

10.0 UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECK

11.0 SMALL

12.0 PULL REQUEST REVIEWS - Small

13.0 [INSERT INSTRUCTIONS FOR LEVEL 1 ISSUES MAKING (good first, and small)]

14.0 Medium

15.0 PULL REQUEST REVIEWS - Medium

16.0

17.0 LARGE

18.0 PULL REQUEST REVIEWS - Large

19.0

FAQ section

Are there exceptions to which size issues I work on?

What should I do if I have a question about an issue I'm working on, and I haven't gotten a response yet?

Resources/Instructions

Prerequisite

Overview

Special Notes

Action Items

1.0 JOINING THE WEBSITE TEAM.

2.0 TEAM MEETINGS

3.0 GETTING YOUR DEVELOPMENT ENVIRONMENT SETUP

4.0 FINDING AN ASSIGNING YOUR FIRST GITHUB ISSUE

5.0 GIVING WEEKLY UPDATES ON YOUR DEVELOPMENT ISSUES

6.0 PULL REQUEST SUBMISSION

7.0 ADVANCED READING TO READY YOU FOR LARGER MORE COMPLEX ISSUES

8.0 MOVE ON TO 2ND GOOD FIRST ISSUE (AKA, IT GETS EASIER AND DID YOU BRANCH CORRECTLY?)

9.0 PULL REQUEST REVIEWS - GFI

10.0 UNDERSTAND HOW TO PROGRESS THROUGH ISSUES IN THE PRIORITIZED BACKLOG AND ON ISSUE MAKING AND TEMPERATURE CHECK

11.0 SMALL

12.0 PULL REQUEST REVIEWS - Small

website
website copied to clipboard