Cleanup Project Board: Pre-work
- Dominant language
- JavaScript
- Stars
- 363
- Forks
- 872
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 18
Description
### 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](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22complexity%3A+prework%22)
#### 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).
```
Contributor guide
Assessment
This issue has not been assessed yet.