Roll Out plan: Make issues required to change all the places that Good Second Issues appears with Good First Issue

[ExperimentsInHonesty]

Dependency

• Find all the places that the "good second issue" labels is used #4423

Issues Created

• Find all the places that the "good second issue" labels is used #4423
• Creating issues to remove all "good second issue" references in CONTRIBUTING.md #4506
• Creating issues to remove all "good second issue" references in Wiki #4508
• replace mention of "good second issue" in prework issue template - dev #5476
• replace mention of "good second issue" in prework issue template - design #5477
• Remove references to "good second issue" labels in the Onboarding infos/links column #4509
• Create a card to explain the changes with removal of the "good second issue" labels #4510
• Remove card explaining the changes with removal of the "good second issue" labels #5587
• Create yml data file for former-sponsors-partners #6199
• Move Code for America svg to new folder assets/images/former-sponsors-partners #6242

Overview

We need to create a plan and issues for changing from good second issue label to good first issue label, so that it all gets rolled out at once

Action Items

• Change all the closed issues and PRs to use the good first issue label instead of the Complexity: Good second issue
• Define and write all the issues required for this roll out plan (all the issues will get dependencies defined below)
  • Finding all the locations Find all the places that the "good second issue" labels is used #4423
  • Updating the code (includes contributing file, so this might require multiple issues) Creating issues to remove all "good second issue" references in CONTRIBUTING.md #4506
  • Updating the wiki with new information (this might make require several issues) Creating issues to remove all "good second issue" references in Wiki #4508
  • replace mention of "good second issue" in prework issue template - dev #5476
  • replace mention of "good second issue" in prework issue template - design #5477
  • Updating the Project Board, Onboarding infos/links column (there could be two tasks here, once to add a card that explains the change and changing the card(s)
    • Remove references to "good second issue" labels in the Onboarding infos/links column #4509
    • Create a card to explain the changes with removal of the "good second issue" labels #4510
  • Updating open PRs text if they need it (if after reviewing the PRs found in 4423 and none need updates to any text inside them, this checkbox can get checked and strike though)
  • Making the label change on issues Replace all "good second issue" labels with "good first issue" label on open PRs and Issues #4431 and adding a note to any issue that has an assignee. No open PRs or Issues with good second issue so 4431 was closed.
  • Making the label change on PRs (open and closed) and adding a note to all the open PRs
• Decide in which order the issues get done, or hold a PR party on a Thursday night to do all the issues at once with the team members.
  • Update all the closed Issues and PRs again to use the good first issue label instead of the Complexity: Good second issue
  • If the issues are going to get done in a certain order (not a party), then edit each issue's dependency to represent the order.
• Update our Data Scientist that this change has been fully implemented Analysis: Collecting Data on Issue Completion per Prework Author and Creating Looker Dashboards to Uncover Insights #4152 (comment)

Resources/Instructions

Dependency for all the issues

### Dependency
- [ ] #4423
- [ ] #4432 is ready for implementation

Message that should go on PR issue. See issue 4423 for example

Hi, we are about to change the label on your PR `Complexity: Good second issue` to `good first issue` to relect the update to our issue ladder of all members will work on two good first issues instead of the dev team making seperate issues for first and second (even though they were essentially the same).  

You might be asking youself, why do you need to do two good first issues, instead of just one?!.  The first two issues is where we catch if anyone has problems with branching appropriately on our project.  So we intentionly make them very very small and perscriptive so that we can focus on making sure you have the branching down before we move you on to the bigger issues that get less and less perscriptive as you go up the ladder.

When you sucessfully finish with this issue/PR, you can go on to a Small issue just as you would have before.

• HfLA Site Audit: Good Second Issue Label

[ExperimentsInHonesty]

@jdingeman Please review this and its related issues and see if these are all the steps required for the roll out plan. Or is there something I have forgotten about.

• I revised the issue formerly know as Replace all "good second issue" labels with "good first issue" label to Replace all "good second issue" labels with "good first issue" label on open PRs and Issues #4431 and lowered is scope
• I moved the scope I took out to Replace all "good second issue" labels with "good first issue" label on open PRs and Issues #4431
• I created this issue to serve as an epic so that you or someone else on the dev lead team can make the rest of the issues.

[jdingeman]

Hi @ExperimentsInHonesty, this looks good and is very thorough. The timing will be a little funny (of course, it's never straightforward lol), but I think #4423 will technically need to happen first before the other issues actually start getting created.

I don't think the order matters so much except that #4423 happens first, but I think it'll get too messy with an issue writing party because of how different the issues might be and it may just be easier to write them up all at once when the places are all found.

[jdingeman]

• Honestly, thinking about it now, I don't think it really matters what order they are in. Just as long as we get the answers from Find all the places that the "good second issue" labels is used #4423, I don't think it will cause any kind of catastrophic confusion if they are not done in order.

[HackforLABot]

@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 8, 2024 at 12:05 AM PST.}

[HackforLABot]

@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 15, 2024 at 12:04 AM PST.}