Cleanup Project Board: Pre-work

[bishrfaisal]

Overview

We need to review, message, prioritize, and move on the board all pre-work issues so that we can improve retention and reduce unnecessary work.

Action Items

• Create a comment for the person whose pre-work you are going to check
• paste template into comment
• check all the items
• write draft message (don't add their GitHub handle to it yet)

Resources/Instructions

• Project board filtered by pre-work

Template

### Name of person
- Date they opened prework issue: 
- Role:
  - [ ] Front End
  - [ ] Back End
- [ ] Review issue
   - [ ] Self Assign
   - [ ] Add role label
   - [ ] Mark check boxes
- [ ] Lookup Github handle on the issue tab
   - [ ] How many issues total
   - [ ] Any issues other than pre-work
   - [ ] Any open issues
   - [ ] Closed Issues
      - [ ] PR and was it successfully closed

#### Draft Message
- [ ] `They never picked up any issues.`
- [ ] `Everythings fine, they just haven't been assigned anything long enough to have done an in progress update`
- [ ] `no small issue assigned after 2 good first issues`
- [ ] `prework successfully completed`
- [ ] `They have not picked up a second good first issue`
### Resources
- [URL for Issue tab with Assignee](https://github.com/hackforla/website/issues/assigned/)

---

Possible Draft Messages

• They never picked up any issues.

Hi.  I see that you didn't pick up any issues after joining the Hack for LA website team.  We are going to go ahead and close this issue. 

If you want to return, you can reopen this issue or write to us in the #hfla-site Slack channel

• Everythings fine, they just haven't been assigned anything long enough to have done an in progress update

I am reopening this issue until you have been assigned to a development issue long enough to make an in progress update.  It can will stay open until you get an issue that takes longer than a week to complete (likely a medium or large size issue).  That way, we know you can make detailed progress updates.  In the meantime, if you get reminders to update this issue, just let us know what size and number issue you are assigned to at the time.  That way, we have a record (in one place) of your progress.

• no small issue assigned after 2 good first issues

I see you finished your 2 good first issus but have not yet picked up a small issue.  Here are the issues that are available that match the role labels you choose on your prework
[Front End, Small](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+small%22+label%3A%22role%3A+front+end%22#column-7198257) | [Back End, Small](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+small%22+label%3A%22role%3A+back+end%2Fdevops%22#column-7198257)

• prework successfully completed

- Has provided two progress updates in this issue [ADD ISSUE LINK]

This prework has been successfully completed!

• They have not picked up a second good first issue

I noticed that you have not picked up a second `good first issue`.  Use this link to find one:

(https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22good+first+issue%22+label%3A%22role%3A+front+end%22+label%3A%22role%3A+back+end%2Fdevops%22#column-7198257).  

[bishrfaisal]

Vanessa Murray

• Date they opened prework issue: 2022-07-20

• Role: User Research

• Review issue

  • Self Assign
  • Add role label
  • Mark check boxes

• Lookup Github handle on the issue tab

  • How many issues total: 2
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

• NOTE: Currently working on issue Quiz for New Volunteers to Help w/ Team Selection #3005

• I suggest asking for an update on the comments of issue Quiz for New Volunteers to Help w/ Team Selection #3005 since ETA of completion was 9/18.

Resources

• URL for Issue tab with Assignee

[bishrfaisal]

Shima Houshyar

• Date they opened prework issue: 2022-07-20
• Role: User Research
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 1
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Message: Hi Shima 😃! I noticed that you joined the Hack for LA website team on July 20th but have not finished the Pre-work process or closed any issues. Will you be coming back? Do you have feedback for us?

Resources

• URL for Issue tab with Assignee

[bishrfaisal]

Matthew Toledo

• Date they opened prework issue: 2022-08-09
• Role: Front-end
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 1
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Message: Hi Matthew 😃! I noticed that you completed an issue in August but have not worked on an issue since then. Will you be coming back? Do you have feedback for us?

NOTE: Matthew attended our PM/Dev meeting on 9/11 so he is active, however he has not been assigned an issue since mid August. - added a note to 2022-09-19 agenda

Resources

• URL for Issue tab with Assignee

[bishrfaisal]

Abraham Diaz

• Date they opened prework issue: 11 days ago
• Role: Front-end
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 1
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

NOTE: Abraham has 2 closed issues that he completed recently. Seems like he has completed pre-work but did not check all the boxes.

Resources

• URL for Issue tab with Assignee

[7kram]

Rachel S

• Date they opened prework issue: 2022-06-15
• Role: User Research
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 1
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Draft Message

Hey Rachel, hope you're doing well! I saw that you joined the hackforla website team and completed most of the onboarding 🙌 ! Do you plan on coming back? Please give us feedback!

Resources

• [URL for Issue tab with Assignee]

[7kram]

Emily Tat

• Date they opened prework issue: 2022-07-20
• Role: User Research & Designer (separate pre-work issues)
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 3
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Draft Message

Hi Emily, I saw that you joined the hackforla website team as a user researcher/ designer 🙌. Do you plan on coming back? Please let us know and give us feedback!

NOTE: She has closed her designer pre-work but still working on her researcher pre-work.

Resources

• [URL for Issue tab with Assignee]

[7kram]

Karen Munnelly

• Date they opened prework issue: 2022-07-20
• Role: User Research
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 2
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Draft Message

Hey Karen! Hope your doing well. I saw that you joined the hackforla website team as a user researcher and started working on an issue 🙌. Were you able to make some more progress on it and do you plan on continuing with us? Please give us any feedback!

Note:

• Unassigned Karen from issue Images of zooms for homepage #2763 due to inactivity. Moved issue to prioritized backlog.

Resources

• [URL for Issue tab with Assignee]

[7kram]

David Attali

• Date they opened prework issue: 2022-08-30
• Role: Back end/Front end
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 10
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Draft Message

• Hey David, hope you're doing well. I saw that you closed/PR merged 3 issues 🙌 Thanks for your help! I also noticed you completed most of the onboarding process. Can you finish checking off the action items on Pre-work Checklist: Developer: David Attali #3509 so that we can close your pre-work checklist. Thanks 😃

Note

David has closed/PR merged 3 issues. Last issue was opened 3 days ago.

Resources

• [URL for Issue tab with Assignee]

[ExperimentsInHonesty]

Name of person Yuri Kim

• Date they opened prework issue: 2023-05-10
• Role:
  • Front End
  • Back End
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 1
  • Any issues other than pre-work: no
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Draft Message

• They never picked up any issues.
• Everythings fine, they just haven't been assigned anything long enough to have done an in progress update
• no issue assigned after second issue
• prework successfully completed
• They have not picked up a second good first issue

Resources

• URL for Issue tab with Assignee

[Josiah-O]

Name of Person: Troy Freed

• Date they opened prework issue: 2023-05-24
• Role:
  • Front End
  • Back End
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total: 1
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Draft Message

• They never picked up any issues.
• Everythings fine, they just haven't been assigned anything long enough to have done an in progress update
• no issue assigned after second issue
• prework successfully completed
• They have not picked up a second good first issue

Resources

• URL for Issue tab with Assignee

[anjolaaoluwa]

Name of person:Siddhanth Iyer

• Date they opened prework issue: 2023-18-07
• Role:
  • Front End
  • Back End
• Review issue
  • Self Assign
  • Add role label
  • Mark check boxes
• Lookup Github handle on the issue tab
  • How many issues total:1
  • Any issues other than pre-work
  • Any open issues
  • Closed Issues
    • PR and was it successfully closed

Draft Message

• They never picked up any issues.
• Everythings fine, they just haven't been assigned anything long enough to have done an in progress update
• no issue assigned after second issue
• prework successfully completed
• They have not picked up a second good first issue

Resources

• URL for Issue tab with Assignee

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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, October 17, 2023 at 12:06 AM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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, October 24, 2023 at 12:05 AM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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, October 31, 2023 at 12:06 AM PST.}

[Josiah-O]

Progress: Ongoing, 2 issues completed.
Blockers: N/A
Availability: 3 hours this week.
ETA: I am actively working on this issue but do not have a definitive ETA at this moment.
Pictures (optional): N/A

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, November 13, 2023 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, November 20, 2023 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, November 27, 2023 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, December 4, 2023 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, December 11, 2023 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, December 18, 2023 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, December 25, 2023 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, January 1, 2024 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, January 8, 2024 at 11:05 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, January 15, 2024 at 11:06 PM PST.}

[github-actions]

@Josiah-O

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (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 Monday, January 22, 2024 at 11:05 PM PST.}