Creating issues to remove all "good second issue" references in CONTRIBUTING.md

[jdingeman]

Dependency

• Find all the places that the "good second issue" labels is used #4423
• Roll Out plan: Make issues required to change all the places that Good Second Issues appears with Good First Issue #4432 is ready for implementation
• Update pr instructions GHA with URL for reviewing changes to CONTRIBUTING.md #5165 or Create Issue Template for Updates to CONTRIBUTING.md #5547

Issues

• Remove "good second issue" from CONTRIBUTING.md Section 2.2 #5590
• Remove "good second issue" from CONTRIBUTING.md Section 2.1 #5588
• Remove "good second issue" from CONTRIBUTING.md Section 2.3.b #5591
• Remove "good second issue" from CONTRIBUTING.md Section 2.3.c #5617

Overview

Since we are deprecating the "good second issue" label we need to to edit the CONTRIBUTING.md guide so that we no longer have references to "good second issue".

Action Items

• This issue should only be assigned to a lead
• Develop a template
• Find all references to good second issue in CONTRIBUTING.md
  • For each reference, create a new issue to replace/remove them from CONTRIBUTING.md as appropriate
  • Add the labels Complexity: Small, size 0.5pt, role: front end, role: back end/devOps, Feature: Onboarding/Contributing.md, ready for dev lead
• Add the new issues to the Issues section above
• Once all necessary issues have been created
  • Add a dependency label
  • Move this issue to the Ice Box column
• If all the dependency issues are closed, remove the dependency label, move this issue from the Ice Box to the In Progress column, and close this issue

For Merge Team/Tech Lead/PM

• When this issue is closed, release the dependency for this issue on Roll Out plan: Make issues required to change all the places that Good Second Issues appears with Good First Issue #4432

Resources/Instructions

• This is part of epic Roll Out plan: Make issues required to change all the places that Good Second Issues appears with Good First Issue #4432
• CONTRIBUTING.md

[roslynwythe]

Template for "Removing good second issue from CONTRIBUTING.md":

• also see sample issue: Remove "good second issue" from CONTRIBUTING.md Section 2.2 #5590

start with the GitHub template Update CONTRIBUTING, then make the following additions:

• specify the section to modify in the issue title
• specify the "before" and "after" text
• add a note to reviewers:

### For Merge Team
- [ ] Resolve the dependency on this issue in #4506.  If all dependencies have been resolved, close that issue.  

• add to Resources section:

- This issue is part of #4506

[github-actions]

@roslynwythe

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 3, 2023 at 12:06 AM PST.}

[github-actions]

@roslynwythe

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 10, 2023 at 12:06 AM PST.}

[t-will-gillis]

All associated issues are merged, closing this issue to release dependency on #4432