Create a card to explain the changes with removal of the "good second issue" labels

[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

Overview

We need to add a card to the Onboarding infos/links column that explains the changes for removing the Complexity: good second issue label so that developers are aware of the change and don't try to look for good second issues.

Action Items

• Add a new card to the Onboarding infos/links column
  • Populate the card with the following text:

#### [Card] Removal of "Complexity: good second issue" label
Dev leads are no longer creating good second issues. If you are a new dev and need to work on new issues, please pick up two good first issues.

Be sure to only work on one at a time, and wait for your first issue to be merged before picking up a second one. 

• When you have created the new card, notify Merge Team to review 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
• HfLA site Project Board

[ExperimentsInHonesty]

@roslynwythe I just want to confirm before I prioritize this, that there is an issue to remove it, once the roll out plan is done.

[roslynwythe]

• @ExperimentsInHonesty Here is the issue to remove the card: Remove card explaining the changes with removal of the "good second issue" labels #5587

[github-actions]

Hi @segbuniwe, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[segbuniwe]

Availability: I will be busy this weekend, but I will have about 6 hours during the week.
ETA: EOD Wednesday 10/25

[segbuniwe]

@JessicaLucindaCheng
Hi Jessica, for this issue a merge team member needs to review and close it. I have made the card needed for the onboarding section.

[JessicaLucindaCheng]

@segbuniwe Hi 😄. I'm not a current member of the Merge Team. I suggest the following to reach out to the Merge Team:

• @hackforla/website-merge in a new comment in this issue, and
• post a Slack message in the #hfla-site channel with a link to this issue.

In addition, move your issue into the Questions / In Review column and add a ready for dev lead label.

[segbuniwe]

@hackforla/website-merge team
Hi Merge Team, for this issue a merge team member needs to review and close it. I have made the card needed for the onboarding section.

[LRenDO]

Hi @segbuniwe! Great work! Thanks for working on this issue! I see that the card has been added in the appropriate column with the correct text.

For the future, when there is an issue like this one that doesn't result in a pull request, a review can be requested by moving it to the Questions / In Review column of the project board and add the ready for dev lead label. We regularly check that column and review those issues.

Thanks again for contributing!