Cleanup Project Board: Pre-work

[bishrfaisal]

trafficstars

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:
- [ ] 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
      
### Resources
- [[URL for Issue tab with Assignee](url)]

[ExperimentsInHonesty]

Calvin Tan

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

Resources

• URL for Issue tab with Assignee

[ExperimentsInHonesty]

Sandharsh

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

sent 2022-09-19 Message: Hi Sandharsh 😃! I noticed that you joined the Hack for LA website team on June 15th 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]

Anna Kirstine Schirrer

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

• Role: User Research

• [x] Review issue

  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes

• [x] Lookup Github handle on the issue tab

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

• Message: Hi Anna 😃! I noticed that you joined the Hack for LA website team on July 17th but have not closed any issues including #2706, which you were working on. Will you be coming back? Do you have feedback for us?

• wrote to her on 2022-09-19 and unassinged her from her issue

Resources

• URL for Issue tab with Assignee

[bishrfaisal]

Vanessa Murray

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

• Role: User Research

• [x] Review issue

  • [x] Self Assign
  • [x] Add role label
  • [ ] Mark check boxes

• [x] Lookup Github handle on the issue tab

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

• NOTE: Currently working on issue #3005

• I suggest asking for an update on the comments of issue #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
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [ ] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 1
  • [ ] Any issues other than pre-work
  • [x] 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
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [ ] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 1
  • [ ] Any issues other than pre-work
  • [x] 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]

Maria Reeves

• Date they opened prework issue: 11 Days ago

• Role: Front-end and devOps

• [x] Review issue

  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes

• [x] Lookup Github handle on the issue tab

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

• NOTE: New joiner and currently working on issue #2824, I suggest asking for an update on the comments of that issue since ETA of completion was 9/10.

She finished her second issue and has completed onboarding. We closed the issue

Resources

• URL for Issue tab with Assignee

[bishrfaisal]

Abraham Diaz

• Date they opened prework issue: 11 days ago
• Role: Front-end
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 1
  • [ ] Any issues other than pre-work
  • [x] 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
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 1
  • [ ] Any issues other than pre-work
  • [x] 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)
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 3
  • [x] Any issues other than pre-work
  • [x] 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
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 2
  • [x] Any issues other than pre-work
  • [x] 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 #2763 due to inactivity. Moved issue to prioritized backlog.

Resources

• [URL for Issue tab with Assignee]

[7kram]

Calvin Tan

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

Draft Message

Hey Calvin, Hope you're doing well! I saw that you closed and did a PR merge for over 5 issues 🙌. Thanks for your help! I haven't seen anything from you since August. Do you plan on continuing with us? Please give us any feedback!

Resources

• [URL for Issue tab with Assignee]

[7kram]

David Attali

• Date they opened prework issue: 2022-08-30
• Role: Back end/Front end
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 10
  • [x] Any issues other than pre-work
  • [x] Any open issues
  • [x] Closed Issues
    • [x] 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 #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]

[7kram]

Phillip Sanchez

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

Note

Philip pretty much completed the onboarding process and closed/PR merged 3 issues.

Resources

• [URL for Issue tab with Assignee]

[github-actions[bot]]

@7kram, @bishrfaisal

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, September 20, 2022 at 12:39 AM PST.}

[github-actions[bot]]

@7kram, @bishrfaisal

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, September 27, 2022 at 12:45 AM PST.}

[github-actions[bot]]

@7kram, @bishrfaisal

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, October 4, 2022 at 12:32 AM PST.}

[github-actions[bot]]

@7kram, @bishrfaisal

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, October 11, 2022 at 12:39 AM PST.}

[github-actions[bot]]

@7kram, @bishrfaisal

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, October 18, 2022 at 12:33 AM PST.}

[github-actions[bot]]

@7kram, @bishrfaisal

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, October 25, 2022 at 12:20 AM PST.}

[github-actions[bot]]

@7kram, @bishrfaisal

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Thursday, October 27, 2022 at 11:57 AM PST.}

[github-actions[bot]]

@7kram, @bishrfaisal

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 developer meeting discussion column 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.

_{You are receiving this comment because your last comment was before Tuesday, November 1, 2022 at 12:20 AM PST.}

[ExperimentsInHonesty]

Name of person Erin Pattison

• Date they opened prework issue: 2023-02-28
• Role: Front End
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 2
  • [x] Any issues other than pre-work: Yes
  • [x] Any open issues: Yes
  • [x] Closed Issues: Only prework
    • [ ] PR and was it successfully closed

Resources

• URL for Issue tab with Assignee

Action taken

Reopened the issue and messaged them.

Draft Message

@erinpattison 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 ```

[ExperimentsInHonesty]

Name of person Aldrin Tunque

• Date they opened prework issue: 2023-02-28
• Role:
  • [x] Front End
  • [x] Back End
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] 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

Resources

• URL for Issue tab with Assignee

Action taken

• [ ] Reopened the issue and messaged them.

Draft Message

• [ ] 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 

• [ ] I see you finished your good first issue and second issue 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 | Back End, Small

[ExperimentsInHonesty]

Name of person Phuong Vu

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

Draft Message

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

Resources

• URL for Issue tab with Assignee

[ExperimentsInHonesty]

Name of person Steven Tran

• Date they opened prework issue: 2023-01-16
• Role:
  • [x] Front End
  • [x] Back End
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 5
  • [x] Any issues other than pre-work: 4
  • [x] Any open issues: 1
  • [x] Closed Issues: 4 (including prework)
    • [x] PR and was it successfully closed

Draft Message

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

Resources

• URL for Issue tab with Assignee

[ExperimentsInHonesty]

Name of person Aldrin Tunque

• Date they opened prework issue: 2023-02-28
• Role:
  • [x] Front End
  • [x] Back End
• [x] Review issue
  • [x] Self Assign
  • [x] Add role label
  • [x] Mark check boxes
• [x] Lookup Github handle on the issue tab
  • [x] How many issues total: 3
  • [x] Any issues other than pre-work: 2
  • [x] Any open issues: 0
  • [x] Closed Issues: 3 (including prework)
    • [x] PR and was it successfully closed 2

Draft Message

Sent:

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

Resources

• URL for Issue tab with Assignee

[ExperimentsInHonesty]

Name of person: Maria Herzer

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

Draft Message

• [x] Everythings fine, they just haven't been assigned anything long enough to have done an in progress update
• [x] no issue assigned after second issue

Resources

• URL for Issue tab with Assignee

[ExperimentsInHonesty]

Name of person Karen G. Cecena

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

Draft Message

• [x] Everythings fine, they just haven't been assigned anything long enough to have done an in progress update
• [x] no issue assigned after second issue

Resources

• URL for Issue tab with Assignee]### ite/issues/assigned/karengcecena)

[ExperimentsInHonesty]

Name of person Brian Mui

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

Draft Message

This prework has been successfully completed!

Resources

• URL for Issue tab with Assignee

[ExperimentsInHonesty]

Name of person Aine Fitzgerald Coleman

• Date they opened prework issue: 2023-03-26
• Role:
  • [x] Front End
  • [x] Back End
• [x] Review issue
  • [x] Self Assign
  • [x] 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

• [ ] 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
• [x] They have not picked up a good second issue

Resources

• URL for Issue tab with Assignee

[ExperimentsInHonesty]

Name of person Reid Hommedahl

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

Draft Message

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

Resources

• URL for Issue tab with Assignee

I am closing this prework issue since you have done all the steps now. The last step was doing a update on your issue even when you don't have any blockers or questions, and you have done that on this issue https://github.com/hackforla/website/issues/4050ed!

[ExperimentsInHonesty]

Name of person Yuri Kim

• Date they opened prework issue: 2023-05-10
• Role:
  • [x] Front End
  • [x] Back End
• [ ] Review issue
  • [x] Self Assign
  • [x] 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

• [x] 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:
  • [x] Front End
  • [ ] Back End
• [ ] Review issue
  • [x] Self Assign
  • [x] 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

• [x] 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:
  • [x] Front End
  • [ ] Back End
• [ ] Review issue
  • [x] Self Assign
  • [x] 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

• [x] 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[bot]]

@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[bot]]

@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[bot]]

@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.}